Just change the authentication on the incoming and outgoing servers to OAuth2, remove the passwords in Options/Security/Passwords/Saved Passwords, check that cookies are allowed in TB Options/Privacy, restart TB, and enter the regular account password in the OAuth browser window when prompted. An oauth token will be stored for each account in Saved Passwords.

Thanks, this worked for the AOL accounts. I also have 1 Comcast email account in TBird, should I also use OAuth2 for that one?

I don't think Comcast supports OAuth2 for email, and even if it does, it's not supported for Comcast in TB.

AOL has been sending this message out since last year with the same threat when they closed their previous web mail system. At that time I already reset both the auth to OAuth2 and reset the password. I'm guessing they are sending this out to all imap users regardless of their settings. -Pv-

This appeared to work at first but now I can receive mail but I cannot send mail. I did enable cookies in TB and restarted TB; alas, No joy.

What else needs to be done?

I've followed the 'chosen solution' suggested above, but every time I click 'next' after entering my AOL email in the 0auth browser, i get the following error message: ' Please reload the page and try again or use another browser'. I don't understand why my login doesn't work in the 0auth browser but I can log in without a problem using firefox.

I've followed the 'chosen solution' suggested above, but every time I click 'next' after entering my AOL email in the 0auth browser, i get the following error message: ' Please reload the page and try again or use another browser'. I don't understand why my login doesn't work in the 0auth browser but I can log in without a problem using firefox.

Check that cookies are allowed in TB Options/Privacy. This is usually why the OAuth authentication fails after Next. Cookies in your browser, Firefox or Chrome etc., are not the issue - they must be allowed in TB.

This appeared to work at first but now I can receive mail but I cannot send mail. I did enable cookies in TB and restarted TB; alas, No joy. What else needs to be done?

Did you change to OAuth2 in both the incoming and outgoing servers, and remove the incoming and outgoing passwords?

I have also tried the Chosen Solution, and was initially confused by the result. I got a popup sign-in window from AOL, rather than TB, so thought something had gone wrong. Went through various combinations of settings, looking for a TB popup. Nope. Finally ran through the AOL login (it also wants you to verify alternative e-mail or phone), and that appears to have resolved the issue. Comparable to getting transported to PayPal when paying for an online purchase.

Curiosity question: What happens if we follow AOL's directions to remove an account and re-add it - will existing mail be lost? Or will new account with same name find it? Same question if TB is removed and reinstalled?

Thanks

I have also tried the Chosen Solution, and was initially confused by the result. I got a popup sign-in window from AOL, rather than TB, so thought something had gone wrong. Went through various combinations of settings, looking for a TB popup. Nope. Finally ran through the AOL login (it also wants you to verify alternative e-mail or phone), and that appears to have resolved the issue. Comparable to getting transported to PayPal when paying for an online purchase. Curiosity question: What happens if we follow AOL's directions to remove an account and re-add it - will existing mail be lost? Or will new account with same name find it? Same question if TB is removed and reinstalled? Thanks

If it's an IMAP account, the existing mail on the server will be re-downloaded. If it's POP, TB will create a new subfolder of Mail in the profile folder with a name like pop.aol-1.com to store subsequent mail, but the old subfolder, pop.aol.com, will still be in the profile, and its mail can be viewed if the Inbox mbox is copied to Mail/Local Folders. So, it's better with POP to just change the authentication, not remove and re-add the account.

anthonyfreeman67 said

I've followed the 'chosen solution' suggested above, but every time I click 'next' after entering my AOL email in the 0auth browser, i get the following error message: ' Please reload the page and try again or use another browser'. I don't understand why my login doesn't work in the 0auth browser but I can log in without a problem using firefox.

Check that cookies are allowed in TB Options/Privacy. This is usually why the OAuth authentication fails after Next. Cookies in your browser, Firefox or Chrome etc., are not the issue - they must be allowed in TB.

Thanks for the suggestion re cookies. On further delving, I realised that my problem was due to initially only allowing cookies for http://AOL.COM when I should have been more precise and allowed them for https://login.aol.com instead. Updating cookie exceptions to include https://login.aol.com resolved my problem. Thanks again.

tamalgr said

This appeared to work at first but now I can receive mail but I cannot send mail. I did enable cookies in TB and restarted TB; alas, No joy. What else needs to be done?

Did you change to OAuth2 in both the incoming and outgoing servers, and remove the incoming and outgoing passwords?

I did change both incoming and outgoing servers to Oauth2. I found only one reference to an AOL password in my saved passwords and I deleted that. The next time I tried to send mail I got an email login for yahoo followed by an email login for AOL. The yahoo request puzzled me because I did not have a yahoo account. I created a yahoo account just so the next time I tried to send mail I would not get the dialog for yahoo. I logged into AOL and AOL dutifully provided token for my password in TB.

I do not understand your question re passwords for both incoming and outgoing servers.

Yahoo owns AOL, so that is probably why you received a notice from Yahoo even though the authentication was done with AOL.

Some users have stored passwords for one or both the incoming and outgoing servers. With OAuth2 there is only a single oauth:// entry.

What I now have is an entry in my saved passwords for oauth://login.aol.com (mail-w). I do not have an entry for an smtp password. I assumed that this login would take care for all transactions with AOL. This is obviously not the case.

I finally gave up assuming I had fouled up something. I removed my account and reinstalled it. This worked for me. In my saved passwords I now have the oauth token for AOL AND the passwords for the imap and smtp servers.

I did a manual set up of the account since TB insisted on picking a yahoo account instead of an AOL account.

My problem is now solved. Thanks for your patience.

I'm not that bright but, FWIW, just wanted to share my AOL/TB experience of this morning....

Before I read this thread I deleted all of my AOL accounts from TB. I tried to re-add them but ran into issues previously mentioned. I found the *key* to fixing the bugger was allowing cookies in TB.

A few issues, not discussed in this thread, still persisted but I finally (and rather easily) worked them out ... and all six of my AOL addresses are now up and running.

• Shout out to sfhowes for explaining the cookie thing.