- Mailman-users - lists.mailman3.org

Changing default language for lists
by Wessel Kraaij April 13, 2026

April 13, 2026

How can I change the default language for lists (and other defaults)? I changed it in mailman-core but Postorius overrides these core defaults with a patch. I am using the docker version of maxking Wessel

2 4

Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment
by Prasanth Nair April 11, 2026

April 11, 2026

Hi all, I am currently running a Mailman 3 setup on a standalone server and planning to migrate it to a Docker-based deployment using the official Docker Mailman images. I would appreciate your guidance on the recommended approach for this migration. *Current (existing) setup:* - Mailman Core: 3.3.5 - Postorius: 1.3.6 - HyperKitty: 1.3.5 - PostgreSQL: 12.22 (Ubuntu) - Host-based installation (non-Docker) - Postfix used as the MTA - Active mailing lists with members and archives - Apache reverse proxy in front *Target (new) setup:* - Docker-based Mailman 3 (mailman-core, mailman-web, PostgreSQL containers) - Based on the official Docker Mailman repository - Postfix as the MTA - Apache reverse proxy in front I would like to migrate the following components safely: - Mailing lists and their configurations - Subscribers and roles - HyperKitty archives - Postorius/web data (users, preferences, etc.) I have a few specific questions: 1. What is the recommended migration approach from a host-based Mailman 3 installation to the Docker-based setup? 2. Is it safe to directly restore the PostgreSQL databases into the Docker environment, or is there a preferred migration method? 3. Are there any version compatibility considerations when migrating from Mailman Core 3.3.5 / Postorius 1.3.6 / HyperKitty 1.3.5 to the versions used in the current Docker images? 4. How to migrate archives? 5. The official Docker Compose file references `postgres:12-alpine`. Is it recommended to stay on PostgreSQL 12 for compatibility, or is it supported to use a newer PostgreSQL version (for example, PostgreSQL 18) with the Docker Mailman setup? 6. Are there any common pitfalls or best practices you would recommend for ensuring a smooth migration? Any guidance or documentation you can provide would be greatly appreciated. Thank you for your time and support. Kind regards, Prasanth Nair

3 2

Why is it so difficult to setup Mailman3?
by htfoot＠gmail.com April 11, 2026

April 11, 2026

I've been using Mailman2 for probably 20 years, and recently I've been looking to move up to Mailman3 on an Ubuntu system. I think I've got the mailing list core part working, but the instructions for setting up the web part(s) are either inscrutable or incomplete, if not both. Is this just a rite of passage?

9 24

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

Integration with spamassassin?
by Peter Chubb April 9, 2026

April 9, 2026

Has anyone integrated Mailman3 with Spamassassin? What I'd like is a way for emails that I click 'discard' on in Postorius, to be submitted to the spamassassin Bayes classifier to make it more likely similar ones will be rejected in future at SMTP conversation time. Peter C

3 4

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