Back in the days when Verizon did it's own thing, everything was
verizon.net.
<name>@
verizon.net pop.verizon.net smtp.verizon.net
Then they decided to push everything to AOL. It was simple and you retained your email and Thunderbird never knew the change. All the
settings were stil
pop.verizon.net and
smtp.verizon.net. I guess they just redirected all dns servers to the right place.
In 2019 I dropped Verizon. Personal decision and now use gmail or yahoo.
Still the emails at Verizon still work. Poor in house maintenance huh! And webmail still works, aol's web interface. But I'm still
<name>@
verizon.net when I log into AOL.
But for IMAP on thunderbird it's screwed up. When you type in your email, the wizard tries to query "
verizon.net" and get the suggested
settings. And they want pop3.
Google info tells you to manually config and say IMAP, it will not show Oauth2 on incoming server though and it wants
imap.verizon.net. I
changed that to
imap.aol.com and with a re-test now the Oauth2 shows up in the authentication drill down. But still no Oauth2 for smtp.
And smtp is still
verizon.net.
As a stab in the dark I found I had to edit (post setup) the smtp to read
smtp.aol.com (as you indicate) and then and only then I finally
got the Oauth2 available for smtp. And on the first send, I got the familiar popup from AOL to allow TB the Oauth2 login and to get the
new password for smtp.
So now it all works. I'm still <name>@
verizon.net but it's all going through
aol.com. And that's the part the eluded me. It finally
dawned on me that I had to point everything to *.aol.* stuff. I guess if I were still a Verizon customer I might have received an email?
Maybe?
Confusing huh?!!!
Al