搜尋 Mozilla 技術支援網站

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

了解更多

Installed to later version of Thunderbird; now its authentication with RoadRunner Email fails.

  • 2 回覆
  • 0 有這個問題
  • 7 次檢視
  • 最近回覆由 jhughey

more options

Was using a version in the 90's, then updated Thunderbird to 102.14.0. I can open Thunderbird, but I can no longer access my RoadRunner Email.

I get the error message "The server does not support the selected authentication method. Please change the 'Authentication method' "  Nothing in the updated versions PW settings seems to have changed.  

I even verified I could access my RR Email directly online with Firefox. T-Bird has the *same exact PW* listed in my Firefox, so then I edited it to the same, just to see if a subsequent PW updating would be consistent with the T-Bird update.

Please help, otherwise I will have to reinstall T-Bird back to the earlier version. This is exactly why I avoid updates.

Was using a version in the 90's, then updated Thunderbird to 102.14.0. I can open Thunderbird, but I can no longer access my RoadRunner Email. I get the error message "The server does not support the selected authentication method. Please change the 'Authentication method' " Nothing in the updated versions PW settings seems to have changed. I even verified I could access my RR Email directly online with Firefox. T-Bird has the *same exact PW* listed in my Firefox, so then I edited it to the same, just to see if a subsequent PW updating would be consistent with the T-Bird update. Please help, otherwise I will have to reinstall T-Bird back to the earlier version. This is exactly why I avoid updates.

被選擇的解決方法

It's fixed. Apparently Re-entering the 2019 saved PWs must have corrected the problem. Thank you!

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

Sorry, I forgot to say:

                                O/S – Windows 7
                                Mailbox – pop-server.hvc.rr.com
                                SMTP – smtp-server.hvc.rr.com
more options

選擇的解決方法

It's fixed. Apparently Re-entering the 2019 saved PWs must have corrected the problem. Thank you!