Is this one case where DKIM could have an impact on list configuration
behavior?
Speaking as a list operator, if I have to choose between running my
lists the way that I've been running them for a decade and that my
users expect or using DKIM, DKIM will lose.
It is incumbent on us to design something that works with mail the way
it is, not the way we might wish it to be. In the particular case of
mailing lists, list software has been changing message headers and
bodies for decades. Senders and recipients like it that way, since
those changes are mostly for the convenience of list users,
e.g. adding subject tags and flattening multipart or HTML to plain
text. If we want the world to use what we design, we'd best design
something that can live with it.
The semantics of a DKIM signature is "you can blame me for this
message." That's it. When I get a message with a signature from a
signer I like, such as the operator of a list I've subscribed to, I'm
going to deliver it.
R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html