Outlook 2016 with Verizon mail setting throws an error

[viafax999]

If I set the Verizon email settings for inbound mail server to the values defined by Verizon - port 995 and SSL checked- in the outlook account more settings advanced field I receive an error message when Outlook starts saying

Internet security error

The server you are connected to is using a security certificate that cannot be verified

The target principal name is incorrect

The only way I can stop this error appearing is by changing the inbound port to 110 and turning off SSL.  Unfortunatley I obviously can't do that when I am not connected to the Verizon network.

Strangely my gmail account uses the same settings, apart from the fact that it connects to the gmail pop server, and it works fine.  That makes me believe there is something wrong with the way the Verizon pop server mail.verizon.com is working.

I have this issue on all the machines that I upgraded to outlook 2016

.

Has anybody else been getting this error?  Does anybody how to fix it as it very annoying getting this popup all the time

[smith6612]

Could you post a copy of the certificate?

I believe Verizon recently made a change to their SMTP/POP servers, which moved them from a Verizon hosted solution, to AOL's infrastructure.

[viafax999]

Here it is.  it's the Avast web/mail shield root one - I use Avast for AV

Works fine with Gmail, just not the pop client in outlook.  I'd switch to the imap client but for some reason, maybe the same one, I don't seem to be able to get anything delivered to me.

[tns2]

??????????????????

As shown it certainly is incorrect.  Verizon email servers should not be showing an AVAST certificate and a principal of Hostingplatform.com .and do not currently support IMAP.   Unless I am not understanding what you are doing this is not the certificate we need to see.

REMEMBER YOU ARE TALKING TO PEERS HERE NOT VERIZON.

Can you make it clearer what settings you are using and what you are trying to do.

What others are mentioning is that verizon servers pop.verizon.net and smtp.verizon.net are now changed to actually be AOL server names (may still be the same servers that have been renamed or may really be Different ones,  With a name change the certificates may not match and be causing errors.  I.e certificated named verizon.net but server named aol.com

[_dot]

viafax999,

   you don't have the servers set for that do you? (mail.verizon.com )

prob just a typo in your rush to ask the question...they ought to be pop.verizon.net and smtp.verizon.net and /or pop.aol.com and smtp.aol.com

 w 587 and 995 the ports,

" That makes me believe there is something wrong with the way the Verizon pop server mail.verizon.com is working."

[viafax999 · Accepted solution]

Sorry, I worked out what the issue was.

The error was actually been thrown by my email provider's system - Network Solutions.  Unthinking, I had set the inbound mail server parameters to same as Verizon, Gmail etc 995 and SSL  Apparently Netsol are a bit behind the times and on a pop3 connection don't support that - they are port 110 and NO ssl.  Think I probably confused myself as I have always used smtp.verizon.net as my outbound server.  Now got rid of all the verizon references and set the netsol connection up as an imap connection which has the added benefit of getting rid of the peculiar Verizon email rejects of attempting to send spam when forwarding received emails.  However, unfortunately I don't appear to be able to receive mail via that imap connection so have reverted it to a pop3 connection using port 110 until I can get the solution to the imap issue from them

The Avast certificate is the client end certificate and works exactly the way it's meant to as it is scanning inbound email.