Bug 313930

Summary:	Kmail2 ignores user-specific encrytion
Product:	[Applications] kmail2	Reporter:	Bernd Weigelt <weigelt.bernd>
Component:	crypto	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	jessie, sknauss
Priority:	NOR	Keywords:	triaged
Version:	4.9.98 RC3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bernd Weigelt 2013-01-26 17:30:23 UTC

Hi

If i want to send an encrypted mail to an user, i have everytime to choose the key or the encryption-rules, like 'evrey time use this key' oder 'only this time' - sorry , i'm using translations from german language. But i have to do this _everytime_ for all users, if i want to send encryted mails and i have to enter the passphrase everytime.
This is very annoying, while i have to do 3-5 clicks and the passphrase to send every mail :(


thx
Bernd



Reproducible: Always

Steps to Reproduce:
1.Write a mail
2. click send
first Popup 'accept encryting key'
3. choose 'everytime with this key' or 'everytime when possible'
second popup 'which entry should the recipient in your addressbook,
4. I'm choosing mostly 'cancel' , because the recipient is in my addressbook and my choose is the same a last time
5a. sometime i got now: 'you have to choose your own key. Why?  I create my keys immediately, when i got a new address and there are on my keyrings
5b. enter the passphrase for your key
6. now the the mail could send


Actual Results:  
Mailsending take a long time and it breaks the workflow

Expected Results:  
Enter the options for every user or for specific user only once and store it, so that Kmail2 can restore my choose next without asking me stupid questions.

This happens for me on every system a long time.

Comment 1 Jessie A. Morris 2013-02-11 19:45:48 UTC

I can also confirm this. It seems it was fixed in 305346, but I can still reproduce this on 4.10.

Comment 2 Jessie A. Morris 2013-02-11 19:47:34 UTC

Actually, I lied, my bug is a different one. I seem to no longer be able to reproduce this in 4.10. I believe that this can be marked as a duplicate of the #305346 bug mentioned before.

Comment 3 Jessie A. Morris 2013-02-11 19:53:16 UTC

Actually, I guess there are 3 different bugs here. I can reproduce this one, but only after re-reading the poor English (no offense intended) above.

Here's what happens:

I have an email I am sending encrypted. I have the encryption settings set up in their contact. I select "Sign" and "Encrypt". It then pops up a dialog box saying, "Encryption Key Approval". Even though I have set up my contact to have their encryption preference be "Always Encrypt with This Key", it shows "<none>" in the dialog box.

Since I have configured the contact, I expect it to skip this dialog box and use my "Always Encrypt with This Key" setting to be honored.

Comment 4 Sandro Knauß 2013-11-25 00:10:07 UTC

Actually with kmail 4.11.4 the preferences from the addressbook are taken. Please use the newest version and describe, if it is solved for you. For me it works like this:
Ctrl+Enter to send , Enter for the "Key Approval Dialog", Passphrase (sometimes)

Btw. if you use gpg-agent to store your passphrase some minutes you don't have to type it for every mail.

Comment 5 Andrew Crouthamel 2018-09-25 03:51:21 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 6 Andrew Crouthamel 2018-10-27 04:15:58 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!