Version: 1.5.3 (using KDE KDE 3.1.3) Installed from: RedHat RPMs OS: Linux following the installation instructions on http://kmail.kde.org/kmail-pgpmime-howto.html kmail 1.5.3, cryptplug-0.3.16, ibksba-0.4.7, newpg-0.9.4, gpgme-0.3.15, pinentry-0.6.9 the plugin seems to work fine. there is one problem with signatures however. When someone sends a message to me, that he/she has signed, kmail sometimes displays that i myself did sign the the message with key (Key ID: 0xncrypted). opening the same email on my client on windows did not produce this error, it correctly stated who signed the message (on win i use PGPi 6.02 and eudora). it seems like this happens when the sender is on windows using outlook. a tried to send a number of mails using kmail from myself to myself (using different email addresses). no problems however.
Please attach a message which shows this wrong behavior to this bug report.
Now i found the problem showing up when sending an email using the inline openPGP. (built in). when sending the email to a friend encrypting and signing. kmail says that my friend has signed the message, clearly this is wrong. it should say that i signed the message. adding screenshot for this scenario. it looks the same way when receiving mail (as reported), only instead of displaying a gren box saying that signed by Friend, it says signed by me.
Created attachment 2210 [details] bad display of the real person that made signature, instead it displays the opposit.
I can't reproduce your problem with KMail 1.5.3 and GnuPG 1.2.3rc1. Which version of GnuPG are you using?
i am using: gpg (GnuPG) 1.2.2
when looking back at older emails that i have sent with previous versions of kmail (version before 1.5.3), signatures looks all right, kmail 1.5.3 says that i signed them, wich is correct. i will try to use gpg 1.3.2 later on, ill be back then.
confirming WORKSFORME with gpg 1.3.2 if no one else has this problem or can reproduce it i suggest -> WORKSFORME
Subject: Re: signature problem using =?iso-8859-1?q?=EF=BF=BDgypten_in_kmail_______?= Works with gpg 1.3.2 according to the reporter of this bug report.