Bug 190672

Summary: Impossible to send unsigned message to recipient with valid encryption key
Product: [Applications] kmail Reporter: Tristan Miller <psychonaut>
Component: encryptionAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: christophe
Priority: NOR    
Version: 1.11.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description Tristan Miller 2009-04-26 00:01:41 UTC
Version:            (using KDE 4.2.2)
Installed from:    SuSE RPMs

Reproducibility: Always

Steps to reproduce:
1. File->New->New Message
2. In the "To" field, enter a recipient with a valid encryption key
3. Make sure that the "Sign" and "Encrypt" toolbar buttons are not pressed.
4. Specify a subject
5. Message->Send Mail

Observed behaviour:
6. A dialog pops up:

  Encrypt Message? – Kontact

  Valid trusted encryption keys were found for all recipients.  Encrypt this message?

  [ Sign & Encrypt ] [ Sign Only] [ Cancel ]

This dialog does not give the user the choice of sending an unsigned message!

Expected behaviour:
6. The dialog should give the user the option of sending an unsigned message.  The easiest way of managing the four options ((un)signed, (un)encrypted) would be with two checkboxes, which should default to unchecked:

  [ ] Sign message
  [ ] Encrypt message for all recipients

  [ Cancel ]
Comment 1 Jaime Torres 2009-04-27 12:10:38 UTC
This is using kde 4.2.70.

To send an unencrypted and unsigned mail, just uncheck both buttons (sign & encrypt).
Then the buttons are:
[ Sign ] [ Send As Is ] [ Cancel ]

The buttons you see are now when sign is checked.

There are also policies that apply to the recipients, such as: sign only, sign & encrypt, encrypt only, ask allways, never ask.....
Comment 2 Laurent Montel 2015-04-12 09:47:44 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.