This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sjt
Recipients barry, dkg, mitya57, r.david.murray, sjt
Date 2013-09-21.19:19:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Following OpenPGP convention is clearly optional (or maybe a SHOULD, but the word "elect" makes it a pretty weak SHOULD).  RFC 2046 is a MUST, it's not a matter of "convention".

The problem is that a parser that works forward in the message will swallow the terminating CRLF of the boundary of the signed multipart, and then not find a CRLF to introduce the boundary that separates the content from the signature.  By MIME rules it will treat the signature (including the unrecognized boundary) as an epilogue, and ignore it.  This is not at all special to multipart/signed.
Date User Action Args
2013-09-21 19:19:03sjtsetrecipients: + sjt, barry, r.david.murray, mitya57, dkg
2013-09-21 19:19:03sjtsetmessageid: <>
2013-09-21 19:19:03sjtlinkissue14983 messages
2013-09-21 19:19:03sjtcreate