Have tested lots of solutions to signing-milter to get rid of the –b parameter. But still it fails validation. I now run all mails through a null filter which does silent-discard on 8bitmime so it downconverts the mail to 7bit before passing it through signing-milter.
I tried to run the unsigned mail, as how it would look when its not run through signing-milter at all (but downconverted to 7bit), through a lint checker, and got the following error: “ERROR: 8-bit characters not permitted in preamble/epilogue line 27” Apparently, the preamble “Det här är ett flerdelat meddelande i MIME-format.” is not permitted. (Which is Microsoft Windows Live Mail putting in a preamble to clients not supporting multipart MIME messages in swedish, the above text is swedish of “This is a multipart message in MIME-format”). lint checker of the mail WITHOUT –b parameter (which does not validate) to signing-milter returns no errors (only warnings). lint checker of the mail WITH –b parameter (which does validate) to signing-milter returns no errors either (only warnings). But can the preamble be the problem? As I can see, its stripped out from the signed mail completely and replaced with “This is an S/MIME signed message” so this shouldnt matter to the signature? Used the following lint checker: http://tools.ietf.org/tools/msglint/ Any ideas? The mail “test without signing.eml” is the mail how it would look before being run through signing-milter, so if someone could find what is the RFC problem in that mail except for the preamble (which seems not to have any concern for signing).
--- Begin Message ---test with signing
smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---test without signing
--- End Message ---
--- Begin Message ---with b parameter to signing-milter
Description: S/MIME cryptographic signature
--- End Message ---
smime.p7s
Description: S/MIME cryptographic signature
