On 01/16/2019 10:26 AM, John R Levine wrote:
Maybe, but that's not what standards are about. The point of a standard is to say here's what you do if you want to interoperate. I have never found it productive to speculate about what you might or might not want to do when you run into people who didn't read the spec.
I agree with you conceptually.However I feel like rejecting things because of additional white space (in front of v=...) or the wrong case is being a little bit pedantic.
Rather, I think that if removing a spurious / leading space or folding case causes the DMARC record to be valid, it behooves us to tolerate such minor errors.
I don't want to be so pedantic that people push back on adopting what I (and I assume others) think is a good technology.
Is doing so against the letter of the specification, absolutely. Is it within the spirit of the specification, I think so.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
