Hi Florian,
At 12:03 25-03-2009, Florian Sager wrote:
According to the mails below the RFC compliant change of content
encoding in MTA-forwarding may break signatures that follow the RFC 4871
recommendation to include header "Content-Transfer-Encoding" in the
signature. This header should be removed from section 5.5. Recommended
Signature Content (The following header fields SHOULD be included in the
signature ...).
Won't the change in content-transfer-encoding (not the header field)
performed by an MTA affect the body part and by extension break the
DKIM signature?
Regards,
-sm
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html