-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
My theory is that DKIM only applies to valid 2822 messages, and it's
not a substitute for a sanity check for all the screwy things one
can send in a non-conformant message. Perhaps it would be a good
idea someday to
collect experience and advice into an implmentation guide, but other
than that, it's not our problem. Agreed?
Completely.
Broken messages should be handled at a different layer.
Jon
-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.3
Charset: US-ASCII
wj8DBQFIW96ZsTedWZOD3gYRAiYrAJ40vRhsGsRk1ShSlQl+brlNBwi6tACg25pa
/XBh0wWusDLw3NkYHlbqueY=
=VSEi
-----END PGP SIGNATURE-----
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html