Bug 304821

Summary: Signing/Encrypting a mail doesn't respect the settings in my addressbook of the contact
Product: [Applications] kmail2 Reporter: regi.hops
Component: cryptoAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: axel.braun, bugs.kde.org, korossy, lars-boettcher, maxi, michael.saalfeld, montel, sknauss
Priority: NOR    
Version: 4.9.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 4.11.4
Sentry Crash Report:

Description regi.hops 2012-08-08 20:02:35 UTC 
I have a PGP and a S/MIME certificate/key.
I have set in my identity settings the preferred format for encryption and signing to all.

When I write an email to alice@example.com, who is configured in my addressbook only to allow S/MIME in the protocol settings, kmail2 silently ignores this and sends the message signed with my PGP-Key.

Additionally the settings for signing and encryption are set to always, kmail2 never signs nor encrypts the message nor warn me to do so.
It silently sends the message.

If you activate the setting "always show encryption key..." in settings->security->create message you'll see that the settings from the addressbook are ignored, except the public key.



Reproducible: Always

Steps to Reproduce:
1. set up an account with a PGP-Key/Cert and a S/MIME Key/Cert
2. let the prefered format for signing and encryption at the default (All)
3. create a contact with a S/MIME public key
4. set the allowed protocol to S/MIME only
5. set the sending options to "always sign" and "always encrypt"
6. send an email to this contact
7. send a signed email to the contact

Actual Results:  
point 6. sends the email not signed and not encrypted
point 7. sends the email signed with my PGP key


Expected Results:  
point 6. kmail2 should warn me about the missing signature / encryption, like it warns me if I forgot to enter a subject in the message. And give me the option to send the email unsigned/unencrypted

point 7. kmail2 should the email sign with my S/MIME key. In the case that I don't have a Cert/Key fitting the options in the contact, it should bring up a dialog where I can choose to abort or send the email unsigned

In both cases an additional link to the respective contact would be the "cream" on top, which would be especially helpful when sending emails to more then one person
Comment 1 regi.hops 2012-08-08 20:08:10 UTC 
To clarify point 4 and 5 of the "Steps to Reproduce"
4. set the allowed protocol to S/MIME only FOR THE CREATED CONTACT
5. set the sending options to "always sign" and "always encrypt" FOR THE CREATED CONTACT
Comment 2 Michael S. 2012-08-10 11:18:59 UTC 
I can confirm this bug. Kmail ignores signing and encryption settings from contacts.
Comment 3 m.eik michalke 2012-08-12 12:12:17 UTC 
i've added a S/MIME certificate, both for encrypting as well as signing, to an identity which already had a PGP key assigned to it. but outgoing messages are still only signed with the PGP key. that's bad, because my contacts won't learn about the S/MIME cerificate at all.

this goes for kmail2 (KDE 4.9.0, kubuntu 12.04).
Comment 4 Laurent Montel 2012-08-13 20:14:10 UTC 
I confirm it.
Will look at it
Comment 5 Lars 2012-09-30 22:37:44 UTC 
I confirm this bug to. (Arch Linux KDE 4.9.1)
Comment 6 Lars 2012-09-30 22:39:33 UTC 
UNCONFIRMED?
Comment 7 Myriam Schweingruber 2012-10-03 10:02:13 UTC 
Setting status correctly.
Comment 8 regi.hops 2013-04-27 16:50:46 UTC 
Are there already some changes ongoing?
I recently recognized that KMail2 (KDE 4.10.2) warn me about missing Signature/Encryption sending a mail to a contact which has these options set.
It wasn't perfect, because activating Signature/Encryption via the Popup-Dialogs failed, but it goes into the right direction.
Comment 9 Axel Braun 2013-08-01 06:57:20 UTC 
Still an issue in 4.10.5: Although I have a preferred key for a contact entered in kaddressbook, it always wants to encrypt with the (deviating) key for the email-address
Comment 10 Sandro Knauß 2013-11-24 14:52:53 UTC 
It is fixed in 4.11.4.

(In reply to comment #9)
> Still an issue in 4.10.5: Although I have a preferred key for a contact
> entered in kaddressbook, it always wants to encrypt with the (deviating) key
> for the email-address

solved too.