Version: 1.9.7 (using KDE KDE 3.5.7) Installed from: Ubuntu Packages OS: Linux KMail can't verify gpg signature with one of public key in my keyring: Message was signed on 10.07.2007 10:52 with unknown key 0xD89B8235E62251D2. The validity of the signature cannot be verified. Status: Good signature Mozilla Thunderbird has no problem with that. Signature verification with other public keys in my keyring is OK in both email clients. Attaching email and public key. Installed GnuPG packages: gnupg: 1.4.6-1ubuntu2 gnupg-agent: 2.0.3-1ubuntu1 gnupg2: 2.0.3-1ubuntu1
Created attachment 21109 [details] signed email
Created attachment 21110 [details] public key to verify the email
I can confirm this. KMail prints the following: >Message was signed on 2007-07-10 11:27 with unknown key 0xD89B8235E62251D2. >The validity of the signature cannot be verified. >Status: Good signature I wonder if something is wrong with the key itself, but I don't know GPG well enough to check this.
I can still reproduce on trunk r948809. I don't know if it's the key or KMail either. Using the test-data supplied I get: $ gpg --verify signature.asc themail.txt gpg: Signature made Di 10 Jul 2007 11:27:23 CEST using DSA key ID E62251D2 gpg: Good signature from "Jan Jergus" which implies that it's valid (if I get it right).
I experience the same problem with kmail version 1.13.2 (and some earlier ones).
Same problem here, with kmail 4.7.1, when verifiing the signature from an encrypted email. The same key appears green, if the email is not encrypted.
Bug still exists on KMail 4.8.2 (Kubuntu). Key was 0xF6CABBA6, message can be decrypted and verified in thunderbird/enigmail and on the command line using gpg.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.
Still seems to be a problem in KMail 4.14.7.