On Feb 25, 2014, at 2:58 AM, J. Gomez <[email protected]> wrote: > > So, in other words, there is not such a thing as a POLICY of REJECT in DMARC; > and if there was ever one, you just cannot trust it nor follow it (as a > receiver). > > At least we still have the reporting feature of DMARC, as something which is > actually useful (for the senders). > This is fundamentally misrepresenting DMARC by making people believe that edge cases are generalities and making people believe that a convenience feature to bolster early adoption is a fundamental flaw. The data is against you, DMARC is working well to stop spoofing at the receiver who adopted it, and yes there is still work to do, but the fundamentals are there. DMARC, improved DKIM interactions between MTA, improved forwarding in several places. DMARC does not work out of the box, until you take control of your email streams, for some organization this is easy, for some others it requires a lot of work. It is all then a question of priority and risk assessment.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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)
