Bug 136384 - The encryption type specified in the contact of kaddressbook isn't used by the composer
Summary: The encryption type specified in the contact of kaddressbook isn't used by th...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-27 17:03 UTC by Rudolf Kollien
Modified: 2015-04-12 10:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rudolf Kollien 2006-10-27 17:03:19 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs

Hello, this report may be similar to bug #101968 but i'm not sure.
In my identity settings i choosed as preferred encryption type "OpenPGP/MIME" and deposed a GPG-key AND a S/MIME key.
In kaddressbook i saved different encryption settings depending on the one the contact uses (GPG/PGP or S/MIME). Now when i open the composer, enter a receipient and the text, activate the "sign" and press send, then always OpenPGP is used. Now when the contact settings say "S/MIME" i get a message, that the signing key isn't found (or specified?). Than i manually have to change the encryption type in the options menu of the composer to use the S/MIME and not the OpenPGP. I think, the composer should automatically use the encryption setting from the contact. Only when more than one contact with different encryption settings are specified as addressees a message to define the type to use should pop up. In the moment, the only sense the encryption type in the contact make, is to be sure to change the encryption type manually.
Comment 1 Laurent Montel 2015-04-12 10:06:06 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.