Stephen J. Turnbull added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14983> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
