搜索 | 用户支持

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

详细了解

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

  • 2 个回答
  • 0 人有此问题
  • 38 次查看
  • 最后回复者为 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!