On Sep 21, 2006, at 7:59 AM, Michael Thomas wrote:
It's my opinion that "strict" means far too many things to far too
many people. Instead of rehabilitating the term, I'd far prefer
that we pick something else and really define what it means. I'm
not sure that I've achieved that and would appreciate help, but
reverting back to the handle that nobody seems to agree on doesn't
strike me as very helpful.
o DKIM Strict: the state where the domain holder believes that all
legitimate mail purportedly from the domain are sent with a
valid DKIM signature and that non-compliant services are avoided.
What is difficult to understand with this definition? Is a
definition is needed for non-compliant services?
A list server would be one such non-compliant service when it damages
initial signatures associated with some email-address. Possible
associated email-addresses might include 2822.From and 2821.Mail_From
when DKIM is also used to ensure DSNs, for example. This would be
much safer than a scheme using address path registration, for example.
-Doug
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
