[Kde-pim] A FYI - a GPG problem that affects KMail

[Anne Wilson]

I recently encountered problems with GPG.  A correspondent had somehow got 
corruption on his private key and had to create a new one.  No matter what I 
did, I could not make KMail use the new key in preference to the old one, so I 
went to the GPG users list to explore the problem.

It seems that where a correspondent has an older trusted key and a new one is 
installed, GPG will always use the first one it encounters, no matter what the 
preferences are in KMail.  My problem was cured by marking his old keys as 
untrusted.

This is undeniable a GPG bug, not a KDE one, but it is something that you 
should be aware of.  I don't know whether there is any way you can ensure that 
KMail's preference settings override GPG's normal behaviour, but at least if 
you come across complaints about this, you now know why and what the user can 
do about it.

HTH

Anne
-- 
New to KDE Software? - get help from http://userbase.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20110701/47a8660c/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/