It appears that Dan Mahoney <[email protected]> said: >All, > >As mentiomed over on Mailop, I've come up with some code to poll the Umbrella >1m (plus the root zone and the >public suffix list) for adoption of t= as well as pct=, so that administrators >can determine when they feel >ready to tell their dmarc-checkers to stop honoring the pct= field. > >I'm choosing to leave parsing of pct= in-place in the next release of >OpenDMARC but make it user-configurable, >to not violate POLA.
Makes sense. >In the top 10,000 u1m domains, I found about 30 with pct=0, including several >major corporate ones >(ciscospark.com, several shopify domains) and a NY state university >(sunysb.edu) that have non-p=none >policies. Is this a small amount? Probably. But it's nonzero. That's 0.3% which I think we can reasonably round to zero. Standards conformance is a two-way street. While we try to accomodate as many people as we reasonably can, at some point, if people want to interoperate they need to read the spec and do what it says. Postel's robustness principle about being liberal in what you accept was intended to apply *when the spec is ambiguous.* I understand he had little sympathy for code that was just wrong. For pct=0. there has been a folk rule that it means for senders to do DMARC workaround rewrites, but the spec never said that, R's, John _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
