Cannot receive emails from verizon.net because of error

[chrisprrnysw]

Task 'incomming.verizon.net - Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted.  If this problem continues, contact your server administrator or Internet service provider (ISP).  The server responded: -ERR Cannot establish SSL with POP server 206.46.232.10:995, SSL_connect error 1:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure'

Any suggestions as how to proceed to solve this problem?

[somegirl]

---

@chrisprrnysw wrote:

Task 'incomming.verizon.net - Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted.  If this problem continues, contact your server administrator or Internet service provider (ISP).  The server responded: -ERR Cannot establish SSL with POP server 206.46.232.10:995, SSL_connect error 1:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure'

Any suggestions as how to proceed to solve this problem?

---

My first suggestion would be to update your settings to the new servers. The incoming.verizon.net and outgoing.verizon.net servers are being phased out by Verizon.

For the sake of example, we are going to pretend that we are setting up fictional account "fakeacct@verizon.net" and the password for logging into that account in webmail is "fakepassword" - Again, this is a fictitious account for the sake of an example.

The settings for using Verizon's servers would be:
Incoming Server: pop.verizon.net
Server Requires Authentication: Yes
Username: fakeacct
Password: fakepassword
Requires a Secure Connection (SSL): Yes
Port: 995


Outgoing Server: smtp.verizon.net
Server Requires Authentication: Yes (You can set it to use the same settings as incoming, or manually enter the username and password.)
Requires a Secure Connection (SSL): Yes
Port: 465

If you are given the option anywhere for Secure Password Authentication (SPA), set it to No or Normal

If all of that is set up and it's still not working, your best bet is to provide a screenshot of your settings (with personal information blocked/removed) and any errors you are getting.

[tns2]

Could also be that you, or your app, are not using TLS.  There have been reports that lots of sites, including Verizon, are shutting off sslv3 and requiring TLS instead.  Most code where you specify SSL actually mean SSL or TLS.  There warning about SSL V3 from the US Goverment and the general work around was to no longer use it.

See https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566

IF you read some details the problem was even in TLS which could be forced to drop back to SSLv3.  SSL V3 (and earlier versions) have all been known to be vulnerable for awhile.