Enigmail / Forum / Enigmail Support: Enigmal prevents Emails being sent after Thunderbird update

Florian Elz - 2019-11-16

Hi, I have a similar problem like the person stated there: https://addons.thunderbird.net/de/thunderbird/addon/enigmail/reviews/1159488/

"99% of the time prevents E-mails from being sent, for no visible reason. Drafts end up duplicated every time. This is just broken, how did this get past basic tests?
Update: Looking at the Error Console, it's throwing an exception. Yeah thanks Enigmail, very helpful."

After Thunderbird update 68.2.2 no Emails can be sent from thunderbird, if enigmail (2.1.3) is activated. Same problem persists if i disable the protection of enigmail in the menu.

When i press the Button send nothing happens. No error, no loading, just nothing.
There is no draft created.

It only works if i disable the enigmail addon, so i can at least send not encrypted emails.

I never had or have the chrome browser installed if that is connected to the error

Error Log:
No chrome package registered for chrome://browser/skin/identity-icon.svg
Enigmail bootstrap completed
installPep.jsm: caught exception: NS_ERROR_FAILURE
Message: 'Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove]'
File: undefined
Line: 301
Stack: performInstall@chrome://enigmail/content/modules/installPep.jsm:301:20
onLoaded@chrome://enigmail/content/modules/installPep.jsm:239:9

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove] installPep.jsm:301
TypeError: err.exception is null
4 pEpAdapter.jsm:696:7
GenericSendMessage FAILED: 2147500036 MsgComposeCommands.js:3835
TypeError: err.exception is null
8 pEpAdapter.jsm:696:7
GenericSendMessage FAILED: 2147500036 MsgComposeCommands.js:3835
TypeError: err.exception is null
3 pEpAdapter.jsm:696:7
TypeError: err.exception is null
pEpAdapter.jsm:696:7
TypeError: err.exception is null
pEpAdapter.jsm:696:7

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Brunschwig - 2019-11-16

There is a bug in the pEp engine that prevents it from starting properly. You need to delete the following files:

$HOME/.gnupg/gpg.conf.*.pep.bkp
$HOME/.gnupg/gpg-agent.conf.*.pep.bkp

Then restart Thunderbird.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Schuster - 2019-11-24

Hi,
in a Windows 10-based environment I face the same issue.
Applying your instructions accordingly I don't find any of the files in "%APPDATA%\GnuPG".
Is there another solution available for Windows 10?

Thanks in advance for your support

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Patrick Brunschwig - 2019-11-25
  
  The issue for which I described the steps above does not exist on Windows.
  
  I rather suspect that you suffer from the problem described here: https://sourceforge.net/p/enigmail/forum/support/thread/d3cf983d0b/
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Schuster - 2019-11-27

Thanks for the quick response.
Meanwhile I tried as a first shot a complete re-installation of gpg4win and Enigmail.
After the re-installation the issue still exists.

In the post you referred to, a script for Linux/macOS/Unix is described. Could you provide as well instructions how to search for poisoned keys in a Windows based environment?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Patrick Brunschwig - 2019-11-27
  
  I don't know of any windows tool that would achieve that easily. This will certainly take a while...
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Schuster - 2019-11-28

Sounds like just another reason why I should say goodbye Windows soon ;).
Would the deletion of my complete public key ring as well be a possibility to check if poisoned keys are the rootcause? If so, how can I achieve that in Windows in a safe way (via GUI of Enigmail or deletion of files)?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Patrick Brunschwig - 2019-11-28
  
  That could possibly work.
  
  I'd recommend you rename pubring.gpg to something else, such that you don't lose it.
  
  Make sure you kill all running gpg and gpg-agent processes first. Also, you'll have to re-import your keys from secring.gpg using gpg --import secring.gpg afterwards.
  
  alternate
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Schuster - 2019-11-29

Deletion of my public key ring didn't help.
I'll wait for the Thunderbird built-in support of PGP encryption planned for next year:
https://www.zdnet.com/article/thunderbird-to-add-built-in-support-for-openpgp-email-encryption-standard/
... or alternatively switch to a linux-based environment and give it a retry.

Thanks so far for the support provided, no further activities required.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ian Campbell - 2019-12-09

I have been using TB for the last 6 months without issue. Updated to 68.3 no issues. Have had Enigmail working without issue until some time on the weekend. last successful email out was Saturday afternoon.
Emails will not go out.
Tested firewall, anti virus, checked SMTP settings, reinstalled TB to no effect. only disabling Enigmail will let my mail go out.
I am on a Mac with OS 10.14.6.. I am pretty new to GPG. I want encryption but don't understand much of its configuration.
Can you please help?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Patrick Brunschwig - 2019-12-10

Did you try my suggestion from above to delete some files from your GnuPG directory? Open a Terminal window and copy & paste the following two lines into the Terminal window, then hit Enter.

rm $HOME/.gnupg/gpg.conf.*.pep.bkp rm $HOME/.gnupg/gpg-agent.conf.*.pep.bkp
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Ian Campbell - 2019-12-10
  
  fantastic job!! It works.
  
  Thanks so much,
  
  Ian Campbell CPA, CMA, CMC
  M: +1 705 321 0135
  T: +1 705 835 5689
  E: iscampbell@iscampbell.com
  W: www.iscampbell.com
  
  On 2019-12-10 02:14, Patrick Brunschwig wrote:
  
  Did you try my suggestion from above to delete some files from your
  GnuPG directory? Open a Terminal window and copy & paste the following
  two lines into the Terminal window, then hit Enter.
  
  rm $HOME/.gnupg/gpg.conf..pep.bkp
  rm $HOME/.gnupg/gpg-agent.conf..pep.bkp
  
  Enigmal prevents Emails being sent after Thunderbird update
  https://sourceforge.net/p/enigmail/forum/support/thread/071570f224/?limit=25#01c4
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/enigmail/forum/support/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  alternate
  
  pEpkey.asc
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Enigmal prevents Emails being sent after Thunderbird update

OpenPGP addon for Mozilla Thunderbird

Forums

Help

Enigmal prevents Emails being sent after Thunderbird update

Enigmal prevents Emails being sent after Thunderbird update

OpenPGP addon for Mozilla Thunderbird

Forums

Help

Enigmal prevents Emails being sent after Thunderbird update document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Enigmal prevents Emails being sent after Thunderbird update