This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

TB 78.4.0 won't download email. Sending email possible

  • 4 àwọn èsì
  • 2 ní àwọn ìṣòro yìí
  • 2 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ romancalzaferri

romancalzaferri
romancalzaferri
more options

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

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à 👍 0

All Replies (4)

romancalzaferri
romancalzaferri Ìbéèrè olóhun
more options

The update to 78.4.0 was from v. 68

jborynec
jborynec
more options

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

jborynec
jborynec
more options

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.

romancalzaferri
romancalzaferri Ìbéèrè olóhun
more options

Ọ̀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.