- Mailman-users - lists.mailman3.org

Authentication of posts to a Mailman installation
by Steve Brown Aug. 10, 2026

Aug. 10, 2026

I have a suspect post that appears to be from a member but has a link to a potential scam site. I am not knowledgeable about spoofed addresses in the header; can a hacker simply put someone else's address somewhere in the header and have the message accepted if that address appears in the list of members? Steve Brown, administrator of a small list.

3 3

urls.py location on venv install
by Torsten Aug. 10, 2026

Aug. 10, 2026

Hey all together, I have just nearly finished the migration of Mailman 3 from Debian packages to venv and mailman (master and runner) is up and running and uwsgi is also up and running. Just when I go to the web page https://<mydomain.tld>/mailman3 I get a server error and looking at the mailman web log I see that the ROOT_URLCONF seems to be missing. Following this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I added urls.py to /etc/mailman3 together with the other configuration files (settings.py, mailman.cfg and uwsgi.ini) and have added ROOT_URLCONF = 'urls' to /etc/settings.py but after restarting mailman (core) and mailman (web) the error is still there. What am I missing? TIA Torsten

4 10

List Message Acceptance and Spam Filtering
by Washington Odhiambo Aug. 10, 2026

Aug. 10, 2026

Hello Admins, I am running MM3 3.3.11b3. The issue at hand also applies to 3.3.10. In my list setting, I have set "Default action to take when a non-member posts to the list" = Discard (no notification). In /etc/mailman3/mailman.cfg I have: [antispam] header_checks: X-Spam-Score: ^[4-9]\. Authentication-Results: dkim=neutral jump_chain: hold I am running rspamd on the host for Spam filtering. Now, I have a number of spam being sent to the list by non-members. The antispam rule in mailman.cfg matches and holds the email for moderation. I am failing to wrap my head around this behaviour. I was expecting that: 1. Any posts from non-members would be discarded 2. Mail classified as spam (from members) would be held for inspection by the list administrator. Can someone please help me untangle my thinking? -- 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]

1 0

hyperkitty not archiving new mail
by Jaldhar H. Vyas Aug. 7, 2026

Aug. 7, 2026

Hello all, Mailman 3.3.10 on Debian 13. I recently upgraded from a well-running installation of Mailman2. Importing the existing mailing lists went well but I'm having problems with hyperkitty. First it was complaining that I didn't have a valid SSL certificate for localhost. I rectified that but in the mean time I ended up with some .pck files in /var/lib/mailman3/archives/hyperkitty/spool . Inspecting these with mailman-wrapper qfile reveals that they are messages which have been sent since the import. How do I reindex just those messages? I tried update_index and rebuild_index but apart from taking forever, they don't seem to help.

2 3

Re: Thank you for the tips a year ago! Please help me gather other use-cases
by Archie Singh Aug. 7, 2026

Aug. 7, 2026

Hello, I am glad you asked these questions, as this can help anyone who will later wish to use the dynamic sublists feature for team collaboration when it is merged into Mailman 3. What does your suggested implementation look like? Would it be something > like main+sub-topic(a)example.com which would create a sub list called > “sub-topic” with inherited permissions from “main”? > Your guess is actually very close because a user will send a mail to a special alias, in your case main-new(a)example.com (with the -new command as a suffix to the parent list main(a)example.com) Then Mailman takes the message-ID, generates a database serial number, and using Base32 encoding generates a unique address for the child list (e.g., main-ab(a)example.com) And indeed because the child list is linked in the database via the parent_id, it inherits its settings from the parent list itself. What would that bring on top of including [sub-topic] in the subject or > body? It reduces inbox flooding :) When you use a subject tag on a mailing list it still follows the broadcast model; if a specific thread for troubleshooting or a specific project gets more replies, every single person on the main list will receive that many emails regardless of whether it was relevant to them or not. And thus, dynamic sublists is an opt-in thread model; the -new email is broadcast both to the main list (main(a)example.com) and the newly made child list ( main-ab(a)example.com) Mailman will send a separate announcement to the main list containing the -join and -leave addresses for the new child list. Also, the creator is automatically subscribed to the new child list and anyone else who is interested can opt-in. All the incoming replies from then on are routed to the child list. > I’m glad our little exchange on the MM3 list was helpful. A great example > of the power of searchable archives of such exchanges. Indeed :D Thanks again! Regards Archie On Fri, Aug 7, 2026 at 4:55 PM Rodrigo Camacho <rodrigo(a)vitz.fr> wrote: > > > > On 7 Aug 2026, at 13:09, Archie Singh <archie.singh2610(a)gmail.com> > wrote: > > > > I am Archie, a Google Summer of Code contributor for GNU Mailman and I > am working on implementing Dynamic Sublists, a type of conversation/thread > model into MM3. > > This sounds like a way to group a set of threads together through a > dynamically created list. > Today a similar result can be obtained (and often is) by adding something > like [UNIQUE ID OF TOPIC] to the subject or even the body of a set of > threads sent to one list. > > What does your suggested implementation look like? Would it be something > like main+sub-topic(a)example.com which would create a sub list called > “sub-topic” with inherited permissions from “main”? > What would that bring on top of including [sub-topic] in the subject or > body? > > > I wanted to let you know that your entire discussion thread was > something I wrote a blog about to explain (dated: 5th May 2026, > https://archiegnumailman.hashnode.dev/a-foundational-approach-to-replacing-…) > one of the use-cases of dynamic sublists and in fact if this feature was > present earlier in Mailman 3 you would have been able to utilize it for > your work :D > > I’m glad our little exchange on the MM3 list was helpful. A great example > of the power of searchable archives of such exchanges.

1 0

New attack in progress
by Paul Tomblin Aug. 5, 2026

Aug. 5, 2026

Judging by the bounce messages I’m seeing, somebody or somebodies are trying to sign up for accounts on my Mailman instance using fake email addresses. Can’t imagine what the end game is, other than annoying people with “please confirm your email address” emails when they use a real address. -- Paul Tomblin

5 4

Mass change Digest delivery mode
by iMark Aug. 5, 2026

Aug. 5, 2026

Hi All, Using the Mailman shell, can the delivery mode of Digests be changed to 'Plain text' for all users on just one list ? If it is, could someone tell me how that's done. Thanks, iMark

4 11

How can we solve ZoneInfoNotFoundError
by Markus Grandpré Aug. 5, 2026

Aug. 5, 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 6

Mailman 3.3.4 logging behaviour, mixed log formats, and REST API error
by Henrik Rasmussen Aug. 4, 2026

Aug. 4, 2026

Hello, I have been chatting with Copilot AI for some days to get help investigating some logging-related issues in a Mailman 3.3.4 Docker installation and, so I would appreciate any guidance. We are working on a long needed upgrade, but for now I need the logs in Elasticsearch, and they are aweful. Environment * GNU Mailman 3.3.4 (Tom Sawyer) * Python 3.8.10 * Docker-based installation * Test environment with a single mailing list: listname(a)example.com<mailto:listname@example.com> Logging configuration I've configured dedicated log files for most logging channels. For example, [logging.http] is configured with format: %(asctime)s (%(process)d) %(message)s, datefmt: %Y-%m-%d %H:%M:%S.%3N, propagate: no, level: debug, and path: http.log. All [logging.*] sections in the generated /etc/mailman-extra.cfg use the same datefmt. format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: info path: mailman.log [logging.archiver] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: archiver.log [logging.bounce] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: bounce.log [logging.config] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: config.log [logging.database] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: database.log [logging.debug] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: debug.log [logging.error] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: error.log [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: fromusenet.log [logging.http] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: http.log [logging.locks] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: locks.log [logging.mischief] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: mischief.log [logging.plugins] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: plugins.log [logging.runner] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: info path: runner.log [logging.smtp] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: info path: smtp.log [logging.smtp-failure] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: smtp-failure.log [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: subscribe.log [logging.vette] format: %(asctime)s (%(process)d) %(message)s datefmt: %Y-%m-%d %H:%M:%S.%3N propagate: no level: debug path: vette.log Issue 1: Mixed log formats Despite configuring all logging sections with datefmt: %Y-%m-%d %H:%M:%S.%3N, I still see multiple timestamp formats in mailman.log, for example: * [30/Jul/2026:12:00:03 +0000] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" * [2026-07-30 12:32:15 +0000] [36] [INFO] Shutting down: Master * Jul 30 12:32:14 2026 (1) Master watcher caught SIGTERM. Exiting This suggests that multiple logging systems may be writing to the same log file. Issue 2: Runner debug noise With logging level set to debug, mailman.log contains a large number of entries such as: * Jul 31 07:58:12 2026 (33) [PipelineRunner] starting oneloop * Jul 31 07:58:12 2026 (33) [PipelineRunner] ending oneloop: 0 * Jul 31 07:58:12 2026 (26) [ArchiveRunner] starting oneloop * Jul 31 07:58:12 2026 (26) [ArchiveRunner] ending oneloop: 0 * Jul 31 07:58:12 2026 (29) [IncomingRunner] starting oneloop * Jul 31 07:58:12 2026 (29) [IncomingRunner] ending oneloop: 0 * Jul 31 07:58:13 2026 (28) [CommandRunner] starting oneloop * Jul 31 07:58:13 2026 (36) [VirginRunner] starting oneloop * Jul 31 07:58:13 2026 (36) [VirginRunner] ending oneloop: 0 * Jul 31 07:58:13 2026 (28) [CommandRunner] ending oneloop: 0 * Jul 31 07:58:13 2026 (37) [DigestRunner] starting oneloop * Jul 31 07:58:13 2026 (37) [DigestRunner] ending oneloop: 0 * Jul 31 07:58:13 2026 (31) [NNTPRunner] starting oneloop * Jul 31 07:58:13 2026 (32) [OutgoingRunner] starting oneloop * Jul 31 07:58:13 2026 (31) [NNTPRunner] ending oneloop: 0 * Jul 31 07:58:13 2026 (32) [OutgoingRunner] ending oneloop: 0 Is there a recommended way to suppress these internal runner loop messages while retaining useful operational logging? Issue 3: HTTP request logging I intentionally keep [logging.http] at level: debug because I want to see which REST endpoints are called. Examples: * [2026-08-03 12:10:28 +0000] [51] [DEBUG] GET /3.1/lists/listname(a)example.com<mailto:/3.1/lists/listname@example.com> * [2026-08-03 12:15:29 +0000] [52] [DEBUG] GET /3.1/lists/listname(a)example.com<mailto:/3.1/lists/listname@example.com> * [2026-08-03 13:00:03 +0000] [53] [DEBUG] GET /3.1/lists My goal is to keep these request entries. Issue 4: Falcon tracebacks in http.log The same http.log also contains Falcon tracebacks. One example is: 2026-08-03 12:10:29 [FALCON] [ERROR] GET /3.1/lists/listname(a)example.com/config<mailto:/3.1/lists/listname@example.com/config> => Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/result.py", line 779, in _getter getter = self._metadata._getter AttributeError: 'NoneType' object has no attribute '_getter' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/falcon/app.py", line 361, in call responder(req, resp, **params) File "/usr/lib/python3.8/site-packages/mailman/rest/listconf.py", line 282, in on_get value = getter.get(self._mlist, attribute) File "/usr/lib/python3.8/site-packages/mailman/rest/listconf.py", line 52, in get return sorted(aliases.aliases) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 565, in aliases for alias in aliases File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/loading.py", line 100, in instances cursor.close() File "/usr/lib/python3.8/site-packages/sqlalchemy/util/langhelpers.py", line 68, in exit compat.raise_( File "/usr/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/loading.py", line 58, in instances *[ File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/loading.py", line 59, in query_entity.row_processor(query, context, cursor) File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 4422, in row_processor _instance = loading._instance_processor( File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/loading.py", line 421, in _instance_processor getter = result._getter(col, False) File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/result.py", line 781, in _getter return self._non_result(None, err) File "/usr/lib/python3.8/site-packages/sqlalchemy/engine/result.py", line 1236, in non_result util.raise( File "/usr/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically. Is it possible to: 1. Continue logging HTTP GET requests to http.log 2. Send Falcon tracebacks and REST API errors to a separate log file At the moment, both request logging and tracebacks appear in the same file. Issue 5: Worker timeout After the traceback above, I consistently see: * [2026-08-03 12:21:29 +0000] [34] [CRITICAL] WORKER TIMEOUT (pid:52) * [2026-08-03 12:21:30 +0000] [53] [INFO] Booting worker with pid: 53 This appears to indicate that the worker handling GET /3.1/lists/listname(a)example.com/config<mailto:/3.1/lists/listname@example.com/config> times out and is restarted. Additional observations error.log contains Mailman Core exceptions such as: (52) deque: subscribe_from_restored Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in next return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 341, in _step_get_moderator_approval raise StopIteration StopIteration However, the Falcon/REST traceback shown above does not appear in error.log. This suggests that: * error.log receives Mailman Core exceptions. * http.log receives REST API/Falcon exceptions. * The two do not appear to be linked. Questions 1. Is the mixed timestamp formatting expected in Mailman 3.3.4 Docker deployments? 2. Which component produces the starting oneloop / ending oneloop runner messages? 3. Can HTTP request logging and Falcon tracebacks be directed to separate log files? 4. Is ResourceClosedError when accessing GET /3.1/lists/listname(a)example.com/config<mailto:/3.1/lists/listname@example.com/config> a known Mailman 3.3.4 issue? 5. Is there a recommended logging configuration that preserves REST API access logging while reducing runner/debug noise? Thanks in advance. Best regards, Henrik

2 1

Advice on upgrading..
by Stephen Daniel Aug. 4, 2026

Aug. 4, 2026

Mailman 3 people -- I am planning an upgrade for my Mailman 3 system, and I have a couple of questions. I am currently running an old install of Mailman 3.3.5 on Debian Bullseye. Rather than trying to upgrade this now ancient VM, my plan is to create a new VM and perform a fresh install of Mailman 3.3.10 on Debian Trixie. I'd like advice on how to migrate mailing lists and archives from the old install to the new one. Is there a standard procedure? My current implementation uses the Python venv installation method. I'd prefer a more container-focused installation, but since I don't believe Mailman 3 has official container images yet, I plan to continue with the venv approach. Please let me know your thoughts. Thanks! -- Stephen Daniel

4 3