>Until we have a solution that lets DMARC mail securely transit email lists, >our two legged >DMARC table will wobble.
We have a perfectly good one that certain people are too pig-headed to use: don't subscribe to lists from addresses with DMARC policies. Speaking as someone who has run mailing lists for 20 years, I can assure you that we didn't take useful features out of our list software to deal with the last dozen FUSSPs, and we're not going to change it to deal with DMARC. Forget it, don't waste your keystrokes asking. If you think your domain is so threatened that you need to publish p=reject (which it probably isn't if your name isn't Paypal or American Greetings, but that's a separate issue), then why isn't it worth an extra 15 minutes of your time to set up a separate address in a subdomain or at gmail to use for lists? Remember, nobody has to accept your mail at all. To the extent that you publish DMARC policies that increase other people's pain, they are going to ease the pain by ignoring the policies, or perhaps by taking your p=reject advice to its logical conclusion and throwing all your mail away. I've already made a one-line config change to my lists to do that. Who needs the grief? R's, John _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
