Bug 336759

Summary:	KMail ignores crypto-settings
Product:	[Applications] kmail2	Reporter:	Carioca <h6zb8-kdebugs20120801>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kfunk, montel, sskyman
Priority:	NOR
Version:	4.14.1
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Carioca 2014-06-26 14:16:36 UTC

When in Kontact is set to always encrypt or sign an e-mail, the settings in KMail composer are not set and changings are ignored. The button for encrpytion is not active and there is no message that the e-mail will be encrpyted. And if you do not want to sign or encrypt, there is no way to deactivate it in Composer. Even if you deactivate the buttons, it will sign and encrypt. 

Reproducible: Always

Steps to Reproduce:
1. set in Kontact settings to always sign and encrypt
2. open composer window
3. see settings are wrong and changes have no effect
Actual Results:  
The settings have to be correct in Composer and changes have to take effects.

Expected Results:  
I except correct hints that the e-mail will be encrypted and I expect to have changes take effect. When I deactivate the signing in Composer the e-mail must not sign.

Comment 1 Kevin Funk 2014-12-15 15:55:08 UTC

Confirmed.

For me the problem is two-fold:
I have 'always sign' set to true for my identity
- If I reply to a signed mail -> 'Sign' enabled => Okay
- If I reply to an unsigned mail -> 'Sign' disabled => Huh? Wrong!

Comment 2 Laurent Montel 2014-12-16 06:57:49 UTC

Here it works.
could you look at in message if you have a "X-KMail-SignatureActionEnabled" ?

Comment 3 Kevin Funk 2014-12-16 15:23:03 UTC

Neither the signed nor the unsigned mail has this header field.

FTR, version info:
Qt: 4.8.6
KDE Development Platform: 4.14.1
KMail: 4.14.1

Comment 4 Laurent Montel 2014-12-16 16:03:16 UTC

4.14.1 is totally obsolete :)
Ok I didn't work on it.
I will try to create unit test and try to debug it.

Comment 5 Denis Kurz 2017-06-23 20:01:27 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 6 Denis Kurz 2018-01-31 16:50:35 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.