MailMan has supported DMARC domains for ages through a simple address re- writing mechanism. It works quite well. The version running this list (2.1.22) definitely supports it, it just needs to be enabled.
Unless there is a good reason which prevents it, turning it on is probably a better long-term solution. ARC isn't going to be universally deployed overnight and some personal domains (mine included) are no doubt DMARC protect too. Not to mention, the irony of the official DMARC mailing list discouraging postings from DMARC protected domains due to compatibility issues! Just my two cents, apologies if this was previously discussed by the list. Ken. -- Ken O'Driscoll / We Monitor Email t: +353 1 254 9400 | w: www.wemonitoremail.com On Fri, 2017-06-02 at 11:08 -0400, Barry Leiba wrote: > The valimail.com domain appears to have recently (it looks like it > started 1 June) set a restrictive DMARC policy, and that's caused a > boatload of disabled subscriptions. Basically, whenever Seth (or any > other valimail.com user, but recently that's been Seth) sends a > message to the list now, anyone whose domain honours that policy has > their copy of the message bounced back and not delivered. After a few > of those, mailman disables their subscriptions. > > Seth, please (1) do not post messages to the list from your > valimail.com address until this is resolved, and (2) do what you can > to get this resolved. > > Thanks, > Barry, chairing > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
