On Saturday, June 07, 2003, Jonathan Angliss wrote... >> I'd think so, but MDaemon manages to break my signatures. When I use >> MDaemon to adjust my outgoing message header with a filter, it seems >> to reflow the base64 encoded message body text. TB! flows the base64 >> encoded text to 65 characters. [..]
> RFCs specify that base64 encoded lines must be wrapped at no more than > 76 characters... unfortunately it doesn't specify anywhere that mail > agents cannot rewrap the lines [..] Bingo... Yahoo and MDaemon break RFCs... http://www.ietf.org/rfc/rfc3156.txt hehe... That RFC states that any email with parts marked as multipart/signed cannot be modified... 3. Content-Transfer-Encoding restrictions Multipart/signed and multipart/encrypted are to be treated by agents as opaque, meaning that the data is not to be altered in any way [2], [7]. However, many existing mail gateways will detect if the next hop does not support MIME or 8-bit data and perform conversion to either Quoted-Printable or Base64. This presents serious problems for multipart/signed, in particular, where the signature is invalidated when such an operation occurs. For this reason all data signed according to this protocol MUST be constrained to 7 bits (8- bit data MUST be encoded using either Quoted-Printable or Base64). Note that this also includes the case where a signed object is also encrypted (see section 6). This restriction will increase the likelihood that the signature will be valid upon receipt. So bad yahoo... naughty yahoo... go sit in the corner with MDaemon :) -- Jonathan Angliss ([EMAIL PROTECTED])
pgp00000.pgp
Description: PGP signature
________________________________________________________ Current beta is 1.63b9 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html
