TB 78.4.0 won't download email. Sending email possible
Since the automatic update to TB 78.4.0 (32-bit), no email will download. TB keeps being stuck at "Connected to [server]". This happens on all accounts, pop3 as well as imap, on 3 different servers. It doesn't even work on my gmail account.
Sending from pop3 account works as it should. Sending from imap account: the email will send, but: "... a copy was not placed in your sent folder due to network or file access error".
In the config editor, I have changed (as described elsewhere): - security.tls.version.min to 1 - security.tls.version.enable-deprecated to true
Ọ̀nà àbáyọ tí a yàn
I Found the culprit: It was the Antivirus, in this case Eset. Disabled Web/Email "SSL/TLS protocol filtering". Now everything works as it should.
Ka ìdáhùn ni ìṣètò kíkà 👍 0All Replies (4)
The update to 78.4.0 was from v. 68
I have the same problem. When I set up logging via set MOZ_LOG=IMAP:5,timestamp I get the following repeated many times
2020-11-02 19:07:33.994000 UTC - [(null) 31888: IMAP]: I/IMAP 2FF3B800:.taiga.ca:NA:CreateNewLineFromSocket: (null) 2020-11-02 19:07:33.994000 UTC - [(null) 31888: IMAP]: D/IMAP SetConnectionStatus(0x805a1fa6) 2020-11-02 19:07:33.994000 UTC - [(null) 31888: IMAP]: D/IMAP URL failed with code 0x805a1fa6 (imap://jborynec@.taiga.ca:993/select%3E.INBOX) 2020-11-02 19:07:33.994000 UTC - [(null) 31888: IMAP]: I/IMAP 2FF3B800:.taiga.ca:NA:ProcessCurrentURL: aborting queued urls
Some poking around suggests that my "0x805a1fa6" problem is related to: SEC_ERROR_INADEQUATE_KEY_USAGE
And that is caused by using a self signed cert.
Getting Thunderbird to fetch the certificate via the certificate management interface seems difficult / impossible.
Ọ̀nà àbáyọ Tí a Yàn
I Found the culprit: It was the Antivirus, in this case Eset. Disabled Web/Email "SSL/TLS protocol filtering". Now everything works as it should.