Configure Haraka for Mailman3

[girish]

OK, thanks. I moved this thread to feature requests. It's quite a bit of automation to do.

[avatar1024]

@girish Is this something you have a particular interest in implementing on your end as a way to bring mailing list to Cloudron or will it need a more collaborative effort from the community? I'm asking because we seem to have someone here with good knowledge of Mailman3 right now and so could be a good time to leverage on this. Are some of the things needed for this that can only be done on your end?

[girish]

@avatar1024 I guess we need an initial mailman Cloudron package for a start. https://github.com/maxking/docker-mailman is quite extensive and too complicated to maintain from the looks of it. After that, we have to make the LMTP addon happen on the Cloudron platform side. It's quite a bit of work to make all this happen.

Is there no other way mailman works? Is there an alternative to LMTP?

Also, is sympa a good alternative to this? If it is, what does that need?

[avatar1024]

@girish Humm I see, it really doesn't sound trivial.

I'm afraid it's unclear that things would be any easier with SYMPA as I don't think there is a docker install.

I guess that means proper mailing list is not likely to land on Cloudron any time soon. Shame as for people I work with it is the last missing piece to move everything to Cloudron.

So far I haven't found a way to really replace mailing list for working group communications as it just trikes the right balance of accessibility (everyone has an email address and roughly know how to use emails), almost instant, yet semi-organised communication. Might start a discussion and ask how other people do it for organisations with non techy people.

[chetbaker]

I just want to revive this thread again. I wonder if @adhodgson can provide more insights about how to have a roundabout for not having Mailman available at Cloudron but needing to have mailing lists. I’m on that side.

[jdaviescoates]

@girish said in Configure Haraka for Mailman3:

it seems we need the ability for mailman3 to receive mail via LMTP from Haraka. This is not possible right now since Haraka only delivers internally to dovecot at this point.

But its seems Haraka itself does indeed support LMTP, no? see e.g. https://cloudinfrastructureservices.co.uk/top-20-best-open-source-email-servers-for-windows-linux/

Or perhaps better:
https://haraka.github.io/plugins/queue/lmtp

[girish]

@jdaviescoates we already use the LMTP plugin but it's configured to only deliver incoming mails to dovecot. In the mailmain situation, we have to deliver mails to one (or more) apps. This requires a bit of work to make a mailman like app possible.

[avatar1024]

@girish I wonder if there have been any progress since September that would help with this?

And if not, where should someone with coding skills start looking?

[girish]

@avatar1024 we haven't worked on this. I think the complication here is that we have to extend haraka's LMTP support to forward emails to apps. Currently, it's a bit outside our radar (given other tasks to do).

[avatar1024]

@girish Sure that's completely understandable, thanks for the reply.

Given that neither mailman or SYMPA seems straightforward to implement in Cloudron I might revive this thread to add a basic moderation function to Cloudron mailing list. I believe for security purpose this is the main missing feature and the proposed approached may not be too hard to implement with the current backend(?).

What users still won't get is the ability for members to subscribe and unsubscribe by themselves, but an admin can do that manually so at least it is doable.

Another thing that would be nice is to be able to create a list from a Cloudron Group (i.e. mailing list that contains emails of everyone in a group and that gets updated each time you add or remove a user from a group). I don't know how your database works and how easy that might be to implement. What do you reckon?
(Again this can be done manually so not as important as moderation, but just something that would be nice and possibly doable if the info are easily retrievable from the user database in the backend.)