Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
First we have changed nothing, we have not done anything to our Yahoo or Outlook 2003 and suddenly this starts popping up all the time.
We have Windows 7, Office Pro. 2003 and use Outlook 2003 with Verizon Fios and Yahoo is our email server. This message started popping up yesterday out no where, does anyone have any thoughts about it? I have posted it on the Verizon site, however I have more faith in the help I receive here thank you.
The server you are connected to is using a security certificate that CAN NOT BE VERIFIED.
A certificate chain processed but terminated in a root certificate which is not trusted by the trust provider.
Do you want to continue using this server?
Solved! Go to Correct Answer
The 995 and 465 are the numbers I had been using at least a year now, Verizon sent them or posted them for Verizon Subscribers.
Yet I was getting the error message over and over the last few days before I called Verizon.
" security certificate that CAN NOT BE VERIFIED."
The Verizon Tech changed those numbers and some other settings and I HAVE NOT HAD A SINGLE ERROR SINCE HE DID.
I tried the old numbers and immediately the errors stated up again. I quickly went back to the new numbers he entered and again NO ERRORS AND NO PROBLEMS.
Yahoo is our email server, could this be a reason that those numbers don't work any longer, has Yahoo changed something that required Verizon to issue the new port numbers?
Did you get any email notification of a change to your email servers? So far I only found these settings from 2010
Incoming Server: incoming.yahoo.verizon.net
Server Requires Authentication: Yes
Username: fakeacct
Password: fakepassword
Requires a Secure Connection (SSL): No
Port: 110
Outgoing Server: outgoing.yahoo.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): No
Port: 25
(Big thanks to SomeGirl for this info)
Are these the settings configured in outlook? If these are the setting they may need to be updated
I am also having this exact issue as of a few days ago. I have been saying NO (in case it's some sort of man-in-the-middle exploit or something), closing Outlook, then re-opening Outlook. Eventually it works. But then the same problem happens again later when sending another message...
These are the current settings, per this Verizon web page.
Mail server settings
(FYI I got this page in a Bing search for "verizon pop3 email server settings.")
The 995 and 465 are the numbers I had been using at least a year now, Verizon sent them or posted them for Verizon Subscribers.
Yet I was getting the error message over and over the last few days before I called Verizon.
" security certificate that CAN NOT BE VERIFIED."
The Verizon Tech changed those numbers and some other settings and I HAVE NOT HAD A SINGLE ERROR SINCE HE DID.
I tried the old numbers and immediately the errors stated up again. I quickly went back to the new numbers he entered and again NO ERRORS AND NO PROBLEMS.
Yahoo is our email server, could this be a reason that those numbers don't work any longer, has Yahoo changed something that required Verizon to issue the new port numbers?
Can you elaborate on "the Verizon Tech changed those numbers and some other settings"? What exactly did they change, and what are your current settings?
The "pop.verizon.net" and "smtp.verizon.net" settings listed in the post above are for NON-"Verizon Yahoo" e-mail accounts. Those settings do not apply to Verizon users with Yahoo-based e-mail. And the NON-SSL settings listed in a post above are not acceptable - we should be using SSL.
It appears that the certificate itself is invalid. The "Key Usage" field with the value "Digital Signature, Key Encipherment (a0)" appears to be the issue.
Incoming Server Port Numbers: 110
Out going server Port number 587
We also were using the 995 and 465 for at least a year and it was set up that way then by a TECH.
The new numbers worked immediately and ever since.
@Friendly wrote:Incoming Server Port Numbers: 110
Out going server Port number 587
We also were using the 995 and 465 for at least a year and it was set up that way then by a TECH.
The new numbers worked immediately and ever since.
Your new numbers are the old NON-SSL numbers. THEY WILL EVENTUALLY STOP WORKING.
What do you suggest then if this is not a fix? Apparently a number of us are having the same problem with our Verizon email accounts. If this is not a fix what is then, what would you suggest?
Friendly wrote:
Incoming Server Port Numbers: 110
Out going server Port number 587
We also were using the 995 and 465 for at least a year and it was set up that way then by a TECH.
The new numbers worked immediately and ever since.
Your new numbers are the old NON-SSL numbers. THEY WILL EVENTUALLY STOP WORKING.
@tns_2 wrote:
@Friendly wrote:Incoming Server Port Numbers: 110
Out going server Port number 587
We also were using the 995 and 465 for at least a year and it was set up that way then by a TECH.
The new numbers worked immediately and ever since.
Your new numbers are the old NON-SSL numbers. THEY WILL EVENTUALLY STOP WORKING.
The current correct settings are provided on this link. TNS_2 is correct.