Menu

#382 Creating a per-recipient rule while sending results in "Internal Error: promised encryption disabled"

fixed
nobody
None
1.7.2
Minor
31.3.0
any
All
3.0
nobody
2020-12-28
2015-01-06
No

Prerequisites: An account with encryption enabled by default.

Steps to reproduce:

  1. Compose a mail to a recipient for whom you have no public key
  2. Click send
  3. The key selection windows appears (as there is no key available)
  4. Click on "Create per recipient rule(s)", assuming you don't want to encrypt to this recipient
  5. Create the following rule: Encrypt: Never, Sign: Never, PGP/MIME: Never. Click Ok.
  6. Compose window comes up with the following error message: "Internal Error: promised encryption disabled"

Step 6 should result in a send operation (unencrypted, unsigned) without any error.

Discussion

  • Sebastian

    Sebastian - 2016-03-21

    Just had the same bug with Enigmail 1.9.1 and Thunderbird 38.6.0

    There was no key for the recipient, but as opposed to the other post, the encryption setting for this account is not set to always.

     
  • Olav Seyfarth

    Olav Seyfarth - 2016-03-21

    Do you use a SmartCard for your private key or just the usual file based keyring? Is your PC rather old/slow? I ask since I suffer a similar issue about every 10th message (sporadically) but Patrick thought it may be related to timing (and I always sign using a SmartCard, on a i7 1st gen).

    What I see is that any message (new, reply, fwd) inherits parts of the sign/encrypt status from a previously viewed usage. Typically, I reply to a (non-OpenPGP) message and the EM sign+encrypt-Icons are both gold although I neither have rules not defaults to switch anything on. It seems to me there are side effects from my using S/MIME. Very difficult to pin. Maybe I should open a new bug for this issue?

     

    Last edit: Olav Seyfarth 2016-03-21
  • Sebastian

    Sebastian - 2016-03-21

    I'm using the file based keyring. Not the newest device, but performant for things I do (e.g. browsing, writing mails), "Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" (from lscpu) to be clear.

     
  • Patrick Brunschwig

    Still reproducible with Enigmail 2.1.8

     
  • Patrick Brunschwig

    • status: open --> fixed
    • Fixed in version: --- --> 3.0
     
  • Patrick Brunschwig

    Fixed as follows: the error message is now changed into a warning message with a better text indicating that encryption was disabled after hitting the Send button.

     

Log in to post a comment.