DKIM's design is predicated on valid input. Therefore, signers and
verifiers SHOULD take reasonable steps to ensure that the messages
they are processing are valid according to [RFC5322
<http://tools.ietf.org/html/rfc5322>], [RFC2045
<http://tools.ietf.org/html/rfc2045>], and
any other relevant message format standards.
Hey, could you talk to the guy who just proposed putting UTF-8 selectors
and domain names into the signature headers and explain to him why that's
a bad idea?
Regards,
John Levine, johnl(_at_)iecc(_dot_)com, Primary Perpetrator of "The Internet
for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html