Thunderbird email not working
I'd be very grateful for any help you can give me with the following issues.
I installed Thunderbird version 78.5.0 on 13 November. As of yesterday, I have the following problems:
1. A continuously spinning circle appears in my inbox as though it's hanging. This does not happen in any of the other folders (eg Sent Mail, All Mail). 2. Incoming emails are not appearing in my inbox. I can get them in GMail. 2. When I send an email I get the following error message: "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent Mail-xxx." Sent emails do reach the addressees.
Other information which may be relevant: 1. I run Windows 10 Home 64-bit version 1909 2. My security software is ESET Internet Security version 14.0.22.0
Looking forward to hearing from you.
Valgt løsning
If you are using ESET/NOD32 security/AV then probability is very high it is causing your problems. According to their forums, you should temporarily disable SSL 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/
Læs dette svar i sammenhæng 👍 0Alle svar (2)
Valgt løsning
If you are using ESET/NOD32 security/AV then probability is very high it is causing your problems. According to their forums, you should temporarily disable SSL 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/
Hi Wayne, many thanks. It is indeed an ESET problem, which ESET has confirmed they are working on. Meantime, your suggestion worked. I closed down Thunderbird, disabled SSL and then re-enabled it before re-opening Thunderbird. That did the trick. Many thanks, Kate