[Mailman-Users] Making a Case for Upgrading MailMan from 2.1.17

[Andrew Hodgson]

Hi,

I was too hasty in sending out the prior message; actually there is a feature in 2.1.18 which I believe will help you with the issue you are having.

Prior to 2.1.18, the DMARC feature was activated on a per list basis, and was set for each member regardless of whether the sender's email provider had the DMARC set up on the domain.  With 2.1.18, you can set it up so the headers only get munged if the DMARC action on the domain is quarrentine or reject.  It is worth noting however that depending on how your host get Mailman, this feature may already be available.  For example, some RedHat packages prior to 2.1.18 already have this feature built into them.

Sorry about that.
Andrew.

________________________________________
From: Andrew Hodgson
Sent: 23 June 2016 12:51
To: Dave Nathanson; mailman-users at python.org
Subject: RE: [Mailman-Users] Making a Case for Upgrading MailMan from 2.1.17

Dave Nathanson [dave.lists at nathanson.org] wrote:

>I'd like some help in making a case to convince my hosting company to upgrade from Mailman 2.1.17.

>I run several email lists for clubs, these are discussion lists that get up to 20 messages per day, and include up to 150 members. Replies are directed back to the list.

>My primary issue with MM 2.1.17 is about list messages from members who don't have their human names configured into their email clients, resulting in a list message from an unknown. It is just from "via listname <listname at example.com>"
>Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer versions. I just know that it's been over 2 years since 2.1.17 which has an annoying omission due the the whole DEMARC thing.

If you download the tar package for the latest version, 2.1.22, the NEWS file will give a changelog of what has changed between the versions.  I don't believe a newer version would help you with the issue you are experiencing, however, as that is due to the way that Mailman handles messages which come from senders who's email operator publishes DMARC records for their domain.

Andrew.