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

Version 45 not sending or receiving emails. Installations with version 38.5 work fine

  • 4 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 3 views
  • Last reply by Matt

We have multiple computers with Thunderbird installations. Most of them stopped being able to send or receive emails this morning, 1/17/17. They all seem to be on version 45. Other installations that are on version 38.5 are working fine.

This same issue is present on both Windows and Apple OS

just began today. Settings with email host have not changed.

We have multiple computers with Thunderbird installations. Most of them stopped being able to send or receive emails this morning, 1/17/17. They all seem to be on version 45. Other installations that are on version 38.5 are working fine. This same issue is present on both Windows and Apple OS just began today. Settings with email host have not changed.

All Replies (4)

Does this affect the same email account in all cases, or different ones? And could you have a look at this question?

multiple addresses on the same T-bird installation. They are all pointing at the same host and domain. I am about to reach out to my domain host, because I have a T-bird installation of version 45.6 with email addresses from two different domains installed, and 1 is fine(gmail account), and the other is not working. So, perhaps the problem is not with Thunderbird at all.

From the Error Console:

Timestamp: 1/17/17, 7:49:29 PM Error: An error occurred during a connection to mail.'mydomain'.com:993.

Cannot communicate securely with peer: no common encryption algorithm(s).

Error code: <a id="errorCode" title="SSL_ERROR_NO_CYPHER_OVERLAP">SSL_ERROR_NO_CYPHER_OVERLAP</a>

Timestamp: 1/17/17, 7:49:35 PM Error: uncaught exception: 2147746065 Source File: resource:///modules/activity/autosync.js Line: 210

How about actually posting the domain name. Clearly it has issues and there is no way to diagnose them without the name.