Bug 94878 - Missing choice in "Unusable Encryption Keys" dialog: don't encrypt
Summary: Missing choice in "Unusable Encryption Keys" dialog: don't encrypt
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-12-11 00:51 UTC by Gilles Schintgen
Modified: 2015-04-12 10:15 UTC (History)
1 user (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 Gilles Schintgen 2004-12-11 00:51:05 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Gentoo Packages
OS:                Linux

Hi, I was in the middle of moving to a different e-mail address when I encountered this error message:

  Unusable Encryption Keys
  Examination of recipient's encryption preferences yielded that
  the message should be encrypted using OpenPGP, at least for
  some recipients;
  however, you have not configured valid trusted OpenPGP
  encryption keys for this identity.
  You may continue without encrpyting to yourself, but be aware
  that you will not be able to read your own messages if you do
  so.

The dialog offers "Continue" and "Cancel" buttons. IMHO an obvious thing to do in this situation would be to send the message in plaintext (that depends of course on the content...) and then fix the configuration. Unfortunately, the dialog doesn't allow the user to override the behaviour defined in the Address Manager. In this particular case the recipient is even only set to "Always Encrypt If Possible" and not to "Always Encrypt". I'd say a third button "Send unencrypted" should be added to this message box.

Kind regards
Comment 1 Gilles Schintgen 2005-03-17 17:38:46 UTC
Same behaviour in KMail 1.8.
Perhaps I could make the description somewhat clearer. To reproduce this:
1. Open the composer
2. Choose an identity for which no private key has been configured
3. Choose a recipient for whom en encryption key is available, so that KMail tries to encrypt
4. Send

By the way, starting a new paragraph after a semicolon looks strange...
Comment 2 Laurent Montel 2015-04-12 10:15:02 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.