- Mailman-users - lists.mailman3.org

captcha for subscription and account registration forms
by Johannes Rohr April 30, 2026

April 30, 2026

Dear all, in mailman installed in venv is there really no canonical way of integrating a captcha into postorius' subscription and account registration forms? We are increasingly getting hammered by spambots, and a captcha would seem like a simple and effective solution. Thanks for any suggestions! Johannes

2 1

Mass subscribe operation fails with http error
by b.watts＠ucl.ac.uk April 30, 2026

April 30, 2026

Hi, We have a mailing list where the admin has configured a custom template: [list:user:action:invite] When inviting a user using Mass Subscribe, the operation fails with the error: HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')) I have reviewed similar threads, including: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I have updated the config in: /etc/mailman3/settings.py to contain: POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk' After adding that item, I've recreated the template and resubmitted the subscribe. But still get the same error. What could I try next? Regards, Brian Senior Systems Administrator, UCL ISD

3 2

How to configure an announce-only list?
by mailman26＠xse.com April 29, 2026

April 29, 2026

I want to create a mailing list that is used for announcements only. I'd like attempts to post to be rejected with a notification. I was able to set the list pw and verify it works with the Approved header using this reference: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… I find that if both: Default action to take when a member posts to the list Default action to take when a non-member posts to the list are set to "reject (with notification)", the approved header is ignored and messages are always rejected (posted via "mailman inject") Would it be bad to test the approved header before rejecting a message? Essentially always accept a message with a valid approved header? Is there another way for me to achieve this? On another front, I'm unable to have messages posted via "mailman inject" use postorius created list templates. Would it be difficult to add this functionality?

2 3

dmarc_mitigate_unconditionally vs. mitigate_owner_mail
by Lichtinger, Bernhard April 28, 2026

April 28, 2026

Hello, We stumbled over an interesting problem with latest mailman-core from git if the setup matches some criteria: 1. Config of mailman3: mitigate_owner_mail = no (default) 2. Config of list: dmarc_mitigate_unconditionally = yes AND dmarc_mitigate_action = munge_from 3. Owner of list has an automatic out-of-office reply enabled 4. Owner is allowed to post on list 5. Somebody writes to list-owner@mailman ==> Result: Somebody's mail gets treated with munged_from and the owner's out-of-office reply is sent to the list and distributed to all members. I expected that with "mitigate_owner_mail = no" there would be no munge_from for mails to list-owner@mailman. But in the end "dmarc_mitigate_unconditionally = yes" has higher precedence than "mitigate_owner_mail = no" in handlers/dmarc.py. I am not sure if this is a bug or a feature ;) As a quick workaround to prevent out-of-office replies going to the list, we configured our postfix to add a "precedence: list" header to all mails sent to an -owner address to prevent to trigger an auto reply. We set dmarc_mitigate_unconditionally = yes AND dmarc_mitigate_action = munge_from to prevent confusing our users if the mails from the list look different dependent on the sender's DMARC policy. And we also don't have to worry about adding tags to the subject or adding headers/footers. With munge_from our DKIM signature is always aligned with the header from domain and gmail, yahoo, etc. are happy. While thinking about our situation I came up with some more thoughts: With mitigate_owner_mail = yes and munge_from is the list posting address really a good choice for the new header from address? Not only auto replies but also owners who click "reply all" without thinking will post to the list. But using the list-owner as new header from would also have some drawbacks, e.g. the possibility of an endless loop of auto replies. Adding the "precedence: list" header also to mails sent to the list-owner might prevent this in most cases at least. But this feels like putting more tape on the problem. In my opinion the least bad solution would be to give "mitigate_owner_mail = no" higher precedence than "dmarc_mitigate_unconditionally = yes". Then the site admin can overrule the list admin. Or will this break other uses cases I did not think about? Regards, Bernhard

2 1

Re: Incorrect error log message in OutgoingRunner._dispose()
by Mark Sapiro April 26, 2026

April 26, 2026

On 4/26/26 10:42 AM, Craig Leres wrote: > On 4/26/26 06:52, Mark Sapiro wrote: >> >> Did you by chance run import21 as root or another non-mailman user >> resulting in template files unreadable by Mailman? > > Yes and no. I ran it as a user in group mailman; the template files are > owned by the user but are group mailman read/write... Then those templates in Mailman's var/templates/LIST-ID/LC/ should be used for the list for that language as long as they are readable and not overridden by a Postorius template or other URI for the list in the template table in the database. Was there anything in mailman.log prior to your defining a Postorius template indicating why they weren't used? >>> Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server >>> 127.0.0.1 on port 25 >> >> This is a well known issue. See <https://gitlab.com/mailman/mailman/-/ >> work_items/582> and related issues referenced therein. > ... > What really bothers me about the error message is that it's reporting a > SMTP connection failure when what really happened was a HTTP connection > failure. That is all part of the above referenced issues. It is a bug and should be fixed but hasn't been yet. It is caused by the low level socket error upon trying to fetch the template, ultimately being caught by the try/except in outgoing runner's sending of the message. >>> I'm using the default webservice port (8001) so I would not expect >>> anything to ever be listening on 8000. >> >> The default web service port (Postorius and HyperKitty) is 8000. Port >> 8001 is Mailman core's rest api. > > Ah. I never noticed anything telling me the apache config needed to also > listen on 8000. It's also confusing to me to call the rest api port the > "web service port" (Also, I'm not running hyperkitty.) Apache doesn't listen on port 8000. The WSGI server (uWsgi or Gunicorn or ...) listens on port 8000 and Apache listens on ports 80 and 443 as normal and proxies the mailman requests to port 8000. > Ok, I added apache config to handle 127:0.0.1:8000 and that solves the > "SMTP" (HTTP) connection error and cpu bound runner. I don't know what you did, but see <https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…> for how Apache should proxy to port 8000. > I still can't get templates to work but I'll debug further and ask for > help later if I still can't get it to work. Do you have a WSGI server running and listening on port 8000? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws…>. You need this for Postorius as Postorius is a Django project and Django is a WSGI application. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Incorrect error log message in OutgoingRunner._dispose()
by mailman26＠xse.com April 26, 2026

April 26, 2026

I'm trying to bring up mailman 3 in a spare vm prior to upgrading a production system from mailman 2. One feature the existing mailman 2 lists uses that I can't get working with mailman 3 are templates. After using "mailman import21" I found files with names such as list:member:regular:footer.txt in the list tree. However they were ignored so I removed them I tried tried creating a template using the web postorius gui. When a message is injected, I see an error log from the out runner: Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server 127.0.0.1 on port 25 Following the error message, the out runner goes cpu bound, creating and deleting queue files in queue/out with .pck and .bak extensions, very quickly. I updated the code to print the exception and it tells a completely different story: Apr 25 12:38:15 2026 (83339) Cannot connect to SMTP server 127.0.0.1 on port 25 (HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/templates/list/test.example.com/list:member:regular:footer (Caused by NewConnectionError("HTTPConnection(host='localhost', port=8000): Failed to establish a new connection: [Errno 61] Connection refused"))) I'm using the default webservice port (8001) so I would not expect anything to ever be listening on 8000. When I stop the runners, the problematic queue file is moved to the shunt queue. Here's what I changed to get the exception detail: mm 287 # pwd /usr/local/lib/python3.11/site-packages/mailman/runners mm 288 # diff -c /var/tmp/outgoing.py outgoing.py *** /var/tmp/outgoing.py Thu Apr 23 14:26:22 2026 --- outgoing.py Sat Apr 25 12:34:33 2026 *************** *** 110,116 **** self._func, msg.get('message-id', 'n/a'))) self._func(mlist, msg, msgdata) self._logged = False ! except socket.error: # There was a problem connecting to the SMTP server. Log this # once, but crank up our sleep time so we don't fill the error # log. --- 110,116 ---- self._func, msg.get('message-id', 'n/a'))) self._func(mlist, msg, msgdata) self._logged = False ! except socket.error as e: # There was a problem connecting to the SMTP server. Log this # once, but crank up our sleep time so we don't fill the error # log. *************** *** 118,125 **** if port == 0: port = 'smtp' # Log this just once. if not self._logged: ! log.error('Cannot connect to SMTP server %s on port %s', ! config.mta.smtp_host, port) self._logged = True return True except SomeRecipientsFailed as error: --- 118,125 ---- if port == 0: port = 'smtp' # Log this just once. if not self._logged: ! log.error('Cannot connect to SMTP server %s on port %s (%s)', ! config.mta.smtp_host, port, e) self._logged = True return True except SomeRecipientsFailed as error:

3 2

Command Emails not Working
by Brinson, Jason T April 24, 2026

April 24, 2026

Hello, I have an issue where command emails (-join, -request, etc.) are getting routed to the list itself (and being moderated). I have my postfix configured according to the instructions here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… And here (for an alias domain): https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… Any insights would be appreciated. ----------------- Jason "Shae" Brinson (They/Them) IT Support Professional Sr. Georgia Institute of Technology College of Computing 801 Atlantic Drive NW Atlanta, GA 30332 Phone: 404-894-7065 Email: jason.brinson(a)cc.gatech.edu<mailto:jason.brinson@cc.gatech.edu>

3 7

How can we solve ZoneInfoNotFoundError
by Markus Grandpré April 22, 2026

April 22, 2026

Dear list members A user of our Mailman system reports having trouble logging in to access a mailing list archive. In the error messages that the Mailman system sends via email, we find: ... Internal Server Error: /mailman3/accounts/login/ ZoneInfoNotFoundError at /accounts/login/ 'No time zone found with key US/Eastern' Request Method: POST Request URL: https://mailman.uni-konstanz.de/mailman3/accounts/login/ Django Version: 4.2.28 Python Executable: /usr/bin/uwsgi-core Python Version: 3.13.5 ... Exception Type: ZoneInfoNotFoundError at /accounts/login/ Exception Value: 'No time zone found with key US/Eastern' Raised during: allauth.account.views.LoginView Request information: USER: **** GET: No GET data POST: csrfmiddlewaretoken = 'E6IT1iObdZYMyGKUgAHSxJ6LCzSZPDOKZmgVCaN9Kaae3s5gJy75Dwh8ptWjzcdI' login = '****' password = '****' next = '/mailman3/hyperkitty/list/basex-talk(a)mailman.uni-konstanz.de/' FILES: No FILES data COOKIES: csrftoken = '********************' ... (full error stack is attached to this email) Is there a server-side solution available for our GNU Mailman system 3.3.10 (Tom Sawyer), which runs on Debian GNU/Linux 13 (trixie)? Best regards, Markus Grandpré -- Markus Grandpré (he/him) Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration 78457 Konstanz Tel: +49 7531 88-4342D

3 4

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

April 20, 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 6

request to held messages yields set of email addresses
by Thomas Krichel April 16, 2026

April 16, 2026

Hi gang, I probably have already developed an uneviable reputation of being able to produce the finest of mess. I stay true to form here. In my 3.12 installation when my admin clicks to view the held messages, he gets an internal server error. The error comes from postorius, where the log entry is 2026-04-15 12:45:25 [FALCON] [ERROR] GET /3.1/lists/bibnez(a)folks.email/held => Traceback (most recent call last): File "falcon/app.py", line 440, in falcon.app.App.__call__ File "/usr/local/mailman/venv/lib/python3.12/site-packages/mailman/rest/post_moderation.py", line 194, in on_get resource = self._make_collection(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/mailman/venv/lib/python3.12/site-packages/mailman/rest/helpers.py", line 189, in _make_collection [etag(resource) for resource in entries] ^^^^^^^^^^^^^^ File "/usr/local/mailman/venv/lib/python3.12/site-packages/mailman/rest/helpers.py", line 104, in etag return json.dumps(resource, cls=ExtendedEncoder, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/json/__init__.py", line 238, in dumps **kw).encode(obj) ^^^^^^^^^^^ File "/usr/lib/python3.12/json/encoder.py", line 200, in encode chunks = self.iterencode(o, _one_shot=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/json/encoder.py", line 258, in iterencode return _iterencode(o, 0) ^^^^^^^^^^^^^^^^^ File "/usr/local/mailman/venv/lib/python3.12/site-packages/mailman/rest/helpers.py", line 68, in default return super().default(obj) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/json/encoder.py", line 180, in default raise TypeError(f'Object of type {o.__class__.__name__} ' TypeError: Object of type set is not JSON serializable Checking the actual set that is returned, by converting the set into a string and writing it to a file (by enhancing helpers.py), I discover that what is returned is as set of 53 email addresses, not of 24 messages as the web interface suggests. Intrestingly, my admin reports that the he is correctly informed about the held messages via email. The then forwards those that need posting to the list. I suspect that to get to the bottom of this problem, I need to use the low-level postorious functions that actually access the parse the held message data. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22230th day.

2 2