Will not accept my password
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: james.m.meyer, Unassigned)
Details
(Whiteboard: [support])
Attachments
(1 file)
|
57.07 KB,
image/png
|
Details |
Steps to reproduce:
I was using Thunderbird to receive incoming mail and, without warning, Thunderbird started asking me to enter my password for IMAP.aol.com. I did not change the password. My phone and my laptop still have access to the email account.
I was prompted to Retry or Enter New Password or Cancel. None of these options allowed me to receive or send mail.
I shut down Thunderbird and restarted it, but the problem continued.
At the upper left-hand corner, the dot that goes back and forth never stops.
I am running release 91.5.1 "You are currently on the release update channel."
Actual results:
Nothing that I knew I did.
Expected results:
I should have been able to continue to use Thunderbird.
I am a long time Thunderbird user and never had a problem until now.
Comment 1•4 years ago
|
||
I think AOL may not be allowing password login anymore? Change the authentication method to OAuth2 and it should work.
Comment 2•4 years ago
|
||
For support, please refer to https://support.mozilla.org/products/thunderbird
I changed to the recommended authentication setting,OAuth2, and Thunderbird went out to the server and brought in the latest mail. However, when I tried to reply to an email the same message appeared. It did not accept either Reply or Enter New Password. I can access my email through Firefox at aol.com.
Of course, I like to use Thunderbird-unique features like tagging email messages.
Comment 4•4 years ago
|
||
You have to change the Outgoing server (SMTP) setting to use OAuth2 as well.
That seems to behave done the trick. I was using smtp.verizon.net and not smtp.aol.com. Once I made both the imap, smtp and the OAuth2 changes, things went back to the way I was used to. I was scared that I would have to use a different email client.
Thanks for your help.
Comment 6•4 years ago
|
||
(In reply to Jim Meyer from comment #5)
That seems to behave done the trick. I was using smtp.verizon.net and not smtp.aol.com. Once I made both the imap, smtp and the OAuth2 changes, things went back to the way I was used to. I was scared that I would have to use a different email client.
Thanks for your help.
I thought we were supposed to use smtp.verzion.net, and I also couldn't send email, so I set Verizon IMAP account to use my default accounts server.
WFM, but I'll try smtp.aol.com.
That worked!
Description
•