- Mailman-users - lists.mailman3.org

clearing pending db
by Morris Jones Aug. 8, 2025

Aug. 8, 2025

I have an admittedly out-of-date installation of Mailman 3.3 (3.3.2 Tom Sawyer) but it's been working without issues for a long time, so I haven't had much incentive to bring it up to date. Sorry! A couple of my larger mailing lists (around 500 members) are currently very slow when making changes through the UI (maybe that's my raison-to-update). They also both have very large lists of members "pending confirmation." My suspicion is that the large pending list is slowing down other operations. But pendingdb.evict() doesn't seem to clear the list. For example, on one of my lists: >>> from mailman.interfaces.pending import IPendings >>> >>> from zope.component import getUtility >>> >>> pendingdb = getUtility(IPendings) >>> pendingdb.count() 5040 >>> pendingdb.evict() >>> pendingdb.count() 5040 >>> I have several lists, but none of them are extremely active, so I don't have a problem with wiping the pending db for all of them. And I also might be totally wrong in my guess. Mojo -- Morris Jones, Monrovia, CA

3 3

Support question, not a bug: Is it possible and how, programmatically to change all settings from domain1 to domain2?
by Wikinaut Aug. 8, 2025

Aug. 8, 2025

@Mark & Stephen, now, where here everything appears to run smoothly on a new server, I want to change the testmail.domain (domain1) settings to mail.domain (domain2) settings. It would be a great help, if this can be done by python script respectively a mailman3 shell script. Is there any on your desk, or can you help me? I already defined in mailman/admin (django admin) that new target domain. I guess, at the end, there might also be a very changes in mailman.cfg and settings.py necessary.

1 0

Main daemon process sticks around after forking
by Jérôme Charaoui Aug. 8, 2025

Aug. 8, 2025

Hello, I'm running a (rather large) mailman3 instance on Debian 13 (trixie) using the distribution packages. To manage the mailman3 daemon, the package installs this systemd service unit: https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ It has been working fine until recently: after a reboot, we noticed the mailman3 unit consistently failing to start due to a timeout error. I figured out that the timeout was related to the service unit type (Type=forking) and the fact that the main/parent process was forking subprocesses (and running normally), writing a PID file, but it wasn't exiting, so systemd identifies this as an error and aborts the service. Since switching to Type=simple, it has been working fine. I'm wondering if anyone else has seen such behavior and how I could troubleshoot it. Thanks! -- Jérôme

2 3

How to create a list with → advertised=false ← by command line "mailman create [OPTIONS] LISTNAME" ?
by Wikinaut Aug. 7, 2025

Aug. 7, 2025

I use the following REST-API sequence (excerpt:) to create a list but want to use the much quicker command line. However, only a few [OPTIONS] can be set via command line. Why? My wish is to have all options available in the command line of mailman? Excerpt from my generateMailinglists.py: # see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… updates = { "description": f"{ML} {listname} ({NOW})", "info": f"{ML} {listname} (autogenerated {NOW})", "display_name": listname, "subject_prefix": f"[{listname.upper()}] ", "advertised": False, # the list will not be shown on mailman3 startpage "allow_list_posts": True, "default_nonmember_action": "discard", "default_member_action": "accept", "subscription_policy": "open", # accepted values are: open, confirm, moderate, confirm_then_moderate "unsubscription_policy": "open", # accepted values are: open, confirm, moderate, confirm_then_moderate "send_welcome_message": False, "send_goodbye_message": False, "archive_policy": "private", # accepted values are: public, private, never "preferred_language": "de", "member_roster_visibility": "members" # accepted values are: public, members, moderators } update_config(fqdn_listname, updates)

4 8

How to run this script (attached) in the mailman shell (or withlist)?
by Wikinaut Aug. 6, 2025

Aug. 6, 2025

https://dpaste.com/39ZMH3M7S (Text below) The code works perfectly when pasted into the live shell of mailman. But not when I start "(venv) mailman withlist -r set_member_pref". ... module = import_module(module_path) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked ModuleNotFoundError: No module named 'set_members_prefs' What is wrong? Please can anyone help? Please can you add information in the documentation how exactly to run a script like that? # def set_members_prefs(): from zope.component import getUtility from mailman.interfaces.listmanager import IListManager from mailman.interfaces.member import DeliveryMode, DeliveryStatus hide_address = False delivery_status = DeliveryStatus.enabled lm = getUtility(IListManager) for mlist in lm.mailing_lists: print(f"... members in {mlist.fqdn_listname}") for member in mlist.members.members: prefs = member.preferences prefs.acknowledge_posts = True prefs.hide_address = hide_address prefs.preferred_language = 'de' prefs.receive_list_copy = True prefs.receive_own_postings = True prefs.delivery_mode = DeliveryMode.regular prefs.delivery_status = delivery_status print(f"Updated {member.address.email} in list {mlist.fqdn_listname}")

2 6

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

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