- Mailman-users - lists.mailman3.org

Configure new list via REST API - trying to add moderators
by Andy Matthews 19 Sep '24

19 Sep '24

I'm stepping into some existing code which creates a new list via the REST API. I know this works because I can shell into the mailman3 box and run `mailman lists` and it shows the newly created list. We're also submitting list config options via the `/lists/<list id>/config` endpoint, but there's a specific key that we have in our config map that doesn't appear in the REST API docs and I'm wondering about it. We have an array of strings called `moderator` that appears to send successfully. But looking at the docs for "Mailing list configuration" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) I don't see anything named `moderator` The "Managing owners and moderators" docs (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…) indicate that we can perform add owners and moderators via a Python shell, but don't indicate that it's possible to do it via REST. Is this true?

2 7

Moving existing lists to a new domain
by Jeremy Stanley 19 Sep '24

19 Sep '24

I've moved lists and archives between domains in Mailman 2.1 and Pipermail, but not yet with Mailman 3 and Hyperkitty. I have a working multi-domain deployment, and one of the organizations using it is working on changing their domain name. Forwarding incoming messages at the MTA and setting up redirects on the Web server are simple enough, but internally within MM3/Django reside the bits I'm less certain about. Since all the lists for the given domain will be moving to the same unused new domain on the existing server, and can move at the same time, I suppose this could be done through (offline if necessary) backend database update queries. Is there anything outside the DB which would need updating or regenerating for this too? Is this how others have tackled similar tasks in the past, or is it recommended to export/import lists one at a time out of one domain and into another? Any tips are greatly appreciated! -- Jeremy Stanley

2 2

Default values for lists in Mailman 3
by Markus Grandpré 19 Sep '24

19 Sep '24

Dear list, I would like to activate the invitation setting for all lists as default. In Mailman 2.1 I have done this in the file </etc/mailman/mm_cfg.py>: DEFAULT_SUBSCRIBE_OR_INVITE = Yes How can I do this in Mailman 3? Can I also transfer other default values like: ... DEFAULT_SERVER_LANGUAGE = 'en' DEFAULT_SEND_REMINDERS = 1 DEFAULT_SUBSCRIBE_OR_INVITE = Yes DEFAULT_PRIVATE_ROSTER = 2 DEFAULT_ARCHIVE = Off DEFAULT_ARCHIVE_PRIVATE = 1 ... from the very same configuration file to Mailman 3? Is there a documentation of the default values for lists in Mailman 3? 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

1 0

Phantom Email Address in Nonmember List
by Steve Brown 18 Sep '24

18 Sep '24

Have an issue that is more of a puzzle than a problem. No real harm done. So don't spend much time on it if you don't recognize the issue. I am administrator for a small list, radg(a)lists.radg.us, hosted by Mailmanlists.net. They are trying hard to figure it out but so far unsuccessful. Looking at the headers of emails sent from steve(a)stevebrown.us to the list and boomeranged back to me, I see a line “X-MailFrom: bounce+66273f.99dcd9c-radg=lists.radg.us(a)stevebrown.xn--us-02t. I gather that it is designating the return path where a message would be sent if there was a delivery problem. From its position in the header, I suspect it is added as they pass through Mailgun, maybe related to DKIM. I am hoping you might know why that bounce address is recognized by Mailman 3 as a real address for my emails, but not for others, even from my wife’s computer traversing the same path from our home to the Mailman 3 server. The Mailman installation does get and process the post, but also puts the “bounce+,,,” address in its list of nonmembers. Mailmanlists.net hasn’t figured out the behavior. I can provide full header information if that would help. My understanding of how headers work is very limited. Steve Brown

2 5

mailman import21 passwords
by Sam Darwin 17 Sep '24

17 Sep '24

Hi, On https://docs.mailman3.org/en/latest/faq-migration.html it says "Mailman 3 has a completely new account management system, none of the passwords from Mailman 2 will work with Mailman 3. Each user needs to sign up in Postorius for a new account to manage their memberships on all lists on a single instance." "Each user needs to sign up in Postorius for a new account" I am (personally) satisfied with this answer. However others at the company are asking for a detailed explanation. Consider that - - Mailman2 has access to password information. - Import scripts such as "import21" are able to import list information. - It seems that scripts such as "import21" could also generate new user accounts and passwords based on the previous ones. Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? (is there a link to where this is already explained? ) Thanks

4 6

Required permissions for mass operations
by mailman3＠werner.by 15 Sep '24

15 Sep '24

Hi, I've Mailman 3.3.3 running with some mailing lists and it works great. Now I'm looking for a configuration option. I'd like to have some users with permission to - moderate lists AND - perform mass operations (add members, delete members) AND - change settings for single members (execute actions in menu point "Users", "Members") It should be impossible to change other list or mailman settings for this users. To give them the moderation permission is quite easy: I add the users to the moderators of the lists. But for the user management I've to add the users to the list owners and then is there no restriction anymore to change the full list configuration. What can I do? I link to a documentation for this would help as well, but I found nothing. Thanks a lot for an answer Torsten

2 1

Problem getting Mailman3 to work with Ubuntu 24.04.1 LTS
by sebensteg＠cod.edu 13 Sep '24

13 Sep '24

Hello everyone, We have been using Mailman3 for over a year and half. We upgraded from Ubuntu 22.04.5, where it was working fine, to Ubuntu 22.04.1. Since then, mailman3 won’t work. When we tried to start it immediately after the upgrade, we got this error: 024-09-12T23:08:04.322353+00:00 weather1 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... 2024-09-12T23:08:04.935569+00:00 weather1 mailman[23628]: SystemError: type psycopg2.extensions.ReplicationConnection has the Py_TPFLAGS_HAVE_GC flag but has no traverse function 2024-09-12T23:08:04.942784+00:00 weather1 mailman[23628]: The above exception was the direct cause of the following exception: 2024-09-12T23:08:04.942869+00:00 weather1 mailman[23628]: Traceback (most recent call last): 2024-09-12T23:08:04.942938+00:00 weather1 mailman[23628]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> 2024-09-12T23:08:04.943001+00:00 weather1 mailman[23628]: sys.exit(main()) 2024-09-12T23:08:04.943123+00:00 weather1 mailman[23628]: ^^^^^^ 2024-09-12T23:08:04.943188+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1157, in __call__ 2024-09-12T23:08:04.943242+00:00 weather1 mailman[23628]: return self.main(*args, **kwargs) 2024-09-12T23:08:04.943284+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943325+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1077, in main 2024-09-12T23:08:04.943449+00:00 weather1 mailman[23628]: with self.make_context(prog_name, args, **extra) as ctx: 2024-09-12T23:08:04.943508+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943553+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 943, in make_context 2024-09-12T23:08:04.943594+00:00 weather1 mailman[23628]: self.parse_args(ctx, args) 2024-09-12T23:08:04.943753+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1644, in parse_args 2024-09-12T23:08:04.943799+00:00 weather1 mailman[23628]: rest = super().parse_args(ctx, args) 2024-09-12T23:08:04.943867+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943911+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1408, in parse_args 2024-09-12T23:08:04.943952+00:00 weather1 mailman[23628]: value, args = param.handle_parse_result(ctx, opts, args) 2024-09-12T23:08:04.944001+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944043+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 2400, in handle_parse_result 2024-09-12T23:08:04.944085+00:00 weather1 mailman[23628]: value = self.process_value(ctx, value) 2024-09-12T23:08:04.944127+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944182+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 2362, in process_value 2024-09-12T23:08:04.944249+00:00 weather1 mailman[23628]: value = self.callback(ctx, self, value) 2024-09-12T23:08:04.944293+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944335+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", line 95, in initialize_config 2024-09-12T23:08:04.944376+00:00 weather1 mailman[23628]: initialize(value) 2024-09-12T23:08:04.944419+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/core/initialize.py", line 229, in initialize 2024-09-12T23:08:04.944460+00:00 weather1 mailman[23628]: initialize_2(propagate_logs=propagate_logs) 2024-09-12T23:08:04.944518+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/core/initialize.py", line 187, in initialize_2 2024-09-12T23:08:04.944561+00:00 weather1 mailman[23628]: config.db = getUtility(IDatabaseFactory, utility_name).create() 2024-09-12T23:08:04.944603+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944708+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/database/factory.py", line 57, in create 2024-09-12T23:08:04.944769+00:00 weather1 mailman[23628]: database.initialize() 2024-09-12T23:08:04.944856+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/database/base.py", line 117, in initialize 2024-09-12T23:08:04.944899+00:00 weather1 mailman[23628]: self.engine = create_engine( 2024-09-12T23:08:04.944941+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944982+00:00 weather1 mailman[23628]: File "<string>", line 2, in create_engine 2024-09-12T23:08:04.945025+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned 2024-09-12T23:08:04.945070+00:00 weather1 mailman[23628]: return fn(*args, **kwargs) # type: ignore[no-any-return] 2024-09-12T23:08:04.945112+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.945165+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/create.py", line 599, in create_engine 2024-09-12T23:08:04.945208+00:00 weather1 mailman[23628]: dbapi = dbapi_meth(**dbapi_args) 2024-09-12T23:08:04.945249+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.945291+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi 2024-09-12T23:08:04.945332+00:00 weather1 mailman[23628]: import psycopg2 2024-09-12T23:08:04.945374+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/psycopg2/__init__.py", line 51, in <module> 2024-09-12T23:08:04.945425+00:00 weather1 mailman[23628]: from psycopg2._psycopg import ( # noqa 2024-09-12T23:08:04.945478+00:00 weather1 mailman[23628]: SystemError: initialization of _psycopg raised unreported exception 2024-09-12T23:08:05.071429+00:00 weather1 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE 2024-09-12T23:08:05.071768+00:00 weather1 systemd[1]: mailman3.service: Failed with result 'exit-code'. 2024-09-12T23:08:05.072429+00:00 weather1 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. So, ultimately, what we decided to do was reinstall it. But the compilation fails when it tries to make a venv (virtual environment) with this error: 2024-09-12T23:08:04.322353+00:00 weather1 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... 2024-09-12T23:08:04.935569+00:00 weather1 mailman[23628]: SystemError: type psycopg2.extensions.ReplicationConnection has the Py_TPFLAGS_HAVE_GC flag but has no traverse function 2024-09-12T23:08:04.942784+00:00 weather1 mailman[23628]: The above exception was the direct cause of the following exception: 2024-09-12T23:08:04.942869+00:00 weather1 mailman[23628]: Traceback (most recent call last): 2024-09-12T23:08:04.942938+00:00 weather1 mailman[23628]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> 2024-09-12T23:08:04.943001+00:00 weather1 mailman[23628]: sys.exit(main()) 2024-09-12T23:08:04.943123+00:00 weather1 mailman[23628]: ^^^^^^ 2024-09-12T23:08:04.943188+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1157, in __call__ 2024-09-12T23:08:04.943242+00:00 weather1 mailman[23628]: return self.main(*args, **kwargs) 2024-09-12T23:08:04.943284+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943325+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1077, in main 2024-09-12T23:08:04.943449+00:00 weather1 mailman[23628]: with self.make_context(prog_name, args, **extra) as ctx: 2024-09-12T23:08:04.943508+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943553+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 943, in make_context 2024-09-12T23:08:04.943594+00:00 weather1 mailman[23628]: self.parse_args(ctx, args) 2024-09-12T23:08:04.943753+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1644, in parse_args 2024-09-12T23:08:04.943799+00:00 weather1 mailman[23628]: rest = super().parse_args(ctx, args) 2024-09-12T23:08:04.943867+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.943911+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1408, in parse_args 2024-09-12T23:08:04.943952+00:00 weather1 mailman[23628]: value, args = param.handle_parse_result(ctx, opts, args) 2024-09-12T23:08:04.944001+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944043+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 2400, in handle_parse_result 2024-09-12T23:08:04.944085+00:00 weather1 mailman[23628]: value = self.process_value(ctx, value) 2024-09-12T23:08:04.944127+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944182+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/click/core.py", line 2362, in process_value 2024-09-12T23:08:04.944249+00:00 weather1 mailman[23628]: value = self.callback(ctx, self, value) 2024-09-12T23:08:04.944293+00:00 weather1 mailman[23628]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-09-12T23:08:04.944335+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", line 95, in initialize_config 2024-09-12T23:08:04.944376+00:00 weather1 mailman[23628]: initialize(value) 2024-09-12T23:08:04.944419+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/core/initialize.py", line 229, in initialize 2024-09-12T23:08:04.944460+00:00 weather1 mailman[23628]: initialize_2(propagate_logs=propagate_logs) 2024-09-12T23:08:04.944518+00:00 weather1 mailman[23628]: File "/home/mailman/venv/lib/python3.12/site-packages/mailman/core/initialize.py", line 187, in initialize_2 2024-09-12T23:08:04.944561+00:00 weather1 mailman[23628]: config.db = getUtility(IDatabaseFactory, utility_name).create() But yet, we have this installed: venv mailman@weather1:~$ pip install psycopg2-binary Requirement already satisfied: psycopg2-binary in ./venv/lib/python3.12/site-packages (2.8.6) Any advice on how to get this working again would be GREATLY appreciated! Gilbert Sebenste Meteorology Support Analyst College of DuPage

4 7

Disabled by bounce
by Allan Hansen 11 Sep '24

11 Sep '24

Hi all, Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yours, Allan

10 19

Trying to understand the mailman.cfg from the virtualenv installation guide
by unite42＠disroot.org 11 Sep '24

11 Sep '24

Hello, I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended. Especially the following two: [archiver.prototype] enable: yes "The prototype archiver stores messages individually in var/archives/prototype/LIST_NAME/." https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Do I need this, when using hyperkitty? Is this a fail-safe recommendation? [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 What is the background of these recommendations? Thank you for your help! Greetings unite42

4 4

Recipient address rejected: User unknown in local recipient table
by eyoelz＠gmail.com 11 Sep '24

11 Sep '24

Hi, I set up mailman3 following the instruction on the mailman3 website. Everything went well until I got to the “Hooking up your mail server” at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… . I followed the instructions, but when I try to send an email to one of the lists I created, I get the error below. I have postfix installed on the same server as mailman3. I was wondering if I missed something during the mail server set up process. Relevant parts of my config files are below. Error: Aug 19 15:06:10 xxx-rocky9 postfix/smtpd[153746]: NOQUEUE: reject: RCPT from xxxx.xxxxxx-xx.iphmx.com[xx.x.xx.xxx]: 550 5.1.1 <devops(a)xxx.xxx.edu>: Recipient address rejected: User unknown in local recipient table; from=<xxx(a)xxxx.edu> to=<xxx(a)xx.xx.edu> proto=ESMTP helo=<xx.xx-xx.iphmx.com> mailman.cfg [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no mailman/config/postfix.cfg [postfix] postmap_command: /usr/sbin/postmap transport_file_type: hash main.cf smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = xxx.xxx.edu alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = $myhostname, mailman, localhost.localdomain, , localhost relayhost = [xx.xx.xx.xx] mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 recipient_delimiter = + inet_interfaces = all inet_protocols = all transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps =$alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Thanks, Eyoel Mengesha

3 2