为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 4 个回答
  • 1 人有此问题
  • 2 次查看
  • 最后回复者为 Matt

more options

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.

所有回复 (4)

more options

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

more options

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.

more options

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

more options

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