FYI, we just solved this DMARC problem for the WG21 lists.
As I mentioned earlier in this thread, the committee reflectors were facing the same problem, and the same loss of Mailman host, because they were also hosted at Indiana. This past weekend, we migrated the committee’s Mailman setup from Indiana to our own servers. Along the way we upgraded Mailman from the 2.1.15 being used on Indiana’s machine, to 2.1.23 which is the latest 2.x version, and the DMARC problems disappeared. (We’re on the latest 2.x, not 3.x, because 3.x does not yet officially support migration from 2.x. So I’m just reporting FYI that the latest 2.x indeed was enough to solve this problem, as it was advertised to be.) Herb From: [email protected] [mailto:[email protected]] On Behalf Of Niall Douglas Sent: Friday, December 16, 2016 2:15 PM To: Boost Steering Committee <[email protected]> Cc: [email protected]; [email protected] Subject: [boost-steering] Re: DMARC and mailman For your information as of the 14th December all mail from boost-dev is now SPF failing as well as DMARC failing. Unlike DMARC which usually just means being sent into the Spam folder, SPF fail means sending email to /dev/null on many systems. Many users are now no longer able to receive any mail at all from boost-dev. Here are the headers: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.nedproductions.biz X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received-SPF: Softfail (domain owner discourages use of this host) identity=mailfrom; client-ip=129.79.39.203; helo=wowbagger.crest.iu.edu; envelope-from=xxx; receiver=xxx Authentication-Results: mail; dmarc=none header.from=hetp.u-net.com Niall On Tuesday, May 24, 2016 at 3:49:43 PM UTC+1, Nevin Liber wrote: Hello... Please let whomever is responsible for the Boost mailing list software know about this. Regards, Nevin :-) ---------- Forwarded message ---------- From: James Sharpe <[email protected] <javascript:> > Date: 23 May 2016 at 16:24 Subject: Fwd: DMARC and mailman To: [email protected] <javascript:> Can I draw your attention to the post below.. Can we get the mailman software for the boost lists upgraded as a matter of urgency? James ---------- Forwarded message ---------- From: James Sharpe <[email protected] <javascript:> > Date: 19 May 2016 at 20:34 Subject: DMARC and mailman To: [email protected] <javascript:> , [email protected] <javascript:> In June 2016 gmail is going to be changing its DMARC policy to reject any unaligned mail. This means that we will be seeing any mailing list responses from a gmail.com <http://gmail.com> address to be considered spam by any mail server that enforces DMARC. For a while now yahoo.com <http://yahoo.com> has had this policy turned on which has meant that yahoo.com <http://yahoo.com> addresses have been considered spam. Mailman has released a workaround in version 2.1.18: https://www.mail-archive.com/[email protected]/msg64098.html The boost mailing list is currently on mailman 2.1.15. I'd strongly suggest that this should be updated as a matter of urgency else we'll find a lot of the conversations on this list will end up in the spam folder... Regards, James -- Nevin ":-)" Liber <mailto:[email protected] <javascript:> > +1-847-691-1404 -- You received this message because you are subscribed to the Google Groups "Boost Steering Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Boost Steering Committee" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
