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

New Thunderbird version 78.4 will not connect to my isp - HughesNet - and will not download or send new email. How do I fix this?

  • 5 replies
  • 2 have this problem
  • 1 view
  • Last reply by rbthorne

more options

New Thunderbird version 78.4 will not connect to my isp - HughesNet - and will not download or send new email. How do I fix this? Older version 68 worked just fine. I'm using Windows 7. At the suggestion of another article I checked the security settings on TB - they seem to be just fine. My address book is intact, and all the older emails downloaded also. Just can't get the new ones.

New Thunderbird version 78.4 will not connect to my isp - HughesNet - and will not download or send new email. How do I fix this? Older version 68 worked just fine. I'm using Windows 7. At the suggestion of another article I checked the security settings on TB - they seem to be just fine. My address book is intact, and all the older emails downloaded also. Just can't get the new ones.

Chosen solution

The TLS change that worked is referenced through the links provided, sorry I didn't write them down! Three or four lines above TLS version in the config editor... Something on the order of "security.TLS. ... enabled-deprecated" changed false to true.

Read this answer in context 👍 0

All Replies (5)

more options

I have the same problem. Thunderbird update alone, and now i don't receive emails. I only can send, but i don't received

more options

See the articles under "see also" https://support.mozilla.org/questions/1297273 - changing the TLS setting allows me to download emails, but TB is terribly slow and hangs a lot.

more options
more options

Changing the TLS version to 1 got me the emails, but the whole program bogged down and made reading them an exercise in extreme frustration. Changing the the TLS from false to true seems to have fixed the issue, after restoring the TLS back to 3. Thanks.

more options

Chosen Solution

The TLS change that worked is referenced through the links provided, sorry I didn't write them down! Three or four lines above TLS version in the config editor... Something on the order of "security.TLS. ... enabled-deprecated" changed false to true.