When signing messages inline (no OpenPGP/MIME attachment), line endings in the message are mixed between \n (Unix line ending) and \r\n (DOS line ending). This equivalent to the output produced on the command line by
gpg --clearsign -a > test_output
The \r\n lines however do not arrive intact after sending: They seem to be converted to \n\n (two newlines), which breaks the signature. The sent-messages folder shows still a correct signature (with \r\n) but in the inbox the signature is shown as invalid (since all newlines from the original message have effectively doubled to \n\n).
This bug happens with several mail servers, it does not happen when sending the content of the above mentioned file test_output manually with e.g. Python's SMTP lib via the same mail servers.
Steps to Reproduce:
1. Compose a multiline message.
2. Sign as Inline PGP.
3. Send message.
Each newline is doubled, GPG signatures are invalid.
Should not change newlines.
Git commit 0b476b100d0afcd144b05b21ce856971862e6c20 by Sandro Knauß.
Committed on 21/03/2013 at 01:35.
Pushed by knauss into branch 'KDE/4.10'.
Fixing newline issue with mailcomposer
Newlines for PGP inline signed/enc+signed mails are wrongly handled.
Newlines are replaced by <CR><LF> before creating the signature. This is
not recommended for inline messages.
M +7 -5 messagecomposer/signencryptjob.cpp
M +7 -9 messagecomposer/signjob.cpp