October 2021 - Mailman-users - lists.mailman3.org

Trying to get mailman3 in docker working with external Mysql database
by bob B 11 Oct '21

11 Oct '21

Our database group has created the database with (charset=utf8mb4&use_unicode=1) and a user For my docker-compose.yaml I will only have two container sections mailman-core mailman-web which should have these database variables set under each: -DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name] - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase Are these all correct? in looking at documentation should it be: DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name]?charset=utf8mb4&use_unicode=1 Or/and should I also use? DATABASE_URL=mysql+pymysql://.... or DATABASE_URL=mysql://... or DATABASE_URL=pymysql://.... Do I have to install pymysql? or is it installed in the dock images? Do I have to run any other commands on the database first? I assume mailman does everything it needs for the database at first launch?

2 2

Edit archived email? Is it possible?
by Prasanth Nair 08 Oct '21

08 Oct '21

Hello, Does anyone know how to edit an archived email in Mailman3? It is possible in Mailman2 ( https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…). Is there any option similar to this in Mailman3? Kind regards, Prasanth

3 8

Activation of HyperKitty archive on Debian
by Eggert Ehmke 04 Oct '21

04 Oct '21

Is there a straighforward instruction how to make it work on Debian Bullseye? All instructions I find seem to use the git method, and also there are warnings to mix the methods. Installing mailman3 with Debian methods was straightforward, and worked out of the box. Though it purged my mailman2 installation without warning, that was a hard blow. Had to reinstall all my lists in a night session. Also lost the old archives and can't get the new get running.

1 0

Confirmation emails to Users has wrong domain name (example.com!)
by Odhiambo Washington 03 Oct '21

03 Oct '21

1. Confirmation emails to Users has wrong domain name (example.com!) <https://docs.mailman3.org/en/latest/faq.html#id1> <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> This happens when your reverse (SSL) proxy isn’t setting up the correct headers when proxying requests. Fix this by setting the right proxy_set_header directives: # For Nginx. location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_pass http://localhost:8000/; } Appropriate headers for different web servers needs to be set if something other the How is this supposed to be mitigated in Apache when using WSGI? My config: WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman user=mailman group=mailman WSGIPythonHome "/usr/local" WSGIProcessGroup hyperkitty <VirtualHost *:443> ServerName lists.doma.ain ServerAdmin odhiambo(a)gmail.com SSLEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem" SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem" SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem" CustomLog /var/log/mm3-lists-access.log combined ErrorLog /var/log/mm3-lists-error.log LogLevel info Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman/static <Directory "/usr/local/mailman/static"> Order Allow,Deny Require all granted Allow from all </Directory> WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman/"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 11

Broken web interface Ubuntu 20.04
by Simon Brown 01 Oct '21

01 Oct '21

Hello, Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath. Any suggestions as to what might have gone wrong? Simon P.S. Hopefully I've got the right list this time. -- Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

5 6