[issue137] composer chooses to encrypt/sign with OpenPGP, although no encrypt-to-self keys are configured for OpenPGP

New submission from Marc Mutz <[email protected]>:

In KAddressBook: 
 
Create an entry with the following preferences: 
 
Allowed protocols: OpenPGP/MIME, S/MIME, S/MIME opaque 
Sign: Always sign 
Encrypt: Ask Whenever Possible 
 
Assign both preferred OpenPGP and S/MIME keys to that contact. 
 
In KMail: 
 
Open a composer, choose an identity with no OpenPGP sign/encrypt keys, but only 
S/MIME sign/encrypt keys. 
 
Uncheck the sign and the encrypt buttons and choose "Any" in the format 
selection. 
 
On send, you'll get an error message telling you that it chose to encrypt/sign 
with OpenPGP, but that there is no OpenPGP encrypt-to-self key available. If 
you have disabled encrypt-to-self, then it will ask the same thing b/c of the 
missing sign key. 
 
It should use S/MIME instead, of course.

----------
assignedto: marc
messages: 636
nosy: marc
priority: urgent
status: in-progress
title: composer chooses to encrypt/sign with OpenPGP, although no encrypt-to-self keys are configured for OpenPGP
topic: KMail
______________________________________________________
Aegypten issue tracker <[email protected]>
<https://intevation.de/roundup/aegypten/issue137>
______________________________________________________