Hi, On 10/24/21 12:27 AM, Pierre-Elliott Bécue wrote: [...] > mailman removal is the decision of the mailman maintainer, Thijs, due to > the fact it relies on python2 which got removed from Debian. > > Regarding mailman3, I did the nginx integration, Jonas the Apache2 one, > from upstream recommendations. Looking from the config, I'd try the URL > without the trailing slash: https://myserver/mailman3
Thanks for your reply. Indeed, in the meantime I found the following bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996105 ... and followed their advice to remove that trailing slash from /etc/mailman3/apache2.conf, and that made it work. > > I don't know if the proxy permissions are really required. Without it, I get a permission error (even with slash removed from apache2.conf) > > Apart from that, mailman3 is in Debian since Buster, so more than three > years, and while it indeed carried out its lot of bugs, it's quite > usable. There are indeed still a number of issues present which make integration cumbersome: - obscure "lmtp" interface to submit mails, makes it difficult to have domains that contain both mailing lists and direct mail users. The old way of calling /usr/lib/mailman/mail/mailman to submit was easier to integrate. Why not ship an lmtp client that can be called the same way as the old /usr/lib/mailman/mail/mailman ? - the non-standard uwsgi proxy for the web interface, rather than plain CGI which just works, and is easy to debug. > > Regards, > -- > Pierre-Elliott Bécue > Regards, Alain
