Opened 2 years ago

Closed 14 months ago

#21325 closed defect (fixed)

Installing Schleuder

Reported by: hiro Owned by: qbi
Priority: Medium Milestone:
Component: Internal Services/Service - lists Version:
Severity: Normal Keywords:
Cc: dgoulet, weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I have been looking for a solution to have a working test of Schleuder working on our mail server.
As per now there are two possible approaches. None of them is ideal for different reasons.

Approach 1:
Schleuder is a Ruby application. More precisely it is installed as a ruby gem as it is written in Thor (a small framework to write command line interfaces as a gem)

As other gems, Schleuder has a number of dependencies that it needs to run. Namely other gems. Some of these gems are just downloaded, some need to be compiled with native extensions.

These gems are basically written in C and need ruby-dev to be compiled for your system. Pulling ruby-dev pulls a lot of packages. Some of these we wouldn't like to keep on the mail server (e.g. having a compiler).

Note that these gems do not need to be compiled system wide. It would be possible to use either rvm or rbenv to manage ruby versions and bundler to manage gem dependencies. These can all run as user. Still we will need the possibility to compile software on the machine (at least during the deployment phase).

Approach 2:
This involve compiling gems on a different machine and creating deb packages that will install the required dependencies for the Schleuder user.
I have left the required packages on:

/srv/schleuder.torproject.org/home/pkg/

This way you can inspect them and see if you are happy with how and what is going to be installed.
Note that I have compiled this on a test VM that I use locally. There might be arch mismatch with our mail server that I will need to address (this is just a test now).

As I said at the beginning there are various pros and cons for each approach, so before continuing I think it would be beneficial to discuss this here and agree on a possible solution. Maybe there is also a 3rd approach that I haven't fully considered, in this case feel free to propose something and I will investigate it.

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by atagar

Sounds like Schleuder is some alternate for standard email? Never heard of this before but that aside, why wouldn't this be on its own virt?

comment:2 in reply to:  1 Changed 2 years ago by hiro

Replying to atagar:

Sounds like Schleuder is some alternate for standard email? Never heard of this before but that aside, why wouldn't this be on its own virt?

Hi, Schleuder (https://0xacab.org/schleuder/schleuder) is actually a mailing list manager that allows subscribers to communicate encrypted. The idea is that if you have 10 subscribers and you have to send an encrypted email to the list you do not have to encrypt the email with all the 10 keys. You will just use the server key and the server will decrypt and encrypt w/ the subscribers key.

Last edited 2 years ago by hiro (previous) (diff)

comment:3 Changed 2 years ago by hiro

Here is another possibility that dgoulet suggested. We could setup schleuder on a separate machine and deliver email from postfix with https://github.com/ehloonion/onionmx.
On the separate machine we could run schleuder and install normally (as a ruby app with its gems).

I'd be happy to try this out if we are happier with this option.

comment:4 Changed 14 months ago by qbi

As far as I can tell we have several Schleuder instances running. So can this ticket be closed?

comment:5 Changed 14 months ago by dgoulet

Resolution: fixed
Status: newclosed

Ah yes indeed it can. We have several list already using it. Thanks to all who helped here!

Note: See TracTickets for help on using tickets.