Bug 358707

Summary: KMail doesn't respect crypto options when replying
Product: [Applications] kmail2 Reporter: Gareth Williams <gareth>
Component: cryptoAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: minor    
Priority: NOR    
Version: 4.14.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Gareth Williams 2016-01-28 21:27:53 UTC
On a system where GPG and S/MIME certificates are installed and KMail is set to prefer S/MIME, replying to a plain, GPG or S/MIME email causes KMail to attempt to use GPG.

Checking Options -> Cryptographic Message Format, shows no radio button selected whereas it should be S/MIME.  When the Send button is sent, KMail asks for the passphrase to open the GPG key.

Reproducible: Always

Steps to Reproduce:
1. Reply to plain, GPG or S/MIME email
2. Check Options -> Cryptographic Message Format for S/MIME but you'll see no radio button selected.
3. Click on Send.

Actual Results:  
KMail attempts to send using GPG signature.

Expected Results:  
KMail should send using S/MIME signature.

Creating a new email works as expected - S/MIME is selected in the cryto message format setting and the mail is signed using S/MIME.

Workaround is to always remember to check Options->Cyptographic Message Fromat and change it to S/MIME before sending.
Comment 1 Justin Zobel 2022-10-19 22:11:01 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-03 05:07:16 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
mark the bug 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 Bug Janitor Service 2022-11-18 05:17:31 UTC
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!