POP3 settings changed because of SSL3/Poodle? Are we supposed to use NTLM?
Harlan2
Enthusiast - Level 2
I have always logged in to netmail.verizon.net for webmail access. Suddenly that page links to the password page of my.verizon.net, which doesn't work. My home email client Thunderbird, which has also worked for years, suddenly cannot log into the POP/SMTP service. Phone support spent 45 minutes finding out that the problem *might* be related to the SSL3 vulnerability called "Poodle". Dear Verizon: If you're going to change security settings, you have to WARN PEOPLE first, and you have to INSTRUCT people in what the new settings should be.
0 Likes
Re: POP3 settings changed because of SSL3/Poodle? Are we supposed to use NTLM?
tns2
Community Leader
Community Leader

They haven't changed the settings recently.  Well over a year ago, may even be two years now.

Not sure what may have happened with the webmail, I rarely use it and it is working fine for me today.

For clients like Thunderbird make sure you are using pop.verizon.net and smtp.verizon.net as listed in

http://verizon.com/emailsettings 

If they have decided to disable ssl3 because of the poodle attack, TLS should still work on almost all clients.  It does work fine on Thunderbird. 

For the warnings about poodle see various reports such as

https://www.us-cert.gov/ncas/alerts/TA14-290A

0 Likes