If you're going to send a message on and are not going to break the
signature, you do one of these:
Sign or don't sign, it works fine either way.
If you're going to send a message on and ARE going to break the
signature, you do this:
You're a mailing list, so filter, sign and earn your own reputation.
DKIM is too complicated as it is, and it strikes me as an extremely poor
idea to add yet more cruft to work around perverse situations that are as
yet (and probably always) entirely hypothetical.
How likely is it that a mail setup that break signatures will add all
sorts of code to support DKIM, check incoming signatures, add A-R headers,
and resign them, but won't filter and sign like a mailing list does?
This is the kind of arcane situation for which the correct advice is
"don't do that."
R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html