- Mailman-users - lists.mailman3.org

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

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

Archive download - unexpected end of file
by Mark March 2, 2025

March 2, 2025

Hi, I have a MM3 list to whose archive I recently added an mbox file of older emails. Viewing/searching the archive (Hyperkitty) is working fine. Downloading archives "for the month" or "last 30 days" delivers the expected ".mbox.gz" file and those are fine. However, when I download the "Entire archive" and attempt to gunzip that ".mbox.gz" file I get the error: " ... unexpected end of file". Or using Gnome desktop's "Extract", I get the error "..truncated gzip input" Any tips on resolving this would be gratefully received. Best, Mark

2 2

Hyperkitty django.request forbidden
by Arpad Horvath March 1, 2025

March 1, 2025

Hi, I moved from mailman to mailman3 in 2021. I hadn't have the time to fix the archiving. I can see the emails older then that in Hyperkitty, but none of the once still there is mailman3. What can be the problem? It's a Debian 12, I use the packages from the repo. In the mailman-web.log I can see this: [pid: 861|app: 0|req: 8277/8277] xxx.xxx.xxx.xxx () {40 vars in 636 bytes} [Wed Feb 26 06:47:31 2025] GET /hyperkitty/api/mailman/urls?mlist=korus%40lists.somewhere.xx = > generated 221 bytes in 33 msecs (HTTP/1.1 403) 7 headers in 211 bytes (1 switches on core 1) ERROR 2025-02-26 06:47:31,705 861 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP xxx.xxx.xxx.xxx, your MAILMAN_ARCHIVER_FROM setting may be misconfigured WARNING 2025-02-26 06:47:31,705 861 django.request Forbidden: /hyperkitty/api/mailman/urls WARNING 2025-02-26 06:47:31,705 861 django.request Forbidden: /hyperkitty/api/mailman/urls I have this line in /etc/mailman3/mailman-web.py MAILMAN_ARCHIVER_FROM = ('https://lists.somewhere.xx/hyperkitty', '::1') I have the Archiving settings: Archive policy is Private archives At Active archivers hyperkitty's checkbox is checked Archive rendering mode is Plain text I have these packages installed right now: ii mailman3 3.3.8-2~deb12u2 ii mailman3-full 3.3.8-2~deb12u2 ii mailman3-web 0+20200530-2.1 ii python3-django-mailman3 1.3.9-1 ii python3-mailman-hyperkitty 1.2.1-1 ii python3-mailmanclient 3.3.5-1 Thanks, Árpád

3 4

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