為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

I cannot send or receive email with a mail server that DOES support TLS 1.2 (was 78 and all its problems)

  • 7 回覆
  • 2 有這個問題
  • 3 次檢視
  • 最近回覆由 Wayne Mery

more options

A message re 78, the latest version: Because so many of us are experiencing problems with the latest version and suggestions re changing security.tis.version.min and security.source etc. do not work, I think you should pull this version, give us back the earlier version, thoroughly check 78 and all the problems we have told you, make sure all these problems have been solved, and then give us 78 I wonder if the program ever went through the usual format when something new is created: trying it out in various stages and rechecking constantly. We should not have to go through so many problems. I still cannot receive/send emails except on my server.

A message re 78, the latest version: Because so many of us are experiencing problems with the latest version and suggestions re changing security.tis.version.min and security.source etc. do not work, I think you should pull this version, give us back the earlier version, thoroughly check 78 and all the problems we have told you, make sure all these problems have been solved, and then give us 78 I wonder if the program ever went through the usual format when something new is created: trying it out in various stages and rechecking constantly. We should not have to go through so many problems. I still cannot receive/send emails except on my server.

由 Wayne Mery 於 修改

所有回覆 (7)

more options
so many of us are experiencing problems with the latest version and suggestions re changing security.tis.version.min

That's a problem of the email provider(s) not bothering to offer TLS version 1.2 to their customers which exists since 2008.

and security.source etc. do not work

Not sure what that means.

I still cannot receive/send emails except on my server.

What prevents you from sending and receiving mail? What exactly does 'except on my server' mean?

more options

Since I cannot receive/send emails via my Mozilla email screen, I go to my server (zzz.com) and deal with the emails there. I reply and send them, open and read them, delete junk, etc., just as I used to do on my Mozella email screen. But I cannot do any of that on my Mozilla screen because the emails don't leave the server.

more options

(It is helpful for the support topic to accurately reflect the problem being investigated - so I have changed it.)

If you have done what is suggested at https://support.mozilla.org/en-US/kb/thunderbird-78-faq#w_after-upgrading-to-thunderbird-78-i-cannot-get-or-send-email-messages and it still 'does not' work then maybe we have something to discuss.

If you have done that and it does work, then the problem is with your provider zzz.com

more options

I received an email from someone with a "do not reply" address so I'm answering here: Yes, I read the article "How to Enable Outdated...", I did what it said with no luck, I changed another "security.tis....." per a suggestion from another support person, and my server DOES support TLS 1.2. I still CANNOT receive emails; I'm reading and answering on my server. So now what? Doesn't this sound like a glitch in 78?

more options

Could someone please, please reply to the above post with a solution to my problem? I've done everything I could and did what some of your people suggested. My server supports TLS 1.2. So it must be a glitch in 78. When you read other comments, you'll see there are many varied problems besides mine.

more options

> So now what? Doesn't this sound like a glitch in 78?

Highly, highly unlikely - if you are running version 78.4.0, given that there is now over 6 million users of version 78 and there have been no version 78 send/receive bugs confirmed other certificate related issues. You can see a list of bugs reported https://mzl.la/32q7cMO, a significant number of which were attributed to TLS.

This is not to diminish the problem you are seeing. But I think the reality is efforts are best directed to identify the cause of your issue. On that point I do not have any recommendations at this time, other than see what happens after starting Windows 10 in safe mode.

more options

Did you solve your problem?