AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Python random email generator4/11/2024 Looking at your stackoverflow post, you might be able to fix this by doing an rstrip on the string body before signing it. That said, there seems to be little harm in adding a CRLF, and some argument in its favor, since the RFC also says that the CRLF before the next boundary is conceptually part of it, and by that interpretation a CRLF could be considered missing (though I think technically it isn't.the reason for the rule is to disambiguate preceding *body* parts that end or don't end in a CRLF, and here we are dealing with an unambiguous ending boundary delimiter). You might want to report bugs about that to the appropriate projects. In particular, *transports* are allowed to add whitespace before the trailing CRLF, and receivers are to handle this case. Section clearly indicates that the ending delimiter ends at the trailing. Then either the signer or the verifier (or both) are broken per RFC 2046 (unless there has been an update that isn't referenced from the RFC). After applying it, it's possible to sign even complicated mails like "multipart/alternate with attachments".Īuthor: R. The attached patch makes email.generator behave like all email clients. Trying to write a email-sending script with PGP-signing functionality, I stumbled upon a problem (see ): it was impossible to sign mutlipart emails (actually the signing was performed, but the verifying programs thought that the signature is bad).Īfter comparing messages produced by email.generator and popular mail clients (Evolution, KMail), I've found out that the mail clients always add line breaks after ending boundaries. PATCH: Always add newline after ending boundary in multipart messages Email.generator should always add newlines after closing boundariesīarry, dkg, mitya57, python-dev, r.david.murray, sjtĬreated on 06:52 by mitya57, last changed 14:57 by admin.
0 Comments
Read More
Leave a Reply. |