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

Thunderbird stopped receiving email. SOLVED caused by ESET/NOD32

  • 7 ŋuɖoɖowo
  • 2 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ hans210

more options

I've been using Thunderbird for over 10 years and suddenly yesterday after an update to 78.5.0 it stopped receiving emails. It also started to raise an error when I send an email "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to a network or file access errors."

When I select "Get all new messages", there is no response, no status message at the bottom of the window and no errors or other response.

I have rebooted and reinstalled Thunderbird - still no joy.

I have ESET Nod32 Antivirus and email still fails if I turn email scanning off.

I have several gmail accounts. They have worked for years. What changed?

Thunderbird 68.12.1 is working fine with these email accounts on a second computer I have.

Thank you, Mike

I've been using Thunderbird for over 10 years and suddenly yesterday after an update to 78.5.0 it stopped receiving emails. It also started to raise an error when I send an email "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to a network or file access errors." When I select "Get all new messages", there is no response, no status message at the bottom of the window and no errors or other response. I have rebooted and reinstalled Thunderbird - still no joy. I have ESET Nod32 Antivirus and email still fails if I turn email scanning off. I have several gmail accounts. They have worked for years. What changed? Thunderbird 68.12.1 is working fine with these email accounts on a second computer I have. Thank you, Mike

Wayne Mery trɔe

Ŋuɖoɖo si wotia

According to their forums, you should temporarily disable SSL in ESET until they solve the problem per https://support.eset.com/en/kb3126-disable-ssl-filtering-in-eset-windows-products?ref=esf - the problem is being reported by dozens of users https://forum.eset.com/topic/26517-problems-with-thunderbird-and-imaps/ https://forum.eset.com/discover/

Xle ŋuɖoɖo sia le goya me 👍 4

All Replies (7)

more options

I got the same problem since today morning. Seems there is not soultion... :(

more options

I have the same problem. I also run ESET. My provider is Cox. I checked with Cox and all my settings are correct. I am only having this problem on my main desktop. I can receive Cox mails on my phone and iPad without issue. Problem started around 11/30/20. Sending emails is ok on this device, just can't receive. Went to Cox webmail and deleted mails back through 11/29. Still no joy. Not aware of any updates recently. I am on Pop-3, Port 995, SSL/TLS. On the bottom left of the screen the Thunderbird status line is hung on "Connected to pop.cox.net...". Usually it tells me it's either downloading or there are no messages to download. I shall sincerely appreciate any help to this problem. Thank you. Steve

more options

Ɖɔɖɔɖo si wotia

According to their forums, you should temporarily disable SSL in ESET until they solve the problem per https://support.eset.com/en/kb3126-disable-ssl-filtering-in-eset-windows-products?ref=esf - the problem is being reported by dozens of users https://forum.eset.com/topic/26517-problems-with-thunderbird-and-imaps/ https://forum.eset.com/discover/

more options

Took action per Wayne Mery's email regarding SSL Filtering, and it worked. Thanks, Wayne.

more options

Followed Wayne Mery's solution and it worked! Many thanks for the super fast solution!!!

more options

I have had this same problem also. Can send but not receive in both POP3 and IMAP (cox.net.) Seemed strange the outgoing emails were ok but not incoming.

The solution suggested above to disable ESET SSL filtering worked for me. I am going to contact ESET and report the issue. Thanks Wayne.

J

more options

You don't have to disable fhe ESET SSL filtering permanently. For me it worked to just temporarily disable the filtering, then re-enable it and restart the computer, just as ESET had proposed in their instruction.