- Mailman-users - lists.mailman3.org

broken route to accounts
by Thomas Krichel March 26, 2026

March 26, 2026

I am using apache to run the web interface, and my Postel port, and I have the proxy routs ProxyPass "/mailman3" "http://127.0.0.1:4386/mailman3" works ProxyPass "/archives" "http://127.0.0.1:4386/archives" works ProxyPass "/accounts" "http://127.0.0.1:4386/accounts" is broken ProxyPass "/admin" "http://127.0.0.1:4386/admin" works ProxyPass "/user-profile" "http://127.0.0.1:4386/user-profile" works What does "is broken" mean here? Well, since I have debug on, GET "http://127.0.0.1:4386/accounts" yields something like (shortened to cut to the salient matter) | <body> | <p> | Using the URLconf defined in <code>mailman_web.urls</code>, | Django tried these URL patterns, in this order: | </p> | <ol> | <li>postorius/</li> | <li>hyperkitty/</li> | <li>mailman3/</li> | <li>archives/</li> | <li>^user-profile/delete$ | [name='mm_user_account_delete']</li> | <li>^user-profile/$ | [name='mm_user_profile']</li> | <li>accounts/</li> | <li>admin/</li> | </ol> | <p> | The current path, <code>accounts</code>, didn’t match any of these. | </p> | </body> Sure I have accounts/ rather than accounts, but neither are working routes endowed with a trailing slash. Digging for mailman_web.urls, I am lead to believe this is related to my settings, and as I inspect them, I am reminded that I appended del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] to my settings file. Commenting these lines out, restarting mailmanweb, still the same error. Ideally an error like this should be shown to the user. Instead it leads to a endlessly repeated requests for users to verify their email address, as seen in my live system at say https://lists.repec.info/accounts/confirm-email/ These have no CSS, pointing to an apache missconfiguration For what it's worth, here is my current apache configuration | <VirtualHost *:443> | ServerName lists.repec.info | ServerAlias www.lists.repec.info | ServerAlias list.repec.info | ServerAlias www.list.repec.info | ServerAdmin webmaster@localhost | | RewriteEngine On | RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/" [R] | | Alias /static "/usr/local/mailman/web/static" | <Directory "/usr/local/mailman/web/static"> | Require all granted | </Directory> | | Alias /favicon.ico "/usr/local/mailman/web/static/postorius/img/favicon.ico" | | <IfModule mod_headers.c> | RequestHeader unset X-Forwarded-Proto | <If "%{HTTPS} =~ /on/"> | RequestHeader set X-Forwarded-Proto "https" | </If> | </IfModule> | | <IfModule mod_proxy.c> | ProxyPreserveHost On | ProxyPassMatch ^/static/ ! | ProxyPass "/mailman3" "http://127.0.0.1:4386/mailman3" | ProxyPass "/archives" "http://127.0.0.1:4386/archives" | ProxyPass "/accounts" "http://127.0.0.1:4386/accounts" | ProxyPass "/admin" "http://127.0.0.1:4386/admin" | ProxyPass "/user-profile" "http://127.0.0.1:4386/user-profile" | </IfModule> | | LogLevel debug | ErrorLog /var/log/apache2/lists.repec.info_error.log | | CustomLog /var/log/apache2/lists.repec.info_access.log combined | ServerSignature On | | Include /etc/letsencrypt/options-ssl-apache.conf | SSLCertificateFile /etc/letsencrypt/opt/live/repec.info/fullchain.pem | SSLCertificateKeyFile /etc/letsencrypt/opt/live/repec.info/privkey.pem | | </VirtualHost> -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22209th day.

3 5

Reject with notification not working
by MegaBrutal March 26, 2026

March 26, 2026

I'm creating a newsletter style mailing list where only one address is allowed to send e-mails, members just receive them, but they shouldn't be able to post to the list. Still I want to send a friendly notification if members accidentally try to post to the list, so I set "Reject (with notification)" as "Default action to take when a member posts to the list", but it doesn't work: my test address didn't receive any notification when I tried to send a message to the list. I tried to define the "list:user:notice:rejected" template for the list, but to no avail.

5 12

Re: Speaking of RFC 8058
by Paul Tomblin March 25, 2026

March 25, 2026

This is what it looks like in Gmail when a message has the correct one click unsubscribe headers: On Wed, Mar 25, 2026, at 9:43 AM, Danil Smirnov wrote: > Hi Paul, > > Could you tell me what's you MUA? I'm struggling to see any relevant controls in Gmail... > > Sincerely, > Danil Smirnov > > ср, 25 мар. 2026 г., 15:15 Paul Tomblin via Mailman-users <mailman-users(a)mailman3.org>: >> On Wed, Mar 25, 2026, at 12:10 AM, Stephen J. Turnbull wrote: >> > It is undeniable that Mailman is not suitable for a large fraction of >> > announce lists. It's also true that (except for the relatively recent >> > RFC 8058 "Signaling One-Click Unsubscribe" protocol) all of your >> >> Speaking of which, I was wondering why my MUA didn’t put a one-click unsubscribe banner at the top of my mailman lists like it does for lots of other “mailing list” email I get. So I just read RFC 8058, and I realized that while Mailman puts on a List-Unsubscribe: header, it doesn’t have a URI in it, just an email address. It also doesn’t put on a List-Unsubscribe-Post: List-Unsubscribe=One-Click. The requirement for an “opaque identifier” looks hard to do in templates. I realize that it probably hasn’t been implemented due to your separation of Core and Web. But are there plans to provide something? >> >> -- >> Paul Tomblin >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to danil(a)smirnov.la -- Paul Tomblin ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: image.jpeg Replaced multipart/alternative part with first alternative.

1 0

stop mailmanweb
by Thomas Krichel March 23, 2026

March 23, 2026

I'm still working on my mailman site https://lists.repec.info. It's now sadder than it was before. To test, I need to restart mailmanweb for testing. I don't quite get how to stop mailmanweb. root@darni ~ # systemctl stop mailmanweb But mailman-web processes are still running root@darni ~ # ps axf | grep mailman-web 532703 pts/4 S+ 0:00 \_ grep mailman-web 516993 ? Ss 0:00 /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517012 ? S 0:05 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517014 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517015 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517016 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517017 ? S 2:09 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings Here for some background. Here is my service root@darni /var/log/mailman3 # cat /etc/systemd/system/mailmanweb.service [Unit] Description=GNU Mailman Web UI After=syslog.target network.target postgresql.service mailman3.service [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/usr/local/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini KillSignal=SIGINT [Install] WantedBy=multi-user.target Here is my config root@darni ~ # cat /etc/mailman3/uwsgi.ini # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /usr/local/mailman/venv/ module=mailman_web.wsgi:application # Set PYTHONPATH env = PYTHONPATH=/etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 plugins = logfile # Setup the django_q related worker processes. attach-daemon = /usr/local/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/usr/local/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/usr/local/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/usr/local/mailman/web/logs/uwsgi-error.log It's the same as is the doc, just the head directory is changed. I also had to add plugins = logfile otherwise I get complaints it can't log. I suspect this could be usefully added to the doc. Thanks and cheers! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22206th day.

4 6

Registration mail is not sent
by Christian H. Kuhn March 23, 2026

March 23, 2026

Hi all, i got mailman-web up and runnung. Wanted to registrate the main user. Got an error ("Bei der Verarbeitung Ihrer Anfrage ist ein Fehler aufgetreten."). In the logs of postfix, i could see the connection from mailman to postfix, but no mail was transmitted to postfix. How could i repair this? TIA QNo

3 4

Internal server error instead of web interface
by Christian H. Kuhn March 22, 2026

March 22, 2026

Hi all, https://lists.qno.de/mailman3 shows an internal server error. I followed https://docs.mailman3.org/en/latest/install/virtualenv.html with MariaDB instead of PostgreSQL. Python 3.13.0 pip 25.3 mailman 3.3.11b mailman-web 0.0.10.dev14?g0997bd postorius 1.3.13 Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi listens on [::1]:8000, apache2 is configured accordingly. Ports show up in netstat. No errors show in logs. If /mailman3 was a directory, i would have thought of user permission problems. But not with TCP ports. As :8000 is available, i would have thought that there is a problem with uwsgi. Requests arrive there and are processed: [pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0) So uwsgi gets the request and delivers data. The problem seems that apache2 does not get the result, and i cannot find any reason. Any help? TIA QNo

4 5

starting mailman2 under Debian
by Thomas Krichel March 22, 2026

March 22, 2026

It took me several hours to figure out how to start Mailman2.1 on a Debian system, where it is package is run as list. It complained it could not open the pid file. --------------------------------------------------------------------------------- ## file: /etc/systemd/system/mailman.service [Unit] Description=GNU Mailman Mailing List Manager After=syslog.target network.target [Service] Type=forking User=list Group=list RuntimeDirectory=mailman PIDFile=/run/mailman/mailman.pid ExecStart=/usr/lib/mailman/bin/mailmanctl -s start ExecStop=/usr/lib/mailman/bin/mailmanctl stop [Install] WantedBy=multi-user.target --------------------------------------------------------------------------------- Hopefully this will save some good folks' time! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22206th day.

1 0

list not found
by Thomas Krichel March 18, 2026

March 18, 2026

I am very sorry to you folks for not getting back on the problems I am having to install on Debian testing. There are two reasons. One is that I have been much offline for personal reasons. The other is that I have another machine called tagol where I have been running Mailman3 for about three years, using the Debian packet on Debian testing. As testing move to 3.13 this installation could not run. I replaced mailman-core with a 3.12 venv install, but left the mailman3-web package of Debian. This half-arsed job held up for a long time but two weeks ago collapsed. No email went through. I have been trying to switch to a full venv version, still staying with 3.12. Tagol hosts a single list mailman@tagol:~$ mailman lists 1 matching mailing lists found: bibnez(a)folks.email I have some bad queue files. Let's look at the oldest mailman@tagol:~$ ls -lt /var/lib/mailman3/queue/bad/ | tail -1 -rw-rw---- 1 mailman mailman 8579 Mar 11 14:32 1773239548.2417333+451b61b8707218b4dc3d0864eb4ee0172bd21d71.psv Write a script "test_bad" to submit this back. mailman@tagol:~$ cat test_bad #!/bin/bash base=/var/lib/mailman3/queue/bad/1773239548.2417333+451b61b8707218b4dc3d0864eb4ee0172bd21d71 psv=$base.psv pck=$base.pck cp $psv $pck mailman unshunt mailman@tagol:~$ When I run this script, I get in my log Mar 15 05:40:46 2026 (2658932) <a930211e778a4aa0829cee5b2a9e7db9(a)kbs-mg.de> runner "in" shunting message for missing list: <object object at 0x7fb1ad1ad730> I suspect mailman does not see the database. But mailman@tagol:~$ mailman info | grep -v credent GNU Mailman 3.3.10 (Tom Sawyer) Python 3.12.9 (main, Feb 5 2025, 01:31:18) [GCC 14.2.0] config file: /etc/mailman3/mailman.cfg db url: sqlite:////var/lib/mailman3/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ The file exists mailman@tagol:~$ ls -l /var/lib/mailman3/data/mailman.db -rw-rw---- 1 mailman mailman 4825088 Mar 15 05:20 /var/lib/mailman3/data/mailman.db I have no idea where to look next. Thanks and cheers! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22199th day.

5 11

alembic version
by Thomas Krichel March 17, 2026

March 17, 2026

On my fresh install I am running into problems with the alembic number. root@darni ~ # systemctl restart mailman3 ; systemctl restart mailmanwebq Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. Failed to restart mailmanwebq.service: Unit mailmanwebq.service not found. root@darni ~ # systemctl status mailman3.service × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2026-03-07 07:01:03 UTC; 2s ago Duration: 23h 33min 7.258s Invocation: dde1db5581914d96b1da564d537df84a Process: 1209747 ExecStart=/usr/local/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) Mem peak: 64.8M CPU: 681ms Mar 07 07:01:03 darni mailman[1209747]: File "/usr/lib/python3.13/contextlib.py", line 162, in __exit__ Mar 07 07:01:03 darni mailman[1209747]: self.gen.throw(value) Mar 07 07:01:03 darni mailman[1209747]: ~~~~~~~~~~~~~~^^^^^^^ Mar 07 07:01:03 darni mailman[1209747]: File "/usr/local/mailman/venv/lib/python3.13/site-packages/alembic/script/base.py", line 245, in _catch_revision_errors Mar 07 07:01:03 darni mailman[1209747]: raise util.CommandError(resolution) from re Mar 07 07:01:03 darni mailman[1209747]: alembic.util.exc.CommandError: Can't locate revision identified by '8cc1f79f4459' Mar 07 07:01:03 darni systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Mar 07 07:01:03 darni systemd[1]: mailman3.service: Failed with result 'exit-code'. Mar 07 07:01:03 darni systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Mar 07 07:01:03 darni systemd[1]: mailman3.service: Consumed 681ms CPU time over 727ms wall clock time, 64.8M memory peak. Indeed: root@darni ~ # sudo -u postgres psql -d mailman3 psql (18.2 (Debian 18.2-1)) Type "help" for help. mailman3=# SELECT version_num FROM alembic_version; version_num -------------- 8cc1f79f4459 (1 row) Setting the number to say 0 mailman3=# update alembic_version set version_num=0; UPDATE 1 and repeating the restart yields the same problem. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22191st day.

3 5

Subscription confirmation email
by Eric Broens March 15, 2026

March 15, 2026

While doing some tests I subscribed to a mailinglist by sending an email to <list>-join@<domain> Mailman correctly emailed the confirmation request, and the mail was accepted by my ISP. For some reason the confirmation mail did not arrive in my mailbox nor in my spam folder, it seems to have been silently dropped. A day later, I again sent a subscription request to <list>-join@<domain>, and I received a mail from <list>-bounces@<domain> with subject "The results of your email commands" saying that I have a pending subscription for that mailinglist. However, no confirmation link is included, nor instructions to visit the website to confirm the subscription. Am I missing something in the configuration? I would expect that a confirmation request is mailed again to the subscriber. Most subscribers don't use the web interface to manage their subscriptions. The versions running with Maxking's docker-mailman and postfix are: Mailman Core versie GNU Mailman 3.3.10 (Tom Sawyer) Mailman Core API versie 3.1 Mailman Core Python versie 3.12.7 (main, Oct 7 2024, 11:30:19) [GCC 13.2.1 20240309] Best regards, Eric

2 2