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

Message is received but is not sent out. Another, similar message, is processed fine.
by Allan Hansen June 27, 2023

June 27, 2023

Hi all, One of my subscribers is trying to send a message to a list, but it is not being posted. The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: mailman@list:~/logs$ grep herName smtp.log Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=40109' Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com> post to theList(a)domain.tlc from herName(a)hotmail.com, 40061 bytes Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18343' Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=19123' Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18930' Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com At the second retry she copied me and I saw nothing untowards in her message. She's not getting any error return messages and her subscription is OK. Both messages were multipart/alternative and both contained Hebrew text. I told her I'd look at this, but I'm at a loss. Yours, Allan

3 6

Problems after upgrading from bullseye to bookworm
by Eggert Ehmke June 27, 2023

June 27, 2023

I upgrade my server to bookworm. In the process python was upgraded from 3.7 to 3.9 . I reinstalled the virtualenv and the mailman packages. When I now start mailman-web, I get this in web/logs/uwsgi-error.log: pkg_resources.DistributionNotFound: The 'flufl.lock>=4.0' distribution was not found and is required by hyperkitty What did I miss? ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 5

attachment.html
by Sam Darwin June 27, 2023

June 27, 2023

Hi, Using a typical modern email client such as Gmail, the messages are usually html formatted. Then, Hyperkitty displays attachment.html on every message. Can that be removed? I was searching for the topic "attachment.html" in the archives and there wasn't much information. What finally cracked the code was Mark's comment: If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. It turns out "Filter content" affects many settings. It's easy to skip over that. I wonder if the UI might call attention somehow, with a graphic element, or with text: "Settings on this page will not take effect. Because 'Filter content' has not been enabled". It is right that "Filter content" must be set in order to remove attachment.html ? And now, a search will have more results. :-)

2 3

clicking on a username when viewing a thread results in "Page not found"
by Ken Alker June 27, 2023

June 27, 2023

If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? Also, why is it that some usernames are not clickable (ie. black text with no hyperlink)? Thanks! Ken

3 4

old usernames appearing in mailman.log
by Ken Alker June 27, 2023

June 27, 2023

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. The server has been active for over 20 years. I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one: Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 where "old-user(a)domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) Ken

2 8

Global ban using regex
by Henrik Rasmussen June 27, 2023

June 27, 2023

Using some regex testers and generators like https://regex101.com and https://www.site24x7.com/tools/regex-parser.html, the regex (.*)(a)inker\.azerbaijan\.su seems to match EVERYTHING(a)inker.azerbaijan.su (EVERYTHING is constantly changing in current spam mails). However, entering the regex to the Global Ban Add ban /postorius/bans/ result in: `An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got (.*)(a)inker\.azerbaijan\.su.'` Same result when using [Ban list] in postorius/lists/[LISTNAME]/bans/. Entering a none regex addresses like eknejfj(a)inker.azerbaijan.su works fine. Does Mailman use a different regex syntax I am using GNU Mailman 3.3.4 (Tom Sawyer) and Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] (maxking/mailman-core:0.3 and maxking/mailman-web:0.3)

2 1

starting gunicorn per mailman.log yet gunicorn not installed
by Ken Alker June 27, 2023

June 27, 2023

I see the below in my mailman.log, yet I installed uwsgi and NOT gunicorn. My mainmanweb.service file includes "ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" and not the gunicorn equivalent. Does this log entry make sense in my case? [2023-06-22 12:44:36 -0700] [411132] [INFO] Starting gunicorn 20.1.0

4 7

messages stuck in the bad queue
by Ken Alker June 26, 2023

June 26, 2023

I am working on a mail server that was migrated from mailman V2 to mailman V3 in February. I just noticed that there are over 1000 messages in the bad queue. All of the messages in the bad queue are dated 2/2/23 and all have a timestamp within a one-hour window of each other. I used mailman qfile to inspect five random emails in the bad queue and so far they are all "successfully subscribed" emails, but I presume there are no guarantees there aren't others mixed in there that might be legitimate emails (ie. I just unshunted 140 emails in the shunt queue and they were all good emails and all got processed). I figure that the easiest way to inspect these 1000 emails is just to have them re-delivered. I tried moving one from the bad queue to the shunt queue and I ran "mailman unshunt" but nothing happened. Is there a way to reprocess the bad queue? Also, what exactly is the bad queue? Thank you, Ken KA6KEN (happy field day weekend)

2 4

re-injecting emails that were not archived
by Ken Alker June 25, 2023

June 25, 2023

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. I noticed when I came onto the project last week that there were 140 messages stuck in the "shunt" queue for the two lists hosted by this server (I have no idea why and the old logs were not available and I don't recall the results of "mailman qfile", assuming that had shed some light on the reason why they were shunted). In any event, I unshunted these messages and they flowed out to the subscriber's email addresses successfully. What I was not expecting is that the system did not inject any of these emails into the archive. AFAICT, the messages are no longer anywhere on the system (but I could be mistaken). Here are my questions: 1) Why would these emails not have been injected into the archive? 2) Is there some way for me to re-inject these messages into the two lists? The only place I (THINK I) have them is in my own personal IMAP box since I'm a subscriber to the lists. 3) Can this be done without the emails being re-delivered to subscribers? Thank you, Ken

2 1

Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question
by Ken Alker June 25, 2023

June 25, 2023

As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv> My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories. That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman). So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.

2 6