- Mailman-users - lists.mailman3.org

MM broken after proxy migration (Nginx -> Caddy)
by Andreas Kemper May 27, 2025

May 27, 2025

Hi, I've been running MM 3 for quite some time, with a couple of lists including members managed via the REST-API from an external program. After some issues with LetsEncrypt certificates, I migrated the HTTPs proxy from previous Nginx now to Caddy with the following Caddyfile: https://listen.dlc-aachen.de { header Strict-Transport-Security max-age=31536000; # Disable access to archive and registration redir /hyperkitty* https://listen.dlc-aachen.de redir /accounts/signup* https://listen.dlc-aachen.de reverse_proxy localhost:8000 { header_up X-Forwarded-Proto {scheme} header_up X-Forwarded-Host {host} } handle_path /static/* { file_server { root /var/lib/mailman3/web/static } } } Following this change, list continued operation as usual, but after a few days it seemed to be attacked via it's GUI, according to the attached Django error message. Since then mailman doesn't send out anymore mails and I have a persistent master.lck file. Furthermore, during mailman start smtp.log always shows a "Connection lost during _handle_client()". I guess the connection loss is related to the master.lck file, hence how can I get rid of it / "reset" mailman? In addion, should I include further directives in my Caddyfile in order to protect mailman from coming attacks? Thx a lot Andreas

2 1

Django: An error occurred while processing your request.
by Florian Sukup May 27, 2025

May 27, 2025

Hi, I running Debian bookworm and have installed mailman3-full (+ postfix). I am new to mailman3 (using mailman2 now) and about exploring how to migrate. I had 3 sites or domains: example.com and two real ones. When I received emails from postorius, then it came from example.com which is nonsense as I worked with the real lists. So I deleted example.com. When I call https://.../mailman3/admin or any of the lists, the result is: Server error An error occurred while processing your request. How can I get out of it? This is only a test environment, so no heart attack. Thank you for any help. Florian.

3 3

Masking email addresses in the archives
by Odhiambo Washington May 26, 2025

May 26, 2025

I must have missed this if it was ever discussed, but is it possible to mask the list members' email addresses in the archives? -- 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]

3 4

Moderation -- implicit destination behavior
by Steve Bachinsky May 24, 2025

May 24, 2025

Hi. We have noticed some posts being held for moderation (even though user has permission to post to list) and Mailman reports: moderation_reasons: ['Message has implicit destination’] The lists are configured for “require_explicit_destination”. However, the email address of the list is clearly in the CC: header of the email (no alias or subdomain). Is there some other reason why Mailman would hold an email for moderation with the reason of “implicit destination”? This moderation is not consistent for same list and poster. The emails come from a large domain with multiple load-balancing email servers. I suspect that it may be something with one or more of the servers being misconfigured, but unable to see anything obvious from the headers and confused why Mailman states the reason to be implicit destination when that does not seem to be the cause. Thanks, Steve

4 4

Execute assorted Mailman functions via Mailman shell terminal
by Andy Matthews May 15, 2025

May 15, 2025

When my company migrated from MM2 to MM3, they discovered there were things that didn't work as expected (don't get me started). So they developed a set of Python functions which allowed then to fill in the missing functionality. However, they've discovered that some of those functions either never worked properly, or no longer work. For example, ``` def list_nonmembers(mlist): for accepted in mlist.accept_these_nonmembers: print("Accepted: ",accepted) for held in mlist.hold_these_nonmembers: print("Held: ",held) ``` They're run by shelling into the machine which hosts mailman and executed like so (where scripts is `scripts.py`) ``` sudo -iu mailman mailman shell -l MAILING_LIST_ID --run scripts.list_nonmembers ``` I'm recommending that we install Postorius, as I suspect many of the functions they've written are already present in that UI, but it's not as simple as that. Instead they're wanting a handful of these functions (including the one listed above) replaced sooner than we could get Postorius up and running. I've gotten this far: ``` from mailman.interfaces.listmanager import IListManager from zope.component import getUtility mylist_id = 'bravo-open1(a)tena-sda.org' list_manager = getUtility(IListManager) mylist = list_manager.get(mylist_id) ``` The mylist variable is of type `mailman.model.mailinglist.MailingList`, and includes an Attributes for nonmembers: ``` mylist.nonmembers <mailman.model.roster.NonmemberRoster object at 0x7ffffa3e65b0> ``` But this nonmembers property doesn't output any users/addresses when printed, and throws a TypeError when I try to iterate over it: ``` Traceback (most recent call last): File "<console>", line 1, in <module> TypeError: 'NonmemberRoster' object is not iterable ``` So, given a mailing list instance, retrieved via `list_manager.get(mylist_id)`, how would I go about printing all nonmembers and their current roles in a list (held, accepted, etc.)? Alternately, is there a different question I should be asking in order to retrieve that information?

2 5

Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)
by Jan Eden May 14, 2025

May 14, 2025

Hi, after installing Mailman 3 in a new virtual environment, I ran into the compatibility issues with django-allauth discussed by Andreas Vetter and Mark Sapira on this list in February[1] and in March[2] – WARNINGS: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] – and solved them with the additions to /etc/mailman3/settings.py suggested by Mark: del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] In the second list thread, Mark linked to the current (patched) version of mailman-web's mailman.py[3], which addresses the deprecation of ACCOUNT_AUTHENTICATION_METHOD, but not of ACCOUNT_EMAIL_REQUIRED. Is there any reason why the patch fixes only one of the two issues? - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [3] https://gitlab.com/mailman/mailman-web/-/blob/c8b9aef1704b75b1cb6d0c925855a…

2 1

Mass subscription and Delivery mode/status
by Andreas Vetter May 14, 2025

May 14, 2025

Hello all, we run a venv installation of "mailman postorius django-mailman3 hyperkitty mailman-web". When I mass subscribe (pre-verified) a new mail address into a list, the Delivery mode appears as Regular in /mailman3/lists/somelist.example.com/members/member/ That is what I expect. When I click on the new mail address from there, i.e. mailman3/lists/somelist.example.com/members/options/eimer@mail.org?role=mem… the Delivery status is ----- instead of Enabled and the Delivery mode is ----- instead of Regular. In fact, all yes/no radio buttons are unset. This is unexpected. What does ----- mean in that case? Is it unset and some default (from the list?) is used? After thinking another round about it: Is the view mailman3/lists/somelist.example.com/members/options/eimer@mail.org?role=mem… only filled with values, when somebody (member, list owner or admin) actively set values and unfilled otherwise? -- Mit freundlichen Gruessen, Andreas Vetter

3 2

Bots outbreak - Subscriptions pending user confirmation (58)
by Odhiambo Washington May 14, 2025

May 14, 2025

Daily, I am getting not less than 50 "Subscriptions pending user confirmation". There must be a way to stop them. I am using https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… already. <Location /accounts/signup> <Limit POST PUT DELETE> Order allow,deny Allow from all Include /opt/mailman/tor-exit-list.conf </Limit> </Location> wash@eu:/etc/apache2/sites-enabled$ cat /opt/mailman/tor-exit-list.conf | wc -l 2081 Does this mean the restrictions aren't caching them? -- 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

Can mailman3 use google or cloudflare captcha ?
by Kim Sunggun May 13, 2025

May 13, 2025

Hello, I can setup client side for any of captcha in /opt/mailman/venv/lib/python3.9/site-packages/django_mailman3/templates/account/login.html. However, I don't understand where I should I put captcha code(Server-side validation) for mailman3. is there any tip to setup captcha ?

2 1

alembic.util.exc.CommandError: Can't locate revision identified by xx
by Lars Bjørndal May 13, 2025

May 13, 2025

I upgraded my Fedora distro from v.40-41. I did pip install wheel mailman psycopg2-binary When running the mailman command, I get alembic.util.exc.CommandError: Can't locate revision identified by '8cc1f79f4459' How do I solve this? Thanks, Lars

1 2