March 2026 - Mailman-users - lists.mailman3.org

broken route to accounts
by Thomas Krichel April 10, 2026

April 10, 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 10

Re: Python 3.13 compatibility
by Thomas Krichel April 2, 2026

April 2, 2026

Hi gang, On mailman import21, I hit the error TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol I found the earlier thread, where Mark wrote > This is https://gitlab.com/mailman/mailman/-/issues/1190 fixed for > Mailman 3.3.11 by https://gitlab.com/mailman/mailman/-/merge_requests/1309 I have (venv) mailman@darni:~$ mailman version GNU Mailman 3.3.9 (Tom Sawyer) I tried (venv) mailman@darni:~$ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web to no avail, the TypeError is not fixed and the version is the same. ok, so I need to spell out a version. Trying pip install -U mailman==3.3.11 postorius django-mailman3 hyperkitty mailman-web 3.3.11 appears not to be available pip install -U mailman==3.3.10 postorius django-mailman3 hyperkitty mailman-web yields the familiar problem with the nntplib. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13" I had earlier gotten around this by installing its successor, standard-nntplib, and it is still there. (venv) mailman@darni:~$ pip3.13 install standard-nntplib Requirement already satisfied: standard-nntplib in /usr/local/mailman/venv/lib/python3.13/site-packages (3.13.0) That used to work for 3.3.9. But the 3.3.10 version may have no verbiage to say that the nntlib is replaced by standard-nntplib Now I seem to have managed to hose my environment. (venv) mailman@darni:~$ mailman version Traceback (most recent call last): File "/usr/local/mailman/venv/bin/mailman", line 3, in <module> from mailman.bin.mailman import main File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/bin/mailman.py", line 25, in <module> from mailman.core.initialize import initialize File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/core/initialize.py", line 29, in <module> import mailman.config.config File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/config/__init__.py", line 20, in <module> from mailman.config.config import Configuration File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/config/config.py", line 32, in <module> from mailman.utilities.modules import call_name, expand_path File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/utilities/modules.py", line 23, in <module> from pkg_resources import resource_filename, resource_listdir ModuleNotFoundError: No module named 'pkg_resources' What now? -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22213th day.

5 14

Delimiter problems
by Christian H. Kuhn March 30, 2026

March 30, 2026

Hi all, i used - as recipient_delimiter for a long time. Now it was brought to my attention that + is the current default, so i changed in the main.cfg of all postfix instances to recipient_delimiter = +- Now of course confirmaiton mails for mailing list qtest to qtest-request@domain fail, because the recipient qtest is unknown. I changed [mailman] listname_chars: [_.0-9a-z] [mta] verp_delimiter: +- but still the generated address is qtest-request@domain. Is it possible to generate emails as qtest_request@domain? If not, would the owner_request_special of postfix help? Kind regards, QNo

2 1

Reject with notification not working
by MegaBrutal March 28, 2026

March 28, 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 16

Django 5.2 LTS and mailman 3
by dlb-ml＠anl.gov March 27, 2026

March 27, 2026

I noticed that Django 4.2 is nearing EOL status in April (no specific day in April is given): https://www.djangoproject.com/download/ I also noticed that there's a planned update to add support for 5.2 to mailman-web: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Is this expected to be released before 4.2 goes EOL? Is there a rough time line? Thanks!

2 4

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

Footer variables
by Washington Odhiambo March 14, 2026

March 14, 2026

In my /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/list:member:regular:footer.txt, I have: Archived at: ${hyperkitty_url I was hoping that variable would be replaced with what I see in this list, i.e. - Archived at: https://lists.mailman3.org/archives/list/mailman-users @mailman3.org/message/HX6NZKICL7V2QWE2V4YNKIMSMQHARPUV/ However, in my posts, it's blank. What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 12

[GSoC 2026] [Feature Proposal] Per-List Backup and Restore Support
by sonika gutha March 14, 2026

March 14, 2026

*Introduction: * My name is *Sonika Chowdary Gutha*, and I am a *second-year Computer Science undergraduate at BITS Pilani, India*. I recently completed a *6-month internship in Backend Development using Python and Django*, where I gained experience in building backend systems and working with REST APIs.I am also familiar with the *MERN stack and the Flutter framework*, and I have experience developing both web and mobile applications. In addition I have been introduced to the fundamentals of several programming languages, including *Python, C++, and JavaScript*. I am exploring the possibility of implementing a *per-list backup and restore feature* for Mailman. The goal of this feature is to allow list administrators or owners to *export the configuration and membership data of a specific mailing list into a portable backup file and restore it later when needed*. This could be useful in situations such as: - Migrating lists between servers - Recovering from configuration mistakes - Replicating list setups across environments *Implementation:* The following diagram provides a visual representation of the proposed backup and restore workflow <https://excalidraw.com/#json=PhUB9tdMrupMfpx7O6_i6,OLBUtBJjL5_sCR-UokrNHw> .: I plan to implement this feature in two parts. The main backup and restore logic should live in *Mailman Core*, since that is where the actual list configuration and membership data are stored. My idea is to define a *versioned JSON format* that captures the important per-list data such as list settings, members, owners, moderators, and relevant subscription preferences. On the export side, Core would gather this data and write it into a portable backup file. On the restore side, it would read the file, validate its contents, recreate the list if necessary, and restore the saved settings and memberships. On the *Postorius* side, I would implement the user-facing workflow for this feature. This would include an option for list owners or administrators to download a backup file for a specific list, as well as a page where they can upload and restore that file when needed. For the initial version, I plan to keep the feature focused and reliable by covering configuration and membership data first, while leaving more complex areas such as archives or other external components out of scope unless they are explicitly expected. *Questions:* 1. For the first version, what exactly should be included in the per-list backup: only settings and memberships, or also items like templates, ban lists, and member preferences? 2. Should the main export and restore implementation live in Mailman Core, with Postorius mainly responsible for the UI and workflow? 3. Is a *versioned JSON format* the preferred choice for the backup file? 4. Should restore only support creating or recreating a list from backup, or should it also support restoring into an already existing list?Thank you for your time and feedback. Please feel free to *suggest any changes or improvements to the proposed implementation*, also if possible hope i can get answers for the above questions which will be helpful for my proposal, I would be happy to incorporate them.:) Best regards, Sonika

2 2

venv and upgrade from python 3.11 to 3.13 because of OS-upgrade
by Andreas Vetter March 13, 2026

March 13, 2026

Hi, I have a venv installation (mailman postorius django-mailman3 hyperkitty mailman-web) with python 3.11 from the Linux distribution. Since distribution EOL nears, I checked python version in next distribution and it is python 3.13. So my guess is, after distro upgrade, this will stop working. How should I upgrade? -- Mit freundlichen Gruessen, Andreas Vetter

5 5

Where to start looking?
by Paul Tomblin March 12, 2026

March 12, 2026

So I imported all our mailman2 lists into mailman3, and it appears it didn't preserve passwords. So my wife (who administers 3 lists of her own) tried to use the reset password link (multiple times) but she never gets the email. I don't see any outgoing email to her in mail.log, or any of the mailman logs. I do the exact same thing as her and I get the email. Any suggestions on what I should be looking for? -- Paul Tomblin

2 1

Accept these non-members
by Lars Bjørndal March 10, 2026

March 10, 2026

Hi, list! I have an announce only Mailman3 list. When I log into the web interface as an admin user, and go to the specified list, and choose Settings, I find the Message Acceptance tab. There, I find the edit field Accept these non-members. But this field is empty, although I know that some people have permissions and are able to post to this list. How can I find the list of these non-members and add more people or delete someone? I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. Any hints? Thanks, Lars

3 10

Reset bounce count in MM3
by iMark March 10, 2026

March 10, 2026

Hi, Is there an equivalent of Mailman 2's "bin/reset_bounce.py" in Mailman 3 ? Thanks, Mark

3 7

Additional info/tags on Members
by mkoerber＠akamai.com March 9, 2026

March 9, 2026

I am managing a few mailing lists which are hosted on a mailman3 instance. None of these are allowing self-subscription, but I have a need to be able to search the membership by association, ie whether they belong to any of a number of named groups Currently there does not seem to be any means for attaching a comment field, tag or such to group members, which would allow keeping such metadata and using it for searching members. (and no, the email addresses of members of one or more groups may not be similar, hence searching by @domain or such will not work) Also, the group-association info should *not* be exposed externally (ie to the member in question or any others), which makes adding the tag/group info as part of the full name impossible. Is there any way to do this in mailman3? If not can this be counted as a feature request: - in mailman3 itself: + add a facility that allows storing additional info to each member , either as a (largish) comment field or an array of tags ++ if tags, it should support managing thousands of them (but each member is likely to only need a few associated) + if tags are used, each list should have its own set of tags (though a means to designate a list to participate in a global tag collection might be useful). - in postorious: + allow modifying the comment field, or adding/removing/modifying one or more tags to each list-member + allow searching a group's membership by tags (or substring in the comment field), ++ following which mass-operations (deletion, setting moderation flags etc) should be possible based on individual selection of the found fields mailman3 really only would need to support storing the additional data for each member, as (at least in my use case) that data is not actually required for mail forwarding. However, it seems to be desirable to store the info in the mailman3 database rather than an external system (to reduce chances that these might get out of sync).

2 1

Opinions wanted.
by Mark Sapiro March 9, 2026

March 9, 2026

There is currently a merge request at <https://gitlab.com/mailman/django-mailman3/-/merge_requests/345> to hide the "Results per page:" dropdown from some Postorius and HyperKitty pages when the full list of items (lists) is on the page. I.e. when the number of items is <=10 and the "Results per page:" is the default 10, don't display the dropdown. However there is some controversy over whether this should also apply say when the number of items is > 10 but still is on one page. So the question is if we are going to hide the dropdown when "Results per page:" is the default 10 and there are <= 10 items so all are on the page, should we also hide it when say "Results per page:" is 25 and there are 22 items all on the page. Your opinion on this is requested via a reply in this thread. See the merge request (link above) for arguments pro and con. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 8

How to upgrade to 3.10
by Paul Tomblin March 9, 2026

March 9, 2026

I installed 3.9 with pip last week, but i want to upgrade to 3.10. But pip install -U mailman postorius django-mailman3 hyperkitty mailman-web doesn't upgrade it. Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Collecting mailman Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more... -- Paul Tomblin

2 10

Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated
by Thomas Krichel March 7, 2026

March 7, 2026

This issue is still there for me. I am starting a new installation from scratch, with the venv method in 3.13. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. I have root@darni /etc/mailman3 # head -15 /etc/mailman3/settings.py # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Which is what I believe Wikinaut suggested works for her/him. But the warning is still there. I added Marks suggestions to add verbiage in the actual codebase root@darni /etc/mailman3 # tail -17 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/settings/mailman.py ### added by ToK #: Django Allauth #ACCOUNT_AUTHENTICATION_METHOD = "username_email" #ACCOUNT_EMAIL_REQUIRED = True #ACCOUNT_EMAIL_VERIFICATION = "mandatory" #ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_LOGIN_METHODS = {'email', 'username'} ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] ACCOUNT_EMAIL_VERIFICATION = "mandatory" ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] Restarted root@darni /etc/mailman3 # systemctl restart mailman3 ; systemctl restart mailmanweb Same old. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Maybe I missunderstood something. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22190th day.

3 6

Archiving Display Email Signature in Plain-Text
by msok＠lalawlibrary.org March 6, 2026

March 6, 2026

The Archiving is still display Email Signature in Plain-Text after I configured filter content: No and convert html to plaintext: No in Alter Messages. And Markdown text in Archiving settings. In addition to that, I also configured HYPERKITTY_RENDER_INLINE_IMAGE = True in settings.py file Where else should take a look into this? My email signature is from CodeTwo. Thanks, Marin

3 4

Can't add emails to accept_these_nonmembers
by Ibiam Chihurumnaya March 4, 2026

March 4, 2026

I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save().

3 17

Debian bug report
by Paul Tomblin March 3, 2026

March 3, 2026

So I went to submit a bug report to Debian about the fact that the mailman3-web page drags in nginx for no reason. Turns out that the bug had been reported in 2021 and nobody who worked on it who understood mailman understood apache and nobody who worked on it who understood apache understood mailman[1]. So I submitted an update. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002795 [1] Literally, one of the developers said Thanks, I admit initially I had no plan on supporting apache2 as I don't use it. Jonas did that part and therefore I did not follow at all. -- Paul Tomblin

2 2

Re: Footer variables
by Stephen J. Turnbull March 3, 2026

March 3, 2026

Please keep this on list. Paul Tomblin writes: > Nope, it's still saying it depends on libapache2-mod-proxy-uwsgi | > nginx, and there's no libapache2-mod-proxy-uwsgi. It appears that > mod_proxy is in base apache now. Oddly I never enabled proxy_uwsgi > in mods-enabled but mailman works. I should probably report it to > Debian. What depends on libapache2-mod-proxy-uwsgi? Mailman core doesn't depend on that at all. It always uses gunicorn as the WSGI server for the REST API, and the Apache config uses ProxyPass on port localhost:8001. And sez who? Are you asking apt or dpkg? I thought you have installed via pip into a virtual environment -- what apt and dpkg think about Mailman dependencies is irrelevant. > > > Is it possible to upgrade to 3.10 with pip? If you installed using Debian, you can't upgrade with pip -- that's a Debian restriction. You have to remove the Debian package(s), and create a virtual environment, typically under /opt/mailman, to install the Mailman suite into. Then, if you have already working lists, you have to either (1) "very carefully" move all the /var/lib/mailman data from your working Debian install into /opt/mailman in appropriate places, or (2) configure the new Mailman to look for data where Debian put it (if you're lucky you can re-use Debian's /etc/mailman3/mailman.cfg for that, although they may have patched the source). The /var data is the queues (mostly bad and shunt, but you may have orphaned qfiles in out, and very very rarely in other queues), the logs, and any in-progress digests being accumulated. The list configurations, user profiles, and most volatile data (eg, pending confirmations) will be in your database. You can use the Debian packaged database, just point the new Mailman at that. > > Yes: see https://pypi.org/project/mailman/. > > Use python3 -m pip install --upgrade mailman. > > Nope, that doesn't work. > python3 -m pip install --upgrade mailman 2>&1 | tee bar > Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Where is '.'? If it's under /var/lib or /var/share, you've got Debian's mailman and you can't upgrade with pip. You want it to be under /usr/local (ugh) or /opt/mailman (happy face). > Collecting mailman > Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) [...] > Requirement already satisfied: zope.schema>=4.9 in ./venv/lib/python3.13/site-packages (from zope.configuration->mailman) (8.1) Are you saying pip returns to the shell prompt without doing anything after that? > If I'm reading that right, I have to guess which requirements I > need to force an update on before it will upgrade mailman. No, that's saying all requirements are satisfied for mailman-3.3.10 as far as I can tell. Are you working as the right user? (If you've previously used Debian packages and have working lists, you probably want to continue using Debian's preferred 'list' user, otherwise you may create a 'mailman' user.) If it's not lacking write permissions to the virtual environment, I have no idea why this isn't working. The only thing I can suggest is the same as Mark, force version 3.3.10 with python3 -m pip install --upgrade mailman==3.3.10 and see what happens. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 0

config_list in Mailman3?
by John Price March 3, 2026

March 3, 2026

Is there a way to do this in Mailman3? # Mailman2 backup individual list config # $list = list name # writes config to mailman.cfg $MAILMAN_ROOT/bin/config_list -o mailman.cfg $list -- Can vegetarians eat animal crackers? Have a great day and don't forget to laugh! http://www.gcfl.net (The Good, Clean Funnies List): Good, clean daily funnies you can safely tell your Mom!

2 1

High IO for 8+ hours
by Paul Tomblin March 2, 2026

March 2, 2026

First time running runjobs monthly since I installed it a few days ago, and it's been maxing out I/O for the last 8 hours. There doesn't appear to be any logging going on. I am using Xapian, by the way. Is this normal? Is this going to happen every month, or is the first month special? -- Paul Tomblin

3 6

Debian upgrade Hyperkitty not archiving
by Phil Steel-Wilson March 1, 2026

March 1, 2026

Hi List, I may be in the wrong place so bear with me. I'm working at a volunteer organization with around a dozen mailing lists that were previously on mm2 that have been upgraded to mm3 with the upgrade to debian trixie. Mailman is running and the lists all work ok but i found 1800 mails in the shunt queue. Hyperkitty also shows all the old archives pre 2020 the same as in the django console. When i tried to unshunt the mails they moved to the bad queue. How do i find whats wrong here? Mailman Core Version GNU Mailman 3.3.10 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0] archive 0 bad 0 bounces 0 command 0 digest 0 in 0 nntp 0 out 0 pipeline 0 retry 0 shunt 0 virgin 0 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 105, in view return self.dispatch(request, *args, **kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 144, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 56, in get return self.post(request, *args, **kwargs) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 67, in post client = _openid_consumer( request, self.provider, self.provider.endpoint) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/openid/views.py", line 29, in _openid_consumer server_settings = provider.get_server_settings(endpoint) TypeError: OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint' ERROR 2026-02-27 20:50:19,995 1769748 django.request Internal Server Error: /mailman3/accounts/fedora/login/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 105, in view return self.dispatch(request, *args, **kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 144, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 56, in get return self.post(request, *args, **kwargs) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 67, in post client = _openid_consumer( request, self.provider, self.provider.endpoint) File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/openid/views.py", line 29, in _openid_consumer server_settings = provider.get_server_settings(endpoint) TypeError: OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint' [pid: 1769748|app: 0|req: 89/89] 185.191.171.15 () {58 vars in 1365 bytes} [Fri Feb 27 20:50:19 2026] GET /mailman3/accounts/fedora/login/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fluv-main%40luv.asn.au%2Fthread%2FINYPCCUO5QRQ3A2M2KRVKLNORHXNK472%2F&process=login => generated 773 bytes in 43 msecs (HTTP/1.1 500) 8 headers in 279 bytes (1 switches on core 1) [pid: 1769748|app: 0|req: 90/90] 185.191.171.13 () {58 vars in 1275 bytes} [Fri Feb 27 20:50:33 2026] GET /mailman3/hyperkitty/list/luv-main(a)luv.asn.au/message/YQDJ3OXAS2EMBUM6TDGZZRI5WT6VI4TR/ => generated 17089 bytes in 25 msecs (HTTP/1.1 200) 9 headers in 398 bytes (1 switches on core 0) [pid: 1769748|app: 0|req: 91/91] 47.82.11.77 () {58 vars in 1224 bytes} [Fri Feb 27 20:50:47 2026] GET /mailman3/hyperkitty/list/luv-main(a)luv.asn.au/message/3UQR62KTUF56C42ZGQ4NNFVEBY3HRILU/ => generated 12640 bytes in 22 msecs (HTTP/1.1 200) 9 headers in 398 bytes (1 switches on core 1) [pid: 1769748|app: 0|req: 92/92] 74.7.243.222 () {64 vars in 1503 bytes} [Fri Feb 27 20:51:11 2026] GET /mailman3/accounts/login/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fluv-main%40luv.asn.au%2Fmessage%2FLLHILHCL6MMC5U5VCOSRX7IEDZL43TID%2F => generated 9659 bytes in 10 msecs (HTTP/1.1 200) 11 headers in 509 bytes (1 switches on core 0) [pid: 1769748|app: 0|req: 93/93] 85.208.96.206 () {58 vars in 1274 bytes} [Fri Feb 27 20:51:15 2026] GET /mailman3/hyperkitty/list/luv-main(a)luv.asn.au/message/VVFNVINSMUEWWLQHY36FO2FF33ZUOW2T/ => generated 13525 bytes in 21 msecs (HTTP/1.1 200) 9 headers in 398 bytes (1 switches on core 1) [pid: 1769748|app: 0|req: 94/94] 185.191.171.7 () {58 vars in 1308 bytes} [Fri Feb 27 20:51:19 2026] GET /mailman3/accounts/signup/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fluv-main%40luv.asn.au%2Fmessage%2F43YMKZGDLKODRYMMJHZ4JUEAMY5H4MFT%2F => generated 9909 bytes in 9 msecs (HTTP/1.1 200) 11 headers in 509 bytes (1 switches on core 0) [pid: 1769748|app: 0|req: 95/95] 85.208.96.201 () {58 vars in 1308 bytes} [Fri Feb 27 20:51:20 2026] GET /mailman3/accounts/signup/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fluv-main%40luv.asn.au%2Fmessage%2F3FICKZQDDQNZLFS6HD47FL2UK64ZQRCB%2F => generated 9909 bytes in 9 msecs (HTTP/1.1 200) 11 headers in 509 bytes (1 switches on core 1) ERROR 2026-02-27 20:51:20,841 1769748 django.request Internal Server Error: /mailman3/accounts/fedora/login/

2 4