On 27/06/2026 20:11, John Levine wrote:
It appears that Dan Mahoney  <[email protected]> said:

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.


I'd be curious to know if any domain was found with both pct= and t=.


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,


Tolerating pct= for some time seems reasonable. However, new implementation will likely drop it. Thus, support for pct= is bound to become more and more deceptive.

Perhaps we need a campaign, similar to what was done for the DNS Flag Day?


Best
Ale
--



_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to