Cannot send email after 38.1.0 update. Clicking "Send" does nothing at all.
After upgrading to 38.1.0, I cannot send any emails. When I click the "send" button, nothing happens. No errors, NOTHING.
Looking into other people's problems on the MozillaZine forums, I have disabled lightning and done what I can to get rid of any logjam vulnerabilities in Postfix and Dovecot. I run the email server that Thunderbird is connecting to.
If I start thunderbird with the -console option, nothing shows up in the console when I click send.
I can receive email, which means that IMAP does work, but it appears that Thunderbird is no longer saving any messages to the Drafts folder.
This is on the console, but these messages do not appear to be associated with any specific user action. When they appeared, I was not doing anything.
enigmail.js: Registered components mimeVerify.jsm: module initialized
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: path is null Full stack: anonymous/winIsAbsolute@resource://gre/modules/osfile/ospath_win.jsm
- 220:7
anonymous/split@resource://gre/modules/osfile/ospath_win.jsm:298:15 makeDir@resource://gre/modules/osfile/osfile_win_front.jsm:509:24 AbstractFile.makeDir@resource://gre/modules/osfile/osfile_shared_front.jsm:534:5
makeDir@resource://gre/modules/osfile/osfile_async_worker.js:215:13 worker.dispatch@resource://gre/modules/osfile/osfile_async_worker.js:31:26 anonymous/AbstractWorker.prototype.handleMessage@resource://gre/modules/workers/ PromiseWorker.js:122:16 @resource://gre/modules/osfile/osfile_async_worker.js:46:43
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: path is null Full stack: anonymous/winIsAbsolute@resource://gre/modules/osfile/ospath_win.jsm
- 220:7
anonymous/split@resource://gre/modules/osfile/ospath_win.jsm:298:15 makeDir@resource://gre/modules/osfile/osfile_win_front.jsm:509:24 AbstractFile.makeDir@resource://gre/modules/osfile/osfile_shared_front.jsm:534:5
makeDir@resource://gre/modules/osfile/osfile_async_worker.js:215:13 worker.dispatch@resource://gre/modules/osfile/osfile_async_worker.js:31:26 anonymous/AbstractWorker.prototype.handleMessage@resource://gre/modules/workers/ PromiseWorker.js:122:16 @resource://gre/modules/osfile/osfile_async_worker.js:46:43
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: path is null Full stack: anonymous/winIsAbsolute@resource://gre/modules/osfile/ospath_win.jsm
- 220:7
anonymous/split@resource://gre/modules/osfile/ospath_win.jsm:298:15 makeDir@resource://gre/modules/osfile/osfile_win_front.jsm:509:24 AbstractFile.makeDir@resource://gre/modules/osfile/osfile_shared_front.jsm:534:5
makeDir@resource://gre/modules/osfile/osfile_async_worker.js:215:13 worker.dispatch@resource://gre/modules/osfile/osfile_async_worker.js:31:26 anonymous/AbstractWorker.prototype.handleMessage@resource://gre/modules/workers/ PromiseWorker.js:122:16 @resource://gre/modules/osfile/osfile_async_worker.js:46:43
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: path is null Full stack: anonymous/winIsAbsolute@resource://gre/modules/osfile/ospath_win.jsm
- 220:7
anonymous/split@resource://gre/modules/osfile/ospath_win.jsm:298:15 makeDir@resource://gre/modules/osfile/osfile_win_front.jsm:509:24 AbstractFile.makeDir@resource://gre/modules/osfile/osfile_shared_front.jsm:534:5
makeDir@resource://gre/modules/osfile/osfile_async_worker.js:215:13 worker.dispatch@resource://gre/modules/osfile/osfile_async_worker.js:31:26 anonymous/AbstractWorker.prototype.handleMessage@resource://gre/modules/workers/ PromiseWorker.js:122:16 @resource://gre/modules/osfile/osfile_async_worker.js:46:43
A coding exception was thrown and uncaught in a Task.
Full message: TypeError: path is null Full stack: anonymous/winIsAbsolute@resource://gre/modules/osfile/ospath_win.jsm
- 220:7
anonymous/split@resource://gre/modules/osfile/ospath_win.jsm:298:15 makeDir@resource://gre/modules/osfile/osfile_win_front.jsm:509:24 AbstractFile.makeDir@resource://gre/modules/osfile/osfile_shared_front.jsm:534:5
makeDir@resource://gre/modules/osfile/osfile_async_worker.js:215:13 worker.dispatch@resource://gre/modules/osfile/osfile_async_worker.js:31:26 anonymous/AbstractWorker.prototype.handleMessage@resource://gre/modules/workers/ PromiseWorker.js:122:16 @resource://gre/modules/osfile/osfile_async_worker.js:46:43
Zgjidhje e zgjedhur
I had an old version of Identity Chooser (1.8.8). Upgrading that to 1.9.3 got everything working again. I was under the impression that add-ons would automatically udpate themselves, but I guess I was wrong.
Lexojeni këtë përgjigje brenda kontekstit 👍 1Krejt Përgjigjet (4)
I have disabled lightning
Lightning is not related to problems with sending messages.
and done what I can to get rid of any logjam vulnerabilities in Postfix and Dovecot.
Are you saying you did adjust the Postfix/Dovecot configs so that your server isn't vulnerable anymore?
Did you get anything like this in the Error Console? Error code: ssl_error_weak_server_ephemeral_dh_key
Starting Thunderbird in safe mode fixed the problems. This prompted me to go through my add-ons and see if disabling any of them would fix it.
I only have two add-ons of my own installed (other than Lightning, which was auto-installed by the upgrade): Enigmail and Identity Chooser. I maintain a lot of identities, so that last one makes life easier.
Identity Chooser was the problem add-on. WIth that one disabled and all the others enabled, I was able to send.
Zgjidhja e Zgjedhur
I had an old version of Identity Chooser (1.8.8). Upgrading that to 1.9.3 got everything working again. I was under the impression that add-ons would automatically udpate themselves, but I guess I was wrong.
I was under the impression that add-ons would automatically udpate themselves
They normally do. In any case, can you mark the thread as 'Solved' please with your solution, so others can benefit from it. Thank you.