What I'm concerned about is that since this has come up before N times
(for, admittedly, some currently small value of N), we've seen enough
disparate cases of it that we may be missing something bigger, and if so,
doing something defensive in the specification would be prudent. There's
smoke here, and there may be fire.
OK, thanks.
My guess is that if we can track it down it is likely to be "my software
is buggy so I want everyone else to work around it."
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
