Mailman 3 - Mailman-Users

mailmanlists.net unreachable via email?
by Brie Yoder Sept. 9, 2026

Sept. 9, 2026

I am one of those who had been hosting email lists with Dreamhost, who moved over to mailmanlists.net <http://mailmanlists.net/>. The experience has been mostly very good - they have been very responsive and helpful. However, in a recent spate of bounces from Apple domains (e.g. mac.com <http://mac.com/>, icloud.com) and MS domains (e.g. msn.com <http://msn.com/>, live.com <http://live.com/>) I have been trying to contact support(a)mailmanlists.net <mailto:support@mailmanlists.net> for help and now emails to THEM are bouncing - they are hosted with MS 365. Is anyone from mailmanlists.net <http://mailmanlists.net/> on this list? I guess I will need to call them in Australia ugh… -Brie

4 7

Re: P.S. Re: Re: problems with mailman version 2 and bounce messages.
by Stephen J. Turnbull Aug. 30, 2026

Aug. 30, 2026

Richard writes: > Thanks Steve, a helpful reminder: Mostly this is a set-and-forget > task for me and I presume many of us since such things are usually > stable for long periods. It is for all of us. But sometimes it's chaos, which is why we provide these lists. You're welcome here (although I hope you can move on to Mailman 3 if you're not already there!) Even if you just need to blow off steam. We all deal with the frustration, even those of us who make it our business to "keep up with the Joneses" (or should I say "feed my jones"?) *Some*body is always out there making mistakes, whether "honest" ones, or "moving fast and breaking things". And sometimes it's us, so stay humble. ;-) > the worst offender of which is Google in my experience. Businesses that provide free stuff on an ongoing basis are invariably antisocial, and untouchable because people love the free stuff. IIRC Google invented the model of free stuff + surveillance capitalism, but half of Silicon Valley piled right in. Somebody would have invented it soon enough. We just have to remind ourselves that Silicon Valley is a nest of stochastic horrors, and invest in perimeter defense. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 5

DreamHost ending discussion lists
by Michael Welch Aug. 25, 2026

Aug. 25, 2026

Mailman friends. We just got the horrible news that DreamHost is going to axe all discussion lists in about 2 months -- no more Mailman. They just sent an email announcing this. Our account at DreamHost is a free nonprofit account, been using their Mailman service since 2008. We have several Mailman 2.1.39 lists there, two of which are extremely important technical lists for solar installers across the nation. We could use some suggestions on new hosts for the Mailman lists. Preferably no- to low-cost to our nonprofit organization. And we will need some help migrating the lists and Pipermail archives to a new site. And possibly an upgrade to Mailman 3. Any suggestions / help will be greatly appreciated.

19 41

problems with mailman version 2 and bounce messages.
by Bernard Hemmings Aug. 24, 2026

Aug. 24, 2026

My hosting company uses version 2 of mailman and over the past 2 months I am getting so many of these bounce error messages. Action: Subscription bounce score incremented. Reason: Excessive or fatal bounces. I am getting these regardless of whether the recipient receives list traffic or not. Earlier today I received 140 of these messages. My hosting company has suspended all email from my domain both email list and personal address twice due to these error messages being considered as spam like behaviour Eventually I had to unsubscribe all list members to demonstrate to my hosting company my accounts were not sending spam. After a week during which time I tested every member's address using a gmail account and the bcc address field sending 99 simultaneous messages. I resubscribed all the tested addresses and set bounce processing to send me copies. Two or 3 days later 70 addresses caused bounce messages so I removed these 70 addresses many being hotmail addresses. Now tonight 140 bounce messages came through. My list has about 360 members but at this rate there won't be any if I keep having to remove addresses. This is upsetting for members especially when they configure and save settings. I have used mailman for many years but if all email from my hosted domain is suspended again I'll have to find another email list system. Everything was fine up until about 3 months ago. A friend suggested I switch to another hosting company but he has done this and his accounts have been suspended twice for the same reason. Again this is due to mailman bounce errors being seen as your accounts being accessed to send spam. I know of other list owners which run much smaller lists than I do and they are experiencing the same bounce messages regardless of the list member receiving the list email or not. I set bounce processing to send me copies so I can see just how bad emailman is at present.

8 14

when a non subscribed person unsubscribes: Internal Server Error
by Julian Stacey Aug. 13, 2026

Aug. 13, 2026

Hi mailman-users(a)python.org Summary: - Is below normal for mailman-2.1.39 ? - Or do I have a corrupted script ? - Is better error handling possible ? If a user who is not subscribed to a list tries to unsubscribe (perhaps he's not sure if he has yet unsubed all in various changes), Example: http://mailman.berklix.org/mailman/listinfo/test scroll to end "To unsubscribe" Type dummy(a)domain.nowhere Click unsubscribe Receive: http://mailman.berklix.org/mailman/options/test Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster(a)berklix.org to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. /var/log/httpd-error.log: [cgi:error] [pid 7888] [client browser_home_ip_number:57904] End of script output before headers: options, referer: http://mailman.berklix.org/mailman/listinfo/test It would be nicer to see: "Your email address is not subscribed" that would save time for user, list & httpd owners. Is the nasty error message to hinder malicious flood probers trying variant addresses eg @target.com to see who may be subscribed [then probed elsewhere] ? Adding a few seconds 'man 3 sleep' would hinder robots. Cheers, -- Julian Stacey http://berklix.eu/jhs/mail/ Can't reply to Gmail & Yahoo. Arm Ukraine. Contraception & plain text email to reduce global warming.

2 3

Munge or don't Munge
by Dave Nathanson July 20, 2026

July 20, 2026

Hi, I'm familiar with Mailman v2 at DreamHost, and now setting up & learning Mailman v3 with Affinity at EMWD.com (EMWD is looking good so far, review coming later). One setting I'd like to check in about is MUNGE . What should I be doing with Munge? My gut feeling is to use; "Explicit Reply-To header set". But I'm here to ask, not to tell. The drawback is that after Munging the "From", it is no longer trivial to see who sent the message to the group. Sort of good. Sort of bad, depending. I mostly prefer to easily see the poster's email address. And the big mail providers would mostly accept this From format if it matched the Mailman sending server. I have set up everything I can think of to try for good delivery; SPF, DKIM, DMARC, and a SSL certificate on the server. My discussion group lists all work best with any reply being sent to the list, not to the poster directly. And it is helpful to somehow indicate who wrote the message. The Munging options I see are: No Munging Reply goes to list Explicit Reply-To header set Explicit Reply-To header set, no CC added. And there are some similar DMARC Mitigations. Anyway, are we still doing Munging with MailMan v3 with Affinity? >> What is the v3 best setting for handling the From address? Best, Dave Nathanson Mac Medix

5 5

Migrating from mailman2 to mailman3 witht het same domain
by Steven Jones June 28, 2026

June 28, 2026

Hi, How would this be done? I assume take Mailman2 down for a day or 2, standup Mailman3 and migrate the lists but this seems a high risk undertaking. regards Steven

3 4

Off-topic: Microsoft SNDS seems to have moved or disappeared, can anyone help?
by Jayson Smith June 15, 2026

June 15, 2026

Hi, In the past whenever I had a problem with my IP being put on Microsoft's infamous internal blocklist, I used the resources at their SNDS sender support site to get it fixed. I had a script which used a URL containing my API key so I could check that my IP wasn't on their blocklist without having to go to their site. This is important because although I've spun down my Mailman installation, I still send about eight messages a year to over 400 subscribers as part of a non-Mailman mailing list. A few days ago I noticed that SNDS doesn't seem to be where it used to be, it just points to the new Microsoft Postmaster site. Even their own links to SNDS on their support pages within this new site seem to go to the same place. Does anyone have any idea what they've done, what's going on, etc? Thanks, Jayson

2 2

mailman 2 verion
by Steven Jones May 11, 2026

May 11, 2026

Hi, We are running a RHEL8 version of mailman2. Is there any test(s) I can run to find out if RH's patched version is the same secure version as the latest/ last mailman2 binary released? Currently we have, mailman-2.1.30-1.module+el8.9.0+19511+cc1b14d9.x86_64 regards Steven

5 6

Spam filter anomaly
by Michael Welch April 12, 2026

April 12, 2026

Hi friends. Mailman 2.1.39, hosted by DreamHost. There's an anomaly happening in my spam filter rules: The filter rule reads: ^subject:.*spam* But it's catching the word "span" Like this, from a held message (it has also caught all the others in this thread): [1][1] Subject: RE: [RE-wrenches] Xantrex XW4548 lifespan Size: 17683 bytes Reason: Header matched regexp: ^subject:.*spam* References 1. http://lists.re-wrenches.org/admindb.cgi/re-wrenches-re-wrenches.org?msgid=…

3 3