Closed Bug 1997062 Opened 11 months ago Closed 2 months ago

Yahoo accounts cannot be added on TB 145.0b3 - "EDGE: too many requests"

Categories

(Thunderbird :: General, defect)

Thunderbird 145
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ramona, Unassigned)

References

Details

Attachments

(1 file)

Affected version:
145.0b3(20251028071931

Platform:
Win 11, macOS15.7.1

Steps to reproduce:
1.Launch latest TB beta.
2.Configure a new account using yahoo provider.

Actual results:
After filling in the email account and password and click on Continue button, the grant permission window opens, a message is displayed "EDGE: to many requests" and no field to enter your password or any of that kind is displayed.
Please check the screenshot attached as in the error console there isn't any errors.
I have tried with 3 different yahoo accounts and the same message is displayed.

Expected results:
2.The account should be added to TB without any problems.

Notes:
I have checked this issue in Troubleshoot mode and it's the same scenario.
Also i have checked this on TB 145.0b2(20251022123303) and yahoo accounts can be added without any problems.

Seems like bug 1992192

Summary: Yahoo accounts cannot be added on TB 145.0b3 → Yahoo accounts cannot be added on TB 145.0b3 - EDGE: to many requests
See Also: → 1992192

This error also occurs for me using Thunderbird 140.4.0esr on Ubuntu Linux 24.04.3. LTS.

(In reply to mark from comment #2)

This error also occurs for me using Thunderbird 140.4.0esr on Ubuntu Linux 24.04.3. LTS.

I should add a little more detail here.

  • The Yahoo account was working perfectly well with TB 104.4.0esr, but it was important to change the password.
  • Password was changed, and access from Chrome was confirmed.
  • I expected a request for new credentials from TB - instead, I see the "Edge: Too Many Requests" popup.
  • I deleted the saved passwords and restarted TB to try and trigger new OAuth tokens: same error.
  • I deleted the account from TB, and restarted: same error when trying to create the new account in TB.
  • Disabled add blockers (you never know!): same error.

So this is about creating the account, not ongoing authentication with Yahoo.

Yes, I too get this error.
I don't think it has to do with network/IP you/client is coming from.
In my case I have had a perfectly working TB+Yahoo account and reinstalled my Fedora and as a result of that, TB needed to re-authenticate itself with/to my Yahoo account - so hours prior to that, TB for many long years - on the same public network/IP I use - was receiving/sending mail a ok.
Also, at the same time TB fails with ".. too many requests.." I open any web browser and do log into my Yahoo Mail without any issue.
As a quick test - I switched over to & for ~hour stayed on my mobile cellular network, so different public network/IP - and issue remained.
thanks, L.

It started 3 days ago for me. I've attempted what was advised so far and what others here have also tried and also had no success. In using FairMail on mobile I have no problems so I can confirm the account works and is accessible.

This error also occurs for me using Thunderbird 140.4.0esr (aarch64) on macOS Tahoe. I can login to the Yahoo account directly from a browser. The only thing I can guess is that Yahoo prompted for an updated authentication request while I was not at my computer for two days. So if Thunderbird was refreshing every 5 minutes, did it try that auth request over and over again?

I decided to wait an extra day (~48 hours?) before attempting another login and received the error immediately again. I know this may be a "Yahoo side" issue but it may be getting exacerbated by the Thunderbird client auth process? My only thought is to wait an entire week and try again.

I am also getting this issue with Thunderbird 140.4.0esr installed using flatpak on OpenSuse Tumbleweed.

Same on Thunderbird 140.4.0esr on Windows 11 25h2

(In reply to Günter Gersdorf from comment #9)

Users in a german thunderbird forum says, that changing from oauth2 to password and using an app password solves the problem.
https://www.thunderbird-mail.de/forum/thread/97589-einrichten-von-yahoo-mail-konto-unm%C3%B6glich-etwas-ist-schiefgelaufen/?postID=563077#post563077
https://www.thunderbird-mail.de/forum/thread/97610-bei-der-einrichtung-kommt-edge-too-many-requests/?postID=563078#post563078

I can confirm this does it - app password works.
In the meanwhile as I needed my emails, because it's Linux/opensource I used one of many available alternatives - Evolution - which works with Oauth2.

Sounds very likely Yahoo quotas for Thunderbird are full. They would need to increase them.

Duplicate of this bug: 1998014
Duplicate of this bug: 1992192

On second thought. From searching the web, it seems this issue is not only affecting Thunderbird, but people also get it in browsers e.g. for yahoo webmail. So seems most likely Yahoo messed something up with their servers.

Foreword: With yahoo it can be hard to distinguish what's a new emerging issue, and what's not, because there is a past steady flow of yahoo problems.

Comment 9 German item translated

So seems most likely Yahoo messed something up with their servers

Yes. And reports in support and elsewhere for AOL, Rogers, Comcast/Xfinity account, etc. Surprisingly, so far I haven't seen reports from users of ATT & Verizon

I am and have been experiencing all the incarnations of bugs related to this and the change in protocol does seem to fix the initial issue.

An interesting related thing to this is if i try to use an att or yahoo account while on an att network it completely crashes Thunderbird instead of getting the edge too many requests.

I can reliably switch back and forth between a tt and spectrum networks with it crashing on att and getting too many requests on spectrum.

Yes I think we try that and also update our app registration with Yahoo to match. Having them mismatched doesn't seem to work

If you are a user of yahoo or a domain/mail provider that uses yahoo servers [1], you should complain to them about their ongoing problems. The more they hear from users the more likely they are to take action.

Workaround instructions for oauth login failing, based on the work of David, Ed and others ...

  1. Generate an app password - see https://help.yahoo.com/kb/SLN15241.html and save it (you can't retrieve it from yahoo)
  2. TB menu > Account Settings > Server Settings and set the following:
    if using imap - Incoming server: imap.mail.yahoo.com, port 993, Connection security: SSL/TLS, Authentication method: Normal password
    if using pop - Incoming server: pop.mail.yahoo.com, port 995, Connection security: SSL/TLS, Authentication method: Normal password
  3. On the left column, scroll down and click 'Outgoing Server' and edit the Yahoo entry:
    Outgoing server: smtp.mail.yahoo.com, port 465, Connection security: SSL/TLS, Authentication method: Normal password
  4. Go to TB menu > Settings > Privacy & Security > Passwords
    click the 'Saved Passwords' button and remove all Yahoo entries (some might show as oauth://xxxxx)
  5. Try logging in.
  • If your mail provider uses yahoo servers/services but not a yahoo domain [1], adjust the "server" setting in Thunderbird accordingly.

To go back to oauth:

[1] mail providers that uses yahoo servers/services but are not "yahoo.com" domain: myyahoo.com, AOL, @att.net, @bellsouth.net, @sbcglobal.net, @verizon.net, @frontier.com, @frontiernet.net, cox, rogers, @comcast.net/xfinity, @ameritech.net, @currently.com, @flash.net, @nvbell.net, @pacbell.net, @prodigy.net, @snet.net, @swbell.net, or @wans.net, and old domains @ymail.com and @rocketmail.com

SOLVED for me:

  • create app password and use normal password, not OAUTH2 I used 144.0.1
  • To clarify, I used the default TB configuration, changing only the authentication to 'normal password'

Seems yahoo may have fixed this recently as I was able to switch back to my old settings today

Duplicate of this bug: 1999015

We received word Yahoo has fixed this now.
Please let us know if you still see this.

I had made no settings changes but had disabled Yahoo server checks. I just re-enabled and logged back in via OAUTH. All appears to be well again.

I have made no changes but logging in is working again. Thanks all!

See Also: → 1999291

Nothing works for me still if using Thunderbird. I get all kinds of errors whether configuring the email account automatically or manually.

I can log in to my Yahoo mail account via Firefox (or any other browser for that matter), however.

Yeah this is fixed for me now as well

(In reply to Magnus Melin [:mkmelin] from comment #11)

Sounds very likely Yahoo quotas for Thunderbird are full. They would need to increase them.

Well, this is not the source of my problem. I have about 6 email messages in the Yahoo account that's not working with Thunderbird.
Still have no idea what the problem is with me.
Reading everyone's comments, neither password, app password, nor OAuth2 work now. But this problem only started several days ago for me, like others.

(In reply to Vartan from comment #29)

(In reply to Magnus Melin [:mkmelin] from comment #11)

Sounds very likely Yahoo quotas for Thunderbird are full. They would need to increase them.

Well, this is not the source of my problem. I have about 6 email messages in the Yahoo account that's not working with Thunderbird.
Still have no idea what the problem is with me.
Reading everyone's comments, neither password, app password, nor OAuth2 work now. But this problem only started several days ago for me, like others.

As things are working well for others, it might be best to post your issue on SUMO and pending outcome there, post a new bug here if necessary.

(In reply to Günter Gersdorf from comment #9)

Users in a german thunderbird forum says, that changing from oauth2 to password and using an app password solves the problem.
https://www.thunderbird-mail.de/forum/thread/97589-einrichten-von-yahoo-mail-konto-unm%C3%B6glich-etwas-ist-schiefgelaufen/?postID=563077#post563077
https://www.thunderbird-mail.de/forum/thread/97610-bei-der-einrichtung-kommt-edge-too-many-requests/?postID=563078#post563078

This also worked for me in 148.0. There were some error messages, but it all worked in the end.

With no new reports of oauth issues I think we can close this bug report.
I've also poked most of the SUMO reports to post a new question in support if someone have a problem.

Perhaps Bug 2019793 - add ability to use system browser for OAuth flow - might also help in some way.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
See Also: → 2019793

I imagine that this will come back when the large number of users on ESR get the updated code and all need to reauth their accounts...

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: