Yahoo Thunderbird Setup Failure
Attempting to set up a yahoo email in thunderbird 140.9.0esr(64-bit). The goal is to have this set up on multiple workstations, so I've made the adjustments recommended per this article: https://support.mozilla.org/en-US/kb/thunderbird-and-yahoo#w_please-check-the-following-before-asking-for-support
So, the toggle for mailnews.oauth.usePrivateBrowser is set to true, site/third-party cookies are always allowed (no exceptions), and the authentication method is set to OAuth2. Using the recommended server settings for yahoo: imap.mail.yahoo.com : 993 smtp.mail.yahoo.com : 465
I am able to set up the initial OAuth. The window pops up, I log in using the account password then put in the texted code, then the window closes and I get an email confirming the login. Hitting done within Thunderbird after this has it check the password again, and it fails: "Unable to log in at server. Probably wrong configuration, username or password."
This is on a fresh Windows 11 install/fresh Thunderbird install.
Ọ̀nà àbáyọ tí a yàn
Resolved. Issue was that for some reason the domain for the oauth used by yahoo, guce.yahoo.com, was resolving through an IPv6 DNS server and returning a local address for some reason. Disabling the IPv6 adapter got the setup to work finally. The workstation doesn't use any IPv6-only services so there is no expected impact for that. Was not able to figure out a workaround while keeping IPv6 on. Even using google's/cloudlfare's IPv6 DNSs was giving the same issue. The router is older and doesn't have IPv6 DNS options so I couldn't figure out how to prevent the behavior. The address resolves fine with IPv6 still enabled on other networks.
Ka ìdáhùn ni ìṣètò kíkà 👍 0All Replies (5)
Also with a fresh antivirus is mu guess. The response comes to Thunderbird via the localhost adapter, many antivirus products block access to that because there was some malware 10 or 20 years ago that used it.
There is no third party antivirus on the PC, or any other typical OEM bloatware.
If you're using a VPN, turn it off for the authentication. If you're running a local web server, or any other service listening on TCP port 80, turn it off for the authentication.
There are no VPNs or proxies running. There are no services (unless used by Windows) that run over TCP/80. At the time of setup no other programs were running in the foreground, and the only programs that would be running in the background are Windows defaults.
Is there a log file that would contain the specific message/response/error related to this type of issue?
Ọ̀nà àbáyọ Tí a Yàn
Resolved. Issue was that for some reason the domain for the oauth used by yahoo, guce.yahoo.com, was resolving through an IPv6 DNS server and returning a local address for some reason. Disabling the IPv6 adapter got the setup to work finally. The workstation doesn't use any IPv6-only services so there is no expected impact for that. Was not able to figure out a workaround while keeping IPv6 on. Even using google's/cloudlfare's IPv6 DNSs was giving the same issue. The router is older and doesn't have IPv6 DNS options so I couldn't figure out how to prevent the behavior. The address resolves fine with IPv6 still enabled on other networks.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.