Bug 101968 - Kmail composer could allow overriding kaddressbook crypto settings
Summary: Kmail composer could allow overriding kaddressbook crypto settings
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: 1.8
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-20 10:48 UTC by Juha Tuomala
Modified: 2012-08-19 00:42 UTC (History)
2 users (show)

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 Juha Tuomala 2005-03-20 10:48:08 UTC
Version:           1.8 (using KDE KDE 3.4.0)
Installed from:    RedHat RPMs

When composing email message, kmail checks recipient encryption capabilities from kaddressbook. It would often be useful to override these settings temporarily for one message. 

Now the composer encryption buttons are grayed and only the addressbook settings matter. It could be so that the addressbook settings are read to the composer and user could change them before sending.
Comment 1 David Faure 2005-07-21 14:38:12 UTC
In which case are the encryption buttons grayed out (other than if no crypto backend is available)?

For me after I set crypto preferences for a recipient, I still get the "key approval" dialog when writing another mail to that recipient, where I can change the kaddressbook crypto setting (and then change them back later if wanted).
Comment 2 Juha Tuomala 2005-08-13 15:56:25 UTC
>In which case are the encryption buttons grayed out (other than if no crypto backend is >available)? 

This happens when the composer window opens. Now I tried and yes, those are grayed when the backend is not available. But I recall that even I had it available, it sometimes impossible to do some change to crypto when I wanted to do so.

I'll keep looking this behaviour more (when I just first could remember my pass phrase, forgot it because crypto was broken for a while and didn't use pgp :( )
Comment 3 Myriam Schweingruber 2012-08-18 08:22:29 UTC
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 4 Luigi Toscano 2012-08-19 00:42:49 UTC
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.