Dmitry Shachnev <mity...@gmail.com> added the comment: > Looking at your stackoverflow post, you might be able to fix this by doing an > rstrip on the string body before signing it.
My body doesn't end with \n, so that doesn't help. If you suggest me any (easy) way to fix this on the level of my script, I will be happy. > Probably adding the CRLF is the way to go, but I wonder, what are the > controlling RFCs for signing/verifying and what do they say? The standard is RFC 1847, it doesn't say anything about multipart emails. I've just looked at what other mail clients do, it works, but I can't say anything about its correctness. Also, looking at some multipart signed emails in my inbox, they *all* have the blank line before the signature part. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14983> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
