Mailman 3 December 2024 - Mailman-Users

Using Mailman at Hostmonster - default server IP
by ski＠brytt.net Jan. 13, 2025

Jan. 13, 2025

Help. I have been using mailman at hostmonster many years. Recently, email delivery to external domains stopped (yes, DNS / SPF/ DKIM/ DMARC all good). Hostmonster says it is a IP address issues Hostmonster - "The emails sent via Mailman use the IP address 127.0.0.1, which is the default IP address of the server. Unfortunately, when emails from this address are dropped due to mailing list restrictions, it becomes challenging to lift these restrictions, thereby preventing us from resolving the Mailman-related issues effectively. " Has anyone else experienced this problem? Is there a solution? Thank you, Michael

5 13

Removing subscriber with illegal email format
by Scott Neader Dec. 29, 2024

Dec. 29, 2024

Hello all! Somehow, one of our Mailman2 lists has a member with a bad email address, in the format of user@@example.com (i.e. two @ symbols). This is breaking at least one cron (disabled) I've tried removing the address via the backend admin, as well as command line, but it's not working. Any other ways to remove it? - Scott

3 8

Odd entries in smtp log for one of our lists
by Johnson, Bruce E - (bjohnson) Dec. 13, 2024

Dec. 13, 2024

One of our list owners got an odd notice from our institutional email security/spam management system (Mimecast) for a bounced email from her list. She was a bit confused because she hadn’t sent anything to the list (it operates as an announcement list, everyone is moderated) since Nov 26. Your message couldn't be delivered The message you sent to tvanhassel(a)yumaregional.org<mailto:tvanhassel@yumaregional.org> couldn't be delivered due to: Recipient email server rejected the message. Further information 5.7.1 Filter Rule 19 - BLANK E-MAIL FILTER (Filter Macro 2977) If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive. When I went poking through the logs I found a bunch of notices in the smtp logs that look like this, that I cannot connect to a message ID... smtp:Dec 12 15:57:46 2024 (1200) <mailman.0.1734044265.3351215.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.087 seconds smtp:Dec 13 08:48:10 2024 (1200) <mailman.0.1734104889.3402091.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.119 seconds smtp:Dec 13 08:50:47 2024 (1200) <mailman.0.1734105046.3402213.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.118 seconds smtp:Dec 13 08:52:53 2024 (1200) <mailman.0.1734105172.3402319.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.136 seconds smtp:Dec 13 08:54:06 2024 (1200) <mailman.0.1734105245.3402387.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.087 seconds smtp:Dec 13 08:55:49 2024 (1200) <mailman.0.1734105349.3402468.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.109 seconds smtp:Dec 13 08:56:58 2024 (1200) <mailman.0.1734105417.3402529.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.088 seconds smtp:Dec 13 08:59:37 2024 (1200) <mailman.0.1734105576.3402651.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.118 seconds smtp:Dec 13 08:59:59 2024 (1200) <mailman.0.1734105598.3402676.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.087 seconds smtp:Dec 13 09:00:33 2024 (1200) <mailman.0.1734105631.3402823.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.087 seconds smtp:Dec 13 09:03:00 2024 (1200) <mailman.0.1734105779.3402959.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.119 seconds smtp:Dec 13 09:17:29 2024 (1200) <mailman.0.1734106648.3403725.preceptors(a)lists.pharmacy.arizona.edu> smtp to preceptors for 1 recips, completed in 0.100 seconds These do not look like normal smtp entries; the last one for this particular list was on Nov 26 and looks normal: smtp-20241201:Nov 26 12:32:27 2024 (1200) <CY5PR19MB63373BA001AA415698B3D026E02F2(a)CY5PR19MB6337.namprd19.prod.outlook.com> smtp to preceptors for 1202 recips, completed in 0.989 seconds Are these retry entries for failed deliveries? Or should I be concerned this is some sort of attack on our list server? (we’re using Postfix for an MTA) -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs

2 1

Looking For Help
by James Schaum Dec. 13, 2024

Dec. 13, 2024

To Whom It May Concern, The organization I work for is looking for a consultant who can assist in the migration of a mailman v2 environment to mailman v3. Any information would be appreciated. Thank you. Jim Schaum

2 1

sudden (?) issue with subscription options CGI
by ddewey＠cyberthugs.com Dec. 1, 2024

Dec. 1, 2024

Have an older RHEL 7 Mailman2 server that's worked flawlessly for years, but whose time is short... new MM3 server slowly being built. However, one of my members alerted me today that they were unable to log into the Subscription Options page due to a 500 Server Error. The page itself displays fine, but entering the username and pass results in the server error. Only thing I see in the apache error logs is as follows (listdomain and list name obfuscated): End of script output before headers: options, referer: https://list.listdomain.com/mailman/options/listname As far as I know (dangerous), this was working fine post-last upgrade, which was September '23, and everything else is working fine other than the Options cgi. Running mailman-2.1.39 installed from source. Minimal config options on build - ./configure --with-cgi-gid=apache Apache httpd-2.4.6-99.el7_9.1 Python 2.7.5 Any other hints to try to debug this? Didn't see anything at all in any of the Mailman logs. Thanks for any suggestions!

2 9