- Mailman-users - lists.mailman3.org

CSV import for mass subscription
by Markus Grandpré Sept. 20, 2024

Sept. 20, 2024

Dear list, we noticed that there is a function to convert the member list into a CSV format and save it.Therefore, we would like to know if the implementation of a CVS import for mass subscription is already planned? If not, how can we submit a corresponding feature request? 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 5

Questions regarding message acceptance
by Pawel Grzywaczewski Sept. 19, 2024

Sept. 19, 2024

Hello, I have few questions regarding usage of Mailman3: 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? We could potentially write a script that would synchronize members of another list to “Accept these non-members” of another list, but with thousands of lists it will be difficult to maintain lists in synchro. So perhaps there is a concept of adding another list to “Accept these non-members” and mailman real-time evaluate membership of another list upon message arrival? 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? Thank you, Paweł

5 7

Configure new list via REST API - trying to add moderators
by Andy Matthews Sept. 19, 2024

Sept. 19, 2024

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

Phantom Email Address in Nonmember List
by Steve Brown Sept. 18, 2024

Sept. 18, 2024

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 Sept. 17, 2024

Sept. 17, 2024

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 Sept. 15, 2024

Sept. 15, 2024

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 Sept. 13, 2024

Sept. 13, 2024

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 Sept. 11, 2024

Sept. 11, 2024

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 Sept. 11, 2024

Sept. 11, 2024

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 Sept. 11, 2024

Sept. 11, 2024

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

Best practice when deleting a mailing-list (archiving an old list)
by Marc SCHAEFER Sept. 10, 2024

Sept. 10, 2024

Hello, With Mailman2, my list deletion procedure was quite simple: - export the list configuration with config_list - export the list members - archive the archives somewhere - remove the aliases manually - delete the list I think that with Mailman3, the above can be done as follows: - export the list configuration with https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - export the list members with https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… - archive the archives somewhere: this is my main question - remove the aliases manually: this is automatic - delete the list So, is there a simple way to export a list's archives in a way it can be reimported, now that everything seems to be in the database? Archiving the whole database is an issue here (its compressed dump size > 2 GB). Thank you for your ideas or pointers!

2 1

Mass Subscribe caused Delivery Status to become "unset"
by chad.hays86＠gmail.com Sept. 9, 2024

Sept. 9, 2024

One of the admins on our Mailman site said they recently performed a mass subscribe operation on list, however they noticed that for each user they subscribed, their "Delivery status" was unset, so they weren't receiving email updates whenever there was new activity on the list. They had to go in after the fact and manually set it to "Enabled" for each user that was subscribed via the mass subscription operation. Is this behavior expected? During the mass subscribed, pre-confirm, pre-approved, and pre-verified checkboxes were all checked.

3 3

It takes a very long time to display the list archives
by bryan.kartzman＠yu.edu Sept. 9, 2024

Sept. 9, 2024

When I try to display the archives of any list in my mailman3 installation it takes forever for it to display. We are talking a good three or four minutes. It doesn't matter if there are 100 messages in the archives or just one. We are using postgres for the mailman3 and django databases. On the server, when I click to display a list's archives, I see the process "gunicorn: worker [gunicorn]" is using nearly 100% of available CPU.

1 0

when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented
by Ken Alker Sept. 9, 2024

Sept. 9, 2024

We have been experiencing a strange anomaly. We are running a small-ish list. When a particular subscriber to the list sends an email to the list, a couple of dozen (or more) of the recipient's of the message end up with their bounce scores incrementing. This particular subscriber uses about three different email addresses when he sends his messages and every one of them causes this behavior. There is another subscriber who also causes this behavior when he sends an email to the list, but only one of the two email addresses he sends from causes this behavior. There is a third person who causes this behavior every time. There are dozens of other subscribes who don't generate this behavior when they send to the list. I can't figure out why this is occurring. I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients but it sure seems like something in the header from the original sender is ending up in the final header (or something is LACKING) which is not liked by the recipient's MTA's. It doesn't seem like a subscriber sending an email to the list should be able to cause this behavior - but I'm no expert. The recipients appear to be using many different mail platforms (ie. their addresses are not all, or even mostly, @google.com or some other domain; the recipients appear to be a pretty good cross section of platforms). This has been going on all year (maybe longer). Any help or troubleshooting suggestions would be greatly appreciated.

5 9

How to tell which lists on my server are being used?
by Bryan Kartzman Sept. 8, 2024

Sept. 8, 2024

Is there an easy way to tell which lists on my Mailman 3 installation are being used (i.e. received posts in the last two or three months)?

4 4

Setting base_url for the domain to use it in the templates.
by Timour Bakeev Sept. 8, 2024

Sept. 8, 2024

Hi all! I'm trying to use extended placeholders for the [templated texts](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/res… in the message footer that are sent to the members: > Along with these, Mailman supports placeholder as URLs for web interface when `base_url` property is set at the Domain level. These include: > domain_url - URL to homepage for a domain. > mailinglist_url - URL to homepage for a mailinglist. > held_message_url - URL to page for handling all held messages. > pending_subscriptions_url - URL to page for handling pending subscription requests. > pending_unsubscriptions_url - URL to page for handling pending unsubscriptions. The REST API docs mention `base_url` as the property of the domain: [domain URLs](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest… But my attempts to use REST API to set it fail: ``` curl --user 'restapi:restpass' \ -X PATCH \ -H "Content-Type: application/json" \ -H 'Accept: application/json' \ -d '{ "base_url": "https://example.net/mailman3" }' \ http://localhost:8001/3.1/domains/example.net | jq '.' { "title": "400 Bad Request", "description": "Unexpected parameters: base_url" } ``` My MM3 instance is the latest(3.3.9), provided by the maxking mailman-core docker image. It looks like there is a lot of confusion about `base_url` in general, as hyperkitty seems also use the property with the same name, for example: https://lists.mailman3.org/hyperkitty/list/mailman-users@mailman3.org/threa… So what is the correct way to get those extended placeholders to work in the templates? It's also not clear to me, what the the primary domain should be for the installation - server hostname, as in `lists.mailman3.org` or the domain, used in the mailing list(s) itself, like `mailman3.org` for mailman-users(a)mailman3.org... With best regards, Timour Bakeev

4 6

Archive not updated
by mailman3＠escapade.ch Sept. 6, 2024

Sept. 6, 2024

Hi All, Env: Debian bookworm debian pkg mailman 3.3.8-2~deb12u2 Status I moved from MM2 to MM3 Import of the archives worked, no issue problem: current emails sent to the list are not being archived. What have I done: - based on the list here I've checked different settings in the cfg files - looked for errors in the log What else can I do to solve this problem ? Many thanks in advance for your help. Manny

3 2

Can you use @list to include members in accept these non-members in v3?
by Lieuallen, Thomas Otis Sept. 5, 2024

Sept. 5, 2024

In Mailman v2, one could use @listname in ‘accept_these_nonmembers’: A line consisting of the @ character followed by a list name specifies another Mailman list in this installation, all of whose member addresses will be accepted for this list. I don’t see this option listed in version 3. Is it no longer supported/allowed? Is there another option? We often send email to lists of lists and have loved that @listname option to help us deliver email to 20+ lists without needing to approve the emails each time or reconfigure all the lists when another sender needs to be added. Thank you Tom Lieuallen Oregon State University

3 4

security app causing django Internal Server Error: /archives/search emails
by sun zi Sept. 5, 2024

Sept. 5, 2024

Greetings, I have set up a few lists and all seems to be working as expected, however I get a large number of emails due to internal server errors received when my security application is testing exploits to list URLs such as the following: https://<mylistdomain>/archives/search?sort=177120&cauft=&page=1&q=../../../../../../../../../../tmb/wditeteet424465304.txt. Is there any django logging filter changes that can be made to avoid receiving these emails? Any assistance would be greatly appreciated. Thank you!

3 3

Assistance Needed for Ubuntu 22.04 Mailman3 Installation and Configuration
by smiithjohn90＠gmail.com Aug. 31, 2024

Aug. 31, 2024

Hello Everyone, I'm trying to install Mailman3 on an Ubuntu 22.04 server right now, and I've run across a few obstacles that I'd like help with. I've followed the installation instructions, but I'm having trouble in a couple places, so I was hoping an experienced someone might help me out. This is what I have completed thus far: - I used the apt-get package manager to install Mailman3. - PostgreSQL was configured as the database backend. - Postfix was installed and set up to function as the Mail Transfer Agent (MTA). - Assemble Postorius, Hyperkitty, and the Mailman3 core. Problems I'm Having: Postorius and Hyperkitty Connectivity: I'm having problems making sure that the Mailman core is correctly connected to Postorius and Hyperkitty. I get a 502 Bad Gateway error when I try to access the web interfaces. Despite checking my specifications, I am unable to identify the problem. Problems with Email Delivery: I'm also having trouble with email delivery. Although Mailman appears to be receiving emails, it is not appearing to be sending any out. I think there might be a Postfix problem, but I'm not sure how to solve it. Generally Suggested Practices: Are there any particular security best practices I should be aware of when it comes to Mailman3 installations? I want to confirm that my configuration is both performance- and security-optimized. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://www.igmguru.com/salesforce/salesforce-developer-training https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I would be grateful for any advice or resources! It would be really beneficial if someone with a similar setup could share their settings or troubleshooting procedures. Thank you in advance.

2 1

Dist. List forwarding and DMARC Reject circumvention. Will this pattern work?
by titan160＠hotmail.com Aug. 26, 2024

Aug. 26, 2024

I would be grateful if someone could vet and verify (or guide otherwise) the following pattern please. With the major mail vendors move to DMARC - Full Reject, I have a small challenge. - We have a number of 365 Distribution List addresses. - These lists accept email from anyone and, currently, then forward those emails onto list members. - List members, however, are NOT necessarily email addresses within the list's mail domain. They might be outlook.com, Gmail, yahoo, Hotmail, username(a)local.ISP. Consequently, DMARC Reject policies are causing these emails to be marked spam as the 365 Dist. List forwarding is not doing any header manipulation. My thinking is: - I could set up a Mailman list (elists.mydomain.com) alongside the 365 Exchange mail domain (mydomain.com) - I leave inbound mail deliver to the 365 Dist. lists. - I reconfigure the (mylist(a)mydomain.com) Dist. Lists to fwd to a similarly-named Mailman address at the email sub-domain (mylist(a)elists.mydomain.com) - The Mailman list, by virtue of having to use the 365 MTA, should be able to accept all inbound from the list (mylist(a)mydomain.com) - Mailman would then need to re-write the mail headers such that the inbound email to-be-forwarded from the Mailman list, both appears to come from the (mylist(a)mydomain.com) address, and also has the 365 'mydomain.com' SPF and DKIM records. And given Mailman has to use the 365 MTA, it would actually be coming from that main mail domain. - Somewhere in there, the original sender's email address would need to be included, such that a Reply-to-All from a receiving List member would not only go back to the List, but also the original sender. My thinking is that with this pattern, I don't need to worry about inbound emails to the list address as that would simply continue to function as normal, and fwdd mails from the List to recipient list members would not be marked spam as the headers would all be good. Is my thinking good? Or am I out of my cotton-pickin' mind?

2 1

Issue with mailman auto subscription
by Francisco Paco López Aug. 26, 2024

Aug. 26, 2024

Hello, I migrated my mailman 2 instance to mailman 3 some months ago. Some users have been reporting lately that auto subscriptions don't work anymore. In the affected list both the Subscription and un subscription policies are open, which means that normally a user that sends a "subscribe" mail automatically subs to the list. This works fine for users that have been subscribed in the past but not for new users. The latter get a mail stating that a confirmation is needed ("Your confirmation is needed to join the XXXX(a)my.lists.com mailing list"). I see nothing out of the ordinary in the mailman.log file and co. Any ideas? Thanks a lot in advance [SIB logo] Francisco López Ayuso System Administrator SIB | Swiss Institute of Bioinformatics Quartier Sorge, bâtiment Amphipôle - CH 1015 Lausanne - Switzerland t +41 21 692 40 36 Francisco.Lopezayuso(a)sib.swiss - www.sib.swiss The information in this e-mail, and those ensuing, is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please destroy this message and notify the sender immediately.

2 1

Mailman config is not being applied
by roberto.blandino＠ibw.com.ni Aug. 26, 2024

Aug. 26, 2024

Debian: 11.10 GNU Mailman 3.3.3 (Tom Sawyer) Server version: Apache/2.4.61 (Debian) PHP 7.4.33 (cli) (built: Apr 12 2024 00:02:16) ( NTS ) I have a list and when i add a no member on the web interface and on the Non-Member options i set "Administration options" to "Accept skip other rules" when i send email from that address it keeps being moderated and when i open again the options it keeps saying "Default by list" The options are not being write on changes

2 1

systemd unit file modification: start / stop both services at once
by Ron / BCLUG Aug. 24, 2024

Aug. 24, 2024

Hi, I've made a slight adjustment to my systemd unit files for Mailman3 such that I only ever need to start / restart / stop mailman3.service and mailman3-web.service will have the same action automatically applied to it. It's called `Upholds` and binds the 2 services together. I humbly suggest it become the default. In my case, I added a file here: /etc/systemd/system/mailman3.service.d/override.conf with these lines: [Unit] Upholds = mailman3-web.service Before = mailman3-web.service Now, starting mailman3.service will *also* start mailman3-web.service. Restarting mailman3.service will *also* restart mailman3-web.service. Stopping mailman3.service will *also* stop mailman3-web.service. Those 3 lines could be placed in mailman3.service, or something like `UpheldBy=mailman3.service` could go in the mailman3-web.service. Hopefully this would make things slightly better for Mailman3 admins out there. rb

1 0

502 bad gateway when unsubscribing users
by laura_thomas＠fas.harvard.edu Aug. 22, 2024

Aug. 22, 2024

Hi everyone, I moderate several email lists for a university using Postorius 1.3.4.1. I've been trying to update our lists by removing members who have left the department. However, when I click on a name and then "Unsubscribe Selected," I always get a 502 Bad Gateway message, and I'm unable to remove any users from the list. This has happened on every attempt across multiple users on multiple mailing lists. Does anyone know what might be going on? I appreciate the help!

2 1

Could You Please Guide Me As A Newbie?
by smiithjohn90＠gmail.com Aug. 21, 2024

Aug. 21, 2024

Hello, everyone! This is my first post after just joining this discussion, so please forgive me and provide kind assistance if I have posted in the wrong subsection! I am new here but a real enthusiast and loving this community so far. I have a background in teaching coding and education, and I feel I could help with documentation, at least for starters. As a new member of this forum, I wish to share and gain some knowledge. I am looking forward to creating my own discussions to resolve my queries and gain more insights. I have participated in various discussions, which have definitely helped me a lot. Also, what factors should be considered when choosing the appropriate category for a post? Thank you in advance.

1 0

trying to understand ARC
by Johannes Rohr Aug. 18, 2024

Aug. 18, 2024

Dear all, I'm confused about how to enable ARC signing and how it is related to DKIM. As it stands, the contents of the section [ARC] in mailmain.cfg are [ARC] enabled: yes authserv_id: *******.org # Should this be the address of the mailserver (postfix) instead? privkey: /etc/mailman3/***.org.mailman.key # Shouldn't this point to the same private key used by rspamd for DKIM signing? selector: mailman # shouldn't this point to the same selector as rspam, or should it be separate? If so, should I also set up a separate TXT entry domain: ****.org # mailman serves multiple domains. Should all be there? Should the exact subdomain be there? Finally, how come that at present, mailman does NOT sign the messages? They come with the original DKIM signature, but there is no ARC signature. Unfortunately, the official documentation says very little about ARC, so I have to post my possibly stupid questions here. Johannes

1 1

Legit login attempts yield, "An error occurred while processing your request."
by Greg Newby Aug. 14, 2024

Aug. 14, 2024

Hi friends. Following up on my message over the weekend about getting web (Django) logins for users who were ported from MM2 to MM3, I now have some people trying to create a new username. Something broke following a system update and reboot. MM3 is installed using the venv method, and the services (mailman and mailman-web) seem to be running ok. Mailing list delivery is happening as usual. I've now come upon a few related situations where a 500 error results, "Server error. An error occurred while processing your request." My primary question is: *How can I find out what's causing this*? I've looked in all the MM and web logfiles, by "tail -f" while generating the error, and nothing is logged there. Apache logs shows something like this: x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" I've come across this error while trying to do authentication-related activities that worked before the reboot: - "Forgot password" (happens whether or not the entered email existed in MM2 or already exists in MM3) - Sign up (ditto) - Email unsubscribes gave a verification email, but then didn't unsubscribe the address (might not be the same problem) Thanks for any breadcrumbs that might guide me to the solution. ~ Greg

2 1

Several Postorius errors over the weekend
by Andrew Hodgson Aug. 14, 2024

Aug. 14, 2024

Hi. I've had several Postorius error messages which have resulted in an email. Is this someone up to mischief or have I missed a configuration somewhere? We had several of these over a short period and nothing since then which makes me think someone was running a script on the endpoint, but would be interested in confirmation from those that know better. Thanks. Andrew. Internal Server Error: /accounts/login/ TemplateDoesNotExist at /accounts/login/ 429.html Request Method: HEAD Request URL: http://lists.hodgsonfamily.org/accounts/login/?next=%2F%61%63%63%6F%75%6E%7… Django Version: 4.2.13 Python Executable: /opt/mailman/venv/bin/python3 Python Version: 3.12.3 Python Path: ['/opt/mailman', '/', '/opt/mailman/venv/bin', '/etc/mailman3', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/opt/mailman/venv/lib/python3.12/site-packages', '/usr/local/lib/python3.12/dist-packages', '/usr/lib/python3/dist-packages', '/etc/mailman3'] Server time: Fri, 09 Aug 2024 15:32:41 +0000 Installed Applications: ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] Installed Middleware: ('allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Template loader postmortem Django tried loading these templates, in this order: Using engine django: This engine did not provide a list of tried templates. Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/views/generic/base.py", line 104, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/utils/decorators.py", line 46, in _wrapper return bound_method(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/allauth/decorators.py", line 10, in wrap resp = ratelimit.consume_or_429(request, action=action, **rl_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/allauth/core/ratelimit.py", line 140, in consume_or_429 return handler429(request) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/allauth/core/ratelimit.py", line 125, in _handler429 return render(request, "429." + app_settings.TEMPLATE_EXTENSION, status=429) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/template/loader.py", line 61, in render_to_string template = get_template(template_name, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/django/template/loader.py", line 19, in get_template raise TemplateDoesNotExist(template_name, chain=chain) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Exception Type: TemplateDoesNotExist at /accounts/login/ Exception Value: 429.html Raised during: allauth.account.views.LoginView Request information: USER: AnonymousUser GET: next = '/accounts/login//**/AND/**/(SELECT/**/DIFFERENCE(NULL,NULL))/**/IS/**/NULL--/**/CiLH' POST: No POST data FILES: No FILES data COOKIES: csrftoken = '********************' META: CSRF_COOKIE = 'ArmbEBfvw1lQgbvFKczV9km53k5UFC6G' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip' HTTP_CONNECTION = 'close' HTTP_COOKIE = '********************' HTTP_HOST = 'lists.hodgsonfamily.org' HTTP_USER_AGENT = 'Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110303 Ubuntu/10.04 (lucid) Firefox/3.6.15 FirePHP/0.5' HTTP_X_FORWARDED_FOR = '141.98.255.143' PATH_INFO = '/accounts/login/' QUERY_STRING = 'next=%2F%61%63%63%6F%75%6E%74%73%2F%6C%6F%67%69%6E%2F%2F%2A%2A%2F%41%4E%44%2F%2A%2A%2F%28%53%45%4C%45%43%54%2F%2A%2A%2F%44%49%46%46%45%52%45%4E%43%45%28%4E%55%4C%4C%2C%4E%55%4C%4C%29%29%2F%2A%2A%2F%49%53%2F%2A%2A%2F%4E%55%4C%4C%2D%2D%2F%2A%2A%2F%43%69%4C%48' RAW_URI = '/accounts/login/?next=%2F%61%63%63%6F%75%6E%74%73%2F%6C%6F%67%69%6E%2F%2F%2A%2A%2F%41%4E%44%2F%2A%2A%2F%28%53%45%4C%45%43%54%2F%2A%2A%2F%44%49%46%46%45%52%45%4E%43%45%28%4E%55%4C%4C%2C%4E%55%4C%4C%29%29%2F%2A%2A%2F%49%53%2F%2A%2A%2F%4E%55%4C%4C%2D%2D%2F%2A%2A%2F%43%69%4C%48' REMOTE_ADDR = '127.0.0.1' REMOTE_PORT = '35918' REQUEST_METHOD = 'HEAD' SCRIPT_NAME = '' SERVER_NAME = '127.0.0.1' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' SERVER_SOFTWARE = 'gunicorn/22.0.0' gunicorn.socket = <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 8000), raddr=('127.0.0.1', 35918)> wsgi.errors = <gunicorn.http.wsgi.WSGIErrorsWrapper object at 0x7dddf0dddf60> wsgi.file_wrapper = <class 'gunicorn.http.wsgi.FileWrapper'> wsgi.input = <gunicorn.http.body.Body object at 0x7dddf0dde540> wsgi.input_terminated = True wsgi.multiprocess = False wsgi.multithread = False wsgi.run_once = False wsgi.url_scheme = 'http' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'andrew(a)hodgson.io'),)" ALLOWED_HOSTS = ['localhost', 'lists.hodgsonfamily.org'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = PosixPath('/opt/mailman/web') CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7dddf3f61440> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_MANIFEST_STORAGE = 'compressor.storage.OfflineManifestFileStorage' COMPRESS_OFFLINE_MANIFEST_STORAGE_ALIAS = 'compressor-offine' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/opt/mailman/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_STORAGE_ALIAS = 'compressor' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL = '/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_MASKED = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = ['https://lists.hodgsonfamily.org'] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'CONN_HEALTH_CHECKS': False, 'OPTIONS': {}, 'TIME_ZONE': None, 'PORT': '', 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATA_UPLOAD_MAX_NUMBER_FILES = 100 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' DEFAULT_CHARSET = 'utf-8' DEFAULT_EXCEPTION_REPORTER = 'django.views.debug.ExceptionReporter' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'postorius(a)lists.hodgsonfamily.org' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = 420 FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/opt/mailman/web/fulltext_index'}} HYPERKITTY_ENABLE_GRAVATAR = True IGNORABLE_404_URLS = [] INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ar-dz', 'Algerian Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('ckb', 'Central Kurdish (Sorani)'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('ig', 'Igbo'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('ky', 'Kyrgyz'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('ms', 'Malay'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('tg', 'Tajik'), ('th', 'Thai'), ('tk', 'Turkmen'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'ar-dz', 'ckb', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.TimedRotatingFileHandler', 'filename': '/opt/mailman/web/logs/mailmanweb.log', 'formatter': 'verbose', 'when': 'midnight', 'backupCount': 5}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}, 'q': {'level': 'WARNING', 'propagate': False, 'handlers': ['console', 'file']}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '/' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' PREPEND_WWW = False Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default', 'workers': 2} ROOT_URLCONF = 'mailman_web.urls' SECRET_KEY = '********************' SECRET_KEY_FALLBACKS = '********************' SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_CROSS_ORIGIN_OPENER_POLICY = 'same-origin' SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = 'same-origin' SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'postorius(a)lists.hodgsonfamily.org' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.JSONSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [{'id': 'yahoo', 'name': 'Yahoo', 'openid_url': 'http://me.yahoo.com'}]}, 'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'facebook': {'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': ['email', 'name', 'first_name', 'last_name', 'locale', 'timezone'], 'VERSION': 'v2.4'}} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/opt/mailman/web/static' STATIC_URL = '/static/' STORAGES = {'default': {'BACKEND': 'django.core.files.storage.FileSystemStorage'}, 'staticfiles': {'BACKEND': 'django.contrib.staticfiles.storage.StaticFilesStorage'}} TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_DEPRECATED_PYTZ = False USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = False USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'mailman_web.wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y'

2 1

Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save
by Henrik Rasmussen Aug. 14, 2024

Aug. 14, 2024

I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? I am currently using Postorius Version 1.3.5 and HyperKitty version 1.3.4. /Henrik

2 1

RDS CA changes
by Hirayama, Pat Aug. 12, 2024

Aug. 12, 2024

Hello, So, my Mailman3 installation (inherited – guy who set it up has left) is using PostgreSQL that is an AWS RDS instance. I have received an alert from AWS that the CA certificate used to create the database is expiring, and they want me to update the certificate before it expires: "Update Your Amazon RDS and Amazon Aurora SSL/TLS Certificates by August 22, 2024 " https://aws.amazon.com/blogs/aws/rotate-your-ssl-tls-certificates-now-amazo… Our DBA team is requesting that we update applications by installing the new CA within the application's certificate store. As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end? Thank you! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

2 2

Removing all moderatortors (and owners) from a list in one go
by Henrik Rasmussen Aug. 12, 2024

Aug. 12, 2024

As there doesn't seem to be a "Disable list" REST call (not an "export list" REST call, I am trying to remove all members, moderators and owners, changing list description etc. I managed to remove all members from a list in one go using https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…, but the same command, using /roster/moderator does not apply for moderators (now owners I guess). To me it seems that each moderator has to be removed one by one, either: * using REST https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… * or using the client https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… * or using Python https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Isn't there an easier way? And why not like https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… ? /Henrik

2 1

User cannot reset password
by Greg Newby Aug. 11, 2024

Aug. 11, 2024

I imported MM2.1 lists to Mailman3 (using import21 - details are in my previous messages to mailman-users), and have had a couple of reports of people for whom the password reset function via "Forgot password" on the list login screen doesn't work as expected. This is a venv installation using PostgreSQL as the database: $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Jul 31 2024, 17:43:48) [GCC 13.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:redacated@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:redacted The user selects "Forgot password" and enters their email - which I've confirmed is subscribed and receiving messages. They get this email: You are receiving this email because you, or someone else, tried to access an account with email redactaed(a)gmail.com. However, we do not have any record of such an account in our database. This mail can be safely ignored if you did not initiate this action. If it was you, you can sign up for an account using the link below. I looked in the PostgreSQL address table and confirmed the entry is there, and also of course looked at the Members list in the web-based front end. Everything looks ok. I suspect that lots of people will have the same problem, but have not yet tried to login & reset their password. The earlier reports indicated that people's saved passwords did not work, but I haven't replicated that. Any advice on what's going on and how to address it? I've migrated over 200 lists with thousands of users, so would rather not need to deal with every user via the web-based front end. But at this point I don't even know what to try to fix things. With the previous reports I unsubscribed the user and had them resubscribe - that worked as expected but required back-and-forth discussion and, more importantly, user inconvenience. Thanks, Greg Newby

2 3

Python program to create lists and import settings from Mailman 2 to Mailman 3
by Greg Newby Aug. 10, 2024

Aug. 10, 2024

Hi friends. A couple of weeks ago I asked for help with calling Mailman functions from within a Python program. This was to avoid using the web interface or shell commands to create a new list from a legacy Mailman 2.x list, and instead do it from within a Python program. Here is the program I ended up using, and I thought it would be worthwhile to get into the Mailman users list archives for future folks. Note that this is for the (recommended) venv installation of Mailman. Some things might be different for other installations. I'll paste the program and also attach it: #!/opt/mailman/venv/bin/python3 # Note: The line above should be the Python3 interpreter for your # installed version of Mailman3. It's the same as the first line in # your 'mailman' command, which might be named manage.py or something # else in your environment. # The venv version of Mailman used to develop this program is: # GNU Mailman 3.3.9 (Tom Sawyer) # Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] # About: # The multiple steps of creating a Mailman 3 list based on a legacy # Mailman 2.1 list. # gbn July 28 2024. This little program is granted to the public domain. ######################################################################## # Adjust these variables for your list, domain, MM2 and MM3 locations: lists_to_import = [ # listname, domainname ('testlist','example.org'), ('testlist2','example.org') # Add more lists as needed ] ######################################################################## # Load prerequisite functionality: from mailman.config import config # Needed for transaction.commit from mailman.core.initialize import initialize # For initialize() from mailman.app.lifecycle import create_list # For create_list import pickle # Pickle file handling from contextlib import ExitStack # Pickle file handling from mailman.commands.cli_import import _Mailman, _Bouncer # "" from mailman.utilities.modules import hacked_sys_modules # "" import subprocess # Subprocess for import21 ######################################################################## # Step 0: Initialize the environment: # Without arguments, initialize() looks in the standard locations for your .cfg def do_init(): initialize() # Alternative: Load an explicit configuration file, such as: # initialize('/etc/mailman3/mailman.cfg') ######################################################################## # Step 1: Create the list # Note: This fails silently if the list already exists or something goes wrong def do_create(new_list): try: # The list might exist or otherwise not be creatable l = create_list(new_list) except: # I did not find useful return values from create_list to diagnose print('create_list('+new_list+') failed. Trying to proceed anyway') # This saves your new list: transaction = config.db transaction.commit() ######################################################################## # Step 2: Rewrite the pickle file from the legacy list. def do_pickle(old_pickle_file, new_pickle_file): # These definitions are so the old pickle file can be parsed: with ExitStack() as resources: resources.enter_context(hacked_sys_modules('Mailman', _Mailman)) resources.enter_context( hacked_sys_modules('Mailman.Bouncer', _Bouncer)) # Input the old pickle file from MM 2.1 with open(old_pickle_file, 'rb') as fp: data = pickle.load(fp) # ban_list was a problematic value from my MM2.1 lists: # print(data['ban_list']) data['ban_list'] = [] # Any other settings you want to change? Add them here. These # variables may be seen with MM2's 'config_list' command data['require_explicit_destination']=1 # yes data['member_moderation_action']=1 # reject data['generic_nonmember_action']=2 # reject data['max_num_recipients']=2 # block cc/bcc to list fp.seek(0) # probably not needed fp.close() # ditto # Output: Rewrite the file in the current MM3 format with open(new_pickle_file,'wb') as ofp: pickle.dump(data, ofp) ofp.close() ######################################################################## # Step 3: Import the legacy settings to the newly created list def do_import(new_list, new_pickle_file): # I did not see how to call import21 directly from Python, so am using # a subprocess which basically uses the CLI syntax. # # CLI syntax: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE def import_list(listname, pickle_file): command = [ 'mailman', 'import21', listname, pickle_file ] subprocess.run(command, check=True) # print(f"List {listname} imported successfully.") # Import the list via a subprocess: import_list(new_list, new_pickle_file) # This saves your changes: transaction = config.db transaction.commit() ######################################################################## # Main process: do_init() # Loop for all lists we want to create & import: for new_listname, new_domainname in lists_to_import: new_list = new_listname+'@'+new_domainname # Adjust for wherever your old MM2 lists are: old_pickle_file = '/var/lib/mailman/lists/'+new_listname+'/config.pck' print('Starting list '+new_list) # The new pickle_file doesn't need to be saved after this program exits new_pickle_file = '/opt/mailman/'+new_listname+'-new.pck' do_create(new_list) do_pickle(old_pickle_file, new_pickle_file) do_import(new_list, new_pickle_file) print('Done with list '+new_list) # Don't forget to import and then index your list for full-text # searching. We're not doing that here because it takes awhile # (depending on the size of the archive). Use a command from the bash # shell such as: # mailman-web hyperkitty_import --since=1971-01-01 -l listname@domainnamed /var/lib/mailman/archives/private/listname.mbox/listname.mbox # followed by: # mailman-web update_index_one_list listname@domainname ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 1

Display the last post time for a list or all lists.
by Henrik Rasmussen Aug. 9, 2024

Aug. 9, 2024

Does Mailman 3 have something similar to https://www.msapiro.net/scripts/last_post.py displaying the last post time for a list or all lists?

3 4

Mailman/Django-allauth integration with Yahoo
by Дилян Палаузов Aug. 9, 2024

Aug. 9, 2024

Hello, Has anybody managed to use the Django-Allauth Yahoo provider to authenticate towards Mailman3? I have integrated mailman3/django-allauth/gmail — it works. I want in the same way to integrate mailman3 with yahoo mail. As advised at https://docs.allauth.org/en/latest/socialaccount/providers/yahoo.html , in yahoo I register an application with redirect URL https://l.bapha.be/mm3/accounts/yahoo/login/callback/ , then I add credentials under mm3/admin/socialaccount/socialapp/: client ID and Private Key. I append in settings.py:INSTALLED_APPS = [… 'allauth.socialaccount.providers.yahoo' ]. After I do all of this, I eventually visit /mm3/accounts/login/?next=/mm3/postorius/lists/at.l.bapha.be/, click on Yahoo: “Sign In Via Yahoo . You are about to sign in using a third-party account from Yahoo.” → [Continue]. Now at https://login.yahoo.com I enter user name and password. Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: Messages: Confirmation of email address sent to ...(a)yahoo.com Menu: Entrance \r\n New registration Confirm your email address: We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I have indeed received an email, which states: New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. Any idea what can I improve? In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? Greetings Дилян

2 3

migrate MM3 list from an old server to a new one
by noc＠iem.at Aug. 8, 2024

Aug. 8, 2024

hi all, i have an old mailman3 instance (3.2.1), and would like to migrate it's lists and archives to a new instance (3.3.8) on a different host. for various reasons, i don't think i am able to upgrade the old instance in-place. unfortunately, i haven't found any documentation on how to proceed. there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? thanks for your help. gamsr4e IOhannes PS: (again) I'm resending this message, as the one i sent yesterday seems to have vanished (i *did* check the archvies). i have no clue why this happens, as i can post via the webinterface just fine (only when using my trusted MUA they just vanish).

4 10

Header settings and Gmail
by erik＠dante.de Aug. 7, 2024

Aug. 7, 2024

Hi, We operate a mailing list on which many members use their Gmail address. In the default settings, this results in a warning and delayed delivery (and maybe marking as spam): status=deferred (host gmail-smtp-in.l.google.com[74.125.128.27] said: 421-4.7.28 Gmail has detected an unusual rate of unsolicited mail. To protect 421-4.7.28 our users from spam, mail has been temporarily rate limited. For 421-4.7.28 more information, go to 421-4.7.28 https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421 4.7.28 review our Bulk Email Senders Guidelines. As a preventive measure, it helps to use DMARC mitigation action with “Replace From: with list address” and “ DMARC Mitigate unconditionally ”. But now some users are unhappy with the From header " Username via Test-liste <test(a)test-liste.org>". They would rather have their email address in it. Is there a solution with which Google delivers the mailing list messages without complaining, but the sender email address is also in the “From:”? Thanks Erik

3 5

Only Recent archive tab works after mailman upgrade
by zoltan＠circle-interactive.co.uk Aug. 6, 2024

Aug. 6, 2024

Hi, since I upgraded mailman to 3.3.9 (python 3.11.2) I have an odd issue on lists' archive page. Apparently only the Recent tab works. If I switch to Active or Popular I see the change in the url but page content does not refresh. I can not see any errors in browser console and in logs so I am quite clueless how to debug further :( Thanks for the ideas.

3 4

Where to put static files referred to from list Info page?
by Greg Newby Aug. 6, 2024

Aug. 6, 2024

Hi friends. Some of my version 2.1 lists had some static files that were referenced from the list's HTML pages. I'd like to do the same for the lists now that they're ported to MM3. My question: Is there a place I can put these files within the Mailman directory hierarchy so they can be linked from the list Info page? I.e., under "Settings / List info / Long description" I'd like to include a <a href=...> to a file that's somewhere in a persistent location in the same directory tree as the Mailman web. I tried putting it under mm/var/lists/listname/ (where 'listname' exists, and is where templates go. This yielded a '404.' I confirmed I can add an href to the Long description, but don't know where in the Mailman3 directory hierarchy I can put the files. Thanks! Greg Newby

2 4

External MTA incoming mail: configuration
by Roland Giesler Aug. 6, 2024

Aug. 6, 2024

I have mailman set up to send mail via an external MTA, which is supported by mailman and described in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Specifically it says: |lmtp_host|and|lmtp_port|are parameters which are used by Mailman, but also will be passed to the MTA to identify the Mailman host. The “same host” case is special; some MTAs (including Postfix) do not recognize “localhost”, and need the numerical IP address. If they are on different hosts,|lmtp_host|should be set to the domain name or IP address of the Mailman host.|lmtp_port|is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using it. However, there is a practical problem with LMTP (to receive incoming email) which is as follows: The setup in mailman.cfg: lmtp_host: lists.fast.za.net lmtp_port: 8024 Now, lists.fast.za.net is the mailman server. The docs say that mailman passes these on to the MTA. However, the MTA (postfix) on box2.gtahardware.co.za has the following setting in it main.cf: virtual_transport=lmtp:[127.0.0.1]:10025 If I reply to a signup confirmation email for example, the mail is received and processed by box2.gtahardware.co.za, and it is not passed on to the mailman server. So what is meant by "but also will be passed to the MTA to identify the Mailman host" in the docs? If I change the config of the MTA (postfix) to be "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming mail will be forwarded, but how does postfix know that only the mailman emails should be forwarded and not all the other mail that the server at box2.gtahardware.co.za receives? This is quite fuzzt to me at this stage. Could someone help me with some clarity please?

3 21

Create a mailman-web admin user
by Roland Giesler July 30, 2024

July 30, 2024

I having a hard time understanding how to create an admin user for postorius (mailman-web). The docs say at https://docs.mailman3.org/en/latest/config-web.html Setting up Admin Account <https://docs.mailman3.org/en/latest/config-web.html#setting-up-admin-account> To create a superuser account in Django, run the following interactive command as|mailman|user: (venv)$ mailman-web createsuperuser However, which user in the mailman user mentioned? I tried to do this as root, but login in as an admin doesn't give me any option to create new lists in postorius. What am I missing / doing wrong? regards Roland

4 6

using SSH/TLS with external MTA
by Roland Giesler July 30, 2024

July 30, 2024

I have managed thus far to get things working on my new install, but I need to use a secure logon to send mail from an external MTA. I have set up: /etc/mailman/mailman.cfg: smtp_host: box2.gtahardware.co.za smtp_port: 465 smtp_user: roland(a)giesler.za.net smtp_pass: <hidden> smtp_secure_mode: smtps smtp_verify_cert: no smtp_verify_hostname: no I'll get a cert installed later, for now just want to get it going. This error occurs when I try to create a new user in postorius. ERROR 2024-07-24 15:29:45,572 2150 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/debug.py", line 89, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 146, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/usr/lib/python3/dist-packages/allauth/account/views.py", line 159, in form_valid return form.login(self.request, redirect_url=success_url) File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 196, in login ret = perform_login( File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 109, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 125, in _send self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) File "/usr/lib/python3.10/smtplib.py", line 901, in sendmail raise SMTPRecipientsRefused(senderrs) smtplib.SMTPRecipientsRefused: {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: Relay access denied')} However, the mailserver is in daily use and accept logon all the time. I believe I'm missing something that should be installed to make SMTPS (SSL) work, but what?

3 28

xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??
by Odhiambo Washington July 29, 2024

July 29, 2024

Today, my hourly cron job has generated an error and continues to do so every hour: ``` Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs hourly ``` Not sure what caused this. Perhaps a reboot when the cronjob hadn't completed? And a possible manual remedy would be to wipe the indexed db and let the cron run again? [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Couldn't read enough (EOF) (pid 85950): Couldn't read enough (EOF) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 119, in do_update backend.update(index, current_qs, commit=commit) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 276, in update database = self._database(writable=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 1160, in _database database = xapian.WritableDatabase(self.path, xapian.DB_CREATE_OR_OPEN) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian/__init__.py", line 3743, in __init__ _xapian.WritableDatabase_swiginit(self, _xapian.new_WritableDatabase(*args)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xapian.DatabaseCorruptError: Couldn't read enough (EOF) Failed to update the fulltext index: Couldn't read enough (EOF) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/hyperkitty/lib/utils.py", line 179, in run_with_lock fn(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/hyperkitty/search_indexes.py", line 117, in update_index update_cmd.update_backend("hyperkitty", "default") File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 342, in update_backend max_pk = do_update( ^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/haystack/management/commands/update_index.py", line 119, in do_update backend.update(index, current_qs, commit=commit) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 276, in update database = self._database(writable=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py", line 1160, in _database database = xapian.WritableDatabase(self.path, xapian.DB_CREATE_OR_OPEN) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/xapian/__init__.py", line 3743, in __init__ _xapian.WritableDatabase_swiginit(self, _xapian.new_WritableDatabase(*args)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xapian.DatabaseCorruptError: Couldn't read enough (EOF) -- 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 2

Internal Server Error, Need 2 values to unpack in for loop; got 1
by Elias Rudberg July 29, 2024

July 29, 2024

Hello! I am using mailman3 (version 3.3.8) and it mostly works fine, but sometimes (usually several times every day) the error below appears. Any suggestions for what could be done about this? Should it be considered a bug in Django, so not a mailman3 problem, or does it indicate something wrong with mailman3 itself? Best regards, Elias Here is what the error message looks like: ------------------------------------------- [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/postorius/lists/ Internal Server Error: /mailman3/postorius/lists/ ValueError at /postorius/lists/ Need 2 values to unpack in for loop; got 1. [...] Django Version: 3.2.19 [...] Python Version: 3.11.2 [...] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 1145, in list_index return render( File "/usr/lib/python3/dist-packages/django/shortcuts.py", line 19, in render content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 170, in render return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 62, in render result = block.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 315, in render return nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 315, in render return nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/library.py", line 234, in render return t.render(new_context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 172, in render return self._render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 162, in _render return self.nodelist.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 938, in render bit = node.render_annotated(context) File "/usr/lib/python3/dist-packages/django/template/base.py", line 905, in render_annotated return self.render(context) File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 203, in render raise ValueError( Exception Type: ValueError at /postorius/lists/ Exception Value: Need 2 values to unpack in for loop; got 1. Request information: USER: AnonymousUser [...] -------------------------------------------

3 7

MM3 generates long lines?
by peter＠chubb.wattle.id.au July 28, 2024

July 28, 2024

I'm seeing emails being dropped when mm3 talks to the local smtp server, with log errors like: 2021-06-23 15:42:24 1lvvea-007r8u-VN H=localhost (<FQDN>) [::1] F=<announce-bounces@<FQDN>> rejected after DATA: maximum allowed line length is 998 octets, got 1036 The email itself did not have such long lines AFAICT. I can disable line length checking on the mailserver, but that sounds like a recipe for the next one along to drop the email. Peter C

4 8

Removing Moderators
by steve.bachinsky＠tena-sda.org July 27, 2024

July 27, 2024

Hi. I'm able to remove a list moderator through the REST interface: >>> dump_json('BASE_URL/3.1/lists/LIST_NAME/roster/moderator') ... find the correct member_id from the output >>> dump_json('BASE_URL/3.1/members/MEMBER_ID', method='DELETE') If I know the moderator's email address, is there a way to do this in a python function? Thanks, Steve

2 4

hyperkitty threads by month question
by Bryan Fields July 27, 2024

July 27, 2024

I have installed a testing server for an organization I'm working with to explore migration from MM2 to MM3. Our main list has archives from 1992, and when importing the mbox into hyperkitty/mm3 I notice the archives by month only go back to July 2007, but the messages are there when I search for specific ones from the old archive in the 1992-2007 range. Is there a better way to get this to show up, or perhaps a better format we can display old archives in that's not 400+ line drop down? Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

3 14

config.pck from mailman2 has characters that won't import with import21
by Greg Newby July 26, 2024

July 26, 2024

Hi. I've set up MM3 in a venv successfully and am importing my legacy lists. I no longer have a running instance of mailman2, so don't know how I can change the offending list settings (i.e., in config.pck). The problem seems to be a digest footer from the previous incarnation of the list (list name is edited below, to protect the innocent): (venv) mailman@mail:~$ mailman import21 abc(a)lists.abcabcabc.org /var/lib/mailman/lists/abc/config.pck Unable to convert mailing list attribute: msg_footer with value "_______________________________________________ ${display_name} mailing list -- ${listname} To unsubscribe send an email to ${short_listname}-leave@${domain} %(web_page_url)slistinfo/%(_internal_name)s" Unable to convert mailing list attribute: digest_footer with value "_______________________________________________ ${display_name} mailing list -- ${listname} To unsubscribe send an email to ${short_listname}-leave@${domain} %(web_page_url)slistinfo/%(_internal_name)s" Importing members [------------------------------------] 0% Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/commands/cli_import.py", line 89, in import21 import_config_pck(mlist, config_dict) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 578, in import_config_pck import_roster(mlist, config_dict, members, MemberRole.member) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 625, in import_roster _import_roster(mlist, config_dict, iterator, role, action=action) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 645, in _import_roster if IBanManager(mlist).is_banned(email): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", line 103, in is_banned re.match(ban.email, email, re.IGNORECASE) is not None): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 167, in match return _compile(pattern, flags).match(string) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile p = _compiler.compile(pattern, flags) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile p = _parser.parse(p, flags) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 979, in parse p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse raise source.error("multiple repeat", re.error: multiple repeat at position 11 It seems that I might need to install mailman2 somewhere to try to change the config.pck. Are there any other options? I have dozens of lists with the same problem. Thanks. Greg Newby

4 4

Run a mailman program outside of mailman shell
by Greg Newby July 25, 2024

July 25, 2024

Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and intend to write a Python program do this this rather than running commands in mailman shell (and rather than running 'command()' functions in mailman shell, if possible). However, when I write a simple Python program to run the types of commands found in the Mailman docs, such as these <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>, I get errors. This is a venv installation, following these instructions <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The Mailman3 installation is working fine and I have a handful of lists in production that I set up manually. Here's a very simple program, import-try1.py, just to create a list: #!/opt/mailman/venv/bin/python3 from mailman.app.lifecycle import create_list l = create_list('testlist2(a)lists.aaabbb.org') Here's the output I get (yes, the domain exists and already has lists - I'm putting aaabbb instead of the actual domain name): ./import-try1.py Traceback (most recent call last): File "/opt/mailman/./import-try1.py", line 4, in <module> l = create_list('testlist2(a)lists.aaabbb.org') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create_list getUtility(IEmailValidator).validate(fqdn_listname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailValidator>, '') I get different errors with other sets of commands. The same commands work fine from `mailman shell`, i.e., (venv) mailman@mail:~$ mailman shell Welcome to the GNU Mailman3 shell on aaabbb.org >>> from mailman.app.lifecycle import create_list >>> l = create_list('testlist2(a)lists.aaabbb.org') >>> Output from mailman info, with the passwords omitted: GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:secretaaabbb@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:reallysecretaaabbb I suspect I just need to either change the interpreter (1st line of my program), or find the correct 'import' lines (I've tried numerous variations; the above is the simplest example). Help will be appreciated! Greg

4 5

Error when click on mailing list: An error occurred while processing your request.
by adam.heathcote＠utas.edu.au July 25, 2024

July 25, 2024

Hey there, We have a Mailman3 server with quite a few lists all running with no issues. Recently I imported a list from our old Mailman 2 server which went fine. I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. The output of /opt/mailman/web/logs/mailmanweb.log is here: ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/list.py", line 411, in get return render(request, 'postorius/lists/summary.html', data) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 52, in render output = self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) TypeError: sequence item 1: expected str instance, NoneType found I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? Cheers

2 5

First time mailman installation
by roland＠giesler.za.net July 25, 2024

July 25, 2024

I have installed mailman3 on Ubuntu including postorius & hyperkitty (from the packages). I have questions now which are not quite clear to me from the docs: 1. How do I specify my mail server details (which is my own server running postfix, etc) 2. How do I create new lists from the postorius UI, or can I only do that in the config files or the command line console for mailman3? thanks!

3 2

Mailman3 service won't start - Ubuntu 20.04
by willie.castillo＠caemilusa.com July 23, 2024

July 23, 2024

This is a fresh install (Ubuntu and mailman3), followed all steps in this document (https://docs.mailman3.org/en/latest/install/virtualenv.html) However, when trying to start mailman3 automatically (step https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma…) it won't start, it's throwing this error: × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-07-22 17:34:27 UTC; 8min ago Process: 1429 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 985ms Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: id SERIAL NOT NULL, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: email VARCHAR, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: list_id VARCHAR, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: PRIMARY KEY (id) Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: ) Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: ] Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: (Background on this error at: https://sqlalche.me/e/20/f405) Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: mailman3.service: Failed with result 'exit-code'. Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Ran "journalctl -xeu mailman3" for details and got this" Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 314, in _invoke_with Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return bind.execute(self) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return meth( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 180, in _execute_on_connection Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return connection._execute_ddl( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1529, in _execute_ddl Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ret = self._execute_context( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return self._exec_single_context( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: self._handle_dbapi_exception( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2353, in _handle_dbapi_exception Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: raise sqlalchemy_exception.with_traceback(exc_info[2]) from e Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: self.dialect.do_execute( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: cursor.execute(statement, parameters) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: sqlalchemy.exc.ProgrammingError: (psycopg2.errors.InsufficientPrivilege) permission denied for schema public Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: LINE 2: CREATE TABLE ban ( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: [SQL: Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: CREATE TABLE ban ( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: id SERIAL NOT NULL, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: email VARCHAR, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: list_id VARCHAR, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: PRIMARY KEY (id) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ] Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: (Background on this error at: https://sqlalche.me/e/20/f405) Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit mailman3.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: mailman3.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'exit-code'. Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. ░░ Subject: A start job for unit mailman3.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit mailman3.service has finished with a failure. ░░ ░░ The job identifier is 1101 and the job result is failed.

2 6

Unable to remove non-member
by kapoortoman＠gmail.com July 23, 2024

July 23, 2024

Hi Everyone, I ran across a strange issue today. A client reported the inability to remove a non-member in the following format: z_email/domain.org.za(a)domain.org.za The reported error from Postorius was: "The user could not be removed" I used https://mailtester.ninja/ to validate the email address and it is syntactically correct. -- JayceonChandler

2 1

Mailman3 on AlmaLinux 9 - Python3.9 errors
by willie.castillo＠caemilusa.com July 19, 2024

July 19, 2024

Hi, I'm trying to configure mailman3 on my AlmaLinux 9 server and when checking the mailman3 status, I get the following: # mailman3 status Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 227, in _catch_revision_errors yield File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 439, in _upgrade_revs for script in reversed(list(revs)) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 793, in iterate_revisions revisions, heads = fn( File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 1420, in _collect_upgrade_revisions current_revisions = self.get_revisions(lower) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 525, in get_revisions return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 525, in <listcomp> return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 549, in get_revisions return tuple( File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 550, in <genexpr> self._revision_for_ident(rev_id, branch_label) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 619, in _revision_for_ident raise ResolutionError( alembic.script.revision.ResolutionError: No such revision or branch '2156fc3f6f7d' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/libexec/mailman3/mailman", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.9/site-packages/click/core.py", line 1052, in main with self.make_context(prog_name, args, **extra) as ctx: File "/usr/lib/python3.9/site-packages/click/core.py", line 914, in make_context self.parse_args(ctx, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 1615, in parse_args rest = super().parse_args(ctx, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 1370, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 2347, in handle_parse_result value = self.process_value(ctx, value) File "/usr/lib/python3.9/site-packages/click/core.py", line 2309, in process_value value = self.callback(ctx, self, value) File "/usr/lib/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/usr/lib/python3.9/site-packages/mailman/core/initialize.py", line 229, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/lib/python3.9/site-packages/mailman/core/initialize.py", line 187, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/lib/python3.9/site-packages/mailman/database/factory.py", line 58, in create SchemaManager(database).setup_database() File "/usr/lib/python3.9/site-packages/mailman/database/factory.py", line 109, in setup_database alembic.command.upgrade(alembic_cfg, 'head') File "/usr/lib/python3.9/site-packages/alembic/command.py", line 320, in upgrade script.run_env() File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 563, in run_env util.load_python_file(self.dir, "env.py") File "/usr/lib/python3.9/site-packages/alembic/util/pyfiles.py", line 92, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python3.9/site-packages/alembic/util/pyfiles.py", line 108, in load_module_py spec.loader.exec_module(module) # type: ignore File "<frozen importlib._bootstrap_external>", line 850, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/lib/python3.9/site-packages/mailman/database/alembic/env.py", line 77, in <module> run_migrations_online() File "/usr/lib/python3.9/site-packages/mailman/database/alembic/env.py", line 71, in run_migrations_online context.run_migrations() File "<string>", line 8, in run_migrations File "/usr/lib/python3.9/site-packages/alembic/runtime/environment.py", line 851, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python3.9/site-packages/alembic/runtime/migration.py", line 608, in run_migrations for step in self._migrations_fn(heads, self): File "/usr/lib/python3.9/site-packages/alembic/command.py", line 309, in upgrade return script._upgrade_revs(revision, rev) File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 435, in _upgrade_revs return [ File "/usr/lib64/python3.9/contextlib.py", line 137, in __exit__ self.gen.throw(typ, value, traceback) File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 259, in _catch_revision_errors raise util.CommandError(resolution) from re alembic.util.exc.CommandError: Can't locate revision identified by '2156fc3f6f7d' Any ideas why?

4 10

Strange URL in error message
by waps＠tantalus.jena.thur.de July 18, 2024

July 18, 2024

(Debian 12) I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) Do you have an idea what can I do about this?

2 5

deployment recommendation(?)
by noc＠iem.at July 18, 2024

July 18, 2024

(sorry, if this comes in double; i sent the same mail yesterday, but it seems it didn't make it (i did check the archives); so i'm re-sending via the webinterface) hi, it's summer here in europe, and students have left the campus. so - like every summer - I ponder on the idea of migrating our old mailman2 instance that has served us for the last twenty years to a new and shiny mailman3. and - like always - i'm a bit unsure about the best way to proceed to find the optimum deployment strategy for a long-running (decades) medium-sized (our largest list has ~1800 members) installation. one of our primary objectives is receiving *security updates*. we also would like to stay on top of development (that is: use the latest and greatest *stable* mailman3 release). in my heart i am a Debian person, so my mailman2 installation just used the Debian packages. the new deployment machine, will be Debian based as well. now https://docs.mailman3.org/en/latest/install/install.html lists three options: # Debian packages this is what I would normally pick, but: my past experience with mailman3 in Debian was... rather suboptimal. (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). i see that the packages in current Debian/stable ("bookworm"), are lagging slightly (3.3.8, rather than 3.3.9), though that's to be expected from a distro with stable releases. otoh, Debian/unstable still ships 3.3.8, which is a bit disappointing. in any case, the really nice thing about (Debian-official) Debian packages is that they are typically - stable - guarantee an upgrade path between releases # Docker packages this is of course the simplest from a deployment perspective, but then i'm a bit worried about the security perspective. in my perception, docker deployments tend to get installed and then forgotten, and while the host OS keeps getting updates, the docker images are just left as is. so they tend to get stale. i would like to know how this is handled # virtualenv this is the deployment method recommended in the docs. however, it doesn't say why this method is any better than the others. also, the website says that it was last updated in 2019, so: is this recommendation still relevant? personally i do not have much experience with deployment of long-running software in virtualenv, and i'm esp worried a bit when it comes to switching python releases (which will happen multiple times in the next few years) i use virtualenv all the time for my pet projects, but there it doesn't matter much, if the venv breaks: i just delete it and start from scratch. but those are not long-running services. so: what are the drawbacks, limitations, advantages and benefits of the various deployment methods? i'd really like to make the switch this year! gmfasdr IOhannes

4 3

Setting PYTHONPATH in the virtual environment installation
by Keith Christian July 15, 2024

July 15, 2024

Before switching from a "git clone" installation to the virtual environment install, "/home/mailman3/mailman/src/mailman" was recommended as the PYTHONPATH setting. Here are some paths that exist in the Mailman3 virtual environment on the server in question: /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__init__.py /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__pycache__ /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/docs /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/mailarchive.py What is the proper setting for PYTHONPATH in this case? Thanks. ----------- Keith

2 1

mailman findmember runs very slow
by Wong, Wesley July 14, 2024

July 14, 2024

Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. On average, it takes about 15 - 20 seconds to run a query which is very slow IMHO. When searching through web administrator interface for Users, it takes only 1 -2 seconds. Is there a reason for such a discrepancy between the two interfaces? Is there any tuning to the CLI that could help with the performance issue? Here is the setup information regarding the VM hosting the Mailman 3 server: Memory: 16G CPU Cores: 6 Mailman CORE version: 3.3.9 Python version: 3.11.5 Database: MariaDB 10.6.15 OS: SLES 15 SP5 Thanks. wesley * * * Wesley Wong Senior Systems Engineer (ACIS) (310) 206-2571 wesley.wong(a)anderson.ucla.edu<mailto:wesley.wong@anderson.ucla.edu> UCLA Anderson School of Management | Transformative Leaders

2 3

repeated headers in mails from mailinglists
by Tobias Diekershoff July 14, 2024

July 14, 2024

Dear all, we have recently migrated from Mailman2 to Mailman3 and now discovered that all mails going through Mailman3 have the headers Archived-At and List-Archive repeated identically in the mail header ~100 times each. We are running Mailman3 on Debian Bookworm from the Debian repositories (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and hyperkitty (1.2.1-1). Can somebody of you help me to get rid of the repeated header? Thanks in advance for you help! Best, Tobias -- Tobias Diekershoff >>> System Hacker Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support OpenPGP-Key ID ... 0x25FE376FF17694A1 Fingerprint ...... 23EE F484 FDF8 291C BA09 A406 25FE 376F F176 94A1 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0x25FE376FF17694A1.asc

3 2

Hiding the "subscribe without creating an account"
by Ben Sturmfels July 14, 2024

July 14, 2024

Hi Folks, My Mailman3 installation is receiving a trickle of fake registrations, for which it then attempts to send a "Your confirmation is needed to join..." email, which typically bounce. I suspect these are coming from the "subscribe without creating an account" form on the list summary page. I notice that lists.mailman3.org doesn't show this form at all - you have to create an account to subscribe: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ compared to mine with: https://lists.softwarefreedom.com.au/postorius/lists/free-software-melb.lis… Is there a configuration option that does this, or was it a custom change made in the templates? Was the change made to reduce fake registrations? Did it work? Regards, Ben -- Ben Sturmfels Sturm Software Engineering www.sturm.com.au +61 3 9024 2467

3 3

500 error on one list
by Seth Seeger July 13, 2024

July 13, 2024

Hello, One of my lists is return a 500 error when I try to visit the list's home page: HTTP Error 500: {"title": "500 Internal Server Error"} mailmanweb.log says: ERROR 2024-07-13 15:22:30,073 1668 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3.8/site-packages/postorius/views/list.py", line 275, in get 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 File "/usr/lib/python3.8/_collections_abc.py", line 666, in __contains__ self[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3.8/site-packages/mailmanclient/restbase/connection.py", line 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ ERROR 2024-07-13 15:22:30,079 1668 django.request Internal Server Error: /postorius/lists/XXXX/ mailman.log says: [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX HTTP/1.1" 200 466 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/owner HTTP/1.1" 200 2401 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.2" [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXX@XXXX/config HTTP/1.1" 200 14262 "-" "GNU Mailman REST client v3.3.2" 2024-07-13 15:23:44 [FALCON] [ERROR] GET /3.1/lists/XXXX/archivers => Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/falcon/app.py", line 361, in __call__ responder(req, resp, **params) File "/usr/lib/python3.8/site-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3.8/site-packages/zope/component/_api.py", line 152, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 619, in __init__ exists = store.query(ListArchiver).filter( File "/usr/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3467, in one_or_none raise orm_exc.MultipleResultsFound( sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() [13/Jul/2024:15:23:44 +0000] "GET /3.1/lists/XXXX/archivers HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.2" Did this one list get corrupted somehow? I'm running GNU Mailman 3.3.4 (Tom Sawyer) in Docker containers on Debian Stretch. Emails to that list are not getting processed. I'm not out of disk space. Anything I should check? Thank you, Seth

2 1

Pkl files with ".last" extension
by Keith Christian July 12, 2024

July 12, 2024

In the MM2 to MM3 migration project I'm involved with, I see files with names like config.pkl.last along with config.pkl. Is there a special reason for the ".last" extension and if so, what is it? Thanks, -------- Keith

2 2

bulk deletion of messages from Hyperkitty
by Danil Smirnov July 12, 2024

July 12, 2024

Hi, community! After importing from Mailman 2, thousands of badly compiled messages from the past appeared with empty content on the same date (date of import). Is there a safe way to delete them all? If we delete them from the database - hyperkitty_email table - do we need to do some clean-up of hyperkitty_thread table as well? Any advice? BR, Danil Smirnov

4 5

Hyperkitty stuck files
by zoltan＠circle-interactive.co.uk July 11, 2024

July 11, 2024

Hi, I have a mailman3 setup in venv with python 3.11.2 mailman 3.3.9 mailman-hyperkitty 1.2.1 I feel I have read a lot about issues with stucked files in spool directory still I am not able to proceed with debugging in my case. Ideas would be welcome and appreciated. Thanks This is the error in archiver.log Jul 09 10:56:12 2024 (47531) HyperKitty archiver processing queued filebase: 1720522497.980487+a88492922feca24ced15594a5ec16556195 6f3ad Jul 09 10:56:12 2024 (47531) hyperkitty archiver: sending message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/archive: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> (500) Jul 09 10:56:12 2024 (47531) Could not archive the message with id <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) archiving failed, re-queuing (mailing-list act.lists.contextualscience.org, message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com>) Jul 09 10:56:12 2024 (47531) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Jul 09 10:56:12 2024 (47531) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html>

3 8

Postfix SMTP REJECT non-subscribers
by Matthew Blissett July 11, 2024

July 11, 2024

Hi, With Mailman 2, I have configuration and scripts to reject non-members from posting to lists _during the SMTP connection_. This is better than bouncing (no backscatter), better than discarding messages (the user finds out) and better than moderation (spammy messages aren't forwarded to external email systems). The configuration and scripts are described here: https://code.launchpad.net/~jimpop/mailman/check_subscriber Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. Thanks, Matt

3 3

An issue with the postfix_domains directory creation and the mailman start command.
by Keith Christian July 10, 2024

July 10, 2024

From Mark's reply of Jul 5, 2024, 3:18 PM: RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. 1 [mailman3@somehost ~]$ ./venv/bin/mailman start 2 Starting Mailman's master runner 3 Generating MTA alias maps 4 [mailman3@somehost ~]$ sudo ls -l /opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl /opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/ What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user. Not sure that i missed any steps, suggestions appreciated.

4 8

Dropdown problem in postorius due to bootstrap
by Greg Newby July 9, 2024

July 9, 2024

(My first post) As has been observed, the Ubuntu 24.04 LTS packaging for native Mailman3 can be challenging. I've been solving all kinds of issues, and I'm writing here about something I've so far been unable to solve. The problem: *In Postorius, dropdown menus are not working*. I.e., as a list admin you can click on a menu option like "Users" or "Mass operations," and nothing happens. As a regular user, the top-right icon to manage settings and logout does not do anything. The same behavior occurs regardless of which browser I use. The dropdown in HyperKitty works, and HyperKitty uses a different code base. In the browser developer console (Firefox & others), the error is: “Uncaught TypeError: n.createPopper is not a function.” I've dug deeply into this. The relevant <script> is bootstrap.min.js. Postorius (via django) is using version 5.3.1 via package libjs-bootstrap5: ** This is what django is using: /usr/share/bootstrap-html/js/bootstrap.bundle.min.js -- version 5.3.1, linked to: /usr/share/javascript/bootstrap5/js/bootstrap.bundle.min.js /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js Here is detail of the error from the Firefox developer console: Uncaught TypeError: n.createPopper is not a function _createPopper dropdown.js:241 show dropdown.js:139 toggle dropdown.js:121 <anonymous> dropdown.js:446 i event-handler.js:118 R event-handler.js:184 on event-handler.js:216 <anonymous> dropdown.js:444 <anonymous> bootstrap.bundle.min.js:6 <anonymous> bootstrap.bundle.min.js:6 By temporarily replacing /usr/share/python3-django-postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js I have tried moving back to 4.6.1 (from libjs-bootstrap4). I have also retrieved the latest 5.3.1 from the CDN, which is slightly different but doesn't change the error: https://cdn.jsdelivr.net/npm/bootstrap@5.3.1/dist/js/bootstrap.bundle.min.js Here's the JavaScript section from the bottom of a sample page from my Postorius site (view-source: https://lists.ogf.org/mailman3/postorius/lists/gfsg.lists.ogf.org/held_mess… ): <script src="/mailman3/static/postorius/libs/jquery/jquery-3.6.0.min.js"></script> <script src="/mailman3/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js"></script> <script src="/mailman3/static/django-mailman3/js/main.js"></script> <script src="/mailman3/static/postorius/js/script.js" defer></script> <script> // Add the .js-enabled class to the body so we can style the elements // depending on whether Javascript is enabled. $(document).ready(function(){ $("body").addClass("js-enabled"); $(".gravatar").addClass("rounded-circle"); }); </script> I would appreciate suggestions about how to solve this problem. Thanks to everyone who is doing a great job building and supporting Mailman3. I've been using Mailman2 for a long time, and have dozens of lists on multiple servers. ~ Greg Newby

2 1

hyperkitty_import performance boosting potential
by dlb-ml＠anl.gov July 9, 2024

July 9, 2024

Our organization is moving to MM3 from MM2, and I'm at the point where I am testing importing our archives. However, many of the lists that we want to transfer over have pretty large mbox files, so it takes a significant amount of time for it to process them. I can throw all of the resources I need at it in order to make it faster, but I'm not sure if the import application is single-threaded only. Is there a way to enable a multi-threaded option? Can I safely run multiple commands at the same time using something like /usr/bin/parallel? Thanks

2 2

E-mail every minute: "Cron <www-data@sharky5> ..."
by Robert Heller July 8, 2024

July 8, 2024

What am I missing? I *think* I have mailman3 *mostly* setup, but there are still some configuration things that are missing, but I am not sure how to fix them (the docs are NOT clear). I am getting an e-mail *every* minute that looks like: From www-data(a)deepsoft.com Sat Jul 6 17:38:03 2024 Return-Path: <www-data(a)deepsoft.com> X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on sharky5.deepsoft.com X-Spam-Level: X-Spam-Status: No, score=-850.0 required=5.0 tests�YES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NO_RELAYS,URIBL_BLOCKED, USER_IN_WELCOMELIST autolearn=ham autolearn_force=no version=4.0.0 X-Original-To: www-data Delivered-To: www-data(a)deepsoft.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d�epsoft.com; s�epsoft.com; t20301883; bh=qGrVTBfV1NiqgxCIzSaXwoKZ0lKxKvaK56k31yXU2Sk=; h=From:To:Subject:Date:From; b=jTml1ZF+qGkmS2tcz5kgZHjOyPxeaWIQiX1mzAF3ZfZWb0ziVLxutkcej5mGapUOq PpH6ExYM1TEipMTYQ/JRY/74vz2dEpebDrZqjyY3KakxLWiyFFEb5glmQYZGvz9wr2 e5ljD0Shku4fbRoaxO7XMQCn/fmx3+D8tI/ZPbMQReceived: by sharky5.deepsoft.com (Postfix, from userid 33) id 5257D4C1296; Sat, 6 Jul 2024 17:38:03 -0400 (EDT) From: root(a)deepsoft.com (Cron Daemon) To: www-data(a)deepsoft.com Subject: Cron <www-data@sharky5> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/var/www> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=www-data> Message-Id: <20240706213803.5257D4C1296(a)sharky5.deepsoft.com> Date: Sat, 6 Jul 2024 17:38:03 -0400 (EDT) X-Scanned-By: MIMEDefang 3.3 on 108.161.129.198 Status: R /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. And I get this output from sudo mailman-web check --no-color : System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. System check identified 14 issues (0 silenced). Again, the docs are not helpful (at least not to me). -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

5 11

Mailman 3 install questions: HAYSTACK_CONNECTIONS
by heller＠deepsoft.com July 7, 2024

July 7, 2024

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

2 1

Subject Munging
by Sam Darwin July 6, 2024

July 6, 2024

Hi, We have a user who is proposing that reply messages from a mailing list should be in the following format: Re: [MM3-users] Ubuntu 24.04 upgrade notes and not [MM3-users] Re: Ubuntu 24.04 upgrade notes Their reason... is that mailman2, and other lists, used to do it that way. I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. The questions are: 1. What could be explained to the user to convince them the new method is preferable. 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). Thanks.

3 3

Mailman 3, postfix domains, and postgresql cannot authenticate user
by Keith Christian July 5, 2024

July 5, 2024

--------------------------------------------------------------------------- First issue:Postfix v3.5.8 on RHEL 8. The below is from journalctl -xe: --------------------------------------------------------------------------- Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or directory I manually created the var_dir: /opt/mailman3/mm/var directory specified in the mailman.cfg file. How do I find out how to populate the postfix_domains.db files, and the postfix_lmtp.db file? --------------------------------------------------------------------------- Second issue: Postgresql authentication. PostgreSQL v10.23. --------------------------------------------------------------------------- I have this in the active mailman3.cfg file, where xxxxxxxxxx is the same complex password in the mailman3 config file: url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 Same password when I created the mailman3 and mailman3web users: create role mailman3 with encrypted password 'xxxxxxxxxx '; create role mailman3web with encrypted password 'xxxxxxxxxx '; psycopg2.OperationalError: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: Ident authentication failed for user "mailman3" --------------------------------------------------------------------------- Contents of the "live" mailman.cfg file, from "mailman info" --------------------------------------------------------------------------- (venv) [mailman3@someserver ~]$ cat -n /opt/mailman3/var/etc/mailman.cfg 1 # /opt/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 # This address is the "site owner" address. Certain messages which must be 8 # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # bounce from a list owner), will be sent to this address. It should point to 10 # a human. 11 site_owner: user(a)example.com 12 13 [database] 14 class: mailman.database.postgresql.PostgreSQLDatabase 15 ##### url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # ---------------------------------------------------------------------------------- 17 # Changed: Fri Jun 28 11:56:02 EDT 2024 18 url: postgresql://mailman3:xxxxxxxx@localhost/mailman3/mailman3 19 # Changed: Fri Jun 28 11:56:02 EDT 2024 20 # ---------------------------------------------------------------------------------- 21 22 [archiver.prototype] 23 enable: yes 24 25 # For the HyperKitty archiver. 26 [archiver.hyperkitty] 27 class: mailman_hyperkitty.Archiver 28 enable: yes 29 configuration: /opt/mailman3/mailman-hyperkitty.cfg 30 31 [shell] 32 history_file: $var_dir/history.py 33 34 [mta] 35 incoming: mailman.mta.postfix.LMTP 36 outgoing: mailman.mta.deliver.deliver 37 lmtp_host: 127.0.0.1 38 lmtp_port: 8024 39 smtp_host: localhost 40 smtp_port: 25 41 configuration: python:mailman.config.postfix 42 verp_confirmations: yes 43 verp_personalized_deliveries: yes 44 verp_delivery_interval: 1 Suggestions appreciated for how to fix the postfix_domains files, and the postgres authentication isssue. ------------- Keith

3 5

Ubuntu 24.04 upgrade notes
by Andrew Hodgson July 3, 2024

July 3, 2024

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

1 0

Mailman Ubuntu 24.04 install notes
by Andrew Hodgson July 1, 2024

July 1, 2024

Hi. Just thought I would write up my installation experiences on Ubuntu 24.04 following this guide as much as possible: Virtualenv Installation - Mailman Suite 3.3 documentation (mailman3.org)<https://docs.mailman3.org/en/latest/install/virtualenv.html> Ubuntu packages: I'm trying not to install dev packages on the server if possible and managed to get away with the following packages: python3-psycopg2 sassc lynx python3-venv python3-certbot-nginx postgresql exim4-daemon-light Creating the venv: python3 -m venv --system-site-packages --symlinks venv This creates the venv referencing the system packages as well which is useful as some of the dependencies for Mailman are met by the Certbot and python3-psycopg2 packages. Using Pip I installed the following packages: pip install mailman mailman-hyperkitty mailman-web Postgres: I ran into an issue with the database after running `mailman-web migrate`. This was because a newer version of Django pulled in from the above command needed some tables creating in the public schema, and from Postgres 15 (Ubuntu ships with Postgres 16) that isn't allowed by default. I solved this by making the Mailman role owner of the mailman database. I am aware of discussions around whether its best to do this or give explicit perms on the databases to allow all on the public schema, but I decided to go with this option. My Postgres commands are now: sudo -u postgres psql create database mailman; create user mailman with encrypted password '[...]'; ALTER DATABASE mailman OWNER TO mailman; Django: I ran into an issue with a newer Django installation not allowing any form submission, was getting a 403 returned due to CSRF protection failure. I resolved this by adding this line to my local Settings.py: CSRF_TRUSTED_ORIGINS=['https://lists.domain.com'] I moved back to using Gunicorn for the backend server, the instructions on this were spot on. I've had this error before but the mailman-web compilemessages command failed because of missing msgfmt. I think I can pull this in from Ubuntu packages but may need to update installation docs with this extra package requirement. Search: I continued to use Woosh as I'm running a very low traffic site and that is what comes with Mailman-Web as part of package requirements. Thanks for the good support as always guys. Andrew.

1 0

Held messages showing a reason not in English on the Postorious
by Alan KT So (ITSC) June 27, 2024

June 27, 2024

We just notice a held message from a user's list showing the held reason in Ukrainian, but the interface is in US English and the list's preferred language is English (USA). We could not repeat the issue. What can be the reason behind? [cid:image001.png@01DAC7B9.AF2B0400] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

3 2

A poll: "Delete this thread"
by Sam Darwin June 26, 2024

June 26, 2024

Hi, If you have a locally installed mailman3 instance, could you try (as an administrator) to visit a thread in Hyperkitty and click "Delete this thread"? Does the thread get deleted, and you return to "Recently active discussions" and everything is fine? Even just a few replies would indicate a pattern. That it's usually ok, for example. I get a spinning wheel, and "Thread matching query does not exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, gunicorn.

5 7

Problem with digests not being sent daily
by Mark June 24, 2024

June 24, 2024

Hi, I have a problem with digests not being sent daily (periodically). Mailman 3.3.9 installed in virtualenv Enable Digests = YES Send Digest Periodically = YES Digest size threshold = 0 Cron is set and is running. An error report (below) is generated and emailed. The last line in the error report says "FileNotFoundError: [Errno 2] No such file or directory ...". Setting the list's folder to 777 didn't help. Any clues on where to start looking for a solution would be greatly appreciated. Thanks, Mark /////////////////////////////////////// CRON IS SET: /////////////////////////////////////// su mailman (venv) mailman:/$ crontab -e ... 5 6 * * * /opt/mailman/venv/bin/mailman digests --periodic ... /////////////////////////////////////// CRON RUNS: /////////////////////////////////////// # tail -100 /var/log/cron.log ... 2024-06-21T06:05:01.815948+00:00 deu CRON[3105464]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) ... /////////////////////////////////////// ERROR REPORT EMAILED BY CRON: /////////////////////////////////////// Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/commands/cli_digests.py", line 126, in digests maybe_send_digest_now(mlist, force=True) File "/opt/mailman/venv/lib/python3.11/site-packages/mailman/app/digests.py", line 106, in maybe_send_digest_now os.rename(mailbox_path, mailbox_dest) FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/mm/var/lists/LISTNAME.LISTDOMAIN/digest.mmdf' -> '/opt/mailman/mm/var/lists/LISTNAME.LISTDOMAIN/digest.252.14.mmdf' ////////////////////////////////////////////////////////////////////////////////

3 14

unique key violation because of case sensitivity of email address
by Jörg Schulz June 16, 2024

June 16, 2024

After updating to the most recent version of mailman-web, the migrations script issued an error: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Traceback (most recent call last): mailman-web | File "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute mailman-web | return self.cursor.execute(sql, params) mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mailman-web | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_email_987c8728_uniq" mailman-web | DETAIL: Key (user_id, email)=(27, John.Doe(a)mynicedomain.de) already exists. mailman-web |(...) Digging into the db, I found the duplicate to result from a duplicate entry using john.doe(a)mynicedomain.de Obviously, the process that originally created the entry, took case sensitivity literally which doesn't seem to be the case any longer for the migration script. I fixed this by removing one of the duplicates hoping no further errors will come up.... What would have been the better approach?

2 1

running a script for the mailman-shell (to discard held messages) gives errors about a package argument for relative import
by stephan.edel＠gmx.net June 16, 2024

June 16, 2024

Our organization has been been communicating through about a dozen mailing lists, running on mailman, with ~200 subscribers, for 15-odd years. After Debian 10 LTS ran out, I had to upgrade our organisations Debian server, forcing me into mailman3. I haven't managed, yet, to get the web interface running, so I need to do the most urgent tasks in the shell for now. I have found out that, for example, to discard all held messages from the list "motor", I need to > sudo -u list mailman shell -l motor.our-server.de and in the shell, >>> from mailman.app.moderator import handle_message >>> rdb = IListRequest(m) >>> for req in rdb.held_requests: ... if req.request_type == RequestType.held_message: ... handle_message(m, req.id, Action.discard) > commit() Now, obviously, I put these exact lines in a script, so I don't have to type it out every single time, and try to run it using > sudo -u list mailman shell -l testlist.our-server.de -r ./mm_discard_held.py but that invariably gives me ------------------------ Traceback (most recent call last): File "/usr/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'mailman')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/commands/cli_withlist.py", line 294, in shell r = call_name(dotted_name, m, *run_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/__init__.py", line 121, in import_module raise TypeError(msg.format(name)) TypeError: the 'package' argument is required to perform a relative import for './mm_discard_held' ------------- I've tried a PYTHONPATH=/root/bin , where mm_discard_held.py lives, as suggested. I've tried moving it to the path where the mailman binary lives, as suggested. I always get the same result. What else can I do? Thank you.

2 1

mailman3 on Rocky 9 is not starting after an OS update and reboot
by dgoldsmith＠sans.org June 12, 2024

June 12, 2024

We are running mailman 3.x in a venv setup using Postgresql. The mailman service hangs during startup and eventually fails with a timeout: # systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: disabled) Active: failed (Result: timeout) since Wed 2024-06-12 13:35:23 UTC; 11s ago Process: 1205 ExecStart=/opt/mailman/venv/bin/mailman start (code=killed, signal=TERM) CPU: 1.019s Jun 12 13:33:53 <hostname> systemd[1]: Starting GNU Mailing List Manager... Jun 12 13:35:23 <hostname>systemd[1]: mailman3.service: start operation timed out. Terminating. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Failed with result 'timeout'. Jun 12 13:35:23 <hostname> systemd[1]: Failed to start GNU Mailing List Manager. Jun 12 13:35:23 <hostname> systemd[1]: mailman3.service: Consumed 1.019s CPU time. Searching I found some similar reports where it seemed to be an issue with a stale .lck lock file. But on our system: - /var/lib/mailman is empty - /opt/mailman/mm/var/locks is empty The last entries in /opt/mailman/mm/var/logs/mailman.log is: 2024-06-12 09:23:44 -0400] [2101411] [INFO] Handling signal: term Jun 12 13:23:44 2024 (2101395) Master watcher caught SIGTERM. Exiting. [2024-06-12 13:23:44 +0000] [2101451] [INFO] Worker exiting (pid: 2101451) Jun 12 09:23:44 2024 (2101412) retry runner caught SIGTERM. Stopping. [2024-06-12 13:23:44 +0000] [2101450] [INFO] Worker exiting (pid: 2101450) Jun 12 09:23:44 2024 (2101408) nntp runner caught SIGTERM. Stopping. [2024-06-12 09:23:48 -0400] [2101411] [INFO] Shutting down: Master Jun 12 13:23:50 2024 (2101395) Master stopped Any help would be appreciated. Postgres appears to be up., Postfix is up, nginx is up. The web UI gives me the error: Something went wrong Mailman REST API not available. Please start Mailman core. Running "mailman version" hangs for a long time and then returns: $ mailman version GNU Mailman 3.3.9 (Tom Sawyer) Running "mailman status" hangs for a long time and then returns: $ mailman status GNU Mailman is not running What other logs can be checked for more detail? What possible services or file/dir permissions may have had something changed by the OS updates? Thanks, David Goldsmith

3 2

Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)
by Mark Sapiro June 11, 2024

June 11, 2024

On 6/6/24 11:22 AM, Marcus Bautze wrote: > Hi, > > Sorry, that was a wrong information in my mail . I already changed the base url to your suggestion as I wrote the mail (and forgot to change it in the mail) but i‘m getting the same error :-( I have some questions. At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/? At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg api_key: Some_key and in mailman-web.py MAILMAN_ARCHIVER_KEY = 'Some_key' What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

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

Recently active discussions - Hyperkitty
by Sam Darwin June 4, 2024

June 4, 2024

Hi, Sometimes not sure if it's preferable to open a gitlab issue, or chat on the mailing list. I have run a large archive import into mailman3/hyperkitty. After that's done, waited a day, for scheduled cron jobs to complete. In "All Threads", all the email archives are present. The import worked. In "RECENTLY ACTIVE DISCUSSIONS" on the main page, it says: RECENTLY ACTIVE DISCUSSIONS No discussions this month (yet). Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? Thanks, Sam

3 7

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

Mailman sending email from user@example.com
by dgoldsmith＠sans.org May 30, 2024

May 30, 2024

I have defined an additional SITE in django and the SITE_ID value in /etc/mailman3/settings.py is set to reference that site's ID value. Messages for a list being distributed that are generating certain bounce errors are resulting in email from Mailman 3.x being sent to the list owners from the address user(a)example.com. Is there something else to update in the settings files, Django or the database to make it use the list owner email address tied to the domain of the site? Thanks, David Goldsmith

1 1

Have postgresql in the mailman.cfg file but sqlite shows in the mailman info command
by Keith Christian May 29, 2024

May 29, 2024

(venv) [mailman3@localhost-live ~]$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.9.18 (main, Jan 24 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] config file: /opt/mailman3/mailman.cfg db url: sqlite:////opt/mailman3/var/data/mailman.db <<<---------------------------------------- devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Class and url were commented out in the mailman.cfg file, did not recognize postgresql but generated a trace (venv) [mailman3@localhost-live ~]$ grep postgresql /opt/mailman3/mailman.cfg # class: mailman.database.postgresql.PostgreSQLDatabase # url: postgresql://mailman:MYPASSWORD@localhost/mailman Uncommented class and url: class: mailman.database.postgresql.PostgreSQLDatabase <<<---------------------------------------- url: postgresql://mailman:MYPASSWORD@localhost/mailman <<<---------------------------------------- Now I get a stack trace from "mailman info" (venv) [mailman3@localhost-live ~]$ mailman info Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1077, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 943, in make_context self.parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1644, in parse_args rest = super().parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1408, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2400, in handle_parse_result value = self.process_value(ctx, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2362, in process_value value = self.callback(ctx, self, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 228, in initialize initialize_1(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 122, in initialize_1 mailman.config.config.load(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 145, in load self.push(filename, user_config.read()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 150, in push self._config.push(config_name, config_string) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 582, in push confs = self._getExtendedConfs(conf_name, conf_data) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 615, in _getExtendedConfs _parser_read_file(parser, StringIO(conf_data), conf_filename) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 49, in _parser_read_file parser.read_file(f, source) File "/usr/lib64/python3.9/configparser.py", line 718, in read_file self._read(f, source) File "/usr/lib64/python3.9/configparser.py", line 1085, in _read raise MissingSectionHeaderError(fpname, lineno, line) configparser.MissingSectionHeaderError: File contains no section headers. file: '/opt/mailman3/mailman.cfg', line: 14 <<<---------------------------------------- 'class: mailman.database.postgresql.PostgreSQLDatabase\n' Here is the complete mailman.cfg file: 1 # /etc/mailman3/mailman.cfg 2 # [paths.here] 3 # var_dir: /opt/mailman/mm/var 4 # 5 # [mailman] 6 # layout: here 7 # # This address is the "site owner" address. Certain messages which must be 8 # # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # # bounce from a list owner), will be sent to this address. It should point to 10 # # a human. 11 # site_owner: user(a)example.com 12 # 13 # [database] 14 # class: mailman.database.postgresql.PostgreSQLDatabase 15 # url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # 17 # [archiver.prototype] 18 # enable: yes 19 # 20 # # For the HyperKitty archiver. 21 # [archiver.hyperkitty] 22 # class: mailman_hyperkitty.Archiver 23 # enable: yes 24 # configuration: /etc/mailman3/mailman-hyperkitty.cfg 25 # 26 # [shell] 27 # history_file: $var_dir/history.py 28 # 29 # [mta] 30 # verp_confirmations: yes 31 # verp_personalized_deliveries: yes 32 # verp_delivery_interval: 1 33 # Ideas? Thanks.

3 2

Django administration - User permissions
by advorkin＠cs.princeton.edu May 29, 2024

May 29, 2024

Hello, I'm trying to setup users with different permissions. For example: I created a group support with an ability to hyperkitty/mailing list/Can add/change/delete/view mailing list. Unfortunately, the user still does not have an ability to create mailing lists as the option does not exist. It does work when the user is set as "Superuser status". I've also tried giving every possible "available user permissions", but it didn't make a difference. Am I missing something? Thank you!

2 4

Installing Mailman3 under a Python Virtual environment running on RHEL9
by Andy Macheta May 29, 2024

May 29, 2024

Hi, So tried, without much success, to get Postorius working on my Mailman3 server and every internet trick& tip I tried did not work so decided to take a new approach as recommended at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Used this reference: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ would also work with Red Hat. Fell at the first hurdle with no packages available called "python3-dev" or "python3-venv" Is there anyone that has managed to install a running version of Mailman3 that has a working GUI whether it is on bare metal or Python virtual environment and if so, could they kindly let me know how they did it?? The closest I've come is a running command line version of Mailman3 which is fine for me of course but not for anyone else as they like access via web browser. Thanks in advance, Andy Macheta

4 13

Circumstances in which a subscriber is added to Pending Confirmation list
by David Owen May 28, 2024

May 28, 2024

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

1 0

FYI: "RuntimeError: command failure: /usr/sbin/postmap /opt/mailman/mm/var/data/postfix_lmtp, 1, Operation not permitted"
by Nils May 27, 2024

May 27, 2024

After mailman was running so well I was wondering if I really need the restart option in the service configuration. When I commented it out, I got this error a few weeks later: > # systemctl status mailman3 > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > vendor preset: enabled) > Active: failed (Result: exit-code) since Tue 2024-05-14 00:34:37 > CEST; 1 week 6 days ago > Process: 1159 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 6.933s > > May 14 00:34:36 SERVER.TLD mailman[1159]: return > f(get_current_context(), *args, **kwargs) > May 14 00:34:36 SERVER.TLD mailman[1159]: File > "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_control.py", > line 109, in start > May 14 00:34:36 SERVER.TLD mailman[1159]: > call_name(config.mta.incoming).regenerate() > May 14 00:34:36 SERVER.TLD mailman[1159]: File > "/opt/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", > line 136, in regenerate > May 14 00:34:36 SERVER.TLD mailman[1159]: raise > RuntimeError(NL.join(errors)) > May 14 00:34:36 SERVER.TLD mailman[1159]: RuntimeError: command > failure: /usr/sbin/postmap /opt/mailman/mm/var/data/postfix_lmtp, 1, > Operation not permitted > May 14 00:34:36 SERVER.TLD systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > May 14 00:34:37 SERVER.TLD systemd[1]: mailman3.service: Failed with > result 'exit-code'. > May 14 00:34:37 SERVER.TLD systemd[1]: Failed to start GNU Mailing > List Manager. > May 14 00:34:37 SERVER.TLD systemd[1]: mailman3.service: Consumed > 6.933s CPU time. I can only guess that the error might be some case of very bad timing, because there shouldn't be any problem with the mentioned call. > # su mailman > (venv) mailman@SERVER:/$ /usr/sbin/postmap > /opt/mailman/mm/var/data/postfix_lmtp Usually works fine. I re-enabled the lines in the server configuration: > Restart=on-failure > RestartSec=15

1 0

Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)
by schaefer＠alphanet.ch May 25, 2024

May 25, 2024

Hello, I already have some success in auto-migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm), using a new container (not upgrading the existing installation, which is obsolete e.g. 32 bit x86). I am doing this using custom scripts. The idea being to be able to import most of the existing configuration and archives, let the list administrators test the new system, and progressively advertise this to users. Then, the old container will be disabled. The basic stuff works (From: domain is OK, HTTP transport works, mail go out, etc) I however bumped into the following problem: How may I automatically (from the command line) replace the example.com which is displayed in the web interface and in the From: comment field of the e-mails (the address itself is OK) -- I only found documentation about changing through the GUI so far. Any pointer? Also, I have a question: if I import my 2.1 config for each ml, will DKIM work-arounds work (e.g. replace This User <user@domain> by This User user@domain <the-mailing-list>) ? Will Mailman 2.1 it required some config changes and also I had to modify mailman using a Debian diversion, AFAIR. Thank you for any input.

5 5

Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?
by Keith Christian May 25, 2024

May 25, 2024

Greetings, Mailman3 List ! mailman3 was installed into the below virtual environment: (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or any other supporting programs be installed into this virtual environment ? PostgreSQL and Postfix have been successfully installed outside of the mailman3 virtual environment and start properly, I assume this is correct. Thanks in advance. ---- Keith

4 3

Congrats & MM3 Development Plans Request - Take 2
by David Wilson May 23, 2024

May 23, 2024

Liang Liu; Congratulations on securing your Summer of Code project with MM3. As someone who is quite interested in the Mailman3 development plans, I tried to follow the link you provided but with no success. It timed out. Is that still a valid or the best link? Can you also please point me to the best source or site to get a general understanding of short and long term *MM3 development plans*, including various upcoming GSOC projects, including yours. Thank you very much in advance. Best regards. Dave Wilson ------------------------------------------------------------------------ ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: qL0JVbh9Fk99UcFT.png Replaced multipart/alternative part with first alternative.

3 2

[GSoC] Self-introduction Liu
by Liang Liu May 21, 2024

May 21, 2024

Hello everyone, I’m Liang Liu, a GSoC student this year. I will be responsible for using the publish-subscribe model to improve communication efficiency between the core and clients. The detail of this function is shown in the link below. https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024#Support_for_RE… I am excited to learn from all of you and share my experiences. Please feel free to reach out to me for any collaboration or discussion—I am keen to contribute and learn as much as I can. Hope we have a productive summer.

1 0

List Configuration Attribute Descriptions
by steve.bachinsky＠tena-sda.org May 20, 2024

May 20, 2024

Where does one obtain a complete and concise description for all of the list configuration attributes? From the documentation, it is shown that the REST "config" interface will provide all of the attribute values associated with a particular list. But how does one find a concise description for all of these attributes? For example, I see that there is a list attribute for "default_nonmember_action" and there are two documentation pages for this attribute, but I can't find a concise description of the attribute and the permitted values. Thanks, Steve

2 1

Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it
by Keith Christian May 20, 2024

May 20, 2024

The path to the mailman3.py file is: /home/mailman3/mailman/src/mailman/bin/mailman.py I created a mailman3 user, then, set the ownership on all directories and files in /home/mailman3 and below to mailman3:mailman3. When trying to run the "mailman info" command to verify that that mailman3 can start, I get this error: File "/home/mailman3/mailman/src/mailman/bin/mailman.py", line 22 in <module> from mailman.command.cli_help import help as help command Not sure what is going on here, help greatly appreciated.

3 4

When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected.
by rqchen＠cnic.cn May 11, 2024

May 11, 2024

When QQ email sends emails to the Mailman service set up by oneself, members of the list who use QQ email cannot receive the emails, and it shows that the emails are rejected.

2 3

cnic-20240510
by 陈汝祈 May 10, 2024

May 10, 2024

cnic-20240510

1 0

Change Dmark settings via command line
by bob B May 8, 2024

May 8, 2024

I need to set all the DMARC settings on are lists to "replace from with list address". Is there an easy want to do this via cli? I could do it by viewing the web interface but we have a lot of lists.

4 9

Deleting A List
by Odhiambo Washington May 4, 2024

May 4, 2024

I have deleted a list (list(a)nog.ke) - list_id = list.nog.ke. I can see from Django Admin UI that the archives are still intact. I created a new list (list(a)lists.nog.ke) - list_id = list.lists.nog.ke Is there a way to move the archives from the old list to the new list? -- 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 6

Welcome message template errors
by Mark May 1, 2024

May 1, 2024

Hi All I'm getting errors when a custom "Welcome message" template is in place [list:user:notice:welcome]. Case: Subscribing a new user via the admin "Mass subscribe". Although the new user is successfully subscribed, a welcome message is not sent and the following error message displays on the webpage. === HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read timed out. (read timeout=5) === And the site-owner receives an email with ... ==== Internal Server Error: /mailman3/lists/ DoesNotExist at /mailman3/lists/ Site matching query does not exist. Request Method: GET Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/ Django Version: 4.2.11 Python Executable: /opt/mailman/venv/bin/python3 Python Version: 3.11.2 ... etc ... === Regarding the second line in the email - my thinking is that it should be looking in "/opt/mailman/mm/var/lists" and not "/mailman3/lists/". If that's right, where would I look to change that directive? If not, any other clues would be greatly appreciated. The error doesn't occur if the is no custom "Welcome message" template - ie. the user is sent the default welcome message. $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg REST root url: http://localhost:8001/3.1/

2 29

Re: [MM3-users off list] Re: Welcome message template errors
by Mark April 29, 2024

April 29, 2024

>> So, I'm thinking (in broad brush strokes) that if I'm stuck with this >> "http glitch" I could write a script to: >> >> 1. extract the text of the custom message from the database, >> 2. write that message text to a file >> 3. update the templates.uri entries to replace the >> http://localhost... with file:///path/to/file >> 4. cron the script to run every few minutes. >> >> It screams of utter clunk I know... > but it would work. > > Note that this may not be as big an issue as it seems. It doesn't > affect all templates, for example list:member:digest:footer, > list:member:digest:header, list:member:digest:masthead, > list:member:regular:footer, list:member:regular:header and > list:member:generic:footer are only used by the `out` runner when > sending messages, so these aren't affected. Right. Affected are all the "list:user:notice:***" (eg. goodbye, hold, reject,...) > > I'm still trying to determine what the issue is. To this end can you > tell me what Python version your Mailman uses and what is the output > from `pip freeze` with your venv active? $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] $ pip freeze aiosmtpd==1.4.4.post2 alembic==1.13.1 arrow==1.3.0 asgiref==3.7.2 atpublic==4.0 attrs==23.2.0 authheaders==0.16.2 authres==1.2.0 blessed==1.20.0 certifi==2023.11.17 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 cmarkgfm==2024.1.14 cryptography==42.0.1 defusedxml==0.7.1 Django==4.2.11 django-allauth==0.60.1 django-appconf==1.0.6 django-compressor==4.4 django-extensions==3.2.3 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.12 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 dkimpy==1.1.5 dnspython==2.5.0 docutils==0.20.1 falcon==3.1.3 filelock==3.13.1 flufl.bounce==4.0 flufl.i18n==5.0.2 flufl.lock==8.0.2 greenlet==3.0.3 gunicorn==21.2.0 HyperKitty==1.3.9 idna==3.6 lazr.config==3.0 lazr.delegates==2.1.0 mailman==3.3.9 mailman-hyperkitty==1.2.1 mailman-web==0.0.9 mailmanclient==3.3.5 Mako==1.3.0 MarkupSafe==2.1.4 mistune==3.0.2 networkx==3.2.1 nh3==0.2.15 oauthlib==3.2.2 packaging==23.2 passlib==1.7.4 postorius==1.3.10 psutil==5.9.8 psycopg2-binary==2.9.9 publicsuffix2==2.20191221 pycparser==2.21 Pygments==2.17.2 PyJWT==2.8.0 python-dateutil==2.8.2 python3-openid==3.2.0 pytz==2023.3.post1 rcssmin==1.1.1 readme-renderer==42.0 redis==3.5.3 requests==2.31.0 requests-oauthlib==1.3.1 rjsmin==1.2.1 robot-detection==0.4 six==1.16.0 SQLAlchemy==2.0.25 sqlparse==0.4.4 types-python-dateutil==2.8.19.20240106 typing_extensions==4.9.0 urllib3==2.1.0 wcwidth==0.2.13 Whoosh==2.7.4 xapian @ file:///opt/mailman/xapian-1.4.24-cp311-cp311-linux_aarch64.whl xapian-haystack==3.1.0 zope.component==6.0 zope.configuration==5.0 zope.event==5.0 zope.hookable==6.0 zope.i18nmessageid==6.1.0 zope.interface==6.1 zope.schema==7.0.1

1 0

Mailman with Python 3.12
by Andrew Hodgson April 26, 2024

April 26, 2024

Hi. What's the latest on Mailman with Python 3.12? Looking at Ubuntu 24.04 upgrade plans and realised it comes with Python 3.12. Ubuntu are shipping Mailman packages from Debian so not sure if they have made any changes to make Python 3.12 work. I don't use those packages myself. Andrew.

3 3

mailman3-web and the django middleware problem
by Thomas Stein April 26, 2024

April 26, 2024

Howdy! I'm trying to migrate an aged mailman3 installation from ubuntu 20.04 to ubuntu 22.04. Fresh install of mailman3-web gives me: Creating config file /etc/dbconfig-common/mailman3-web.conf with new version creating database mailman3web.db: success. verifying database mailman3web.db exists: success. Creating config file /etc/mailman3/mailman-web.py with new version /usr/lib/python3/dist-packages/django_q/conf.py:174: UserWarning: Retry and timeout are misconfigured. Set retry larger than t imeout,failure to do so will cause the tasks to be retriggered before completion.See https://django-q2.readthedocs.io/en/maste r/configure.html#retry for details. warn( Traceback (most recent call last): File "/usr/bin/django-admin", line 33, in <module> sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', 'django-admin')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 416, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 124, in populate app_config.ready() File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line 15, in ready raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: mailman3-web needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) I've already seen this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… ...but that does not get me anywhere. Could someone please push me in the right direction? cheers! t.

4 12

Slow performance when listing members on Postorius
by Alan So April 24, 2024

April 24, 2024

We are about to upgrade to Mailman core 3.3.9 and Postorius 1.3.10. We notice that for setup with large number of members, the performance is much slower when listing members on web (Postorius). Further troubleshooting show that there are quite a number of API calls which do not appear in Mailman core 3.3.5 and Postorius 1.3.6 when we list members. [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/33a6266d0a04472c8d5d6c78869a964c/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/7a18b7cb90a34ac98881a3f01b5488d1/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/61c6c3e2aaf443babd3bd191519b0424/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/8dd681165b8c436fac6793cae1ed2c27/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" Further tests showing that each database query using "_member_id" in table member can take as much as 0.3 to 0.5 seconds for some large installations. The default 25 members per page mean that it will take at least 7.5 to 12.5 seconds. Changing to 200 members per page will take even longer time. We wonder whether "_member_id" should be indexed just like most other id in the database mailman_core in order to solve the issue. Or are there any other workarounds? +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | _member_id | char(32) | YES | | NULL | | | role | int(11) | YES | MUL | NULL | | | list_id | varchar(255) | YES | MUL | NULL | | | moderation_action | int(11) | YES | | NULL | | | address_id | int(11) | YES | MUL | NULL | | | preferences_id | int(11) | YES | MUL | NULL | | | user_id | int(11) | YES | MUL | NULL | | | bounce_score | int(11) | YES | | NULL | | | last_bounce_received | datetime | YES | | NULL | | | last_warning_sent | datetime | YES | | NULL | | | total_warnings_sent | int(11) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+

1 1

Change config to create a new list with all archives off
by Tibor Molnar April 21, 2024

April 21, 2024

Can archiving be changed anywhere in mailman3 configs, so then all new lists created do not archive by default?

5 8

Mailman 3 hosting query
by Bill Robertson April 18, 2024

April 18, 2024

Hi I'm investigating the possibility of transferring a fairly small mailing list I own from Google Groups to MM3 via a hosting service. I'd appreciate any pointers regarding what I should be looking out for with companies that offer this service It also seems very hard to find out which hosting companies are worth considering (In particular, reliability and support are important) Any help much is much appreciated Thanks

4 5

Is there a way to find out when a user subscribed to a list
by Mohsen Masoudfar April 17, 2024

April 17, 2024

Hi, We need to find out when a specific user joined a list. Is there a way to get this information? Thanks!

3 2

Mailman-web stop responding.
by Paul Rubin April 17, 2024

April 17, 2024

I was trying to administrate a list and discovered that mailman-web was unresponsive. I have tried stopping and restarting it. The error logs update for the startup, but not when anything connects to localhost:8000. The last entry in uwsgi.log was two hours ago and nothing has been added since. I tried both lynx http://localhost:8000 and telnet to http://localhost 8000 and GET request instantly closes the port and logs nothing. As far as I can tell both mailman and postgres are working fine. This is what logs on startup. ==> uwsgi-error.log <== *** Starting uWSGI 2.0.22 (64bit) on [Sun Apr 14 10:45:51 2024] *** compiled with version: 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b] on 05 October 2023 13:37:28 os: Linux-6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) nodename: mail.rubinsoftware.com machine: x86_64 clock source: unix detected number of CPU cores: 4 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! your processes number limit is 15246 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 0.0.0.0:8000 fd 8 Python version: 3.11.5 (main, Aug 31 2023, 07:57:41) [GCC] PEP 405 virtualenv detected: /opt/mailman/venv/ Set PythonHome to /opt/mailman/venv/ Python main interpreter initialized at 0x7f2c3d709d58 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 250128 bytes (244 KB) for 4 cores *** Operational MODE: preforking+threaded *** added /etc/mailman3/ to pythonpath. WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x7f2c3d709d58 pid: 16064 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 16064) spawned uWSGI worker 1 (pid: 16065, cores: 2) spawned uWSGI worker 2 (pid: 16067, cores: 2) [uwsgi-daemons] spawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 72 gid: 67) 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile starting. 14:45:52 [Q] INFO Process-1:1 ready for work at 16072 14:45:52 [Q] INFO Process-1:2 ready for work at 16073 14:45:52 [Q] INFO Process-1:3 monitoring at 16074 14:45:52 [Q] INFO Process-1 guarding cluster white-green-ten-mobile 14:45:52 [Q] INFO Process-1:4 pushing tasks at 16075 14:45:52 [Q] INFO Q Cluster white-green-ten-mobile running. What should I do to diagnose further?

4 5

ModuleNotFoundError: No module named 'xapian_backend'
by Ron / BCLUG April 17, 2024

April 17, 2024

I had a working mailman3, tore it down, switched to PostgreSQL (from MySQL), and now everything is working, except: mailman-web update_index and mailman-web update_index_one_list They fail with: ModuleNotFoundError: No module named 'xapian_backend' I rebuilt and re-installed xapian: (venv) mailman@mail:~$ echo $XAPIAN_VERSION 1.4.25 (venv) mailman@mail:~$ pip list | grep -i xapian xapian 1.4.25 Any ideas? Thanks! rb

2 1

mailman3 digest sending questions and also adding docker to the mix
by bob B April 17, 2024

April 17, 2024

So I have been down the digest rabbit hole. So to confirm my assumptions/findings: Digest size threshold---- means when the total size of held messages hits this setting, a digest is sent Digest Volume Frequency. ---- specifies when the digest volume number gets incremented for digest messages, IT DOES NOT send out digests based on the setting, daily, weekly ... So what does the GUI setting "Send Digest Periodically yes no" do? how periodically does it send digests, if this is set to yes? If I want to send a digest out for a list every day, or every week, how do I set that, especially in the docker environment? Is this something that can be configured in the GUI and configured by each of my list admins? I found that ”'mailman digests --periodic' via cron” should be set in googling, but does that mean I have to do a cron job for any list that wants a scheduled digest sent? My use case is, that I have a list admin who set a size threshold, but regardless of that, they also want their list digest sent out daily, they thought it was the "Digest Volume Frequency" setting but that is not correct. However in their testing they are not getting daily digest, they are getting digests only when the threshold is reached, BUT they have "Send Digest Periodically" set to "yes" and "Enable Digests" is set to "yes"

7 17

hyperkitty.lib.utils Failed to update the fulltext index
by Ben Harris April 13, 2024

April 13, 2024

hello there, i migrated to a new host last night and i've been getting this error from a cronjob mail every minute. anyone have any ideas what would cause this? ERROR 2019-04-17 14:26:33,056 27205 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/utils.py", line 186, in run_with_lock fn(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/hyperkitty/search_indexes.py", line 87, in update_index update_cmd.update_backend("hyperkitty", "default") File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 276, in update_backend last_max_pk=max_pk) File "/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 178, in update self.setup() File "/usr/lib/python2.7/dist-packages/haystack/backends/whoosh_backend.py", line 126, in setup self.index = self.storage.open_index(schema=self.schema) File "/usr/lib/python2.7/dist-packages/whoosh/filedb/filestore.py", line 176, in open_index return indexclass(self, schema=schema, indexname=indexname) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 421, in __init__ TOC.read(self.storage, self.indexname, schema=self._schema) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 632, in read check_size("int", _INT_SIZE) File "/usr/lib/python2.7/dist-packages/whoosh/index.py", line 626, in check_size sz = stream.read_varint() File "/usr/lib/python2.7/dist-packages/whoosh/filedb/structfile.py", line 191, in read_varint return read_varint(self.read) File "/usr/lib/python2.7/dist-packages/whoosh/util/varints.py", line 102, in read_varint b = ord(readfn(1)) thanks, ben

5 8

Error -- postorius Un-handled exception
by Mark April 12, 2024

April 12, 2024

Hi All, I've just installed MM3 on a fresh Debian 12 using the Virtualenv method. (venv)...$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Postorius Version 1.3.10 After creating a couple of lists, the lists are shown in the table on the "Mailing lists" webpage as they should, but clicking on any of the listnames returns an error page: Something went wrong HTTP Error 500: {"title": "500 Internal Server Error"} And the Mailman log is a mystery to me, and no error is reported in the Nginx log ... # tail -f /opt/mailman/web/logs/mailmanweb.log ERROR 2024-01-24 05:41:46,327 51799 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/list.py", line 359, in get and 'hyperkitty' in archivers # noqa: W504 ^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen _collections_abc>", line 780, in __contains__ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ Could anyone steer me in the right direction for fixing this? Thanks, Mark

6 20

Sibling lists in Mailman3
by Markus Grandpre April 10, 2024

April 10, 2024

Dear list, after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or something similar) in Mailman3. How are sibling lists treated in Mailman3? Thank you in advance for your answers. Best Markus -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

4 5

Requesting help with a turnkey mailman installation
by biobee7＠gmail.com April 7, 2024

April 7, 2024

Hello Everyone! If you can install mailman turnkey on my server - email me biobee7(a)gmail.com

2 1

Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4
by Jered Floyd April 4, 2024

April 4, 2024

A heads-up for anyone else on RHEL 8, because the error is mystifying. django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for MariaDB 10.3. For some reason I haven't yet been able to identify, this causes pyMySQL integrations to fail with the mysterious error: django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is required; you have 1.4.6. (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is coming from as it appears... nowhere.) Bypassing that error check gives the more informative: django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found 10.3.39). Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past LTS, so I would recommend that Mailman systems be migrated to RHEL 9. --Jered

1 1

Question: What happens if I delete a user from all lists and that user is sole owner of some list?
by David Partain April 3, 2024

April 3, 2024

Hi, One of the great things about our new installation compared with our old is the ability to manage users via https://our.wee.domain/postorius/users I might have been able to manage them using the command line on the old installation, but there is no 'mailman delmembers' on that box. Since I now have this Mighty Power, I want to use it to clean up. There are many users who should no longer be on the system, so I want to run something along the lines of: mailman delmembers --member some(a)email.address --fromall \ --no-goodbye-msg --no-admin-notify or, if I'm feeling brave, something like this. mailman delmembers --file somefile --fromall \ --no-goodbye-msg --no-admin-notify My question is: If one of these users is the sole owner of a list, what will happen? Will the user be deleted and that list now owner-less? Will mailman refuse to delete that user until I add a new owner? Thanks in advance for your feedback. Cheers, David

3 4

Help with mailman2 to mailman3 archive migration
by francisco.lopezayuso＠sib.swiss April 2, 2024

April 2, 2024

Hello all, I'm having some issues with a migration I'm performing right now from our old mailman2 server to a mailman3 one. The mailing lists imports work fine, but the archives seems to work sometimes: This means that some lists archives appear but others are missing when browsing the archives in the web UI. This happens despite the command line telling me that the import went fine. Here are the steps I run for the archives: # Copy the archives into the my new server # Cleaning old archives, where $LIST is my mailing list name $ /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/contrib/check_hk_import /opt/mailman3/archives/private/"$LIST".mbox/"$LIST".mbox $ /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/contrib/cleanarch3 /opt/mailman3/archives/private/"$LIST".mbox/"$LIST ".mbox # Importing the archives $ mailman-web hyperkitty_import -l "$LIST(a)my.domain.com" /opt/mailman3/archives/private/"$LIST".mbox/"$LIST".mbox # Indexing the new archive $ mailman-web update_index_one_list "$LIST(a)my.domain.com" Here is also an example log of an archive I'm migrating that does not appear in the UI, for reference (list and domain were renamed for privacy): $ mailman-web hyperkitty_import -l my_list(a)domain.com --since=1900-01-01 /opt/mailman3/archives/private/my_list.mbox/my_list.mbox Importing from mbox file /opt/mailman3/archives/private/my_list.mbox/my_list.mbox to my_list(a)domain.com Computing thread structure Synchronizing properties with Mailman Adding admin as owner of MailingList: my_list.lists.domain.com 2070 emails left to refresh, checked 1000 2070 emails left to refresh, checked 2000 Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list my_list(a)domain.com'. $ mailman-web update_index_one_list my_list(a)domain.com Indexing 22 emails Any help would be greatly appreciated, I'm very lost here... Cheers,

2 1

Mailman stops processing....... where to start looking for root cause?
by bob B April 2, 2024

April 2, 2024

Today was the 2nd time mailman stopped sending out mail, it receives mail but sends nothing out. To resolve the issue I restarted the mailman services and then all the incoming/queued mail was sent out... last time this happened was 21 days ago.... Before that, it has been rock solid for years. We are running in a docker environment with no recent changes. On the host in /var/log/maillog, I see the mail coming in and going to mailman in docker. for docker, the mailman logs are in /opt/mailman/core/var/logs in /opt/mailman/core/var/logs/smtp.log ---------- I see the messages coming in /opt/mailman/core/var/logs/debug.log ------------ is empty /opt/mailman/core/var/logs/mailman.log -------------- I do not see anything that looks like it had an issue So where can I look to try to determine a cause? If it happens again, what and where can I cook to troubleshoot before restarting the service? Thanks

4 4

Seeking help completing a useful installation
by Hugh Esco March 30, 2024

March 30, 2024

I have more fully documented where I am at with this attempt to build a working installation of mm3 at this link: https://gitlab.com/mailman/django-mailman3/-/issues/73 My questions include: - the template for /etc/mailman3/mailman.cfg, defines vardir, but no DATA_DIR. See test failure #1 (closed) <http:///mailman/django-mailman3/-/issues/1>, above. Where does that want to be? Any issue with putting the mm3.db next to the mm3_web.db at /opt/mailman/mm/var/data? - there are two possible virtualenv's in my build: (a) /opt/mailman/venv/ and (b) /opt/mailman/.pyenv/. I say more about these below. Which do I want to use in this instance? I'm guessing the latter where the mailman3 libraries are published, but have doubts. The link above urges a dependency on python ^3.11, but bookworm provides only python 3.8, so I used pyenv to satisfy the requirement. It wanted to deploy to its own path, though perhaps there is some switch which would consolidate everything under /opt/mailman/venv/. I do not work with python enough to know. - attempts to run bin/mailman-web startapp mm3web fail to add any new processes to the process list. bin/mailman-web start fails with errors. What change of state to the server should I expect from running this command? How do I test for success? If startapp is the correct invocation, what argument does it want on a working installation? - having run the command in the previous point, I see nothing in the browser except for the apache starter page at the root path '/'. None of the paths defined in the apache2 configuration seem to offer any joy. I assume that uwsgi wants to proxy the requests to a running mailman-web service somehow, but that no such service is found. I see one hopeful line in the log at: /opt/mailman/mm/var/logs/mailman.log "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" - I assume that once I get apache2 wired to a running application through the uwsgi proxy, that I can proceed to create an admin user, use it to explore the web gui, and begin to consider how to migrate my legacy mm2.1 lists into the new installation. Any further help crossing the finish line would be appreciated. Thanks, -- Hugh

2 2

Disabling the footer on a mailing list: Is this how?
by David Partain March 28, 2024

March 28, 2024

Hi, I regularly get requests from users to disable footers since they use email clients that simply show an attached text file. Yes, I know that's broken. I never got this working with my old broken installation. Since we're now running a shiny new version of mailman3, I thought I'd give it a go again. From what I've read, I thought the following would do the trick: # sudo -u mailman -s /usr/bin/bash $ source /local/mailman/venv/bin/activate $ cd ~/var/templates/ $ mkdir -p lists/test-list.our.domain/en/ $ cp /dev/null "lists/test-list.our.wee.domain/en/list:member:regular:footer" However, sending mail to test-list(a)our.wee.domain<mailto:test-list@our.wee.domain> still includes the footer. What am I missing? Do I need to restart something? Did I misunderstand what I've read? With kind regards, David

2 2

See list of subscribers
by Tom Yates March 27, 2024

March 27, 2024

I'm sure I'm just doing something stupid, but I can't work out what. I have a list, as admin under "Settings" -> "List Identity" -> "Members List Visibility" I have it set to "Only Mailinglist Members". But a random subscriber, who's signed up and authenticated, when she visits the list page she sees her subscription, but no option to list the other subscribers. Is she looking in the wrong place? Do I need to open up more settings? Am I just being an idiot? Thanks for any light anyone can shed. -- Tom Yates - https://www.teaparty.net

2 2

Hyperkitty on Debian 12
by Markus Grandpre March 27, 2024

March 27, 2024

Dear list members, when following the instructions to migrate list archives from Mailman21 to Mailman3 (see [1]), I face the following problem: # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 /var/mailman21/testlist.mbox python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such file or directory and have no clue, where to find the right <manage.py> file. The command dpkg returns: # dpkg -l | grep hyperkitty ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives In </etc/mailman3/mailman-web.py> I find: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', ... Can you please help me? Thank you in advance? Best, Markus [1] <https://docs.mailman3.org/en/latest/migration.html> -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

5 7

Topics - Tags
by Mark March 27, 2024

March 27, 2024

Hi, I'm reading the docs on "Message tagging" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) as saying shell access is needed to: (a) enable topics, and (b) write the keywords. In Mailman 2 there is an Admin web UI for "Topics". Is there such a web UI that can be enabled in Mailman 3 so that the list owners can create topics (tags) in their lists? Thanks.

3 5

Deleting messages from HyperKitty archive
by Mark March 25, 2024

March 25, 2024

Hi, I'm running Mailman 3.3.9 with HyperKitty version 1.3.8 (venv installed as per the docs). As superuser (listmaster) I can "Delete message/thread" and "Delete archive". These options aren't there for the list owners. The docs (link below) say that in the newer HyperKitty version 1.3.9, list owners can delete messages/threads Is there a patch I can implement on HyperKitty version 1.3.8 (so list owners can delete messages), or is it possible to update HyperKitty to version 1.3.9 without bringing everything crashing down? *** https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html 1.3.9 (2024-02-27) List owners can now delete messages and threads and reattach threads. (Fixes #261) *** Thanks, Mark

2 4

Issue converting table charset to utf8mb4 on mysql
by Helio Loureiro March 24, 2024

March 24, 2024

3 3

How to fix lists with characters errors?
by Helio Loureiro March 24, 2024

March 24, 2024

Hi, I just found several lists have the issue like this regarding charset: (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members listas-charset-issue(a)mailman.domain.com anders(a)domain.com beth(a)domain.com charlie(a)domain.com david(a)domain.com ellen(a)domain.com Traceback (most recent call last): File "/local/mailman/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_members.py", line 222, in members display_members(ctx, mlist, role, regular, File "/local/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_members.py", line 109, in display_members print(f'{address.display_name} <{address.original_email}>', UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 9: ordinal not in range(256) Since this service is running since time of python2, I guess the old lists handled accented characters was to save as latin-1. But how can I fix this now? Note: apparently the list remains working just fine. It is just the command line failing. And perhaps some other side effect. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

2 4

Badsignature on uwsgi-error.log
by Helio Loureiro March 22, 2024

March 22, 2024

Hi, I keep receiving a lot of errors like this: --- Logging error --- Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher task = SignedPackage.loads(task[1]) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads return signing.loads( File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign result = super(TimestampSigner, self).unsign(value) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature('Signature "%s" does not match' % sig) django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit msg = self.format(record) File "/usr/lib/python3.10/logging/__init__.py", line 943, in format return fmt.format(record) File "/usr/lib/python3.10/logging/__init__.py", line 678, in format record.message = record.getMessage() File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting Call stack: File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py", line 22, in handle q.start() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 78, in start self.sentinel.start() File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen return Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ self._launch(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch code = process_obj._bootstrap(parent_sentinel=child_r) File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 168, in __init__ self.start() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 172, in start self.spawn_cluster() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 248, in spawn_cluster self.pusher = self.spawn_pusher() File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 201, in spawn_pusher return self.spawn_process(pusher, self.task_queue, self.event_out, self.broker) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 197, in spawn_process p.start() File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start self._popen = self._Popen(self) File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen return _default_context.get_context().Process._Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen return Popen(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ self._launch(process_obj) File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch code = process_obj._bootstrap(parent_sentinel=child_r) File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 358, in pusher logger.error(e, traceback.format_exc()) Message: BadSignature('Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match') Arguments: ('Traceback (most recent call last):\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher\n task = SignedPackage.loads(task[1])\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads\n return signing.loads(\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads\n base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age))\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign\n result = super(TimestampSigner, self).unsign(value)\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign\n raise BadSignature(\'Signature "%s" does not match\' % sig)\ndjango.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match\n',) The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY on setting.py are the same. Any clue what could be the issue? And this is on the latest mailman. > pip freeze aiosmtpd==1.4.4.post2 alembic==1.13.1 arrow==1.3.0 asgiref==3.7.2 atpublic==4.0 attrs==23.2.0 authheaders==0.16.2 authres==1.2.0 blessed==1.20.0 certifi==2024.2.2 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 cmarkgfm==2024.1.14 cryptography==42.0.3 defusedxml==0.7.1 Django==4.1.13 django-allauth==0.61.1 django-appconf==1.0.6 django-compressor==4.4 django-extensions==3.2.3 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.11 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 dkimpy==1.1.5 dnspython==2.5.0 docutils==0.20.1 falcon==3.1.3 flufl.bounce==4.0 flufl.i18n==5.0.2 flufl.lock==8.0.2 greenlet==3.0.3 gunicorn==21.2.0 HyperKitty==1.3.8 idna==3.6 lazr.config==3.0 lazr.delegates==2.1.0 mailman==3.3.9 mailman-hyperkitty==1.2.1 mailman-web==0.0.8 mailmanclient==3.3.5 Mako==1.3.2 MarkupSafe==2.1.5 mistune==2.0.5 mysql==0.0.3 mysqlclient==2.2.4 networkx==3.2.1 nh3==0.2.15 oauthlib==3.2.2 packaging==23.2 passlib==1.7.4 postorius==1.3.10 psutil==5.9.8 publicsuffix2==2.20191221 pycparser==2.21 Pygments==2.17.2 PyJWT==2.8.0 PyMySQL==1.1.0 python-dateutil==2.8.2 python3-openid==3.2.0 pytz==2024.1 rcssmin==1.1.1 readme-renderer==42.0 redis==3.5.3 requests==2.31.0 requests-oauthlib==1.3.1 rjsmin==1.2.1 robot-detection==0.4 six==1.16.0 SQLAlchemy==2.0.27 sqlparse==0.4.4 types-python-dateutil==2.8.19.20240106 typing_extensions==4.9.0 urllib3==2.2.0 uWSGI==2.0.24 wcwidth==0.2.13 Whoosh==2.7.4 xapian @ file:///local/mailman/xapian-1.4.23-cp310-cp310-linux_x86_64.whl zope.component==6.0 zope.configuration==5.0.1 zope.event==5.0 zope.hookable==6.0 zope.i18nmessageid==6.1.0 zope.interface==6.2 zope.schema==7.0.1 Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

4 6

need help to migrate from Mailman2 to Mailman3 (french if possible)
by pascalleval＠yahoo.fr March 22, 2024

March 22, 2024

Hello everybody, I'm trying to migrate my mailing lists on Debian 11 server from Mailman2 to Mailman3, and I'm having difficulties ! Mailman3 is already functional, but I could not configurate Postfix for this. Is there anyone speaking french that could help me ? Thanks in advance.

4 5

ValueError: The ADMINS setting must be a list of 2-tuples.
by David Partain March 21, 2024

March 21, 2024

Greetings, We're trying to move from an ancient and bad Ubuntu-package based installation of mailman3 to a venv-based do-it-the-right-way installation. # mailman --version GNU Mailman 3.3.9 (Tom Sawyer) Things seem much better than past migration attempts. We are, though, seeing tons of errors in uwsgi-error.log that look like this: Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 131, in __call__ response = self.get_response(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 140, in get_response response = self._middleware_chain(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 58, in inner response = response_for_exception(request, exc) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 144, in response_for_exception log_response( File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 241, in log_response getattr(logger, level)( File "/usr/lib/python3.10/logging/__init__.py", line 1506, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.10/logging/__init__.py", line 1624, in _log self.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 1634, in handle self.callHandlers(record) File "/usr/lib/python3.10/logging/__init__.py", line 1696, in callHandlers hdlr.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 968, in handle self.emit(record) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 128, in emit self.send_mail(subject, message, fail_silently=True, html_message=html_message) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 131, in send_mail mail.mail_admins( File "/local/mailman/venv/lib/python3.10/site-packages/django/core/mail/__init__.py", line 124, in mail_admins raise ValueError("The ADMINS setting must be a list of 2-tuples.") ValueError: The ADMINS setting must be a list of 2-tuples. Our ADMINS setting in /etc/mailman3/settings.py has ADMINS = ( ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), ) Can someone point me in a direction to correct this? Thanks in advance. David

3 4

mailman3 3.2.2 python3.8 problem on focal
by Thomas Stein March 21, 2024

March 21, 2024

Hello list! I saw a few posts regarding the "Uncaught runner exception: module 'time' has no attribute 'clock'" problem but no solution to that. It seems this issue sneaked in at some point. I was getting aware of it when suddenly notifications to non-member posts did not work anymore. Everything else seems still to work. So, what is the prefered solution here? Is it possible to "repair" focal? There is python2.7, python3.6 and python3.8 installed currently. Or do I need to switch to a supported distribution like debian something? Wait for ubuntu 24.04? Any hints are really appreciated. cheers! t.

2 3

SpamAssassin and clamav?
by Marisa Giancarla March 16, 2024

March 16, 2024

Is there a way to have mm3 use SpamAssassin and/or clamav? Marisa

3 3

How to disable global templates for all lists
by christopher.claus＠tgcamberg1848.de March 14, 2024

March 14, 2024

Hallo togeher, I´m using the docker version from maxking and mailman core-version 3.3.9. I was wondering why there were messages in the list with "non-configured" footers. I found the files > mailman-core:/opt/mailman# find / -name "*list:member:*" /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:generic:footer.txt /usr/lib/python3.11/site-packages/mailman/templates/de/list:member:digest:masthead.txt /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:generic:footer.txt /usr/lib/python3.11/site-packages/mailman/templates/ca/list:member:digest:masthead.txt /usr/lib/python3.11/site-packages/mailman/templates/nl/list:member:generic:footer.txt but I found no option to disable them. How can I disable these global list-configuration? Best regards, chrclaus

3 2

outgoing messages not sent in a busy loop
by Igor Serebryany March 13, 2024

March 13, 2024

incoming messages are showing up in hyperkitty but not going out as emails to list members. i've tried enabling the following debug logging: format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: info path: mailman.log [logging.smtp] level: DEBUG [logging.smtp-failure] level: DEBUG [logging.runner] level: DEBUG [logging.debug] level: debug [logging.smtp-failure] level: debug with these options, if i run `tail -f *` in the `log` directory of mailman, i get the following in essentially a busy loop: ``` ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1c9ad050> ==> debug.log <== Mar 13 19:08:46 2024 (17) [NNTPRunner] starting oneloop Mar 13 19:08:46 2024 (17) [NNTPRunner] ending oneloop: 0 Mar 13 19:08:46 2024 (18) [OutgoingRunner] finishing filebase: 1710356926.1738262+0a50dc0e393ba4de10bcdadb5376d4330f670c77 Mar 13 19:08:46 2024 (18) [OutgoingRunner] doing periodic Mar 13 19:08:46 2024 (18) [OutgoingRunner] committing transaction Mar 13 19:08:46 2024 (18) [OutgoingRunner] checking short circuit Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing filebase: 1710356926.2733445+d044aeb93be86fbf662b6e0feffc89d0f2e4eb66 Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing onefile Mar 13 19:08:46 2024 (18) [outgoing] <function deliver at 0x7fef1cda27a0>: <CADJyiOV1RAth=3CkNoHJ1qTVzedzX8BG0k6iwe019jXau30pLw(a)mail.gmail.com> ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1cb0f390> ``` which doesn't give me a lot to go on. anyone know what could be causing this or any way to get additional debug information?

2 1

Hyperkitty tracebacks: possible DB corruption?
by peter＠chubb.wattle.id.au March 13, 2024

March 13, 2024

Hi Folks, Just recently I've started seeing backtraces from Django when trying to view old threads in hyperkitty. They say that more than one LastView is being returned, and at a later date cannot delete a LastView. I'm using the Debian-packaged hyperkitty and postorius, but this code hasn't changed from upstream. The backtraces come when a logged in used revisits a thread. So I see: Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ MultipleObjectsReturned at /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ get() returned more than one LastView -- it returned 2! Then later on I see: LastView.objects.delete(pk=del_id) ^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Manager' object has no attribute 'delete' Here are the backtraces: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/thread.py", line 162, in thread_index last_view_obj, created = LastView.objects.get_or_create( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( and Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/2022/1/ AttributeError at /hyperkitty/list/devel(a)sel4.systems/2022/1/ 'Manager' object has no attribute 'delete' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 127, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 173, in _thread_list LastView.objects.delete(pk=del_id)

3 6

localtime() cannot be applied to a naive datetime
by Freerk Bosscha March 12, 2024

March 12, 2024

Since yesterday I get the following error-message when I go to the webinterface: ValueError at /admin/login/ localtime() cannot be applied to a naive datetime Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Exception Type: ValueError Exception Value: localtime() cannot be applied to a naive datetime Exception Location: /usr/lib/python3/dist-packages/django/utils/timezone.py in localtime, line 207 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: vr, 1 Mrt 2024 11:52:50 +0100 Mailman info: mailman info GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman3:xxxxxxx If this issue was posted before, i'm sorry, i haven't found it: Any ideas how to solve this issue would be appreciated Environment: Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Python Version: 3.9.2 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 145. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 143. response = response.render() File "/usr/lib/python3/dist-packages/django/template/response.py" in render 106. self.content = self.rendered_content File "/usr/lib/python3/dist-packages/django/template/response.py" in rendered_content 83. content = template.render(context, self._request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 169. with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py" in __enter__ 117. return next(self.gen) File "/usr/lib/python3/dist-packages/django/template/context.py" in bind_template 246. updates.update(processor(self.request)) File "/usr/lib/python3/dist-packages/postorius/context_processors.py" in postorius 38. mailman_day=(timezone.localtime(timezone.now()).day == MAILMAN_DAY), File "/usr/lib/python3/dist-packages/django/utils/timezone.py" in localtime 207. raise ValueError("localtime() cannot be applied to a naive datetime") Exception Type: ValueError at /admin/login/ Exception Value: localtime() cannot be applied to a naive datetime

2 2

Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)
by Wikinaut March 8, 2024

March 8, 2024

Hello, I miss sadly the option of both: i) discarding the current message of a sender (not member of a closed list) ; and in the same action ii) adding this person to the whitelist, i.e. accept further mails from this sender. How can this be achieved?

3 4

Re: [Mailman-Developers] Re: Help on Gitlab
by Mark Sapiro March 8, 2024

March 8, 2024

Plese keep the thread on the list. On 3/8/24 6:36 AM, Daniel Azubuine wrote: > Sir, I get this error > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python: can't > open file '/home/daniel/Documents/repos/mailman/mailman/setup.py': > [Errno 2] No such file or directory > ERROR: invocation failed (exit code 2)/ > _______________________________________________ summary > ________________________________________________ > ERROR: qa: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python > /home/daniel/Documents/repos/mailman/mailman/setup.py --name (exited > with code 2) > when i run tox -e qa. What is your tox version (tox --version)? You shouldn't need this, but adding ``` skipdist = True ``` in the [tox] section of tox.ini may help. > I also get this when i run tox -e py310-diffcov > ------------- > src/mailman/interfaces/listmanager.py (75.0%): Missing lines 37 > ------------- > Total: 4 lines > Missing: 1 line > Coverage: 75% > ------------- > > ERROR: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/py310-diffcov/bin/diff-cover coverage.xml --fail-under=100 --compare-branch origin/master (exited with code 1) This is expected output in this case. Line 37 in your src/mailman/interfaces/listmanager.py is not covered by any tests. Modifying the test_cannot_create_a_list_twice test in src/mailman/model/tests/test_listmanager.py to use assertRaisesRegex rather than assertRaises may help. See <https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRai…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

mm3 installation question
by advorkin＠cs.princeton.edu March 7, 2024

March 7, 2024

Hello, everyone. I just completed the initial installation by following the instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. The same goes for Lists and Archives. What did I do wrong? I've found some discussions online, but they seem to be related to a different installation, thus my confusion. Thank you!

4 10

mass unsubscribe/subscribe
by ronn.ramirez＠pge.com March 6, 2024

March 6, 2024

Hi Mailman Admins, Whenever we mass subscribe or unsubscribe more than 500+ users, we would get a "500-internal-server-error" or a timeout. Is there something we can tweak or increase to way to increase this threshold?

3 2

export/import list?
by Dave McGuire March 1, 2024

March 1, 2024

I'm migrating to a new Mailman3 instance, finally escaping a fairly old (3.1.1) and problematic distribution repo install on a Linux VM and moving to a venv install in a native SmartOS Zone. I've gotten everything running well and integrated with our (fairly complex) mail server. I'd like to begin migration of the lists on the old mm3 instance. Is there a way to export a list from one Mailman 3 instance and import it into another, on a different machine? Ideally some way to capture its settings, members, members' settings, etc? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

6 9

Migration from old server to new server failed
by Helio Loureiro March 1, 2024

March 1, 2024

Hi, So we tried to the migration following the steps: - stop mailman in the old machine (v3.1.1 from ubuntu packages) - dump DB mailman3 and mailman3web - backup /var/lib/mailman3 content On the new machine: - checkout from git the version 3.1.1 to match production and install the services - stop mailman3 and mailman3-web on the new machine - load DBs into new machine - copy content from /var/lib/mailman3 into /local/mailman/var (which means: archives/ cache/ data/ ext/ lists/ locks/ messages/ public_suffix_list.dat queue/ templates/ web/) - start mailman3 and mailman-3web - run mailman3-web migrate And I stopped here. Because it crashed. (venv) mailman@new-mailman3-server ~ (v3.1.1) [0|SIGINT]> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0003_alter_emailaddress_create_unique_verified_email... OK Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK Applying hyperkitty.0017_file_attachments... OK Applying hyperkitty.0018_threadcategory_color... OK Applying hyperkitty.0019_auto_20190127_null_description... OK Applying hyperkitty.0020_auto_20190907_1927... OK Applying hyperkitty.0021_add_owners_mods...Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) MySQLdb.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py", line 349, in handle post_migrate_state = executor.migrate( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py", line 130, in apply operation.database_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards schema_editor.add_field( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/schema.py", line 104, in add_field super().add_field(model, field) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 636, in add_field return self.create_model(field.remote_field.through) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 447, in create_model self.execute(sql, params or None) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 199, in execute cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") I tried to drop the table, but then it complained about another one. I dropped all the complained tables and as result hypperkitty never started. So I went back to see why the first error happened. Any clue what to do next? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 8

Google Summer of Code 2024
by Stephen J. Turnbull Feb. 26, 2024

Feb. 26, 2024

Hi, everybody It's that time of year again! PSF is in GSoC 2024, I'm 99% certain PSF will accept Mailman as a suborg (don't ask about the 1%, it's embarrassing ;-). Student applications open on March 18. So ... If you have ideas for improving Mailman 3, whether misfeatures that need fixing or cool new features, please consult our ideas page https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024 to get an idea of level of detail and style of description needed (and to see if maybe it's already there. You can send them to me if they're already formed in your mind, or send them here for input from users on requirements, or to mailman-developers(a)python.org for input on implementation feasibility and appropriateness for GSoC. If you know anybody who would be interested in participating as a contributor, please encourage them to look at us. Rules are somewhat relaxed from years ago. They still don't accept below college age, but they no longer restrict to students. They're also offering multiple period lengths from 8 to 22 weeks (stipends vary according to period and by price level in country of residence, see https://developers.google.com/open-source/gsoc/help/student-stipends) They're not as generous as a few years ago, at least for the "rich" countries (US, UK, Japan). You don't need to be an experienced coder or project manager to be a secondary mentor, just willing to communicate with the code contributor. If you're interested in being a primary or secondary mentor, the burden is likely to be "as much as you want". We rarely get more than one good application, and we have enough "default" primary mentors to cover the likely maximum number of slots we could be allocated. It would be very helpful to us and to the PSF organization administrators if you express interest and get signed up by the end of next week, but as far as I know we can add or substitute mentors at any time. Potential mentors should 1. Have a Google account (needed for step 2, and required by GSoC) 2. Sign up with Python-GSoC at https://forms.gle/coJYxhor6FAZcZfU8 3. If you have been a GSoC mentor or org admin in the past, go to https://summerofcode.withgoogle.com and accept the contributor agreement and program rules for 2024. (Definitely if you did last year, probably for 2022 the system still remembers you, and unlikely it has more memory than that.) Steve

1 0

Settings for prevention of spam obfuscation
by Richard Rosner Feb. 26, 2024

Feb. 26, 2024

Are there any settings that may help with making it easier seeing spam as spam? E.g. some mail programs, including Outlook, allow the user to set a from mail address that most mail clients will show instead of the true sender address, but the senders mail address is still present in the sender header field. While some people and companies carelessly abuse that functionality, hiding their true mail address, those bad practices also are abused my spammers and others. Does mailman have any settings that would remove any such obfuscations, e.g. in this case detect the manipulated from address and replace it with the sender address? While I do run my own spam filter, it's virtually getting harder every day to make sure you detect all spam while not having too many false positives. If it was possible to reverse at least the most obvious manipulations, that would probably already help. Also, it would make it much easier for the users to see at first glance who actually wrote an email. It's always less trustworthy if the senders address is shown as user3168(a)suspiciousdomain.gg instead of it being manipulated to say support(a)yourprovider.com.

3 8

Unable to get Postfix to bounce messages to non-existent lists
by skenny＠scss.tcd.ie Feb. 21, 2024

Feb. 21, 2024

We have Mailman working well in our environment, but there's one thing I can't seem to make happen no matter what I try. The situation is as follows: Postfix runs on on a different server than Mailman. Its main.cf says local_recipient_maps = $alias_maps transport_maps = regexp:/var/mailman-data/postfix_lmtp relay_domains = regexp:/var/mailman-data/postfix_domains The file postfix_lmtp is initially generated by Mailman (running on a different machine). A background process creates a version of the file wherein the lmtp IP address is changed to the network IP of the Mailman server, and that version is sync'd over to the Postfix server. On the latter, a typical block for a list then reads as follows (where A.B.C.D is the IP address of the Mailman server): /^some-list(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-bounces(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-confirm(\+.*)?(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-join(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-leave(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-owner(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-request(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-subscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 /^some-list-unsubscribe(a)lists\.scss\.tcd\.ie$/ lmtp:[A.B.C.D]:8024 The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. Many thanks Stephen Kenny

3 4

Hyperkitty is not archiving due to 405 error - GET instead of POST
by Matthias Feb. 15, 2024

Feb. 15, 2024

Hi there, I am running mailman3 on Debian 12 - latest package (GNU Mailman 3.3.8 (Tom Sawyer)). Message handling in general is working fine, but as soon as a message is released, archiving with Hyperkitty is not working, due to a 405 error: --- Feb 11 16:18:48 2024 (3479662) HyperKitty failure on http://lists.domain.tld/mailman3/hyperkitty/api/mailman/archive: (405) Feb 11 16:18:48 2024 (3479662) Could not archive the message with id <170766472771.3479669.4791049109141956450(a)otherdomain.tld> Feb 11 16:18:48 2024 (3479662) archiving failed, re-queuing (mailing-list jahrgang.domain.tld, message <170766472771.3479669.4791049109141956450(a)otherdomain.tld>) Feb 11 16:18:48 2024 (3479662) Exception in the HyperKitty archiver: Feb 11 16:18:48 2024 (3479662) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError --- When tracing this back, even the frontend Nginx server receives a get in his logs, hence I assume that hyperkitty is really creating a GET instead of a POST request? --- 217.72.204.162 - - [11/Feb/2024:16:18:48 +0100] "GET /mailman3/hyperkitty/api/mailman/archive HTTP/1.1" 405 0 "-" "python-requests/2.28.1" --- Any idea how to trace this down any further? Any help is really appreciated! Thanks, Matthias

2 2

Retrieve users from a list
by pau.baiges＠csuc.cat Feb. 11, 2024

Feb. 11, 2024

A moderator has deleted all the users from a list, is there a way to recover them?

5 6

add / remove / set moderation bit of non-members via mailman shell
by Zaheer Abbas Feb. 9, 2024

Feb. 9, 2024

I have a situation where I need to add / remove 10-20 non-members to a particular list every week and set the moderation bit to 'accept immediately (bypass other rules). I do the above via postorius because I couldn't find a way to do this via mailman shell. Can anyone help me please to achieve the above? I know how to remove all non-members via /opt/mailman/mm/bin/mailman shell -l list.example.com for nonmember in m.nonmembers.members: ... nonmember.unsubscribe() ... commit() I am just having difficulties adding the non-members and setting the moderation bit to 'Accept' Currently I am using Mailman 3.2.2 (La Villa Strangiato) and Postorius Version 1.2.4 so cant use 'postorius => settings -> message acceptance -> id_accept_these_nonmembers' -- Regards, Zaheer

2 1

Problems with mailman core translation and other details
by celi＠dieese.org.br Feb. 9, 2024

Feb. 9, 2024

Hi. We did a fresh install of the Debian Mailman 3 full package. I'd like all components to be translated into pt_BR. I downloaded the latest updated translations from weblate, which says that 100% of the project (all components) are translated. I checked and recompiled mailman.po with msgfmt without errors. I followed all instructions I saw, included the ones from the topic How to change the language in mailman3 in this list. Everything almost OK, except from the fact that none of mailman's core email messages are being translated, even though mailman.po shows the right messages. Also, strange things happen to these .po files. The web interface is almost perfect, but some messages (just some) are not correct - although the corresponding django.po appears to be OK. It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. #: templates/postorius/lists/summary.html:88 #, python-format msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" " " msgstr "" "\n" " Para se inscrever você pode enviar um e-mail com o assunto " "'subscribe' para\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " ou use o formulário abaixo:\n" What am I doing wrong? Or what can I do to make things suitable? Additional info: GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Postorius v. 1.3.4 HyperKitty v. 1.3.4 Thanx for any help

4 9

Hiding an ML from a site
by Odhiambo Washington Feb. 8, 2024

Feb. 8, 2024

I host two MLs on the same server/same MM3 instance. Under the Django Admin interface, I created two sites. I expected that each ML will belong to its own site and should not be visible on another site. On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two lists. How do I stop the "Users" list from showing up on this site ( https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own site - https://exim4u.org/mm/lists/ ? -- 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]

5 10

search this list searches more then just this list
by Marco van Tol Feb. 6, 2024

Feb. 6, 2024

Hi there, We run the following versions: mailman-core: 3.3.9 mailman-core-api: 3.1 mailman-core-python: 3.11.6 hyperkitty: 1.3.8 We have several lists on our server, I will write down a list of example list names that are good enough for the purpose of my question. xx(a)domain.tld <mailto:xx@domain.tld> yy-xx(a)domain.tld <mailto:yy-xx@domain.tld> zz-xx(a)domain.tld <mailto:zz-xx@domain.tld> When I now visit the archives for xx(a)domain.tld <mailto:xx@domain.tld> and enter a search phrase in “search this list”, the results include the other 2 lists. It looks like “search this list” searches for keyword in any listname that matches the one from "this list". Is there a way to really only search “this list” when I go to the archives for xx(a)domain.tld <mailto:xx@domain.tld>? I have tried to change the url for the results to have a ‘^’ in front of the listname, but that gives an error :-) Thanks in advance! Marco van Tol

4 23

Disable all mail capabilities
by Hope Less Feb. 2, 2024

Feb. 2, 2024

I have a decades old list that was abandoned on my server. I upgraded it to mailman3 but it never came back to life. It is causing me some grief. I want to keep the archives up but totally disable any mail capabilities. I have turned off mail for the domain but I still get 'crap' that tries to relay. I've manually tried to remove stuff from the transport tables in Postfix but I still get mail. I'm not sure where the problem lies. If I can't stop this I'll have to remove the list entirely which includes the archives. I really wish to leave the archives up. Any idea on how I can remove the mail capabilities and leave the rest? Thank You.

4 4

after upgrade: OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode
by Hans Mayer Jan. 31, 2024

Jan. 31, 2024

Dear All, recently I did a system os upgrade debian 11.8 -> 12.4 / bullseye -> bookworm This did also upgrade Mailman3 version 3.3.3 -> 3.3.8 as a used the packages which came with Debian OS. Initially after the upgrade I had some troubles with the MM3 services to start, but I fixed this. Now almost everything is running. Only the Archives are not working. The browser shows a server error, when I look at the mailman-web.log I see ERROR 2024-01-31 15:14:14,403 2699563 django.request Internal Server Error: /mailman3/hyperkitty/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 423, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode When I check the schema I find such a column in table "mailinglist" I assume there is only one solution, to uninstall and delete everything and start from scratch. Or is there a way the check all tables with a script and do an table update for missing columns ? Or a partial installation of hyperkitty, as I don't care about the archives. I am using sqlite3 as DB backend. Kind regards Hans --

2 1

transport map (postfix_lmtp) does not update - new lists not working
by Nils Jan. 29, 2024

Jan. 29, 2024

End of last year, I've re-installed mailman3 using the virtualenv installation method on ubuntu 20.04. Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) has not been updated even though, new mailing lists were created. The old mailing lists, that existed before the re-installation work perfectly fine but those created after are not accessible. Because the entries for those new lists are missing in the transport map, postfix replies with a "mail for ... loops back to myself" error. I'm quite sure, that I did all the steps in the documentation (except that I use a slightly different apache2 vhost configuration). I double checked on the cronjobs. crontab -u mailman -e @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly Any idea, what I could have missed??? Kind regards, Nils

2 2

Fresh installation mailman3-suite via "pipx" - any experiences yet?
by Wikinaut Jan. 27, 2024

Jan. 27, 2024

I recently found the "pipx" wrapper very useful and wanted to ask you if this could be facilitate the fresh installation of the mailman3-suite. Has anyone in the list already experiences installing mailman and mailmanweg through "pipx"? Here are my general tipps for using pipx # https://pipx.pypa.io/stable/installation/#on-linux sudo apt install pipx python3-venv To install a package systemwide for all users, I recommend the tip from https://github.com/pypa/pipx/issues/754#issuecomment-951162846 . sudo PIPX_HOME=/opt/pipx PIPX_BIN_DIR=/usr/local/bin pipx install <package>

4 6

Single Click Unsubscribe
by J D Jan. 26, 2024

Jan. 26, 2024

I know this has been discussed in the past: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… However, Google has recently announced that they will be enforcing one-click unsubscribe for bulk senders: https://techcrunch.com/2023/10/03/gmail-to-enforce-harsher-rules-in-2024-to… Thoughts?

5 5

mailman-web compress - Invalid template socialaccount/login_cancelled.html
by Odhiambo Washington Jan. 24, 2024

Jan. 24, 2024

Running an install on Debian12 VM. Getting a new error message that I haven't seen previously: (venv) mailman@debian12:~$ mailman-web compress Compressing... Invalid template socialaccount/login_cancelled.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Invalid template account/verified_email_required.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 13

share directories between postfix and mailman 3
by Thomas Schachtner Jan. 24, 2024

Jan. 24, 2024

Hi there, I think I have (finally) set up a working instance of mailman 3 on a host separate from the companion postfix mail server actually sending out the mails. One server (postfix) is directly in the internet and the other one is in an internal network not directly reachable from the internet (but connected using a reverse proxy). The services on the hosts are available to one another (i. e. the postfix server is reachable using 127.0.0.1:25 from mailman and mailman is reachable using 127.0.0.1:8024 from postfix using a permanent ssh tunnel betwenn the two hosts). I think that this solution could work quite reliably... (at least I hope so.) But that's not the full deal. Postfix needs access to some hashed configuration files containing the transport maps and the domains of the mailman installation, and mailman needs the contents of the postfix configuration file. As a quick and dirty solution, I've established a process which periodically copies the /var/lib/mailman3 directory from the mailman box to the postfix box using rsync. But I would like to have a more professional solution, like a directly shared directory between both. I did not yet find any suggestions on how to achieve this. Are there any best practices recommendations? I already tried sharing the directories using sshfs, but that did not work. I connected the remote directory postfix.example.com:/var/lib/mailman3 to my local directory /var/lib/mailman3 using sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 This seemed to work pretty fine, as all files and directories seemed to be available, but when starting mailman 3, the following error message was shown: FileExistsError: A race condition might have happened. /var/lib/mailman3 actually exists and is not a directory. Any idea why this message is shown? So, is it a bad idea to use sshfs? Do I have to install an NFS server? But I am not sure if sharing directories using NFS across the Internet is a good idea... Any suggestions? Best regards Tom

3 6

Re: Process on migrating mailman
by Odhiambo Washington Jan. 24, 2024

Jan. 24, 2024

On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > About 500 list. Not sure how to check size of the archives. > > On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> >> >> On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> >> wrote: >> >>> Any suggestion on how to migrate mailing list and archirve with >>> diffirent server and domain. For the mailing list from >>> sample.domain1.example.com to sample.domain2.example.com >>> >>> Old Mailing list >>> Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) >>> [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] >>> Domain Domain1.example.com >>> >>> New Mailing list >>> Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) >>> [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] >>> Domain domain2.example.com >> >> >> >> How many lists? How big are the archives? >> >> Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, >> it seems like it's not a trivial exercise. >> >> However, I am wondering about the consequences of: >> 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then >> re-importing >> 2. editing settings.py and webserver config to reflect the DOMAIN2 >> 3. reconfiguring your MTA to handle list mails using the DOMAIN2 >> >> I am imagining a virtualenv type of installation. >> > The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… . -- 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 3

log rotation for bounce.log
by Quanah Gibson-Mount Jan. 22, 2024

Jan. 22, 2024

I noticed that our smtp.log and bounce.log files haven't been rotated in years. I see the reason for smtp.log not being rotated is due to <https://gitlab.com/mailman/mailman/-/issues/931>. Does this same issue affect bounce.log or is it safe to rotate similar to mailman.log?

2 1

Extract a list of the lists and the administrators who manage it
by pau.baiges＠csuc.cat Jan. 22, 2024

Jan. 22, 2024

Hello, Is there a way to extract all the lists and show the administrators who manage those lists? Thanks!

3 2

emails to list missing from archive after upgrade
by Quanah Gibson-Mount Jan. 19, 2024

Jan. 19, 2024

So next issue post upgrade: I sent three emails to one of the lists today. All of them went to the list, as I got copies of each one, and the headers clearly show them coming from the list. However, when I go look at the archives for the list, they don't show up at all. And it's been over 8 hours since I sent them. --Quanah

2 3

Delivery to mail@domain.tld failed with code 444, [Errno 111] Connection refused
by christopher.claus＠tgcamberg1848.de Jan. 19, 2024

Jan. 19, 2024

Hi together, I´m using Mailman3.3.9 and postfix in docker containers seperatly. Everything worked fine since this afternoon. The error occurs, after postfix transports an incoming mail to mailman. After processing the mail, sending to all recepients failed >> Delivery to mail(a)domain.tld failed with code 444, [Errno 111] Connection refused I checked the configuration of postfix and added a wide IP-range to mynetworks: postfix-main.cf mynetworks = mailman-core tgc_mailman_core t 127.0.0.0/8 [::1]/128 [fe80::]/64 172.18.0.0/16 172.21.0.0/16 [2001:8d8:1800:283]/64 172.0.0.0/24 relay_domains = $mydestination #smtpd_sender_restrictions = reject_unknown_sender_domain,reject_unknown_reverse_client_hostname smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_relay_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_recipient_restrictions = permit_sasl_authenticated check_recipient_access hash:/etc/postfix/filtered_domains permit_mynetworks reject_unauth_destination smtpd_data_restrictions = reject_unauth_pipelining Does anyone have a clue for me as to why delivery to Postfix is failing? My last change a couple of days ago was adding an public ipv6-address to the host. But docker still works without IPv6. I thought about client-identification issues between maiolman-core and postfix but did noch find anything to fix ... Best regards, Christopher

2 2

moving list from mm3 -> mm3
by Jens Günther Jan. 19, 2024

Jan. 19, 2024

Hey there, I'm still trying to figure out, how to move a bunch of lists from one mm3-instance to another. If somebody has a working solution, I would be really glad to hear from it. I came across this thread, but I don't think it tackles my question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (or maybe I missed the right parts) We have equal setups and versions: - maxxking docker install 0.4.5 - Core 3.3.8 - API 3.1 - Postorius 1.3.8 ## Config So I found the possibility to get the config of a list via REST-API: curl -u restadmin:restpass localhost:8001/3.1/lists/$short.$domain/config | jq > short.domain This is a nice collection of the configuration of a certain list. Does anybody know how I would get this data back to the newly created list in the second working mm3-instance? Shouldn't it be possible via POST command? I thought of something like: curl -u restadmin:restpass -d @short.domain -H "Content-Type: application/json" localhost:8001/3.1/lists/&short.&domain/config But it returns {"title": "405 Method Not Allowed"} and I don't know where to look in the docs, since it shows almost always a way through mailman shell. Here I found something about POST: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but how would it work exactly? ## Members, moderators, owners To export all members I normally run within mm-core-container as user mailman the following command: mailman members &short.&domain > &short.txt To fill them back in, it can be done in Postorius (or is there a way through API?). What I would love to know is how to get out Owners of the corresponding lists and reimport them in the new one (which will be the same at the end :-D but different instance). ## registered users This part is somehow tricky, since I have no clue how to do it. Some of the mailinglist-admins don't want to bother their list-owners again with registering newly on the other system. Is there a way to export all users (I think I found them in the DB in the table auth_users, somehow in combination with account_emailaddress) and get them over to the new instance (actually I just need part of them, but that's another question that I might solve lateron on my own). Maybe the answer is already here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)? Thank you in advance, I hope it's not too much or too nooby :-) Jens.

3 10

All users getting disabled after upgrade of mailman3
by Quanah Gibson-Mount Jan. 19, 2024

Jan. 19, 2024

Hello, We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method). Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today). I used the mailman shell command from <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> to see who has been disabled. I had to make one fix to it, it should be m.list_name not mlist.list_name. Confirmed that dozens of valid users have had their sub disabled. In the logs I see: Jan 18 19:25:17 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 1. Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 2. Jan 18 19:37:11 2024 (952) Disabling delivery for quanah(a)fast-mail.org on list openldap-technical.openldap.org by bounce Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score 2 >= threshold 2, disabling delivery. Jan 18 10:05:42 2024 (938) Peer: ('127.0.0.1', 36100) Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) handling connection Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'LHLO hypatia.openldap.org' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'MAIL FROM:<openldap-commit-bounces(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) sender: openldap-commit-bounces(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'RCPT TO:<openldap-commit-owner(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) recip: openldap-commit-owner(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'DATA' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'QUIT' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) connection lost Jan 18 10:05:42 2024 (938) Connection lost during _handle_client() Jan 18 10:05:45 2024 (940) <170557233590.937.7274928299237969540(a)hypatia.openldap.org> post to openldap-commit(a)openldap.org from openldap-commit-owner(a)openldap.org, 20265 bytes Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> low level smtp error: [Errno 111] Connection refused Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> delivery to quanah(a)openldap.org failed with code 444, [Errno 111] Connection refused But... postfix is working fine, and I've had hundreds of emails generated *by* mailman about it disabling people due to bounces. Thoughts on how to proceed appreciated. Regards, Quanah

2 4

Splitting hosts: mta&core vs postorius
by Ruth Ivimey-Cook Jan. 18, 2024

Jan. 18, 2024

I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. I've checked the settings and I don't think I have misconfigured postorius. Is it possible that the bad url is being passed from core to postorius in some way and reused without changing the host? In the config at present, both hosts are visible to the browser, and each host can communicate with the other. Any ideas on how to pin down the problem better? Ruth

6 31

Process on migrating mailman
by Mark Labeste Jan. 18, 2024

Jan. 18, 2024

Any suggestion on how to migrate mailing list and archirve with diffirent server and domain. For the mailing list from sample.domain1.example.com to sample.domain2.example.com Old Mailing list Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] Domain Domain1.example.com New Mailing list Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] Domain domain2.example.com

3 3

how to migrate mailing lists to a new domain using mailman 3
by C. Souza Jan. 18, 2024

Jan. 18, 2024

In a few days my current domain will be disabled (it is out of my control) and I would like to know how to migrate the mailing lists to the new domain name. As a solution I added a new domain in mailman 3 and created a script that replicates the lists in this new domain. To forward the emails received by the old lists, the script removes the members and adds the email of the new list. Is there a fashionable way to do that? Also, one problem that I don't have a solution is the archive of the old lists. How to bring them to the new ones? Thanks for your help. My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: Package Version ------------------- ---------- 1 aiosmtpd 1.2.4 2 alembic 1.5.3 3 arrow 0.17.0 4 asgiref 3.3.1 5 atpublic 2.1.2 6 authheaders 0.13.0 7 authres 1.2.0 8 bleach 3.3.0 9 blessed 1.17.12 10 certifi 2020.12.5 11 cffi 1.14.4 12 chardet 4.0.0 13 click 7.1.2 14 cmarkgfm 0.5.2 15 cryptography 3.3.1 16 decorator 4.4.2 17 defusedxml 0.6.0 18 Django 3.0.12 19 django-allauth 0.44.0 20 django-appconf 1.0.4 21 django-compressor 2.4 22 django-extensions 3.1.0 23 django-gravatar2 1.4.4 24 django-haystack 3.0 25 django-mailman3 1.3.5 26 django-picklefield 3.0.1 27 django-q 1.3.4 28 djangorestframework 3.12.2 29 dkimpy 1.0.5 30 dnspython 2.1.0 31 docutils 0.16 32 falcon 2.0.0 33 flufl.bounce 3.0.1 34 flufl.i18n 2.0.2 35 flufl.lock 3.2 36 gunicorn 20.0.4 37 HyperKitty 1.3.3 38 idna 2.10 39 importlib-resources 5.1.0 40 lazr.config 2.2.3 41 lazr.delegates 2.0.4 42 mailman 3.3.2 43 mailman-hyperkitty 1.1.0 44 mailman-web 0.0.3 45 mailmanclient 3.3.2 46 Mako 1.1.4 47 MarkupSafe 1.1.1 48 networkx 2.5 49 nose 1.3.7 50 oauthlib 3.1.0 51 packaging 20.9 52 passlib 1.7.4 53 pip 21.0.1 54 postorius 1.3.3 55 psycopg2-binary 2.8.6 56 publicsuffix2 2.20191221 57 pycparser 2.20 58 Pygments 2.7.4 59 PyJWT 2.0.1 60 pyparsing 2.4.7 61 python-dateutil 2.8.1 62 python-editor 1.0.4 63 python3-openid 3.2.0 64 pytz 2021.1 65 rcssmin 1.0.6 66 readme-renderer 28.0 67 requests 2.25.1 68 requests-oauthlib 1.3.0 69 rjsmin 1.1.0 70 robot-detection 0.4 71 setuptools 39.2.0 72 six 1.15.0 73 SQLAlchemy 1.3.23 74 sqlparse 0.4.1 75 typing-extensions 3.7.4.3 76 urllib3 1.26.3 77 uWSGI 2.0.19.1 78 wcwidth 0.2.5 79 webencodings 0.5.1 80 wheel 0.36.2 81 Whoosh 2.7.4 82 zipp 3.4.0 83 zope.component 4.6.2 84 zope.configuration 4.4.0 85 zope.deferredimport 4.3.1 86 zope.deprecation 4.4.0 87 zope.event 4.5.0 88 zope.hookable 5.0.1 89 zope.i18nmessageid 5.0.1 90 zope.interface 5.2.0 91 zope.proxy 4.3.5 92 zope.schema 6.0.1 -- Carlos Souza

2 1

Postorius and some CSS issue?
by Odhiambo Washington Jan. 12, 2024

Jan. 12, 2024

Happy New Year to you too all. MM3 installed today using the virtualenv method. On my testbench, I am having this strange issue where the Postorius is not displaying correctly perhaps because of some CSS issue - or just my own hangovers! I have used the standard method as documented. The error I get: https://pastebin.ubuntu.com/p/dhvsHFG4jH/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 1

Loops back to myself
by David Krantz Jan. 12, 2024

Jan. 12, 2024

Hi, I have a problem with my Mailman 3-setup. The symptom is that postfix rejects non-existing addresses for my list domains with <adr(a)example.com>: mail for example.com loops back to myself What I guess happens happens is that postfix for some reason accepts the mail as it is for a relay domain and finds that it is not deliverable locally as the address does not exist locally and then tries to relay it on to the appropriate MX server, which is itself and then fails and generates a bounce message. This is a bit annoying as I have set up postfix to only accept valid addresses. I have set the transport_maps, local_recipient_maps and relay_domains to the files generated by MM3. I run an older version of MM3 (3.0) but prefer to fix this without upgrading as upgrading is a relatively big undertaking. This is mostly a backscatter problem for spam I guess. Any ideas of very simple and easy to forget things that I've probably missed? Cheers // David

5 6

Review requested for some merge requests
by Stephen J. Turnbull Jan. 10, 2024

Jan. 10, 2024

Reply-To set to Mailman Developers. Please check that your replies go there. Or you can comment on MRs directly if you have a GitLab login. I have three merge requests pending: [1] https://gitlab.com/mailman/mailman/-/merge_requests/1159 [2] https://gitlab.com/mailman/mailman/-/merge_requests/1160 [3] https://gitlab.com/mailman/mailman/-/merge_requests/1161 [1] fixes the logging initialization bug that prevented the `smtp` log from rotating properly, and maybe some others. I don't think it needs user review because it's a pure bugfix, but if you're curious and take a look, and you think it needs better documentation let me know. [2] adds a configuration variable `lmtp_max_size`. This is user-visible, so review of the documentation in docs/mta.rst and config/mailman.cfg for clarity and readability would be appreciated. [3] adds postfix-pgsql support for use of the PostgreSQL database to route Mailman traffic. It's really most useful in an edge case (migration of 10,000+ list Mailman 2 instances), but it's theoretically attractive on the principle of "single source of truth", and possibly for implementing a "microservices" style cloud instance (it eliminates the need for Mailman and Postfix to share a file system). Besides opinions on the value of the general idea I have two specific questions: - Postfix docs recommend not looking up domains in the database to reduce load on the database server. But on a dedicated Mailman system, you're going to be looking up pretty much everything twice anyway (once to check for local recipient and once to fetch the transport), and my experience so far is that this isn't a big load on Postgres, and it's not a drag on list traffic distribution. Should I implement domain lookup in Postgres? Should it be optional if the lists are being looked up in Postgres? - The current patch completely disables generation of the postfix_lmtp alias file, even for the `mailman aliases` command. Should I implement an option to force generation of the files for documentation (and maybe a backup in a very rare and contorted situation where Mailman can see Postgres but Postfix can't)? Thanks, Steve

3 3

Mailman 3 Core user assistance
by Tony Deshields Jan. 10, 2024

Jan. 10, 2024

I currently have a docker mailman stack that utilizes Django LDAP backend for authentication. I have my users attributes mapped as you see below in my settings.py file. Whenever a user logs into postorius with their 'uid', mailman-core uses their 'uid' as their email address instead of the 'email' attribute. Is there anyway to change this functionality? I would like my users to be able to login with their enterprise uid but be mapped to their email but I feel like there is a disconnect between Django and MM3 core. Any assistance is much appreciated. AUTH_LDAP_USER_ATTR_MAP = { "uid" : "userPrincipalName", "first_name": "givenName", "last_name": "sn", "email" : "mail", }

2 1

Docker mailman image can't access https://publicsuffix.org/
by bob B Jan. 9, 2024

Jan. 9, 2024

Thanks so it looks like Mailman can not get to publicsuffix. The wrinkle is I am running maxking's docker version. The host can get there, but not from the docker image. Any idea to to configure that? and this only comes into play when I set the dmarc settings.

3 8

The 'flufl.lock>=5.1' distribution was not found, but flufl.lock 8.0.2 was installed
by Nils Jan. 8, 2024

Jan. 8, 2024

3 2

The doubled entries issue
by Lars Bjørndal Jan. 7, 2024

Jan. 7, 2024

I've got the problem Multiple rows were found when one or none was required. I found the issue and a script here: https://gitlab.com/mailman/mailman/-/issues/657 I did su - mailman3 and ran: python scriptname.py and got: Traceback (most recent call last): File "/opt/mailman3/fix-doubled-entries.py", line 21, in <module> listmgr = get_list_manager() ^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/fix-doubled-entries.py", line 6, in get_list_manager return getUtility(IListManager) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/component/_api.py ", line 180, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfa ces.listmanager.IListManager>, '') (venv) 1[mailman3@dalen ~]$ Do I miss something? How can I fix the problem? Thanks, Lars

4 10

Archive import fails: "IndexError: list index out of range"
by Johannes Rohr Jan. 6, 2024

Jan. 6, 2024

I am now importing the archives of my old mailman2 installation. Unfortunately, with some of the larger and older lists, import fails halfway through, with an exception, the last message of which is IndexError: list index out of range Below is an example. This means that the last few years are missing from the archive in several lists. Are there any suggestions what I could do to still get them importet? Thanks! Johannes File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '@localhost>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 387, in handle importer.from_mbox(mbfile, report_name) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 212, in from_mbox progress_marker.tick(unquote(message.get("message-id", 'n/a'))) File "/usr/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range

6 10

Not receiving email from outlook or gmail.
by Mark Labeste Jan. 5, 2024

Jan. 5, 2024

From mailman web it was able to deliver the email to outlook and gmail but when replying or confirming subcription it can't reach the mailman. This error is bounce back from outlook. Server at destination.email.com (192.10.10.10) returned '400 4.4.7 Message delayed' 1/4/2024 12:16:13 PM - Server at destination.email.com (192.10.10.10) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketTimedout: Socket error code 10060 Thanks, mARK

2 1

Programmatically modify Thread-Topic *before* message is sent out the door?
by Thomas Ward Jan. 3, 2024

Jan. 3, 2024

We use a custom plugin to do numeric thread stamping, which has been working well in the code system. However, it was discovered by Microsoft that Microsoft Outlook and OWA prioritize the Thread-Topic header over the Subject header, which results in the oddness we've experienced in MS365 clients in testing. During our tasks though a custom handler goes through during the pipeline and modifies the Subject field accordingly, adding a thread tag to it. While this is 'fragile' it does work; the only problem is that Thread-Topic doesn't get altered. Programmatically, how would we alter the Thread-Topic during the handler's processing to prepend the corresponding prefix/tag so that when the message actually goes out the door it is properly sending with the modified Thread-Topic? Thomas

2 6

REST API for list owners/moderators
by mathias＠koerber.org Jan. 3, 2024

Jan. 3, 2024

Does Mailman 3 have an REST API that allows list-owners/moderators to perform list-management functions without having access to the whole server/other lists etc? ie, an API that uses the same credentials as Postorious but allows mass-subscription/un-subscription/membership-export etc and changes to list settings, membership settings (mod etc) via REST or python? The documentation seems to only indicate a single one-admin-user REST API that should not even be accessible from outside?

2 1

Message getting shunted with enabling Dmarc replace with list address
by bob B Jan. 3, 2024

Jan. 3, 2024

So we host a mailing list for domain X, the MX record points to us, we are domain y. If we have Dmarc set to "no dmarc mitigations" I can send a message from my email in domain Y and it goes to the list in domain x and is processed and sent out. If I set the dmarc to "replace with list address". the same message gets shunted. I included the logs below Not sure why it is trying to contact publicsuffix.org? ************* /mailman/core/var/logs/mailman.log Jan 02 20:41:50 2024 (29) No cached copy of the public suffix list found Jan 02 20:41:55 2024 (29) Uncaught runner exception: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) Jan 02 20:41:55 2024 (29) Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 174, in _new_conn conn = connection.create_connection( File "/usr/lib/python3.10/site-packages/urllib3/util/connection.py", line 95, in create_connection raise err File "/usr/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection sock.connect(sa) TimeoutError: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 703, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 386, in _make_request self._validate_conn(conn) File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn conn.connect() File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 358, in connect self.sock = conn = self._new_conn() File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 179, in _new_conn raise ConnectTimeoutError( urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)') During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/requests/adapters.py", line 489, in send resp = conn.urlopen( File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 787, in urlopen retries = retries.increment( File "/usr/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/runners/incoming.py", line 80, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.10/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 316, in check if maybe_mitigate(mlist, address): File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 292, in maybe_mitigate org_dom = get_organizational_domain(from_domain) File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 142, in get_organizational_domain parse_suffix_list() File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 109, in parse_suffix_list filename = ensure_current_suffix_list() File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 77, in ensure_current_suffix_list content = get(config.dmarc.org_domain_data_url) File "/usr/lib/python3.10/site-packages/mailman/utilities/protocols.py", line 39, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.10/site-packages/requests/api.py", line 73, in get return request("get", url, params=params, **kwargs) File "/usr/lib/python3.10/site-packages/requests/api.py", line 59, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.10/site-packages/requests/sessions.py", line 587, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.10/site-packages/requests/sessions.py", line 701, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.10/site-packages/requests/adapters.py", line 553, in send raise ConnectTimeout(e, request=request) requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) Jan 02 20:41:55 2024 (29) SHUNTING: 1704228115.0417743+619bfacfe7e6d030991468aa2707d065418c56e5

2 1

Editing the "example.org" site
by Stephen J. Turnbull Jan. 3, 2024

Jan. 3, 2024

Hi all, I don't know how many people will need this, but I just realized that you can edit Django's SITE 1 and (probably, 100% untested but I'm going on the clock so want to get this done quick :-) use that. When you add your first domain, there's a link in that page (not a button, a link!) to edit the domain list. Then you can click on the link to "example.org" in the list, and edit both display name (which I assumed) and the domain name. Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site <whatever.tld>" the whole time. :-) But then you have to edit the SITE = 1 statement in settings.py (which I often forget and hilarity ensues). Of course adding a web site and editing settings.py (which you have to do anyway for other variables) works too, but this seems cleaner to me. Steve

2 3

Can't edit lists anymore: "Something went wrong HTTP Error 404"
by Nils Dec. 30, 2023

Dec. 30, 2023

When I try to edit any list at "postorius/lists/LISTNAME.SUBDOMAIN.DOMAIN.TLD/", I get this error. The lists are displayed correctly at "postorius/lists/". Selecting any of those lists leads to that error. First step of creating a new list is possible but I get the same error right after the creation of the new list. These lines in the mailman.log seem suspicious: Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] Postorius Version 1.3.5 Here are the full logs of this event: mailman3/web/mailman-web.log ERROR 2023-12-29 11:59:30,571 2416033 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ [pid: 2416033|app: 0|req: 9/9] 2003:ca:bf1d:b000:efc2:8dfa:6fd:715f () {72 vars in 1618 bytes} [Fri Dec 29 11:59:30 2023] GET /postorius/lists/testliste.lists.DOMAIN.TLD/ => generated 6285 bytes in 466 msecs (HTTP/1.1 404) 7 headers in 227 bytes (1 switches on core 0) mailman3/mailman.log Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD HTTP/1.1" 200 384 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/owner HTTP/1.1" 200 640 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/moderator HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/config HTTP/1.1" 200 2132 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/archivers HTTP/1.1" 200 61 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/requests?request_type=subscription HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b HTTP/1.1" 200 286 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/addresses/USERNAME(a)DOMAIN.TLD HTTP/1.1" 200 369 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Kind regards

2 3

"From address" for list moderation notification
by ronn.ramirez＠pge.com Dec. 30, 2023

Dec. 30, 2023

Hi Mailman Group, I noticed that the from address for list moderation notifications are coming from a certain user address. May you please help me figure out where to change this? In this example, I would like to change the From address "listadmin(a)domain.com" ================================================================ -----Original Message----- From: Admin <listadmin(a)domain.com> Sent: Thursday, December 28, 2023 12:00 AM To: dummy-list <dummy-list(a)domainx.com> Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. The dummy-list(a)domainx.com list has 2 moderation requests waiting. Held Messages: Sender: user1(a)domain.com Subject: You missed a call | Transcription Available . Reason: The message is not from a list member Sender: user2(a)domain.com Subject: Update/Access Required Notice on Friday, September 29, 2023 Reason: The message is not from a list member Please attend to this at your earliest convenience. =================================================================

2 3

Again, after systemupgrade the log file in /var/log/mailman was owned by list:list instead of mailman:mailman and starting failed for this reason [support request]
by Wikinaut Dec. 28, 2023

Dec. 28, 2023

I made for a repeated time (after system update and/or system reboot) the experience,that my mailman3 installation fails to start because of permission error to write the log file. For some unknown reason, an empty file /var/og/mailman/mailman.log was apparently owned by list:list. I deleted that file and mailman3 core could now be started. The start problem i solved. I asked myself and you, how can this happen for many times? Has anyone an idea what the reason could be? There is still a user list from a previous mailman3 installation, where I assigned the (former user for mailman2), but I suppose the problem is a different problem than a simple user definition. The other log files are always correctly assigned to mailman:mailman <pre> -rw-rw---- 1 mailman mailman 7487 Dec 22 18:21 bounce.log 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 debug.log 4 -rw-rw---- 1 mailman mailman 1909 Dec 24 09:10 mailman.log 57448 -rw-rw---- 1 mailman mailman 58820418 Dec 24 09:00 mailman.log.1 108 -rw-rw---- 1 mailman mailman 108407 Oct 24 12:18 mailman.log.2.gz 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 plugins.log 232 -rw-rw---- 1 mailman mailman 229585 Dec 24 09:10 smtp.log 4 drwxr-xr-x 2 mailman mailman 4096 Oct 20 00:00 <font color="#729FCF"><b>web</b></font> </pre>

3 10

subscribing to a list from a WordPress site
by Johannes Rohr Dec. 25, 2023

Dec. 25, 2023

Dear all, is there a wordpress plugin/widget allowing visitors to subscribe to a mailman3 hosted mailing list? Else, what is the most convenient way? Sure, I could just link to the maiman site, but since joining a list is as easy as sending mail to LISTNAME-join, there should be a simple way to impement this. What is the best practice? Cheers, Johannes

2 1

Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`
by Wikinaut Dec. 22, 2023

Dec. 22, 2023

Wheras my older lists handled these format apparently correctly, I now cannot add any more "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> In any of these cases, only the part <mailaddress> is added. Is this strange behaviour know? What can be done to have the correct function back to working again?

2 1

django-allauth failures, but only for some users (independent of browser?)
by Jered Floyd Dec. 22, 2023

Dec. 22, 2023

Django-allauth seems to just be a basket of woes, but I figured I'd toss this one out there to see if anyone has seen similar: I have Google and Facebook social logins configured. They work fine for me. They work fine for most people. Huzzah! For some people, even when they use different browsers/OSes/etc, attempting a social login generates an error. On the callback, they get "Server error" "An error occurred while processing your request." These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! Any pointers for investigation? --Jered Internal Server Error: /accounts/google/login/callback/ ImproperlyConfigured at /accounts/google/login/callback/ You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. [...] Traceback (most recent call last): File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 84, in view return self.dispatch(request, *args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 162, in dispatch return complete_social_login(request, login) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/helpers.py", line 197, in complete_social_login sociallogin.lookup() File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 282, in lookup provider_id = self.account.get_provider().id File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( Exception Type: ImproperlyConfigured at /accounts/google/login/callback/ Exception Value: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. Raised during: allauth.socialaccount.providers.oauth2.views.view [... internal state elided ...]

2 14

mailman3-web generating huge amount of error logs
by Helio Loureiro Dec. 22, 2023

Dec. 22, 2023

Hi, Now my finished installation is generating a lot of errors and filling up /var/log/syslog 1GB in a few hours. The errors are like this one: Dec 21 08:42:17 new-server mailman-web[981806]: --- Logging error --- Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: task = SignedPackage.loads(task[1]) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads Dec 21 08:42:17 new-server mailman-web[981806]: return signing.loads( Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads Dec 21 08:42:17 new-server mailman-web[981806]: base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: result = super(TimestampSigner, self).unsign(value) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: raise BadSignature('Signature "%s" does not match' % sig) Dec 21 08:42:17 new-server mailman-web[981806]: django.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match Dec 21 08:42:17 new-server mailman-web[981806]: During handling of the above exception, another exception occurred: Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit Dec 21 08:42:17 new-server mailman-web[981806]: msg = self.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 943, in format Dec 21 08:42:17 new-server mailman-web[981806]: return fmt.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 678, in format Dec 21 08:42:17 new-server mailman-web[981806]: record.message = record.getMessage() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage Dec 21 08:42:17 new-server mailman-web[981806]: msg = msg % self.args Dec 21 08:42:17 new-server mailman-web[981806]: TypeError: not all arguments converted during string formatting Dec 21 08:42:17 new-server mailman-web[981806]: Call stack: Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/bin/mailman-web", line 8, in <module> Dec 21 08:42:17 new-server mailman-web[981806]: sys.exit(main()) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main Dec 21 08:42:17 new-server mailman-web[981806]: execute_from_command_line(sys.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line Dec 21 08:42:17 new-server mailman-web[981806]: utility.execute() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute Dec 21 08:42:17 new-server mailman-web[981806]: self.fetch_command(subcommand).run_from_argv(self.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 407, in run_from_argv Dec 21 08:42:17 new-server mailman-web[981806]: self.execute(*args, **cmd_options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 453, in execute Dec 21 08:42:17 new-server mailman-web[981806]: output = self.handle(*args, **options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py", line 22, in handle Dec 21 08:42:17 new-server mailman-web[981806]: q.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 78, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.sentinel.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 168, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 172, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.spawn_cluster() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 248, in spawn_cluster Dec 21 08:42:17 new-server mailman-web[981806]: self.pusher = self.spawn_pusher() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 201, in spawn_pusher Dec 21 08:42:17 new-server mailman-web[981806]: return self.spawn_process(pusher, self.task_queue, self.event_out, self.broker) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 197, in spawn_process Dec 21 08:42:17 new-server mailman-web[981806]: p.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 358, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: logger.error(e, traceback.format_exc()) Dec 21 08:42:17 new-server mailman-web[981806]: Message: BadSignature('Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match') Dec 21 08:42:17 new-server mailman-web[981806]: Arguments: ('Traceback (most recent call last):\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher\n task = SignedPackage.loads(task[1])\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads\n return signing.loads(\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads\n base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age))\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign\n result = super(TimestampSigner, self).unsign(value)\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign\n raise BadSignature(\'Signature "%s" does not match\' % sig)\ndjango.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match\n',) So any clue how to fix this? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 4

delete unverified accounts
by noemi Dec. 21, 2023

Dec. 21, 2023

Hi, I'm noticing that a lot of 'spammers' are registering themself via postorius. They do not send emails, neither they are in any list, so they are not technically spammers, but they are a lot [maybe around 500 subscribed in the last month]. While waiting for a captcha system[0] for the main distribution, I'm looking for a rapid/easy way to delete this accounts; since they are not 'verified', I was wondering if I can locate this information in the mailman3 database or if there is some easier way to delete all unverified accounts. Do some of you any help or indications? I'm using GNU Mailman 3.3.9 (Tom Sawyer). Thanks, noemi for pangea.org [ https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ]

2 1

Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?
by Pierre Malard Dec. 20, 2023

Dec. 20, 2023

Hi, Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3 installed on Debian 11? I specify that I want to stay in the Debian repositories, not a "hand" installation of MM3. I tested on a specific server. It was long and tedious but it seemed to me that it was working. In fact everything seems to work except the archive management :-( Here is the procedure followed: Stopping MM services Backup of the database (PostgreSQL) and the base MM directory Switch server from Debian 11 to Debian 12 and restart migrate the database from PG 113 to PG 15 (pg_upgradecluster 13 does this very well) Modify the file /etc/mailman3/mailman.cfg with a URL reference "postgresql://" instead of "postgres://" (see https://lists.mailman3.org/archives/list/ mailman-users(a)mailman3.org/thread/CU6YU44V4WLRJI3WJH2VBWO2HCUF4YEA/) update MM3 databases with "mailman-web migrate" restart MM3 and MM3-web With that MM3 works but not the archiving management! Note that there are no real error messages in the logs… In fact when we go to a list archive, we have pretty waiting wheels... infinite :-( The only reference in mailman3-web.log: [pid: 1429|app: 0|req: 12/12] NNN.NNN.NNN.NNN () {68 vars in 1445 bytes} [Mon Dec 18 16:35:56 2023] GET /hyperkitty/list/admin@ teledetection.fr/ => generated 37443 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 221 bytes (1 switches on core 1) If you have any solution... Thank you in advance, have a good day and happy Christmas -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Il n'y a pas de Paradis, mais il faut tâcher de mériter qu'il y en ait un ! » Jules Renard (1864-1910) - Journal, 10 septembre 1903 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 9