- Mailman-users - lists.mailman3.org

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

Postorius Suggestion: Give owner a view of all users of all owned lists
by Andreas Vetter March 10, 2025

March 10, 2025

Hi, it would be real great if owners that own several lists, but are not superusers, can see all users of all *their* lists and manage them. A down-"selected" version of the superusers view. Use case is an organisation (here are the superusers) with sub-organisations (here are the owners, e.g finance, research, production) having lists for the very sub-org itself and its sub-sub-orgs (e.g. research-all, research-solar, research-wind, research-battery). Would that be possible? -- Mit freundlichen Gruessen, Andreas Vetter

2 1

Bad Request 400 error with nginx/uwsgi install of venv
by zachr＠mta.ca March 10, 2025

March 10, 2025

Hello, and thanks in advance for any assistance. I followed the installation guide at: https://docs.mailman3.org/en/latest/install/virtualenv.html# I opted to use nginx and uwsgi. I can access mailman in the browser at https://SERVER_IP/mailman3 but when I try to use the hostname I get an nginx 400 bad request error. It seems like there is an issue with the nginx proxy. I used the example config and updated the required information: --------------------- server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name HOSTNAME_OF_SERVER; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /etc/pki/tls/certs/our_certificate.crt; ssl_certificate_key /etc/pki/tls/private/our_key.key; } --------------------- I thought maybe that because Im using uwsgi I should try the ngx_http_uwsgi_module and uwsgi_params in the nginx config, but that did not work, or I didnt use the correct syntax. Not sure what to try next!

2 2

Migration of the e-mail templates
by Markus Grandpré March 6, 2025

March 6, 2025

Dear list, When migrating the lists and archives from Mailman 2.1 to Mailman 3, the e-mail templates were obviously not migrated. Is there a way to make up for this? Kind regards, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

3 3

Bug Report - REST API
by Peter Knowles March 6, 2025

March 6, 2025

OS: Debian 12 Mailman Core: 3.3.10 Install Method: venv When I apply the "count" and/or "page" param on: /3.1/lists/name.sub.domain.tld/requests This resulted in a "404 Not Found" error from the REST API. If I remove the params, the API returns results. From what I read in the docs, pagination should be possible on this type of endpoint as it returns "entries", "start" and "total_size". Tests against: /3.1/domains /3.1/lists Works fine with the "count" and "page" param as expected.

2 1

Hyperkitty Replies showing up as new posts
by Arte Chambers March 6, 2025

March 6, 2025

Hello, my Hyperkitty is creating a new post for each reply in a thread. I would expect that new posts to a list would show up in the archive and once you click on that thread you would see all replies. However in my Hyperkitty each reply to a thread shows up as its own post usually with the subject line saying RE: Original Message. How can I set up Hyperkitty to behave more like the lists.mailman3.org archives where replies to topics are filed under their respective threads? Thank you, Paul 'Arte Chambers' Robey 502-408-6922

3 4

Using clean_users.py
by Odhiambo Washington March 6, 2025

March 6, 2025

I have run clean_users.py with: DELETE_MAILMAN_USER = True DELETE_DJANGO_IF_MAILMAN = True However, when I go to https://mm3-site/mm/lists/listname.mm3-site/members/nonmember/ I still have hundreds of users listed despite the script having run and it showed hundreds of addresses removed. What might be the issue? I expect to NOT find anything listed as nonmembers. -- 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]

2 1

Set member.moderation_action via REST API as part of message approval?
by Andy Matthews March 5, 2025

March 5, 2025

We're using Mailman 3.3.9. My team and I have written a simple UI for displaying and approving/rejecting held messages from non list members. When an email receives an "always accept" flag from the UI we call the API to pass in the requested information: ``` Form form = new Form(); form.param("action", "accept"); Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); String safePath = UriBuilder.fromPath("lists/{listId}/held/{messageId}").build(listId, messageId).toString(); response = getTarget().path(safePath).request().post(data); ``` If that request is successful we update the `accept_these_nonmembers` property of the mailing list with the user's email. ``` Form form = new Form(); if (fieldValue.getClass().isArray()) { for (String val : (String[])fieldValue) { form.param(property, String.valueOf(val)); } } else { form.param(property, String.valueOf(fieldValue)); } Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); ``` The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). The docs indicate that I should be able to submit a patch request to update the moderation action for any user: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: `/3.0/addresses/abc(a)123.com` returns ``` { "email": "abc(a)123.com", "original_email": "abc(a)123.com", "registered_on": "2025-03-03T19:18:35.169703", "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" } ``` So I'm not sure how I would be able to update this particular record without a member or user id. So, all that said, I'm looking for information on how to do one of the following. 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? There may of course be additional approaches that I'm not considering, but that's about the gist of it. Thoughts?

2 6

How to follow up to a question on a Mailing List
by Odhiambo Washington March 4, 2025

March 4, 2025

Hello listers, I always find some members' posts to MM3 lists breaking threads to an extent no one can easily figure out what portion of the discussion they were responding to. In a way, they end up creating a loosely-attached thread of their own. I have a suggestion for you that can help improve this. Please refer to http://www.lemis.com/questions.html#answer/ The guide was written decades ago by a very respectable member of the FOSS community for freebsd-questions ML, but it's a guide that is pretty standard for every ML. Thank you for your understanding and consideration of the advice. -- 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

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