Open Elompenta opened 8 years ago
I can confirm this issue.
To replicate it: This happened after adding this public key. After importing the key in Kleopatra and trusting+certifying it, it will appear under Trusted Certificates. However when attempting to send an encrypted email to any of the aliases, the "KeyItem Selection" dialog will appear (complaining that no appropriate public key was found), showing all possible recipients except the aforementioned one.
Anything special about the key? Newer or older?
On Apr 12, 2017, at 11:07 AM, Alexandro Sanchez notifications@github.com wrote:
I can confirm this issue.
To replicate it: This happened after adding this public key. After importing the key in Kleopatra and trusting+certifying it, it will appear under Trusted Certificates. However when attempting to send an encrypted email to any of the aliases, the "KeyItem Selection" dialog will appear (complaining that no appropriate public key was found), showing all possible recipients except the aforementioned one.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I cannot see any specials in the affected keys. You can check my key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x229F68D65AD0240C
Since i have a second alias in my public key - another one that use this Outlook Plugin cannot send me encrypted emails.
If he write a new email, the popup for keyselection show all keys - but not my key.
Is there any Problem with aliases within in a key? My KEY ID: 0x5AD0240C