June 2024 - Mailman-users - lists.mailman3.org

To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues
by Keith Christian June 10, 2024

June 10, 2024

Hello, mailman list: Trying to add the mailman3.service unit so that mailman3 will start on system boots/reboots. Seeing different behavior with the mailman3.service unit commands vs. with the "/opt/mailman3/venv/bin/mailman" command line. Everyone on this list is more experienced than I with reading systemd error messages and Python code, so your ideas are appreciated. I am using letters and numbers to navigate the six screenshots in this email, I hope this is helpful, without being too much info. Running the following OS and Python versions. Mailman was installed with "pip install wheel mailman psycopg2-binary" per the virtual environment instructions: (venv) [keithchristian@localhost ~]$ cat /etc/redhat-release AlmaLinux release 9.4 (Seafoam Ocelot) (venv) [keithchristian@localhost ~]$ python3 -V Python 3.9.18 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To begin: here is the current mailman3.service unit file, taken from the "Starting Mailman automatically" portion of: https://docs.mailman3.org/en/latest/install/virtualenv.html, with all /opt/mailman/ paths set to /opt/mailman3/ for my sandbox system. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- A 1 [mailman3@localhost ~]$ cat /etc/systemd/system/mailman3.service A 2 [Unit] A 3 Description=GNU Mailing List Manager A 4 After=syslog.target network.target postgresql.service A 5 A 6 [Service] A 7 Type=forking A 8 PIDFile=/opt/mailman3/mm/var/master.pid A 9 User=mailman3 A 10 Group=mailman3 A 11 ExecStart=/opt/mailman3/venv/bin/mailman start A 12 ExecReload=/opt/mailman3/venv/bin/mailman restart A 13 ExecStop=/opt/mailman3/venv/bin/mailman stop A 14 A 15 [Install] A 16 WantedBy=multi-user.target ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below in line B-6, systemd thinks mailman isn't running, but with the "/opt/mailman3/venv/bin/mailman" commands, line B-2 says it is. I could be misinterpreting the systemd output, however. Python not happy about some directories. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- B 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status B 2 GNU Mailman is running (master pid: 10004) B 3 [mailman3@localhost ~]$ systemctl status mailman3.service B 4 mailman3.service - GNU Mailing List Manager B 5 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) B 6 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 7min ago B 7 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) B 8 CPU: 762ms B 9 B 10 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist B 11 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) B 12 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs B 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) B 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs B 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) B 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' B 17 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE B 18 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. B 19 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below, we stop mailman with the command line and check status with systemd. C-1, C-2, show stopped. I'd think systemctl status should show stopped but it doesn't. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- C 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman stop C 2 Shutting down Mailman's master runner C 3 [mailman3@localhost ~]$ systemctl status mailman3.service C 4 mailman3.service - GNU Mailing List Manager C 5 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) C 6 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 8min ago C 7 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) C 8 CPU: 762ms C 9 C 10 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist C 11 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) C 12 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs C 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) C 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs C 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) C 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' C 17 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE C 18 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. C 19 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Below, we start mailman, the "/opt/mailman3/venv/bin/mailman" command line works, D-1 through D-5. Line D-6, the systemd status command (erroneously) shows otherwise. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- D 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman start D 2 Starting Mailman's master runner D 3 Generating MTA alias maps D 4 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status D 5 GNU Mailman is running (master pid: 10457) D 6 [mailman3@localhost ~]$ systemctl status mailman3.service D 7 mailman3.service - GNU Mailing List Manager D 8 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) D 9 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 10min ago D 10 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) D 11 CPU: 762ms D 12 D 13 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist D 14 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) D 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs D 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) D 17 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs D 18 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) D 19 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' D 20 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE D 21 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. D 22 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------------- E 1 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman status E 2 GNU Mailman is running (master pid: 10457) E 3 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman stop E 4 Shutting down Mailman's master runner E 5 [mailman3@localhost ~]$ /opt/mailman3/venv/bin/mailman start E 6 Starting Mailman's master runner E 7 Generating MTA alias maps E 8 [mailman3@localhost ~]$ systemctl status mailman3.service E 9 mailman3.service - GNU Mailing List Manager E 10 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) E 11 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 2h 21min ago E 12 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) E 13 CPU: 762ms E 14 E 15 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 16 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) E 17 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 18 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) E 19 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 20 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) E 21 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 22 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 23 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 24 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 25 [mailman3@localhost ~]$ systemctl stop mailman3.service E 26 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== E 27 Authentication is required to stop 'mailman3.service'. E 28 Multiple identities can be used for authentication: E 29 1. keith christian (keithchristian) E 30 2. mailman3 E 31 Choose identity to authenticate as (1-2): 2 E 32 Password: E 33 ==== AUTHENTICATION COMPLETE ==== E 34 [mailman3@localhost ~]$ systemctl status mailman3.service E 35 mailman3.service - GNU Mailing List Manager E 36 Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) E 37 Active: failed (Result: exit-code) since Sat 2024-06-08 09:35:57 MDT; 2h 21min ago E 38 Process: 10342 ExecStart=/opt/mailman3/venv/bin/mailman start (code=exited, status=1/FAILURE) E 39 CPU: 762ms E 40 E 41 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 42 Jun 08 09:35:57 localhost.localdomain mailman[10342]: makedirs(directory) E 43 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 44 Jun 08 09:35:57 localhost.localdomain mailman[10342]: os.makedirs(path, mode) E 45 Jun 08 09:35:57 localhost.localdomain mailman[10342]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 46 Jun 08 09:35:57 localhost.localdomain mailman[10342]: mkdir(name, mode) E 47 Jun 08 09:35:57 localhost.localdomain mailman[10342]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 48 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 49 Jun 08 09:35:57 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 50 Jun 08 09:35:57 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 51 [mailman3@localhost ~]$ systemctl start mailman3.service E 52 ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ==== E 53 Authentication is required to start 'mailman3.service'. E 54 Multiple identities can be used for authentication: E 55 1. keith christian (keithchristian) E 56 2. mailman3 E 57 Choose identity to authenticate as (1-2): 2 E 58 Password: E 59 ==== AUTHENTICATION COMPLETE ==== E 60 Job for mailman3.service failed because the control process exited with error code. E 61 See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. E 62 [mailman3@localhost ~]$ journalctl -xeu mailman3.service|tail -20 E 63 Defined-By: systemd E 64 Support: https://wiki.almalinux.org/Help-and-Support E 65 E 66 An ExecStart= process belonging to unit mailman3.service has exited. E 67 E 68 The process' exit code is 'exited' and its exit status is 1. E 69 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 70 Subject: Unit failed E 71 Defined-By: systemd E 72 Support: https://wiki.almalinux.org/Help-and-Support E 73 E 74 The unit mailman3.service has entered the 'failed' state with result 'exit-code'. E 75 Jun 08 11:58:52 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 76 Subject: A start job for unit mailman3.service has failed E 77 Defined-By: systemd E 78 Support: https://wiki.almalinux.org/Help-and-Support E 79 E 80 A start job for unit mailman3.service has finished with a failure. E 81 E 82 The job identifier is 9400 and the job result is failed. E 83 E 84 [mailman3@localhost ~]$ journalctl -xeu mailman3.service|grep -a "Jun 08 11:5[0-9]:[0-9][0-9]" E 85 Jun 08 11:58:51 localhost.localdomain systemd[1]: Starting GNU Mailing List Manager... E 86 Jun 08 11:58:52 localhost.localdomain mailman[11160]: Traceback (most recent call last): E 87 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/bin/mailman", line 33, in <module> E 88 Jun 08 11:58:52 localhost.localdomain mailman[11160]: sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) E 89 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1157, in __call__ E 90 Jun 08 11:58:52 localhost.localdomain mailman[11160]: return self.main(*args, **kwargs) E 91 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1077, in main E 92 Jun 08 11:58:52 localhost.localdomain mailman[11160]: with self.make_context(prog_name, args, **extra) as ctx: E 93 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 943, in make_context E 94 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self.parse_args(ctx, args) E 95 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1644, in parse_args E 96 Jun 08 11:58:52 localhost.localdomain mailman[11160]: rest = super().parse_args(ctx, args) E 97 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1408, in parse_args E 98 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value, args = param.handle_parse_result(ctx, opts, args) E 99 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2400, in handle_parse_result E 100 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value = self.process_value(ctx, value) E 101 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2362, in process_value E 102 Jun 08 11:58:52 localhost.localdomain mailman[11160]: value = self.callback(ctx, self, value) E 103 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config E 104 Jun 08 11:58:52 localhost.localdomain mailman[11160]: initialize(value) E 105 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 228, in initialize E 106 Jun 08 11:58:52 localhost.localdomain mailman[11160]: initialize_1(config_path) E 107 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 122, in initialize_1 E 108 Jun 08 11:58:52 localhost.localdomain mailman[11160]: mailman.config.config.load(config_path) E 109 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 141, in load E 110 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self._post_process() E 111 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 163, in _post_process E 112 Jun 08 11:58:52 localhost.localdomain mailman[11160]: self.ensure_directories_exist() E 113 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 256, in ensure_directories_exist E 114 Jun 08 11:58:52 localhost.localdomain mailman[11160]: makedirs(directory) E 115 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/utilities/filesystem.py", line 68, in makedirs E 116 Jun 08 11:58:52 localhost.localdomain mailman[11160]: os.makedirs(path, mode) E 117 Jun 08 11:58:52 localhost.localdomain mailman[11160]: File "/usr/lib64/python3.9/os.py", line 225, in makedirs E 118 Jun 08 11:58:52 localhost.localdomain mailman[11160]: mkdir(name, mode) E 119 Jun 08 11:58:52 localhost.localdomain mailman[11160]: PermissionError: [Errno 13] Permission denied: '//var/templates' E 120 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE E 121 Jun 08 11:58:52 localhost.localdomain systemd[1]: mailman3.service: Failed with result 'exit-code'. E 122 Jun 08 11:58:52 localhost.localdomain systemd[1]: Failed to start GNU Mailing List Manager. E 123 [mailman3@localhost ~]$ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- For the PermissionError: [Errno 13] Permission denied: '//var/templates' in Line E-119 above, every /var/tamplates directory except the last one has write permissions for mailman3, I doubt that the "/home/keithchristian/var/templates directory" had been tried. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- F 1 1716996947 drwxr-xr-x. 2 mailman3 mailman3 6 May 29 09:35 /opt/mailman3/var/templates F 2 1716999414 drwxr-xr-x. 2 mailman3 mailman3 6 May 29 10:16 /opt/mailman3/mailman_install_documentation_edits/var/templates F 3 1717774226 drwxr-xr-x. 2 mailman3 mailman3 6 Jun 7 09:30 /opt/mailman3/venv/var/templates F 4 1717779523 drwxr-xr-x. 2 keithchristian keithchristian 6 Jun 7 10:58 /home/keithchristian/var/templates ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- END OF MAILMAN INSTALL ISSUES SCREENSHOTS -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

5 6

Email to list owner on list creation only sent when using mailman create --notify command
by Perry Kollmorgen June 10, 2024

June 10, 2024

Hi, This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. Is there an option to include a notify option when using mailmanclient or the API direct perhaps ? Or even maybe a way to trigger a notification manually at some point once the list is completely setup including both short and long descriptions ? Thank you. Regards, Perry

2 2

Digests not working correctly
by Joel Lord June 8, 2024

June 8, 2024

So I seem to have problems with both periodic AND size-triggered digests. Size first, this is simpler. Just got one sent out, clearly triggered by a new email getting added to the queued up messages, but the setting for the list is the default 30KB and the digest came out at 23.2 KB. Is it measuring the accumulated queue as size on disk including metadata and filesystem block sizes or something, rather than the size of what the emailed digest will be? Periodic is much more complicated, even to explain. I have the cron job running nightly at 11:00 PM and it certainly seems to be working, except for one really odd thing. The list also definitely has periodic digests enabled in the web UI. This is a very bursty list, so it will go mad with traffic for a few weeks and then will go mostly idle for a month or so. The first digest of a burst is definitely size-triggered, but pretty reliably it has the last few messages from the previous burst in there. So the one I got today had three messages from today and one message from May 4th. But that May 4th message should have gone out at 11:00 PM on May 4th with the daily digest and then gotten flushed from the pending digest queue, right? -- Joel Lord

3 14

Using the API to create nonmembers with a different moderation action than the list default
by Perry Kollmorgen June 8, 2024

June 8, 2024

Hi, My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. When using the mailmanclient python bindings I have worked out I can add nonmembers with something like: mailing_list.add_role('nonmember', 'nonmember(a)yourdomain.com', display_name='Non Member') However I can't see anything in the mailmanclient docs which suggest it is possible to configure a member_moderation_action or moderation_action field for that member. I assume I'll need to fall back to using the REST API directly, and most likely something along these lines: 1/ Obtain the member ID for an email address of someone who already been added as a nonmember. 2/ Patch an endpoint which looks something like: /members/{member_id} I'm not able to use the mailman binary (e.g mailman shell) on the mailman-core host itself as I would like to query an existing database of people and reach out to a mailman endpoint from the database host rather than opening that host up to further network access. I figured it might be a good stage in which to ask for a little help and pointers before I continue, perhaps there is something I have missed for a better way to approach this. Thanks. Regards, Perry

3 4

Trying to save a new style
by Perry Kollmorgen June 7, 2024

June 7, 2024

Dear Mailman-users list, I have embarked on project to stand up a Mailman3 instance for general staff email announcements and a small number of adhoc lists. I have a fair amount up and working using Docker and Postfix, with generally emails to/from lists working well, as well as the web interface. One of the reasons I've used Mailman3 is the API and mailman shell options which I'm slowly trying to wrap my head around, but having some progress. I have a question for the moment on something which has stumped me, and whilst I may have more questions as I continue on this implementation, I am hopeful someone can point out where I am going wrong on this. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> >>> >>> from zope.interface import implementer >>> from mailman.interfaces.styles import IStyle >>> @implementer(IStyle) ... class TestStyle: ... name = 'AB-Announce-Style' ... description = 'AB Announce mailing list style.' ... def apply(self, mailing_list): ... mailing_list.admin_immed_notify = true ... mailing_list.admin_notify_mchanges = true ... mailing_list.advertised = false ... mailing_list.allow_list_posts = false ... mailing_list.anonymous_list = false ... mailing_list.archive_policy = "private" ... mailing_list.archive_rendering_mode = "markdown" ... mailing_list.collapse_alternatives = false ... mailing_list.convert_html_to_plaintext = false ... mailing_list.default_member_action = "defer" ... mailing_list.default_nonmember_action = "hold" ... mailing_list.digest_send_periodic = false ... mailing_list.digests_enabled = false ... mailing_list.emergency = false ... mailing_list.include_rfc2369_headers = true ... mailing_list.max_message_size = 40000 ... mailing_list.max_num_recipients = 30 ... mailing_list.member_roster_visibility = "moderators" ... mailing_list.send_goodbye_message = true ... mailing_list.send_welcome_message = true ... mailing_list.subscription_policy = "moderate" ... mailing_list.unsubscription_policy = "moderate" ... >>> manager.register(TestStyle()) >>> >>> commit() >>> >>> for style in manager.styles: ... print(style.name) ... AB-Announce-Style legacy-announce legacy-default private-default So at this point the style has been registered, however it doesn't look to save this permanently. When I quit the shell and log back in, it only shows the original 3 styles. Nor can I see the style from the web interface. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> Is there a way to save this style permanently ? Thank you for any assistance you can provide. Regards, PerryK

3 2

Mailman3 memory footprint
by Marc SCHAEFER June 6, 2024

June 6, 2024

Hello, It seems the mailman & mailman-web memory footprint are somewhat big. It looks a lot of instances are started. I have seen this: https://gitlab.com/mailman/mailman/-/issues/1050 and added this to the end of /etc/mailman3/mailman-web.py: Q_CLUSTER = { 'workers': 2, 'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5, } However, it does not seem to really reduce the memory footprint. Any other suggestions? Thank you.

2 1

Mailman3 doesn't send Mails to users (Debian12 with Plesk)
by marcus＠mbautze.de June 6, 2024

June 6, 2024

Hello, i already send this question to the plesk-forum but it seems that nobody there can help me :-( After updating from Debian 10 to 11 to 12, I now have mailman3 running on my server I then converted all lists from Mailman2 to Mailman3 following the instructions from mailman. I can access it via the web interface, manage everything etc. When I register on the web interface, I also receive the corresponding mails from Mailman (forgotten password...) Mails are also arriving, at least mails that are not allowed go into the mails to be approved. The problem, however, is that it does not send out any mails, nor do they appear in the archive. When I look in the Mailman-Log I find: May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost [Errno 111] Connection refused May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: [Errno 111] Connection refused The configuration of Mailman.cfg looks like this: incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 In Mailman manuals I find hints that the transport routes have to be added to the Postfix-config. Doesn't Debian/Plesk do this automatically? Does anyone else have an idea what I need to change to get my mails out? I did the conversion from mailman2 to mailman3 with root because it didn't work with "sudo -u list "m, but the files stored in the file system all belong to list, so that shouldn't be the problem.

9 25

Sending to mangled 'From' addresses.
by hansen June 5, 2024

June 5, 2024

All, Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. For example, say the mail client captures my address as “Allan Hansen via <listname>” <listaddress> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: “Allan Hansen via <listname>” and, to make it worse, the actual email address, <listaddress>, is often hidden. The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., "Allan Hansen via <listname>" In other words, filtering is done on the name part of the recipient, not the address part. Should I get onto the other list to request this as an enhancement? Yours, Allan

3 3

Sign and encrypt e-mail responses
by Markus Grandpré June 4, 2024

June 4, 2024

Dear List, is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 3

import21 detailed usage instructions in 2024
by Keith Christian June 3, 2024

June 3, 2024

1 Soon, I will be executing the first test imports from Mailman2.1 to Mailman3.9. 2 Planning to copy over the entire production Mailman2.1 to a new directory structure on the Mailman 3.9 machine. 3 Expecting that all .mbox and .pkl files will be present and no special work has to be done to bring them over will a "full" mailman2.1 copy. 4 Can the import21 program find the mailman2.1 .mbox and .pkl files on its own and process them? 5 Other than the mailman2.1 instance being shut down, any other prep that needs to be done? 6 Any special command line parameters to be aware of for import21? 7 Is there a list of troubleshooting steps for commonly encountered migration issues? Thanks. ------------------ Keith

2 1

import21 caused a few mails to be sent out
by Marc SCHAEFER June 2, 2024

June 2, 2024

Hello, After importing a (big > 3000 subscribers) list with import21, I noticed the following: 36 mails went out from LIST-NAME-bounces to subscribers, but they apparently all bounced. Could those be subscribers that Mailman2 saw bouncing and added the appropriate flag, and Mailman3 sent a probe after the import21? I checked for one of the e-mail address and: Mailman2: - that e-mail has the [X] R flag for "noncourriel" (no delivery) Mailman3: - that e-mail is Delivery mode Regular, Bounces to 0 NB: in MM2 and MM3, all users are in Hold for moderation, that's normal. In addition, there are a few mails in /var/lib/mailman/messages for example that same user: one file, showing a bounce from a remote server. So my questions: 1) is this behaviour to "probe" already disabled addresses normal, and not "port over" the "don't deliver"? 2) why are those messages held in messages/ ? 3) should I then, before running import21, clean the MM2 installation of all those users with [X] R flag? If yes, is there a simple command? Thank you for pointers or help. PS: there was no trafic on that imported mailing-list yet, it's a test.

2 1