Menu

Can't send Mails when Enigmail is activated

2018-10-20
2019-02-04
  • Andre Hulle

    Andre Hulle - 2018-10-20

    Hi,

    I have a problem on Thunderbird 52.9.1 with using Enigmail 2.0.8:

    If I create a new Mail (without using any of the Enigmail possibilities
    in that mail) than its not possible to send the Mail. The send-button is
    clickable, but nothing happens if I click on it. No error message, no
    status appears. Just nothing. It doesnt matter how often I click on and
    how long I wait - nothing happens.

    If I leave the Message open and go to the Add-ons page of Thunderbird
    and deactivate Enigmail and try again to click on the send-button, the
    button works und the Mail gets sended.

    So Im sure, that the problem is definitely caused by Enigmail. I have
    not installed any other addons except the Lightning calendar addon.

    What could be the problem? How can I find out what the problem is?

    Best regards

    Andre

     
  • Patrick Brunschwig

    This looks like something is blocking Enigmail from doing its job. Do you have any other add-ons installed apart from Enigmail and Calendar/Lightning?

     
  • Martin Gregoire

    Martin Gregoire - 2018-11-20

    I have exactly the same problem as Andre Hulle described above, using Thunderbird 60.2.1 and Enigmail 2.0.8 on Ubuntu 18.04.1 LTS.

    When starting Thunderbird from the terminal, there is a message which might be helpful: first time when entering the recipient mail address, second time when clicking the "send" button, this message is logged:

    JavaScript error: resource://enigmail/pEpAdapter.jsm, line 689: TypeError: err.exception is null

    Please let me know if I can help by providing more information.

     
  • Patrick Brunschwig

    It looks like there is a problem with the pEp engine. The easiest solution is to go to menu Enigmail/pEp > Preferences and switch to the "Compatibility" tab. Select the option "Force using S/MIME and Enigmail"

     
  • Furlong

    Furlong - 2018-12-14

    Same problem here with the forced pEp mode ... it occurred out of nothing

    pEpAdapter.getIdentitiesForEmails: ERROR: {"code":"PEP-unavailable","exception":null,"message":"Cannot establish connection to PEP service"}

    Solved it by switching back to Enigmail/SMIME until the pEp people fix it.

     

    Last edit: Furlong 2018-12-14
  • Anonymous

    Anonymous - 2018-12-20

    Hello everyone,

    just wanted to let you know that I am experiencing the same problem. I'm on up-to-date MX Linux. I'm using Enigmail Version 2.0.8 (20180804-1515) and TB 52.9.1 (64-bit). The problem came up out of the blue, the Send-Button stopped causing any response. Emails can also not be saved on the Draft-Folder on IMAP.
    Oddly, disabling Enigmail does not cause Enigmail buttons to disappear and also does not solve the mentioned problem. I have to start TB in Safe Mode, that helps.

    Is there anything I can do to help fix the bug? Can we report this to the guys developing PEP?

     
  • Patrick Brunschwig

    How about killing all pEp processes (pep-json-server or pep-json-server-bin) and then retry? Alternatively, switch to the "classical" mode as described above.

     
    • Anonymous

      Anonymous - 2019-01-09

      Thank you Patrick, I will try this later today. Will let you know about the results.

       
  • Marc Hansen

    Marc Hansen - 2018-12-27

    I had the same problem under Windows Terminal Server.
    Restart the Server solved the problem. After investigation together with with Olav we had some problems with the keyserver. Opening the firewall Port 11371 and using a stable keyserver solved the problem.

     
  • Furlong

    Furlong - 2019-01-23

    It seems like we found the error: https://pep.community/t/send-button-of-emails-not-working-anymore-in-pep-mode/39/#post-141

    For a quick workaround: Just move all the backup files counting up to gpg.conf.98.pep.bkp from /home/yourname/.gnupg to a subfolder.

    A real fix will follow from the pEp developers, I guess.

     
  • Martin Gregoire

    Martin Gregoire - 2019-02-04

    Thanks for the workaround @Furlong, I can confirm this is working on my setup.

     

Log in to post a comment.