- Mailman-users - lists.mailman3.org

MM3 not processing some mails from specific user
by Stefan Bauer 12 Aug '22

12 Aug '22

Hi, we are running MM3¹ and from time to time, a mail to a mailing list is not processed by MM. MM sees the mail but still does nothing with it. If another user is sending _same_ mail, it is processed. Any idea what that could be? Here are some logs: Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) handling connection Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'LHLO mal01.mydomain.tld' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'MAIL FROM:<john.doe(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) sender: john.doe(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'RCPT TO:<ssa(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) recip: ssa(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'DATA' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'QUIT' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) connection lost Here is a snipped from same user, but different mail that is also not processed by MM: Subject: =?iso-8859-1?Q?Kleine_=C4nderung?= From: john.doe(a)mydomain.tld To: =?us-ascii?Q?ssa=40mydomain=2Etld?= <ssa(a)mydomain.tld> Date: Wed, 10 Aug 2022 12:33:36 +0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c" Thread-Index: AdistWce8WLKbSqIReeBnR+y5yR5Mw== Message-Id: <kcEE.3C4Toxi/SomLpNH7qUNdhg.gBB2y7Ws2AE(a)mx1.mydomain.tld> This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Das ist ein Test --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c-- Any help is greatly appreciated. Thank you. ¹ 3.1.1-9 (update is scheduled)

3 5

Getting information to connect mailman to new web host
by tg337＠drexel.edu 11 Aug '22

11 Aug '22

We moved over to a new platform and now our lists.(domain).org address is not working. I'm trying to find the records I would need to update on the new site to connect them, and not sure how.

2 1

Mailman recovery test did not go as planned
by bob B 09 Aug '22

09 Aug '22

I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. I need to perform a DR recovery test. I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). While Mailman was stopped, I had our database team take a backup dump of the database. I then restarted Mailman in docker. I threw some more messages at a test list. I validated that the new messages were delivered, and showed up in the archive. I shut down Mailman again. I had the database team restore the Mailman database from the backup. I started Mailman I logged into Mailman I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. When went into the list archive, I get a spinning icon and no messages showed up. I quit, restarted my browser, and logged in again, and the same thing. I then sent a test message to the list and the message was delivered to the list. Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Is this normal? After a restore did the new message cause a refresh of archived messages etc? Is there a way to do this without sending a message to a list after a restoration of the database? Are there better steps I should take when restoring the database? Thanks

3 6

Detectors and Bounces
by summersan＠nclack.k12.or.us 05 Aug '22

05 Aug '22

Hello All, I've recently upgraded a Mailman 3 server from Debian 10.12 to Debian 11.4 [1]. In that process, I've also upgraded Mailman 3 from version 3.3.4 to version 3.3.5. I think the following guide was originally used when setting up Mailman 3 on the present server: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 . After that upgrade process, I've noticed that at least one `mailman` process and one `postgres` process were at something like 40 %CPU or higher for extended periods of time (seen using `top` command). Upon further inspection, and through some research online, it seemed like the issue might have to do with bounces (maybe not processing or something) [2][3][4][5][6][7][8]. In my logcheck logs, I was seeing this message multiple times a second: `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` I ended up trying to clear out the `/opt/mailman/mm/var/queue/bounces` and `/opt/mailman/mm/var/locks` directories to see if that would help. There seemed to be some sort of positive change, because the log message "spamming" seemed to decrease. The high %CPU for the `mailman` and `postgres` processes in question also seemed to go down over time. But the related `mailman` process would still run at a high %CPU from time to time. I tried checking the `mailman` process using `strace` at some point, but I didn't see an easily evident cause for what was going on—from what I remember, there was something about a "POLLIN" or something that kept looping. When I go to check the same `mailman` process with `strace` today, I just see occasional messages like this: `select(0, NULL, NULL, NULL, {tv_sec=45, tv_usec=43171}) = 0 (Timeout)` My Questions: Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? Should there normally be other detectors listed in the logs beyond the `DSN` one? If so, is there a setting I can change somewhere to make this happen? For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Here is an example of previous log lines: Running detector: <class 'flufl.bounce._detectors.sina.Sina'> Running detector: <class 'flufl.bounce._detectors.llnl.LLNL'> Running detector: <class 'flufl.bounce._detectors.exim.Exim'> Running detector: <class 'flufl.bounce._detectors.qmail.Qmail'> Running detector: <class 'flufl.bounce._detectors.exchange.Exchange'> Running detector: <class 'flufl.bounce._detectors.netscape.Netscape'> Running detector: <class 'flufl.bounce._detectors.dsn.DSN'> Running detector: <class 'flufl.bounce._detectors.caiwireless.Caiwireless'> Running detector: <class 'flufl.bounce._detectors.aol.AOL'> Running detector: <class 'flufl.bounce._detectors.yale.Yale'> Running detector: <class 'flufl.bounce._detectors.smtp32.SMTP32'> Running detector: <class 'flufl.bounce._detectors.groupwise.GroupWise'> Running detector: <class 'flufl.bounce._detectors.simplewarning.SimpleWarning'> Running detector: <class 'flufl.bounce._detectors.microsoft.Microsoft'> Running detector: <class 'flufl.bounce._detectors.postfix.Postfix'> Running detector: <class 'flufl.bounce._detectors.simplematch.SimpleMatch'> Running detector: <class 'flufl.bounce._detectors.yahoo.Yahoo'> Thank you for your time, Andy ----- Web References: [1] https://www.debian.org/News/2022/2022032602 [2] https://mail.python.org/archives/list/mailman-developers@python.org/thread/… [3] https://phabricator.wikimedia.org/T282348 [4] https://mail.python.org/archives/list/mailman-users@python.org/thread/MISUM… [5] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [6] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… [7] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [8] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

2 9

Rpsamd greylist configuration for Mailman3
by Prasanth Nair 03 Aug '22

03 Aug '22

Hello, I'm in the process of configuring Rspamd with the Mailman3 server. If Rspamd flags a message under 'greylist' and accepts it after the temporary rejection, is there any way mailman can move that message to the moderator's queue? if it is possible, can someone send me the instructions, please? Kind regards, Prasanth Nair

2 2

Mailman 3 questions (purge archives, list metrics, and auto discard held messages)
by bob B 02 Aug '22

02 Aug '22

Some quick mailman3 questions --Just wanted to check that there is still no way for mailman3 to automatically purge archived emails after a set amount of time? it looks like you have to export the database, purge the messages, then re-import, is this still the only/best way to purge old archived messages? --I noticed on the list info page you have metrics, which is straightforward except for "volume" My volume number is not increasing? What is that counting exactly? --Is there any way to auto discard held messages after x amount of time? I assume not but had a user ask if that was an option. Thanks for the assistance in advance.

3 4

Mailman 3 Consultant needed
by Mark Taylor 01 Aug '22

01 Aug '22

A customer we support wants to migrate a substantial Mailman 2 installation to Mailman 3. We have a team that can handle much, even perhaps most of this, but it’s an important project and we’d prefer to have a deep expert on the team for help/advice and the heavy lifting. Can anyone here recommend and engineer, perhaps even you, who could get involved with us commercially to help make a Mailman 2 to 3 migration successful? Thank you all, and I hope I’ve not violated any list guidelines by asking… You can contact me off-list if you prefer - I’m quite easy to find… Best regards to all, Mark Mark Taylor, Chief Executive Officer SiriUS: Infrastructure for Entrepreneurs® https://www.siriusopensource.com t: +001 509 254 5005

1 0

Programmatic Creation of Users
by jciesla＠techsupportme.com 30 Jul '22

30 Jul '22

I am returning to Mailman after being away for a LONG time and I need to create 40 lists with ~350 subscribers spread across those lists. After a lot of testing I am now able to create users from the Core Shell and set (most of) the necessary values. Having jumped that hurdle I have hit a roadblock and I am hoping that the list can provide some insight and/or solutions. After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? Any information is greatly appreciated! -John

2 1

User display name entry field input ignored
by Christian 27 Jul '22

27 Jul '22

Whether I try and add users using mass subscribe, or individually, it seems the display name field entry is ignored. The default is then "none" for the user. Please advise. Thank you!

2 3

Shorted Subjects in Mailman
by Stephan Krinetzki 27 Jul '22

27 Jul '22

Hello all, We have been experiencing the following problem lately: When a user sends a mail with an unusually long subject to a mailing list, this subject is shortened. Here are the two examples: Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos Anti-Virus on" (57 characters long) Is there a rule that Mailman truncates the subject or why does this happen? Is there any way to work around this? In the Mailman Topic Header, however, the full subject is always readable. Translated with www.DeepL.com/Translator (free version)

4 13