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

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