http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5179
------- Additional Comments From [EMAIL PROTECTED] 2006-11-12 12:48 ------- Earlier today I had a look at parts of DKIM finally http://www.ietf.org/internet-drafts/draft-ietf-dkim-base-06.txt Section 3.4 Canonicalization is of particular interest talking of how the handling of white space is to conducted with "simple" and "relaxed" algorithms. The last two paragraphs of 3.4 is of particular note worthy: Canonicalization simply prepares the email for presentation to the signing or verification algorithm. It MUST NOT change the transmitted data in any way. Canonicalization of header fields and body are described below. NOTE: This section assumes that the message is already in "network normal" format (e.g., text is ASCII encoded, lines are separated with CRLF characters, etc.). See also Section 5.3 for information about normalizing the message. I understand "network normal" to mean the message in its RFC 2822 form, regardless of how it was received, is submitted to the signing/verifier subject to one of the two white space algorithms. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
