[Pkg-mailman-hackers] Bug#997060: Bring back mailing list support to Debian

[Pierre-Elliott Bécue]

Hi,

Alain Knaff <alain at knaff.lu> wrote on 23/10/2021 at 14:21:32+0200:

> Package: mailman3-web
> Version: 0+20200530-2
>
> Hi,
>
> After I recently upgraded my server to Debian 11, I was rather appalled
> that mailman was dropped without a clear migration path.
>
> I figured out that this is now replaced by mailman3-full, but apparently
> that package is still pretty much work in progress.
>
> /usr/share/doc/mailman3-web/README.Debian.gz says to run
> dpkg-reconfigure mailman3-web after installing it, and this does indeed
> prompt me to set up a superuser account, and installs its configuration
> in the webserver
>
> However, when navigating to https://myserver/mailman3/ , I encounter
> several issues:
>
> 1. Proxy permissions are not set up.
>
> So I added the following:
>
> <Proxy "uwsgi://localhost/">
>         Require all granted
> </Proxy>
>
>
> 2. After the above, I see a message "Page not found This page either
> doesn't exist, or it moved somewhere else."
>
> Links in the top menu bar are broken, they snip off the last letter of
> "mailman3", so it becomes "mailman". After setting up a ProxyPass for
> the path "mailman" as well, I see that another letter is snipped in the
> top links, so it becomes "mailma", then "mailm", ...
>
> What is going on here?
>
>
> 3. So, I tried clicking on login, and manually added back the missing 3
> to the URL and went to
> https://myserver/mailman3/accounts/login/?next=/mailman3/accounts/login/
>
> => Still the same page with "Page not found. This page either doesn't
> exist, or it moved somewhere else."
>
>
> So, what gives?
>
> I can understand that it takes some time for a full rewrite of a major
> software to become production-ready. However, in that case, please don't
> drop the working previous version (mailman 2.1) until the new one is
> actually usable.

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

I don't know if the proxy permissions are really required.

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.

Regards,
--
Pierre-Elliott Bécue
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 853 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/attachments/20211024/d78f38fd/attachment-0001.sig>