On Thursday, April 21, 2022 1:21:22 PM EDT Olivier Hureau wrote: > Hello, > > Todd pointed out that the with the "v=DMARC1" txt records for external > verification explain why 'dmarc-request' is optional but we can still > modified the rules in this way. > > I also found out that on the with current rules : tags can be in > uppercase (the only strings that are "hardcoded" are the "DMARC1" from v > tag) and it also allow whitespace between the tag, the "=" and the value. > > As it the above TXT records are valid : > - "V=DMARC1;P=REJECT" > - "v=DMARC1; p=ReJeCt" > - "v=DMAR1; p = reject" > > A lot of dmarc libraries out there says that the records is not valid, > but according to the RFC7489 : it is. > Doing some active measurements on some email service provider i also > found that some are case/whitespace sensitive. > > I am currently writing a paper and want to submit it at the Applied > Networking Research Workshop - IETF-114. I hope I will share all my > results with you in a near future.
Thanks. authheaders [1] handled the space/no space difference correctly and passed the DMARC records through with the case unchanged. I just did an update to lower case everything except DMARC1 since that seems to match most people's expectations. Scott K [1] https://github.com/ValiMail/authentication-headers _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
