- Mailman-users - lists.mailman3.org

Held messages not delivered after approval
by Stephan Krinetzki Aug. 6, 2025

Aug. 6, 2025

Hi all, I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members. The message does not end up in the shunt queue, and nothing is delivered. Here's what I see in the Mailman log: Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from sender(a)sub.example.com held, message-id=<20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a list member Jul 30 16:12:39 2025 (213338) held message approved, message-id: <20250730141221.5VVrn%sender(a)sub.example.com> In the mail log, I only see the message arriving — there's no sign of it being sent out. Any ideas on what could be going wrong or where else I should look? Mailman Core-Version GNU Mailman 3.3.10 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.11.11 (main, Jun 20 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] OS: Rocky 9 with Postfix MTA, installed as venv Thanks in advance Stephan

5 29

Whitelist in mailman3: How to allow only ~400 e-mail senders in a file whitelist to send to a list?
by Wikinaut Aug. 5, 2025

Aug. 5, 2025

In mailman2, it was quite handy to place "@whitelist" into the field sender/accept_these_nonmembers, when such a file has been set up. How can I (per list or programmatically) define the ~400 e-mail senders to be allowed to send to my about 30 lists? And, yes, I already searched for a solution of this problem, but could not find any.

2 2

How to create (or change) certain member preferences (in a list, or for all lists) by command line "mailman create [OPTIONS] LISTNAME" ? (Suggestion: modification of this command)
by Wikinaut Aug. 5, 2025

Aug. 5, 2025

Some member preferences - such as hide_address - cannot be set with the [OPTIONS] in the command line. I suggest to modify the code so that all member preferences can be set via the command line. What do you think? This is how I currently patch (some) member preferences (hide_address is a variable here) in a python script, but this takes a lot of time, depending on the number of users.... YMMV. patch_url = f"{member['self_link']}/preferences" patch_data = { "acknowledge_posts": True, "hide_address": hide_address, "preferred_language": "de", "receive_list_copy": True, "receive_own_postings": True, "delivery_mode": "regular", # accepted values are: regular, plaintext_digests, mime_digests, summary_digests "delivery_status": delivery_status # accepted values are: enabled, by_user, by_bounces, by_moderator, unknown } r = requests.patch(patch_url, json=patch_data, auth=AUTH, headers=HEADERS)

3 3

Disable Sign-up per domain
by Mark Aug. 5, 2025

Aug. 5, 2025

Hi, GNU Mailman 3.3.10 (Tom Sawyer) VENV installation Disabling the Account "Sign-up" globally can be done by adding the following to "/etc/mailman3/settings.py". ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' I have several domains on the server. Is it possible to disable the Sign-up for only one of the domains ? Regards, Mark

2 13

cron error - /opt/mailman/venv/bin/mailman-web runjobs daily
by Odhiambo Washington Aug. 4, 2025

Aug. 4, 2025

I wonder what this means and whether it's fatal. How do I fix it? ``` ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django_extensions/management/commands/runjobs.py", line 51, in runjobs job().execute() File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute sync_with_mailman() File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/lib/mailman.py", line 178, in sync_with_mailman mlist.update_from_mailman() File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/models/mailinglist.py", line 226, in update_from_mailman self._update_owner_mods_from_mailman(mm_list) File "/opt/mailman/venv/lib/python3.11/site-packages/hyperkitty/models/mailinglist.py", line 231, in _update_owner_mods_from_mailman user = get_django_user(owner) ^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/lib/user.py", line 30, in get_django_user email_addr = EmailAddress.objects.get(email=member.address.email) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/manager.py", line 87, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/db/models/query.py", line 640, in get raise self.model.MultipleObjectsReturned( *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() returned more than one EmailAddress -- it returned 2!* ``` I suspect it's something to do with my action yesterday while attempting to reply to a thread from HyperKitty. The superuser account uses my address - odhiambo at gmail dot com.I am also the listowner for most lists. I tried unsuccessfully to create an account on Postorious using the same email address. I kept getting sent links to verify the account, over and over. Finally, I was able to verify the account, but cannot login with it. -- 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

Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated
by Andreas Vetter Aug. 1, 2025

Aug. 1, 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

4 9

Advice on how to set announcement only lists?
by Sparks, Paul July 31, 2025

July 31, 2025

Here's the basics of what I'm trying to set up: The Web UI is not available. CLI tools are being used for configuration and ongoing maintenance functions. The server instance is ephemeral, but has persistent storage for postfix / mailman configuration. There are a series of notification lists list-0000(a)example.com, list-0001(a)example.com, etc. Users can subscribe / unsubscribe via email. A list-all(a)example.com list can be used to send posts to all lists (this is rare). A siteadmin(a)example.com email address is the only sender allowed to post to any list. A list-admin(a)example.com list is defined. This list should be copied on all posts that are sent to any of the notification lists. The admin list membership is maintained via CLI tools by list admins Below are a couple of ideas I've played around with, but haven't gotten a good solution. Suggestions would be welcome. I've had a little experience with the CLI tools, but I'm not having luck with trying to add non-members. Idea 1 Have list-all(a)example.com be an umbrella list with all notifications lists as members. list-admin(a)example.com is added to all lists as a member siteadmin(a)example.com is added to all notification lists as a member with moderation_action = Action.defer to allow sending posts. ues-all(a)example.com is added to all notification lists as a member with moderation_action = Action.defer to allow "nested" sending to members of the list-all list. There seem to be issues with having the senders as members of the list. Having them as non-members might be a solution, but I haven't yet figured out how to add non-members via CLI. Idea 2 Use cron with CLI tools to extract all notification list members and update (mailman syncmembers) the list-all membership. Use script to add all list-admin users to each notification list. Update all notification lists when the list-admin membership changes. This is somewhat problematic since individuals could be direct members of notification lists and removal from list-admin would remove the direct membership. siteadmin(a)example.com is added to all lists as a member with moderation_action = Action.defer to allow sending posts. ________________________________ The contents of this e-mail, including attachments, are intended for use by the named addressee only and may contain information that is confidential or private according to applicable law. If you received this electronic transmission in error, please notify the sender by a reply to sender only message, permanently delete the original message and any attachments from your electronic device and keep this message confidential. Unauthorized use, copying, review and/or distribution to unauthorized persons is strictly prohibited and subjects the user to penalty of law. Thank you for your cooperation.

1 2

server/accounts/confirm-email/ lacks skinning (css)
by Wikinaut July 30, 2025

July 30, 2025

The newly installed mailman3 systems works, however the page accounts/confirm-email/ lacks the css. Can someone confirm my observation? Is there a fix?

2 1

Upgrading other python packages than the mailman ones in a venv results in dependency conflicts
by Ulf R. July 29, 2025

July 29, 2025

Hello, I know this should be the way to upgrade: https://docs.mailman3.org/en/latest/upgrade-guide.html I have 3.3.10 installed. I saw that some python packages are outdated an tried this which install all outdated packages in a row: pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install -U One outdated package was django and this part happened: ------------------------------- vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) Installing collected packages: Django Attempting uninstall: Django Found existing installation: Django 4.2.16 Uninstalling Django-4.2.16: Successfully uninstalled Django-4.2.16 ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 which is incompatible. postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. Successfully installed Django-5.1.4 ------------------------------- So I made a roll back. Is this really the only secure way to update the venv?: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web May be yes and I have to ignore the rest? ;-) Thank you und regards

5 6

Missing Archived emails - Hyperkitty - CERT Issue
by willie.castillo＠caemilusa.com July 29, 2025

July 29, 2025

Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck The CERT on the website is now up-to-date

5 11