If the option "Word wrap at column: XX" (say 78) is set in the "General" tab of the "Composer" settings then the PGP/MIME signature generated by KMail is not accepted by Thunderbird's Enigmail. If line breaks are added by hand and/or if "Word wrap at column: XX" is deselected, then the generated signature is reported as valid by Thunderbird's enigmail. Reproducible: Always Steps to Reproduce: 1. Select "Word wrap at column: 78" in the "General" tab of the "Composer" settings 2. Write an e-mail, say, with text longer than 78 characters (do not add any line breaks by hand) 3. Sign the message using PGP/MIME and send it 4. Open the mail in Thunderbird Actual Results: Thunderbird's Enigmail reports: "Error - signature verification failed; click on 'Details' button for more information". Clicking on details reports: "OpenPGP Security Info; Error - signature verification failed" Expected Results: Thunderbird's Enigmail reports: "Good signature from XXX" I don't know if this is a bug in Thunderbird's Enigmail or in KMail2. Note that the messages rejected by Thunderbird's Enigmail are accepted by KMail2, i.e. KMail2 is consistent. Disabling automatic word wrapping makes the issue disappear.
Created attachment 84444 [details] automatic word-wrap enabled, rejected by Thunderbird's Enigmail
Created attachment 84445 [details] manual word-wrap, accepted by Thunderbird's Enigmail
Acctually it is a problem in enigmail. You can easily test if you use the cmd line tool gpg, that the signature is valid, but is is binary signature. The problem is that thunderbird can't handle binary signatures correctly. The failing mail has a space as last letter at the line and thunderbird removes this, cause for textmode signatuers this is a allowed modification.
I reported a similar problem to the Enigmail bug-system. It's fixed in the current nighties of Enigmail. So maybe you can close this bug. http://sourceforge.net/p/enigmail/bugs/332/ https://www.enigmail.net/download/nightly.php @Martin Albrecht Can you do a test with a current Enigmail nightly?
I can confirm that the bug is gone with a current Enigmail nightly.