[Assp-test] need some help on DKIM

[Thomas E. <Tho...@th...>]

Hello all,

I need some help from some native english speeking of you.

In RFC4871 3.7.  (http://www.ietf.org/rfc/rfc4871.txt) "Computing the 
Message Hashes" there is a part:

 .... 
   When calculating the hash on messages that will be transmitted using
   base64 or quoted-printable encoding, signers MUST compute the hash
   after the encoding.  Likewise, the verifier MUST incorporate the
   values into the hash before decoding the base64 or quoted-printable
   text.  However, the hash MUST be computed before transport level
   encodings such as SMTP "dot-stuffing" (the modification of lines
   beginning with a "." to avoid confusion with the SMTP end-of-message
   marker, as specified in [RFC2821]).
...

The SMTP "dot-stuffing" is described in RFC2821 "4.5.2 Transparency".

The question is:

Do we have to remove the transport level encodings like SMTP 
"dot-stuffing" only in quoted-printable encoded mails or in all (base64 
encoded mails will never have a leading dot).

NOTE:
even Mail::DKIM::Signer says:
......
=head2 PRINT()

Feed part of the message to the signer.

  $dkim->PRINT("a line of the message\015\012");

Feeds content of the message being signed into the signer.
The API is designed this way so that the entire message does NOT need
to be read into memory at once.

Please note that although the PRINT() method expects you to use
SMTP-style line termination characters, you should NOT use the
SMTP-style dot-stuffing technique described in RFC 2821 section 4.5.2.
Nor should you use a <CR><LF>.<CR><LF> sequence to terminate the
message. 
......


The problem is - if I remove the leading dot from lines in text/plain - 
ASCII MIME parts, most of the online DKIM checks are failing. (?????)

Thomas



DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************