Package: mailman3-full Version: 3.2.1-1 I installed the package mailman3-full and configured the files in /etc/mailman3 /usr/share/mailman3-web/
Next I created an apache virtual host entry in /etc/apache2/sites-available/ and used the content of /etc/mailman3/apache.conf as a template. I enabled the apache modules proxy and proxy_uwsgi. After restarting the services apache2 and mailman3-web, I accessed the website in a browser via url: https://lists.my-tld/mailman3/ The page showed: *Seite nicht gefunden* Diese Seite ist entweder nicht vorhanden, oder sie wurde an einen anderen Ort verschoben. With DEBUG = True, it shows: *Page not found (404)* *Request Method:* GET *Request URL:* https://lists.my-tld/mailman// Using the URLconf defined in urls, Django tried these URL patterns, in this order: 1. ^$ 2. ^postorius/ 3. ^hyperkitty/ 4. ^user-profile/delete$ [name='mm_user_account_delete'] 5. ^user-profile/$ [name='mm_user_profile'] 6. ^accounts/ 7. ^admin/ The current path, /, didn't match any of these. Note that in the Request URL, the name "mailman3" has been replaced by "mailman", making the URL invalid. This behavior could be reproduced in two separate installations on different machines. As a workaround, I changed this line in the apache vhost config from: ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost to: ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Note the other references to /mailman3 had to stay to access the static css files. This solved the problem for me, but that is not an acceptable behaviour. Also note that the mailing lists had been installed some weeks before and ran fine during that time. Some update in the Debian system caused this fault. I am using Debian GNU/Linux 10.11, kernel 4.19.0-16-amd64 and libc6 2.28-10 Kind Regards Eggert
