February 2025 - Mailman-users - lists.mailman3.org

Login confusion
by Markus Grandpré April 22, 2025

April 22, 2025

Dear list, We've encountered an issue with Postorius after migrating from Mailman 2.1. It appears that Postorius is treating email addresses with differing capitalization as distinct user accounts. For example, <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate identities. This is causing significant confusion. Users registered with one capitalization pattern are not seeing the list subscriptions and settings that were previously associated with their account (imported from Mailman v2.1) which used a different capitalization. Is there a known configuration option or method within Postorius (or Mailman 3 itself) to normalize or unify account identification, effectively treating email addresses as case-insensitive for account matching? We need a solution that ensures users see their correct list memberships regardless of the capitalization they use when logging in or that was used during the original Mailman 2.1 import. Thank you in advance Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 19

Upgrade docker-mailman to v0.5.2
by Christopher April 21, 2025

April 21, 2025

Hi Abhilash, I checkout the v0.5.2 for testing my upgrade from 0.4.6 and noticed, that the docker-image-version is still set to 0.4 in docker-compose.yaml. Is there any reason for it or should it be set to 0.5? I´m still using my good old mariadb. I did not find any upgrade-informations about breaking-changes. Do you have any experience with migrating from 0.4.6 to 0.5.2 on mariadb? Best regards Chrclaus

1 1

makemigrations --merge error after Debian upgrade
by Chupin Maxime April 16, 2025

April 16, 2025

Hi, I upgraded my debian version, and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: ``` CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). To fix them run 'python manage.py makemigrations --merge' ``` So I tried `mailman-web makemigrations --merge` that ended with ``` PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' ``` There is no such a file in the migration directory. Any idea ? Thanks in advance, All the best Maxime Chupin

7 28

Find a smtp server to send out emails
by Leon March 12, 2025

March 12, 2025

Hi, This problem is not caused by mailman, but I still want to give it a shot here. I'm hosting a mailing list on top of mailman3. Emails are supposed to be sent out by AWS ses. However, ses requires that sender address must be verified, which leads to a problem that emails sent by subscribers to mailing list cannot be sent to other subcirbers, since their addresses are not verified. And it is impossible to verified every subscriber. Are there smtp service providers allowing unverified email address to send out emails, or do I have other solutions? Thanks. -- Best wishes, Leon

4 3

Moderation of held emails vs. spam
by David Krantz March 11, 2025

March 11, 2025

Hi, I now run Mailman 3.3.1, installed from pip. Is there now any way to prevent Mailman from forwarding the contents of the held message when notifying moderators of held messages? In my case these messages often are spam messages and if the entire contents are forwarded it triggers spam handling in the recipient address(es) which over time risks classifying all moderation emails as spam or even classifying the list domain or server as a spam source. Even my own outgoing filter classifies it as spam, which I will fix. I currently run rspamd for spam filtering, graylisting and DKIM and ARC verification/signing. Someone on this recommended it, thank you for that as it removes the need for other milters. I guess that this would be a simple change to make as a kludge but a proper implementation as a setting would be a lot better. I'd like it as a global setting but that might be too coarse. Cheers // David

3 4

Issues with a DMARC record leading to message being shunted
by Ralf Hildebrandt March 4, 2025

March 4, 2025

Hi! Recently a mail was not being distributed via our MM3 instance; I searched the logs and found: Dec 22 04:54:27 2023 (24) ACCEPT: <1d431542-b386-467b-8bf2-305f19ee7eb4(a)somenet.org> Dec 22 04:54:28 2023 (28) Uncaught runner exception: list index out of range Dec 22 04:54:28 2023 (28) Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.10/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 125, in process authenticate(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/utilities/retry.py", line 44, in f_retry return f(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 93, in authenticate auth_result = authenticate_message( File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 395, in authenticate_message dmarc_result = check_dmarc(msg, spf_result, dkim_result, dnsfunc=dnsfunc, psddmarc=psddmarc) File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 343, in check_dmarc result, result_comment, from_domain, policy = dmarc_per_from(from_domain, spf_result, dkim_result, dnsfunc, psddmarc) File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 90, in dmarc_per_from record, orgdomain = receiver_record(from_domain) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 117, in receiver_record retval = lookup_receiver_record(hostSansDmarc, dnsfunc) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 92, in lookup_receiver_record tags = answer_to_dict(str(result)) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in answer_to_dict retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in <dictcomp> retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} IndexError: list index out of range Dec 22 04:54:28 2023 (28) SHUNTING: 1703220868.1418982+b27f5db154375fcd2c418d467172e4aad0d3d57a So the message has been shunted, due to this error. Something with DMARC and tags. So I checked the DMARC record for the sending domain somenet.org. It is "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;mailto:postmaster@somenet.org;ri=3600;fo=1;" which is syntactically incorrect. The extra ";mailto:postmaster@somenet.org" is wrong, I guess the tag "ruf=" is missing here! It should probably read "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;ruf=mailto:postmaster@somenet.org;ri=3600;fo=1;" So, should mm3 somehow "catch" this error somehow? According to the DMARC specs, an syntactically incorrect DMARC record should be ignored / handled as if none were present. -- Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 ralf.hildebrandt(a)charite.de https://www.charite.de

5 12

cannot import name 'parse_header' from 'django.http.multipartparser
by Stefan Bauer March 3, 2025

March 3, 2025

Dear Users, i recently tried to upgrade to latest MM3 and followed this[1] steps. However (venv) $ mailman-web migrate fails with: from rest_framework import mixins, views File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", line 15, in <module> from rest_framework.request import Request File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", line 17, in <module> from django.http.multipartparser import parse_header ImportError: cannot import name 'parse_header' from 'django.http.multipartparser' (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) (venv) mailman@edmmal03$ vi /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py Could this be a broken dependency? However I got no errors during (venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web Log here[2] Any help is greatly appreciated. Thank you. [1] https://docs.mailman3.org/en/latest/upgrade-3.2.html [2] https://nopaste.boris.sh/#XQAAAQCyQAAAAAAAAAAUHYinEVmYO1nmXgjfXeN/2+F2nR7ib8+aroH2BRQb6TN1QTkpiu4cw9JJL55OI9JmmIdaOopbd7jPBVeOhc446nWh65PbRcOQu27P9o2ybMeUQoVgw22CT3QYBQ9uklS8h5JrAjxIM+6X+gFBWn5E2kwmYszTAaLWVqvhMfTLmTLM4XyxfZrEYdaSC3/CZJgSRXYED2aMIvgiCpPeUzhA4HZM3ACJKj8yEBOIY+CNlMD7vfwDn1jsActZ24WmwZc2cj0Bad8MHRVcXZ67wlbgFFhd15M+TkFv+/QayJcZPOL+iJmbzXzeThF4rqhXjblJxiwWW6i+0c/fDvY5UurL3imJkrwEXA2ydX/fWuDCIsqn9m0yrvwPBIolTuRlqwMJPmGsv2i9gg3KPAKrJ5jT2OFEhrHoE2Rq/xPuTnVAD/AhQ1E9+AMyPRGaQxOsB9dTFb3Aw0dYTA81XKygjBqilmxKqSPV+60b6/xFQUAsbi3FAgDy32GIUfUrdcqkWeBez4Olcj6/caEBGFA/zhaWR2YOId6BJO0mWbDLbCdGW3QSnBbzTGIAFhKARImsdOFyly+U44Ho2uiIlZm+86AgthR87XnT+NzZ2bmtouRQJksRvRzeSaJ70DYgoxGtqZjCWIoB1dv4oLyPMNg81fqXiY+q8B4GCPWQsrQXpqfibOJaDYAUZ7MxJgxM0XYISS5lEHRtigzK4kGKIRgJMlsXhPlVPn5RcXXCQRR62YBjrPEfU81KY5tmcM2MpgiD3fvMcTgygS6drd0t14r7xJPwefGAFabI7gBJEgR5VMyr2TTFpOwWLuH6MGKdeeDiSbPVoBVwCjlMHgikjLh9x5g5XpptP3s4Zf98/B9viH4H1WmuxPvxyMGXm86PNo/o+vRInF2lrOc89XD9yvXQYoCXcHkYta4xudsdK33sjnuDub2z3Poe5YHgSYziH5d/OLaF4KsT5LQuEl0KBs3loSPpVBD/PAOnVErZnR8iYcuNhZaVFIFrP5swIt1yc/Y7FA9+Yd2w8FKNK4eB4r9BYCfNtspShVsz53rGA0HcrpvA4XLwRWPSZtIB2zH1JGftKNgM8j9OKbuvhLKTk+ixa08YnBT5dtlUN9pgaGbGVz2VDN2cQCRRIIsvjYM1vKl9xmFrWE/DKf/JgbWHr/QlraAuiXwNxE5ZqCrfXcW4RJWYHp7I8CNKDJa+dUt4QBE3hvJUghenkSBK09Pr9h7/de5gzwsVROT/yVarSBpBk9yspO96VTSF1+8+pJuolnNSjsfzTM/VxjHXregtnWx6D1HL9MMSfIxVn0o5qRuNEqeXOXqmCSyM1AiUOHPxsvag3RDI3od12CPGLtjHlIaY59zs4dRMJJz12QBeueGr52aTi8bBB13bq83sOrLiyXI+gRAjV+mPMnZnZqBXDEkIBndx3XvNosT0uwqLrL2jrCbnKkweLuwv+SyEjt/3WRdA6W18JBvHAMMzKmnLJPBIDJzEX5HglG2SSFWwxp9E/PayFx4F4HBHZLtBjs37kGXlGaXaiQv91DtAwdOtErpUImdKAMXXtd9/LlDEAMGB0PMuA0Ci7hUsMQ6VqRKsqfDE2WhzQwhP1Plwkg/cImJIMOirFo5n8TSGRt2s5QcTHiWI+ZLHQZxgkgQghbS5YoVJaVMDtnfvuamI4Z9IyQn4nSzlldj6m3tQhMOnB3rQNUW+51GAENoiOPGWI4MqM9abwb6sYmU/CxlFnaOBBrK0qLvQ3oxud0cvaHDzRYyErZSU9h7ZSDmWk7zRav8n9XveETZXYpko0O6h5GStOYuPGN+MgmIZ1rGs09oMmDuLqlH0wZppPuO6ejl0S8xsNXSmVExM0ze+6hHFYr4vaq1n6dufJQrevc7QTClm3mTQ0F8p991fKyP1FVfGsbq8QR1xGstlPpJuer+9wnp4l19n3FbO0IPe+9n9oJN9obkLN2GANLSr3OyWi7jIItcAZUY4f9q8TdqCBfktHdnpkASjtN38+wDVTu8dnmUV3GuvQYMiMr9WiCrIx0gzC+ichqmeBvuhbwL5dTp2nAX7NwxfhWsaZWM7JjzW641F2S7e1V7LAb4xzA3ah6W8TOlpD5Yb6tyQmzwng5lhzzD5P2F0VJIzZSwMa+42L/e4LatUtw8v4ZulOLTbQETNYvPaB7uZ+E1wI5/wqfLVSRnABVQmFnOmu30p7hYwCNg/gPd3bbIh9mVsiibuI1/1Zxz2vYFnNExFxRkJQTAZ8JndagzTPHTqribSm/pqmx+RZHN7ADP6zFvPCK0pjqM7iIkdtvsdcy6xieMlRKnw9BtaJM7F8LMiZf+eKkKhMptc8zXmemRD7nIMUqL0dJbf3rHw8s/Ns6I5KAQZYV9aB4MIlGvNOUMasIHubHDnt151X3EV9maruTB/t92+wUCHJhmTJHjBfJMm/oaximDoK14G1o1TtsvmKbsQPuyGRuEcQ0mhz2AeUpc7bUxAlwSC4ttfcoii9l4N4urBv7dHSj4h0Nz1c9tOtqXHm+ikoZVsq3GgXmFUkaCL8x/vWf3hTalCmgIxYx0CAlNaUER1wkPyDgo7ZDBj07ea0DnabrQPmgRWzz2U9+725Ta0w+Q+VFb4VnwrSIpgF/XWqcaepf98GI431sQ3AbDQJis57wdvc5eFWqb5oUTpZ3ZLjOHYv59BsYw46IUJTDWxIIzguPxbx3vd7KdEk2S0yTwXdmEl6FRlb1ZXAcxA34339Gj05mY0pzwtaGIOcjhQVFAspP3Xgpw57u4GFRHnJN23QtAqrDXtmiChI+gXxfzgXVaICnA18S0Oww0rbMdX64/0U3aX00wurFtaVh65H/v9ogIsVTui6wAF9CWtSj/9nkplqeczZMPvkINkz73BahhRgsGaJoPvN5LVfxB3DbR0m6kCNGIANFpnm1NYdVygcVfIQBSFaSxhTg6OTPtvbC7wDQjq+8lHMC6N7dpAmtmOTMFW7REPEbVPXAYFq+0vmOUh0om+AiK1U1s7b63Q/wDVxprwyjqjPNcbhXYFir7v4S7mWl59QW4JWRS70wJrwCVs9wuUvK7TbRSV2Q6cc5GoDGQWwHPb/7q8KmaExg+mRr7J+a2hHMq3mTD0sc4O/YowvhXS8/ug1YXHJlCkLFHDG0bbx/Z6sjoMUC13/KhkRMkgIruuzhKcDa6Au5fdqaA8ArZsAixauOZ4Ze1U9GQVJ4gOrvsWryyCGDzbAJqFETJ00jFf2z3UTod2eywfZfHWP09BPgrruX1HIAPHdgbrkbWdHIJM7JpoH0ZTz5TjAF0kjIBKkwxjO6SjP8Q7AS0+yptuLaqQuXNjyxyYX53sh05wb61adTTSJCsAxYWca4f4+zflxIDqpR9q2kIiVfy96RIJBUQPc7QR7QaFGVl6xb2D06lZmc5Z6OxxuOaodG9c1pNY1dqpr9tYkR0mxGpKiTwMtjtnyxrpBI9l8fWQwfPkYtqZabuanwaJMbcgUQvI9xXmtS6WqHBX5ku0gohxDNa3yR/AYhoPxC4bwZe8JGfYouKefKr5TBnE/CG3PBooM6jFo//JgwzNgVjypUSyiWlbzf0tCuU=

2 2

Postorius extremely slow on some of the mailinglists
by Eric Broens March 1, 2025

March 1, 2025

Hi, Postorius became extremely slow recently on some of our mailinglists, but not on all of them. Postorius even times out when opening some of them (https://<hostname>/postorius/lists/<mailing_list>.<domain>/) and shows the message "Mailman REST API not available. Please start Mailman core." This only happens when I am logged in (as administrator), but not when I am not logged in. It seems to be independent on the number of subscribers on the particular mailing list. Below you'll find an extract from the logs for a case where it timed out, and for a case where the page showed up after a long time. Mainly "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" takes a long time. There is nothing unusual going on regarding database queries, and mails are delivered normally. Any idea why this happens and how it can be solved? [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 378 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2283 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3107 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [2025-02-05 19:05:14 +0100] [1612] [CRITICAL] WORKER TIMEOUT (pid:1653) [2025-02-05 19:05:14 +0100] [1653] [INFO] Worker exiting (pid: 1653) [2025-02-05 19:05:15 +0100] [64429] [INFO] Booting worker with pid: 64429 [07/Feb/2025:13:42:14 +0100] "POST /3.1/lists/find HTTP/1.1" 200 18226 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 414 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2337 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3232 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>.<domain>/member/<my.email>%40<mydomain> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Thanks, Eric

2 3

Postfix + MariaDB + Mailman 3 Core
by Peter Knowles Feb. 28, 2025

Feb. 28, 2025

== ENVIRONMENT == OS: Debian 12 Mailman Core: 3.11.2 Install Mode: venv == QUESTION == I'd like to do a more advanced setup with regards to my MTA setup. *** I have mastered the art of setting up Mailman 3 Core to use MariaDB vs PostgreSQL *** What I'm after is the ability to make use of MariaDB with: transport_maps local_recipient_maps relay_domains In particular, with regards to Mailman 3 Core generated content. So instead of referencing a postmap generated file which MM3 presently generates, but have MM3 add and/or remove those records to/from a MariaDB table. Appreciate any insights on this task.

3 8

Saving settings of non-members does not work
by Torge Riedel Feb. 28, 2025

Feb. 28, 2025

Dears, I just experienced, that saving the settings of a list's non-member does not work with Postorius 1.3.13 I find this in mailman.log when saving the settings of a list's member, you see the PATCH there: [28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=1.vorsitz%40xxxxxxxxxxxxx.de HTTP/1.1" 200 633 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "GET /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "PATCH /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=1.vorsitz%40xxxxxxxxxxxxx.de HTTP/1.1" 200 633 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:55:24 +0100] "GET /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 200 184 "-" "GNU Mailman REST client v3.3.5" When saving the settings of a list's non-member I find this in mailman.log, but the PATCH is missing: [28/Feb/2025:12:56:52 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:52 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=admin%40xxxxxxxxxxxxx.de HTTP/1.1" 200 1292 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:52 +0100] "GET /3.1/members/dc13c0500496485abd7b95001f605aa9/preferences HTTP/1.1" 200 212 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:52 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:53 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=admin%40xxxxxxxxxxxxx.de HTTP/1.1" 200 1292 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:53 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:53 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [28/Feb/2025:12:56:53 +0100] "GET /3.1/members/dc13c0500496485abd7b95001f605aa9/preferences HTTP/1.1" 200 212 "-" "GNU Mailman REST client v3.3.5" Where can I search deeper to find the cause of the issue? Kind regards Torge

2 1

Postorius custom web forms?
by Johannes Rohr Feb. 28, 2025

Feb. 28, 2025

Dear all, I am trying to understand how to replace a web template used by postorius by a custom version. I need to replace /accounts/signup by a version with a captcha (using django-simple-captcha) because my instance is being overrun by spambots. Can anyone point me to the correct instructions? I've tried to get instructions for chatgpt and co, but that's totally hopeless. Most of what they say is made up and doesn't work.. Cheers, thanks so much in advance, Johannes

3 2

Error: ConnectionRefusedError at /accounts/login/
by Kim Sunggun Feb. 28, 2025

Feb. 28, 2025

Hello, When I sign in new id, it has an issue. Could you please guide me to fix it? error: ConnectionRefusedError at /accounts/login/ [Errno 111] Connection refused Request Method: POST Request URL: https://lists.klnpa.org/accounts/login/ Django Version: 4.2.19 Exception Type: ConnectionRefusedError Exception Value: [Errno 111] Connection refused Exception Location: /usr/lib64/python3.9/socket.py, line 844, in create_connection Raised during: allauth.account.views.LoginView Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.9.21 Python Path: ['.', '', '/etc/mailman3', '/usr/lib64/python39.zip', '/usr/lib64/python3.9', '/usr/lib64/python3.9/lib-dynload', '/opt/mailman/venv/lib64/python3.9/site-packages', '/opt/mailman/venv/lib/python3.9/site-packages']

3 7

Easy way to integrate captcha/reduce subscription spam?
by Johannes Rohr Feb. 25, 2025

Feb. 25, 2025

Dear all, my mailman3 instance is flooded with subscription spam, yet I haven't found any canonical method of integrating a captcha in to the subscription form. Is there really none at all? Perplexity.ai says I should install the python package django-simple-captcha but is unclear about the steps needed to actually make the captcha appear. Are there other ways? Is there any method that is robust and survives upgrades? Also, would there be a way of batch-deleting all those thousands of spam registrations that have accumulated (what they have in common is that their email is unconfirmed) Thanks in advance for any suggestion! Johannes

2 3

Hi, Does the mailman community have any tips on accepting cookies?
by TomNewChao Feb. 25, 2025

Feb. 25, 2025

Hi, I want add the tips about accepting cookies in mailman-web that include the postorius(https://gitlab.com/mailman/postorius) and kyperkitty (https://gitlab.com/mailman/hyperkitty) eg: Can the mailing list community support tips for accepting cookies? Thank you very much ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Replaced multipart/alternative part with first alternative.

1 0

How To Install Mailman 3 on Debian 10 (Complete Guide)
by Brian Carpenter Feb. 25, 2025

Feb. 25, 2025

I have finished my how-to install Mailman 3 on Debian 10 completed to the point where you can use it to get a fully functional Mailman 3 environment up and running. This is a comprehensive guide that walks you through installing EVERYTHING (currently!) that Mailman 3 needs to run. It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have not added the update directions yet but will very soon. I also plan on adding a section on setting up DKIM and Xapian with Mailman 3. I hope this helps those who wish to get a Mailman 3 server up and running quickly and brings a sense of sanity to the confusion regarding the various documentation out there concerning the installation of Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 at some point. Without further ado: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I am sure the above guide can use improvements. Feel free to contact me off-list to point out mistakes/improvements, etc. -- Brian Carpenter Harmonylists.com Emwd.com

13 38

Speed up importing mailman2 lists
by t.maintz＠fz-juelich.de Feb. 24, 2025

Feb. 24, 2025

We are currently planning to migrate from mailman2 to mailman3 as a container, have around 1500 lists and would like to complete the migration ideally in a few hours. We would like to switch off mailman2 to have a defined state of the lists and import them to mailman3. The import of all lists via script takes about 3 days. Parallelizing the imports does not work due to lockings in the database. However, we cannot accept a downtime of 3 days. Does anyone have tips on how we can speed up the procedure or are there best practices for larger environments? Thanks and best regards, Thomas

4 8

clean up spambot generated accounts
by Johannes Rohr Feb. 23, 2025

Feb. 23, 2025

Dear all, I'm trying to find a way to clean up hundreds of spambot generated accounts on my system. I was pointed to this script that should be capable of doing the task: https://www.msapiro.net/scripts/clean_users.py However, it seems outdated. First, the path to the interpreter is not what I find on my mailman3 installation. It says: #! /opt/mailman/mm/venv/bin/python However, the python command is located in /opt/mailman/venv/bin/python instead, no "mm" After fixing this, the script still throws an error: (venv) mailman@ida:~$ clean_users.py Traceback (most recent call last): File "/usr/local/bin/clean_users.py", line 55, in <module> django.setup() File "/opt/mailman/venv/lib/python3.10/site-packages/django/__init__.py", line 19, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 102, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 89, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", line 217, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' Can somebody explain to me, why this module is not found and what I can do to fix it, if anything? Thanks a lot in advance! Johannes

2 2

Enforcing SSO and subscription options
by dlb-ml＠anl.gov Feb. 21, 2025

Feb. 21, 2025

Contrary to the messages I found in the archive, rather trying to delete or remove the social login portion of the sign in page, I'm looking to see if there's any way to isolate the third-party login section and prevent local account sign in and sign up. This way, we can ensure that the people within our organization are using a stronger auth method that prioritizes MFA, rather than just username/password. To do this, our plan is to block signups using "ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter'" and to remove the portions of the login template such that the username/password/forgot password fields are removed, leaving just the button to our SSO instance. I'm anticipating that this should be sufficient to block username/password sign ins, and is resistant to page manipulation due to CSRF tokens, but I wanted to ask to see if there was a better way, like an official configuration (which I have not found yet). I did see that there is the SOCALACCOUNT_ONLY option, as provided by allauth (https://docs.allauth.org/en/latest/socialaccount/configuration.html) but that broke any attempt to display the sign in page, and I'm assuming is not supported with the current version of MM3. Is my plan to modify the templates viable? Additionally, because external users would not have access to their own dashboards within the web UI, and since we are planning on disabling anonymous subscriptions with "SHOW_ANONYMOUS_SUBSCRIBE_FORM=False", the only two viable ways to subscribe to a list for them would be: 1) Send a request directly to the list owner or a superadmin to subscribe/unsubscribe the address 2) Allow email commands to subcribe/unsubscribe users (i.e. $LISTNAME-join@$DOMAIN) Given the discussions on disabling the anonymous subscription form, are the email commands a less spam-susceptible solution or are they just as vulnerable as the form? Thanks

2 3

Hyperkitty performance problem
by Tobias Diekershoff Feb. 20, 2025

Feb. 20, 2025

Hey all, last week we caught some AI bots causing high LOAD on our mailman3 servers archive, that we blocked with nginx rules. I'm not sure if it is related to this incident, but we noticed this when analyzing the log files at the time. In the mailman.log hyperkitty is listed 10k times and more to archive a single mail over the time of 2h, seemingly all with the same process ID > (1186) HyperKitty archived message [...] The mailman3-web.log has matching log entries that the mail was archived > hyperkitty.views.mailman Archived message every 0.5 seconds. In the web interface to the archive, the mail is only listed once though. My suspicion is, that these archiving processes are now overloading the system, preventing a timely catching up work of the queued messages. I could not find anything in the Mailman3 nor Hyperkitty documentation to better distribute the system resources to the Mailman runner or prevent Hyperkitty to restart archiving a mail over and over again. Any hint about where to look for the reason of this is highly appreciated. Best, Tobias -- Tobias Diekershoff >>> System Hacker Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support OpenPGP-Key ID ... 0x25FE376FF17694A1 Fingerprint ...... 23EE F484 FDF8 291C BA09 A406 25FE 376F F176 94A1

6 16

Mailman Core: REST API: Member Subscription Invitation
by Peter Knowles Feb. 20, 2025

Feb. 20, 2025

Product: Mailman Core Version: 3.3.10 When I post an "invite" to the REST API: http://localhost:8001/3.1/members Params: list_id = list.domain.tld subscriber = some(a)email.address display_name = Some Name invitation = true Should Mailman Core be attempting to send an "invitation" email to the "subscriber" address, or is this the job of the "client" calling the API? I understand the API does return "token", and "token_owner" on success, which I assume the "token" would be used for a subsequent "verification" process. I'm developing my own "frontend" for "subscribers", "moderators", "list admins", and "system admins" respectively. Sort of working through understanding what Core does and does not do itself.

2 3

REST API: potential bug
by Peter Knowles Feb. 16, 2025

Feb. 16, 2025

I'm starting to develop against the REST API and found what might be a bug in the validation process. Sending a POST request with an "empty" payload returns 201 (created): http://localhost:8001/3.1/domains Since "mail_host" should be required at minimum to create a domain, this seems like there may be a bug with the REST API. The workaround for the moment is to add validation at the application layer, but the API should really be returning a 4xx code and error respectively.

2 5

install v3.3.11
by Jose Bernal Feb. 14, 2025

Feb. 14, 2025

I'd like to install Mailman v3.3.11. Are there instructions for installing from pip? If not, is there an alternate way to install this latest version? When executing: pip install mailman==3.3.11 I get: ERROR: No matching distribution found for mailman==3.3.11 Thank you,

2 2

Re: Moderation action "None" is misleading
by Stephen J. Turnbull Feb. 13, 2025

Feb. 13, 2025

Adding mailman-users(a)mailman3.org. Technical suggestions should go to distro channels or to Mailman's issue tracker: https://gitlab.com/mailman/mailman/-/issues/1176. Further discussion of technical details is best done there. Thomas Krichel writes: > Stephen J. Turnbull writes > > Debian has traditionally been quite slow to update Mailman, > > And now it has the addition issue that Debian testing python > standard it 3.13, so the nntplib is no longer supported. > Thus the current Mailman debian testing appears broken. That's Debian's problem, as we currently don't support Python 3.13, although of course we intend to. This is the only issue that came up in a quick search of Mailman's issue tracker for Python 3.13 (but I did not check the other subprojects such as Postorius). I conclude that not a lot of work has been done on supporting Python 3.13 (rather than the optimistic "there's nothing to be done"). From Mailman's point of view, users have two excellent options for the forseeable future: (1) don't gateway list <-> newsgroups (2) install Mailman into a Python 3.9--3.12 virtual environment. I'm sympathetic to the needs of the Debian developers, and at this point for 99% of software it's perfectly reasonable to aim to use 3.13 in the next Debian release. Unfortunately for Mailman users on Debian hosts that's not high on our list of priorities since we recommend a virtual environment installation in any case. At present there seem to be three ways forward for Debian packaging: 1. Remove NNTP support. (In honor of larsi, I'd rather not.) 2. Add nntplib.py from the Python 3.12 nntplib, as a stopgap until option 3 can be implemented. I can't speak for other developers but we might be willing to add it as a contrib module, especially if that might make life easier for distro packagers. It's suboptimal though since that absolutely has to be considered techical debt that will need to be paid someday. 3. Port Mailman to pynntp (that may need to be Debian packaged, too), which has seen a revival of activity and two feature releases since 2023. My inclination as a Mailman core developer is not to participate actively in development of NNTP support in Mailman for Python 3.13+ unless we see an outpouring of support from site admins. However, I would be happy to answer questions and work on Mailman-side issues that are blocking or inconvenient for the NNTP work. Mark and Abhilash would undoubtedly contribute as well, on a time-available basis. > I certainly would love to build an alternative Mailman Debian > package that would be more up-to-date, but I don't want > to do it on my own. Debian and Python are compatible free software; just take the existing package metadata, in a recent Mailman (presumably the most recent release) drop in the most recent nntplib, and change all the import statements. mailman/src/mailman/mta/nntplib.py seems like a plausible location. IWBNI you could keep all Mailmanisms out of nntplib (because of the GPL) so any bugfixes or improvements could be available to the Python community. I think you could probably be up and running VERY quickly with that approach. Of course it wouldn't just slot into the next iteration of Debian because they have stringent QA (or maybe that could go into unstable?). I'm pretty sure it would be useful right away to a whole lot of people who are willing to use a PPA. Regards, Steve

6 13

Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated
by Andreas Vetter Feb. 11, 2025

Feb. 11, 2025

Hello, I have a venv installation of: mailman postorius django-mailman3 hyperkitty mailman-web I just did a pip install -U --upgrade-strategy eager When running mailman-web runjobs -l I get the following Warning: System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} I guess this is from allauth (version django-allauth-65.4.1). Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in /etc/mailman3/settings.py is not enough. One has to edit venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py -- Mit freundlichen Gruessen, Andreas Vetter

2 5

Pck files stuck in out queue
by Lieuallen, Thomas Otis Feb. 10, 2025

Feb. 10, 2025

Running Mailman 3.3.10 I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. The out runner is consuming copious CPU time. I was hoping this would help: [logging.runner] level: DEBUG But, if so, I don’t see the logs anywhere. I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. Ideas on where/how to track down the status of these files and fix whatever’s broken? Thank you Tom Lieuallen Oregon State University

3 14

How to limit numbers of outgoing emails per connection
by Alain D D Williams Feb. 10, 2025

Feb. 10, 2025

Exim tells me "no immediate delivery: more than 30 messages received in one connection" The emails then sit in the exim queue until a queue runner kicks in - which happens once every 30 minutes. The result is considerable delays which makes list email conversations bouncy. Question: how do I tell MM3 to send no more than 30 emails in one connection to exim (via SMTP to localhost port 25) ? If that is not possible, how do I find the number that MM3 batches outgoing emails so that I can configure exim to match (as I did with MM2) ? I see documentation pages like the following. They are useless to me, incomprehensible without a lot of learning. I program in several languages but only a little Python. What I am looking for is a setting in a config file. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do… -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

3 2

Filter question
by Chris Feb. 9, 2025

Feb. 9, 2025

List has "filter content" set. Filter Mime-Type [] Filter Extensions exe bat cmd com pif scr vbs cpl Accept Mime Media Types multipart message/rfc822 text/plain text/html application/pdf application/nappdf application/x-pdf application/rtf application/vnd.oasis.opendocument.spreadsheet application/vnd.openxmlformats-officedocument.spreadsheetml.sheet application/vnd.ms-excel application/vnd.oasis.opendocument.text application/vnd.openxmlformats-officedocument.wordprocessingml.document application/msword Allow Extensions .zip .7z Reduce Alternative No Convert to Plain-Text No Now I'm sending an Message from outlook (html) with Inline Images. Content Filter off: Works fine Conent Filter On,: All except the image ist fine. The image gets lost and only a placeholder is shown <img data-cid="image001.png(a)01D65210.566F56E0" height="51" id="Grafik_x0020_1" src="../../attachment/view/tmai1738975737149948386/aW1hZ2UwMDEucG5nQDAxRDY1MjEwLjU2NkY1NkUw;jsessionid=03FDBB0F16AFB10F7439822AB2C59450-n4.bap20a" style="width: 3.3437in;height: 0.5312in;" width="321"> Even if MimeTypes filter is [] signature (p7s) gets filtered. Any hint? TIA Chris

2 4

User with abo to list can not set to another moderation flag
by Chris Feb. 8, 2025

Feb. 8, 2025

Hi again, I've one weird problem. I've some lists and a user which is a moderator on both lists. Steps to reproduce Postorius -> Users -> search for the user to change -> manage Both Lists are shown Moderarion Flag on a newer List was changed from standard to accept -> On the older list I've tried from Standard to Accept -> click on the button to accept changes result in reverting to "standard" (the setting which I want to change). Any hints on that? (can't find any difference between those lists except name und descriptions. )

2 3

How to add new Domain?
by c.benner＠apd-it.eu Feb. 7, 2025

Feb. 7, 2025

Hello, i'm really new to mailman3 and I've been using mm2.1 couple of years. It's really hardto understand documentation. But I'll do one in german language next time. I've got it installed ob Debian12 and it's working now. It takes a little more time to understand all settings and also the difference between postorius and django and what is when used for. But what I do not understand 'til now is how to add a new domain. My running config has one domain (e.g.) testdomain1.org and everything is working fine. The Domain has a virtualhost which listens on *:443 (with LE cert) Postfix works like a charm. The interface of the machine is bound to one IP Address public but for example here written as: 192.168.200.15 Id like to add a new Domain. My first step would be to add another IP Address to the interface: (e.g.) 192.168.200.16 Then I'll change the virtual host settings in apache conf from first domain which is actually listeing to *:443 to 192.168.200.15:443 And add a second site with 192.168.200.16:443 So the "physical" part is done Is that right 'til now? After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. On that page I'll add "websites" and add testdomain2.net Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! But it's alos possible that I'm not finding it and it's somewhere out there. Thanks in advance.

3 5

Error while mass operation, no progress display while mass operation is running
by Markus Grandpré Feb. 7, 2025

Feb. 7, 2025

Dear List, At the University of Konstanz we have mailing list administrators who frequently add and remove up to 10000 (and sometimes more) list members. I have therefore tested the “Mass subscription” and “Mass removal” operations and found that both the “Remove ALL members” operation and the “Mass subscription” operation report an internal server error on the website, but continue to run in the background until all new members have been successfully added or deleted. Unfortunately, I have not found any error message in the log files. I also tested that mass operations “Remove listed users” and “Remove Selected” ran successfully and without any errors. Regardless of whether a mass operation process runs without errors or continues to run despite an error, I find it hard that Postorius does not display the progress of such a mass operation in order to monitor the process, as mass operations with more than 1000 members are very time-consuming. Perhaps this could be changed in a future version of Postorius? Best Markus -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

3 2

Which folder should I share between pods with kubernetees persistentVolumeClaim ?
by antoine.depoisier＠ikmail.com Feb. 7, 2025

Feb. 7, 2025

I use mailman with kubernetees, and I have four pods. I currently use persistentVolumeClaim for two folders in the mailman configuration "cache" and "messages". I share these folders, as mailman needs to be consistent for these two folders, but I'm wondering if I should share other folders as well, like locks and such. There are all the folders in mailman archives cache data etc lists locks logs master.pid messages queue templates I ask this question because I often have a problem when creating a mailing list. I think I have a problem with the locks, but I'm not sure if the problem is due to the fact that the locks folder is not shared. If you want more details, here's the trace I sometimes get, when someone tries to create a mailing list: File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3.12/site-packages/mailman/rest/lists.py", line 322, in on_post mlist = create_list(**validator(request)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 102, in create_list call_name(config.mta.incoming).create(mlist) File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 96, in create self.regenerate() File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 106, in regenerate with Lock(lock_file): ^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 467, in __exit__ self.unlock() File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 417, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked When I check the lock folder, I have these two files, and I'm wondering if I should delete these two files : -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck|mailman-core-deployment-5f59557b66-bkkf4|16|4268829230172994873 Do you have any answer for me ?

3 4

Configuring ARC with multiple domains in Mailman3
by Lance A. Brown Feb. 6, 2025

Feb. 6, 2025

I'm working on setting up MailMan 3 on an Ubuntu 24.04 LTS server. I've got everything running and working with docker-mailman. Now I'm looking at configuring ARC and am a bit lost. How is ARC configured in a mailman3 with multiple domains? Do I set it up to use the hostname of the server Mailman is running on? Thanks for any assistance, --[Lance]

2 4

One-click unsubscribe?
by Jered Floyd Feb. 5, 2025

Feb. 5, 2025

I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. In particular, there is an issue with the fact that Google ignores dots in email addresses. So I have many (MANY!) subscribers who try to use the List-Unsubscribe header target, but because they are subscribed as "idiotsubscriber(a)gmail.com" rather than "idiot.subscriber(a)gmail.com" (which they have since changed their sender to) they get a reject that they are not subscribed. These people are also far too unobservant to read the footer of every message that reads "You are subscribed as idiotsubscriber(a)gmail.com". Is there any way to provide personalized List-Unsubscribe header links, or have Mailman ignore dots in gmail.com addresses... or... anything? I'm finding reported spam percentages in the Google Postmaster Dashboard exceeding 0.1%, which causes massive delivery blocking to GMail-based subscribers. While I would gladly ban everyone who uses gmail, that sadly accounts for about half of the Internet today and would be incredibly unproductive. Thanks, --Jered

3 3

Moderation action "None" is misleading
by Markus Grandpré Feb. 5, 2025

Feb. 5, 2025

Dear List, I find the use of the term 'None' (or 'Kein' in the German translation; see attachments) in the 'Moderation action' column of the member list misleading, as the term suggests that no moderation action is applied to the respective member. However, this is not necessarily the case. If you check a member’s "Administration options / Moderation" setting, a moderation action, such as "Moderation" or "List default", may be in effect. I suggest that the 'Moderation action' column should display the currently set value of the 'Administration options / Moderation' setting for each member. Since some of our mailing lists frequently add and remove thousands of members, manually adjusting this setting for each member would not be practical. Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: mm3_memberlist_de.png Content-Type: image/png Name: mm3_memberlist_en.png

3 4

Mailman shutting down Hyperkitty: Request too large
by Arte Chambers Feb. 2, 2025

Feb. 2, 2025

Hello I need help troubleshooting a problem with MM. The service is stopping and throwing this error in the mailman log "Exception in the HyperKitty archiver: 413 Request Entity Too Large" I'm not sure what my next steps should be to troubleshoot this issue. System CTL has this message and i'm not sure if it's relevant to the issue. ``` >sudo systemctl status mailman3.service systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: No such file or directory ``` The MM Service will run for a while then shuts down. /mailman.log ``` Jan 30 05:22:20 2025 (1547) HyperKitty failure on https://list.louisvillecommunitygrocery.com/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> (413) Jan 30 05:22:20 2025 (1547) Could not archive the message with id < CAPesOD3EWaFzfVZAbUzFm3Vk3Xnqcf9KodVic6agaT27Kmhy0w(a)mail.gmail.com> Jan 30 05:22:20 2025 (1547) archiving failed, re-queuing (mailing-list lcg-board-private.list.louisvillecommunitygrocery.com, message < CAPesOD3EWaFzfVZAbUzFm3Vk3Xnqcf9KodVic6agaT27Kmhy0w(a)mail.gmail.com>) Jan 30 05:22:20 2025 (1547) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> Jan 30 05:22:20 2025 (1547) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> Jan 30 05:22:21 2025 (1547) HyperKitty archived message <CAPesOD25frujqYsAXU3kk8MUOY=h3ZV4cgzUXSi9L0c3K2W0NQ(a)mail.gmail.com> to https://list.louisvillecommunitygrocery.com/archives/list/testing@list.loui… [30/Jan/2025:05:22:43 +0000] "GET /3.1/users/lcgcoop(a)gmail.com HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "GET /3.1/users/a6af988d603c49c9ac61a3a41562d132/addresses HTTP/1.1" 200 927 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "POST /3.1/members/find HTTP/1.1" 200 3407 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "POST /3.1/members/find HTTP/1.1" 200 4705 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "GET /3.1/addresses/lcgcoop(a)gmail.com HTTP/1.1" 200 401 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "GET /3.1/lists/ testing(a)list.louisvillecommunitygrocery.com HTTP/1.1" 200 482 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:43 +0000] "GET /3.1/lists/ testing.list.louisvillecommunitygrocery.com/roster/owner HTTP/1.1" 200 763 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:22:44 +0000] "GET /3.1/addresses/lcgcoop(a)gmail.com HTTP/1.1" 200 401 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:23:53 +0000] "GET /3.1/lists/ testing.list.louisvillecommunitygrocery.com HTTP/1.1" 200 482 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:23:53 +0000] "GET /3.1/lists/ testing.list.louisvillecommunitygrocery.com HTTP/1.1" 200 482 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:23:53 +0000] "GET /3.1/lists/ testing@list.louisvillecommunitygrocery.com/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:23:53 +0000] "GET /3.1/lists/ testing(a)list.louisvillecommunitygrocery.com/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5" [30/Jan/2025:05:24:15 +0000] "GET /3.1/lists/ testing(a)list.louisvillecommunitygrocery.com HTTP/1.1" 200 482 "-" "GNU Mailman REST client v3.3.5" Jan 30 05:42:54 2025 (1550) ACCEPT: <008401db72ce$cb6d50d0$6247f270$@ iglou.com> Jan 30 05:42:55 2025 (1547) HyperKitty failure on https://list.louisvillecommunitygrocery.com/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> (413) Jan 30 05:42:55 2025 (1547) Could not archive the message with id < CAPesOD3EWaFzfVZAbUzFm3Vk3Xnqcf9KodVic6agaT27Kmhy0w(a)mail.gmail.com> Jan 30 05:42:55 2025 (1547) archiving failed, re-queuing (mailing-list lcg-board-private.list.louisvillecommunitygrocery.com, message < CAPesOD3EWaFzfVZAbUzFm3Vk3Xnqcf9KodVic6agaT27Kmhy0w(a)mail.gmail.com>) Jan 30 05:42:55 2025 (1547) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> Jan 30 05:42:55 2025 (1547) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.24.0 (Ubuntu)</center> </body> </html> Jan 30 05:42:57 2025 (1547) HyperKitty archived message <008401db72ce$cb6d50d0$6247f270$(a)iglou.com> to https://list.louisvillecommunitygrocery.com/archives/list/lcg-board-private… [2025-01-30 05:46:02 +0000] [1554] [ERROR] Worker (pid:1586) was sent SIGKILL! Perhaps out of memory? [2025-01-30 05:46:02 +0000] [2227] [INFO] Booting worker with pid: 2227 Jan 30 05:46:09 2025 (1553) pipeline runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1553) pipeline runner exiting. Jan 30 05:46:09 2025 (1551) lmtp runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1551) lmtp runner exiting. Jan 30 05:46:09 2025 (1558) digest runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1558) digest runner exiting. Jan 30 05:46:09 2025 (1557) virgin runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1557) virgin runner exiting. Jan 30 05:46:09 2025 (1556) task runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1556) task runner exiting. Jan 30 05:46:09 2025 (1541) Master watcher caught SIGTERM. Exiting. Jan 30 05:46:09 2025 (1555) retry runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1555) retry runner exiting. Jan 30 05:46:09 2025 (1552) out runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1552) out runner exiting. Jan 30 05:46:09 2025 (1549) command runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1549) command runner exiting. Jan 30 05:46:09 2025 (1548) bounces runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1548) bounces runner exiting. Jan 30 05:46:09 2025 (1547) archive runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1547) archive runner exiting. Jan 30 05:46:09 2025 (1550) in runner caught SIGTERM. Stopping. Jan 30 05:46:09 2025 (1550) in runner exiting. [2025-01-30 05:46:09 +0000] [1554] [INFO] Handling signal: term [2025-01-30 05:46:09 +0000] [2227] [INFO] Worker exiting (pid: 2227) [2025-01-30 05:46:09 +0000] [1585] [INFO] Worker exiting (pid: 1585) Jan 30 05:46:10 2025 (1541) Master watcher caught SIGTERM. Exiting. [2025-01-30 05:46:10 +0000] [1554] [ERROR] Worker (pid:1585) was sent SIGKILL! Perhaps out of memory? [2025-01-30 05:46:10 +0000] [1554] [ERROR] Worker (pid:2227) was sent SIGTERM! [2025-01-30 05:46:10 +0000] [1554] [INFO] Shutting down: Master Jan 30 05:46:11 2025 (1541) Master stopped ``` Thank you, Paul 'Arte Chambers' Robey 502-408-6922

3 13

The paradox of VERP probe messages
by Jeremy Stanley Feb. 2, 2025

Feb. 2, 2025

tl;dr: Is there a way to have VERP probe messages not include copies of the bounce message that triggered them? Longer form... Some months ago I turned on bounce processing for a fairly large list with a long history, because I could see from the MTA logs that there were easily hundreds of old subscribers whose addresses had become defunct and this seemed like a great way to clean that up and make the server more conscientious at not repeatedly trying to deliver messages to sites that were just going to reject them. This worked really well. Until legitimate subscribers also started to get removed, that is, due primarily to false positives from overzealous spam filters. I had previously read about MM3's VERP probe message feature, which seemed to solve the main reason I had kept bounce processing disabled in the MM2 days, and thought it was on by default but clearly it wasn't. So I found the necessary config option and switched that on. This worked really well. Until legitimate subscribers started to get removed again, that is, due primarily to false positives from overzealous spam filters. See, I realized that the VERP probes were helpfully including copies of the most recent bounce for that user, and those NDRs quite often helpfully included their own copies of the messages which had been bounced. So if a subscriber's MTA was rejecting a message because the content looked like spam, then there was a good chance it would also reject the VERP probe message because it included the same content which had caused the earlier rejection. The VERP probe feature was essentially defeating its own purpose as a neutral confirmation that the subscriber hadn't been rejecting messages due to their content. This behavior raises a more significant concern as well. The MTA on the Mailman server in this case (Exim if it matters) wants to perform batch deliveries when there are multiple subscribers who all share the same remote MTAs. If multiples of those reject a list post, then the NDR back to Mailman aggregates those multiple rejections into a single message. If that incident triggers a VERP probe, the bulk NDR enumerating the addresses of all the subscribers who were rejected gets forwarded along as part of the VERP probe, disclosing a potentially sensitive litany of random subscriber addresses to other subscribers within that batch. I don't know whether this is a misconfiguration, or an unintended consequence of the intersection of Mailman and MTA features. While I understand that the inclusion of a bounce sample within a VERP probe may be a way to take some workload off list admins in that users can possibly see a message/rejection to explain the reason for the probe, the downsides of that choice make the feature unfortunately unusable for some lists that could otherwise have benefited from it. Am I possibly missing an existing switch that could make VERP probe messages *not* include copies of the bounces that triggered them? This is in some ways similar to the problems I've noticed with message hold notifications to moderators including copies of the held messages, since these are (at least in the case of the lists I manage) often spam, so has a tendency to cause the mail providers for the list moderators to start considering the mailing list server a spam source. If there were a switch to make message hold notifications to moderators *not* include copies of the messages themselves, I'd start allowing moderator notifications again. Suggestions welcome! Also willing to try to submit patches to enable some of these solutions if they don't already exist. And thanks to anyone who read this far! -- Jeremy Stanley

2 4

Outgoing runner lockup? + "slice inspector" tool
by Stephen J. Turnbull Feb. 1, 2025

Feb. 1, 2025

Hi, I'm advising a user on a system which experiences occasional lockups in an outgoing runner. The runner contacts a remote smarthost, and occasionally locks up with the smtp connection still open according to "lsof -i :25". This state seems to be permanent: the backlog for that slice starts to grow without bound, for at least an hour. When this was happening once a month, they would just restart Mailman core, and the backlog would clear in minutes. But recently it's been happening daily which is distracting their staff, and worries me. Another thing that is strange about this site is that it should be possible to hit that runner with a SIGUSR1 and restart it. This works for me, but on that system the stuck runner exits, but does not restart. Since normally it only happens to one runner of several, I wanted to identify the runner and process. I attach the tool I developed, for anyone who might have configured multiple runners and is interested to see the distribution across runners. Has anybody seen an outgoing runner lock up with an open smtp session? Any ideas on why? My analysis so far: - Because a restart works every time, I'm pretty sure it doesn't have anything to do with message content. - I believe both the Mailman host and the outgoing smarthost are Linodes, in the same datacenter. The problematic Mailman system is Mailman 3.3.6, Python 3.10 on Ubuntu 16.xx LTS. I believe the smarthost is a more recent Ubuntu LTS, probably running Postfix 3.7 as the MTA. (Yes, they have sufficiently paranoid security and QA teams. ;-) - We're using smtplib, which as far as I can tell basically has a 60s timeout for each command. Thus you'd think it would time out. I guess it could be inflooping on timeout, retry, timeout, retry, but I don't know how to check that. Maybe ss(8) will serve? - My system where SIGUSR1 works as documented is Python 3.11.2 on a Digital Ocean droplet with Debian 12.9, Linux 6.1.0. - I haven't tried to reproduce the Python 3.10 + Mailman 3.3.6 configuration and test SIGUSR1 in that configuration yet. Seems unlikely, waiting for the proverbial "round tuit". - It has occurred to us to use the local Postfix as the relay MTA. I'm waiting on a report whether that alleviates the problem. Even if so, I want to fix the underlying defect if possible. Any ideas would be welcome, including general debugging advice. Here's the promised slice_inspector tool. (Patches and suggestions welcome, though I don't promise to implement any time soon.) The tool imports some files from Mailman core, click, and psutil (not psutils!) I believe the latter modules are required by Mailman, so you should be able to run it as is under the 'mailman' user (or perhaps 'list' on Debian) in the environment Mailman itself uses. It defaults to assuming that mailman.cfg is /etc/mailman3/mailman.cfg. You'll probably need to fix the shebang if you want to chmod +x. The '--help' should be pretty self-explanatory. Steve

2 1

messages with attachments, without text discarded silently
by Schulz Feb. 1, 2025

Feb. 1, 2025

Using the current mailman version, I can reproduce the following: - send a text-formatted email with attachment but without text body to a list. - the msg will be received by mailman - the msg shows up in shunt, the log shows: ile "/usr/lib/python3.12/email/message.py", line 343, in set_payload payload = payload.encode(charset.output_charset, 'surrogateescape') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) an attempt to unpickle the file leads to the same error. I know it's uncommon to send emails without txt but with attachments - but it may happen; at least we would welcome an error message.

2 3