Bug 228698

Summary:	Addressbook crypto settings are no longer respected
Product:	[Applications] kmail2	Reporter:	Christoph Lange <langec>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	sskyman
Priority:	NOR
Version:	Git (master)
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Christoph Lange 2010-02-27 01:58:10 UTC

Version:           1.13.0 (using 4.4.00 (KDE 4.4.0), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.31-thinkpad

I have a contact in the addressbook whose crypto settings say "never sign".  That addressbook is an Akonadi resource.  KMail is otherwise configured to sign by default.  When I send a mail to that contact, KMail encrypts it nevertheless.

(Sometimes I realized that I didn't want to encrypt such mails, canceled the pinentry dialog, thus making the signing fail, then tried to send the unsigned mail, and then KMail got stuck with the composer window still open but grayed = inactive and the main window not usable, so I had to kill it and lost my mail.  Not sure whether/how I can reproduce this, but it has happened a few times.)

Comment 1 Sylvain Demers 2010-07-08 04:40:01 UTC

Same thing here, except in reverse: I have only one contact with whom I sign and encrypt, and that contact's crypto settings set to always sign and ask for encryption. Those settings are now ignored. I can still manually select sign and encrypt from the toolbar while composing the email, but that defeats the purpose of the contact crypto settings in the first place.

KMail 1.13.3
KDE 4.4.4
Gentoo Linux x86_64

Comment 2 Christophe Marin 2011-05-01 16:45:06 UTC

Can be reproduced with KMail2.

Comment 3 Denis Kurz 2016-09-24 17:59:26 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 22:18:21 UTC

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