Bug 258137 - Encryption always shows key verify box, and setting the preference to always use the selected keys for that recipient gets put back to none. Changing it, kmail wants to add contact under address of contact@localhost
Summary: Encryption always shows key verify box, and setting the preference to always ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: config dialog (show other bugs)
Version: 2.0.89
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-11-28 04:01 UTC by octo
Modified: 2018-10-27 02:38 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 octo 2010-11-28 04:01:56 UTC
Version:           2.0.89 (using KDE 4.5.80) 
OS:                Linux

Encryption always shows key verify box, and setting the preference to always use the selected keys for that recipient gets put back to none.  Changing it, kmail eventually wants to add a contact under the address of contact@localhost and asks for a name to save it under. I thought maybe It did that because the recipient info in the gpg key was different than what I currently had in my contact list so I let it make a new one and I just used that one instead. Upon creating another email to that recipient the verify keys dialog pops up still and when I try to select always use these keys, it prompts me to save the recipient again under another name and saves the address as contact@localhost ? It just keeps going in circles.

If I leave the option in the key verify dialog to none , then it sends the mail signed and encrypted and doesn’t try to create a new contact. 

Reproducible: Always




OS: Linux (i686) release 2.6.34.7-0.5-default
Compiler: gcc
Comment 1 Sandro Knauß 2013-11-24 23:48:21 UTC
Is this bug still valid? Please test the behaviour with the newest stable kmail.
Comment 2 Andrew Crouthamel 2018-09-25 03:44:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 02:38:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!