The server you are connected to is using a security certificate that CAN NOT BE VERIFIED.

[Friendly]

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?

[EmilyGPS]

I am having the same issue with the certificate error - this started about a week ago if not a bit longer -  and I am one of those using the Yahoo portal.  It sounds like there is nothing we "users" can do; this has to be fixed by Yahoo or Verizon folks.  Is that where this discussions stands?

[Friendly]

Are you installing the Outlook 2007 updates? We get them all the time and yet we have Outlook 2003 I wonder if they are not part of the problem.

The issues began about the time of the updates from MS.

[Beelzy]

I finally took some time to look at the certificate chain here, and found the problem/solution.  The fundamental problem is a missing intermediate CA.  We all have the root CA, but we're missing the intermediate.  I realized that I had the intermediate CA in Firefox, and exported it, then imported it for IE/Outlook to use.  This resolved the issue since it completes the CA chain.  I do not know how most users are supposed to find and import this intermediate CA since it does not automatically come from Microsoft.  See below for the complete certificate chain:

ROOT (we all probably have this root CA)

Subject:
CN = Baltimore CyberTrust Root
OU = CyberTrust
O = Baltimore
C = IE
Issuer:
CN = Baltimore CyberTrust Root
OU = CyberTrust
O = Baltimore
C = IE

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

INTERMEDIATE (most users are probably missing this intermediate CA)

Subject:
CN = Cybertrust Public SureServer SV CA
O = Cybertrust Inc
Issuer:
CN = Baltimore CyberTrust Root
OU = CyberTrust
O = Baltimore
C = IE

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

LEAF (so Outlook is seeing this certificate and can't find the issuer intermediate CA)

Subject:

CN = outgoing.yahoo.verizon.net
OU = Messaging
O = Verizon Data Services LLC
L = Grapevine
S = Texas
C = US

Issuer:

CN = Cybertrust Public SureServer SV CA
O = Cybertrust Inc

[Friendly]

Is this something we can fix ourselves? That must sound stupid, I just don't know enough and had to ask.

[Beelzy]

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...

[zeroday1]

Customer's Beware!    

Verizon email server's are riddled with bad certificate warnings within multiple browsers...

Verizon's {please keep your posts courteous} support staff would rather 'save face' than admit there is a problem with the site...

Verizon telling customer's that its a problem with their pc's when clearly each browser warning I've gotten specifically states that it is a problem with the site using bad ssl certificate, invalid, etc...

These warnings have popped up within the latests versions of Firefox, Internet Explorer, and Comodo Dragon...

Verizon won't even acknowledge their is a problem unless your complaint hits the spotlight...

If enough formal complaints are made, that just might prompt Verizon to actually get up off that "warrior-arm-chair" of theirs' and crack the whip on their own technicians to be more on top of these major security issues, rather than simply assigning blame to end-users because they're too big for their own good, too busy to address concerns about how their servers incorrectly interact with the most popular and most trusted browsers on the net...

Stop pretending there is not an issue with the website...Intead just figure out the problem and please just fix it already!!!   

ATTN:  Customers 

In most instances, this will not be a problem with your computers or that they have a bad certificate...rather it is a problem with Verizon's website and how they obtain and update their certificates, of which we have yet to see them fix...   

[Friendly]

Zeroday1,

Nicely stated, like a many of us we just don't visit or count on one forum. The Verizon Certificate is being brought up and discussed all over the WWW.

It is no secret now, what has been shared here and the fact THERE HAVE BEEN NO RESULTS OR RESOLUTION from Verizon is spreading as fast as the WWW can tell a story. 

This is going to impact Verizon in ways they would not want to go, their complete lack of help, answers, resolution is alien to all their Customer Service Commercials on all the national medias.

It is no secret, THE WORD IS OUT ON MANY FORUMS, the only way they can fix their bad public image and poor public service is to fix the Certificate and soon.

"The Certificate is being read as a Fraudulent Certificate in its' properties. There is no way a client or paying customer can correct this themselves."

[Friendly]

I just was sent this link, several people found it and forwarded to us. People were complaining to Verizon already in 2011 about the Security Certificate, and have been complaining for at least 2 years.

http://forums.verizon.com/t5/Verizon-net-Email/Security-Certificate-Errors/td-p/312677

[tns2]

---

@Friendly wrote:

I just was sent this link, several people found it and forwarded to us. People were complaining to Verizon already in 2011 about the Security Certificate, and have been complaining for at least 2 years.

http://forums.verizon.com/t5/Verizon-net-Email/Security-Certificate-Errors/td-p/312677

---

If Beelzy's posts are right, then the error is on your Computer.  The Verizon certificate is valid, and its your computer that is missing the necessary certificates  (intermediate/root) to verify the Certificate.  Note I am not having the problem using windows live mail and Thunderbird. 

As noted for some other non-verizon posts getting similar errors at least one of the root/intermediate Certificates for Cybertrust expired in August.  New ones were issued quite awhile ago but perhaps Outlook 2003 is not updating, and XP users need to update there's to at least this years Microsoft Root certificate package.

[kaytabor30]

just like all the other problems verizon has they blame someone else

GO VERIZON

[Friendly]

Since we can not receive or send email without clicking OK on the error message to go around the Untrusted Fraudulent Security Certificate does it do any good, do we EVEN have any kind of security?

We might as well go back to the Verizon Techs setting for NO SSL at least we did not get an error every email.

Can someone give us an answer please?

[tns2]

If you accept the certificate then ssl is used, so it is secured.

There has been an argument over multiple vendors, not just Verizon, having this problem.  Some say its up to the Certificate user (in this case Verizon) to supply their certificate and intermediates up to but not including the root.  Others argue that that is optional. I don't know which is correct.

You can get around the problem by installing the missing intermediates on your machine.  Back when I was doing this kind of thing for my company we always had to install all the certificates by hand on the servers(and track all expiration dates to make sure they stayed current), and I guess the customers were given which ever ones they needed.

[Friendly]

I was searching for a discussion on Outlook and when I did I found there are sooooooo many discussions about problems with OUTLOOK AND THE VERIZON connections on this forum.

There has to be more to this then what someone thinks.

A dozen times I have read someone is told to change to incoming.verizon.net. HOWEVER no one has been able to explain to me when I do this there is NO way it goes to my Yahoo server THAT VERIZON set up years ago when we went with Verizon.

Everyone was given a choice of several servers with out Yahoo in our incoming and outgoing there is NO way our emails can reach us.

http://forums.verizon.com/t5/forums/searchpage/tab/message?filter=labels%2Clocation&location=forum-b...

[Friendly]

EVERYONE SIT DOWN AND HOLD ON TO YOUR CHAIRS.

I GOT IT RIGHT, THE OLD PA DUTCHMAN GOT IT RIGHT, IT FINALLY CAME TOGETHER NOW I AM GOING TO WORK ON MY ENGLISHER.

I followed your suggestions, went to the www.verizon.net web page,

followed the ACCOUNT > Account Profile > Residential > Jump to "Online Experience" route and was able

to finally change my "Online Experience" from Verizon Yahoo!  to just plain Verizon.  

  Changed my home page to http://myverizon.com in Safari Preferences, then clicked OK on the confirmation page.

 Updated my e-mail server settings as follows as shown on:       http://www22.verizon.com/Support/Residential/Internet/fiosinternet/email/setup+and+use/questionsone/... 

Information repeated here as an example for the fictional account:   nomoreyahoo@verizon.net   (password = Example1)

Mail server settings

• Incoming mail server (POP3😞 incoming.verizon.net
• IncomingServerPort Numbers: 995
• Outgoing mail server (SMTP😞 outgoing.verizon.net
• Outgoing ServerPort Numbers: 465  Why is this important?
• Your Verizon Online user name -->  nomoreyahoo
• Your Verizon Online password   -->  Example1
• Make sure "This server requires a secure connection (SSL)" is checked.

In Apple Mail, use the above information as follows -- In Mail version 5.2 for Mac OSX 10.7.x:

• Mail > Preferences  
• Accounts tab > Account Information tab
•   Description (tailor to your needs):  Verizon: Nomoreyahoo
•   Email Address:  nomoreyahoo@verizon.net
•   Full Name:  Ima Happycampernow
•   Incoming Mail Server:  incoming.verizon.net
•   User Name:  nomoreyahoo
•   Passsword:   Example1
•   TLS Certificate:  None
• Accounts tab > Advanced tab
•   Port:  995  [ checked ] Use SSL
•   Authentication:  Password
• Accounts tab > Account Information tab > Outgoing Mail Server (SMTP):  Edit SMTP Server List ... (select from pull-down)
• Account Information tab:
•   Description:     Verizon (just verizon)
•   Server Name:  outgoing.verizon.net
• Advanced tab:
•   Use custom port:  465    [checked]  Use Secure Socket Layer (SSL)
•   Authentication:  Password
•   User Name: nomoreyahoo
•   Password:  Example1
• CLICK "OK"
• Close Mail Preferences

Update:  verified that the settings above work from both my iPad and my iPhone for both incoming and outgoing messages.

[Friendly]

You know if someone could help me to fix this maybe now that I finished my 45 Radiation Treatments for my Prostate Cancer someone could come up with a fix for my newest Therapy.

For 24 MONTHS I HAVE TO HAVE A MONTHLY HORMONE TREATMENT. The Oncologist said I may have some side effects.

At my first check up he asked me if anything had changed.

I SAID I NOW HAVE SUCH A STRONG IMPULSE TO RUN OUT AND HAVE MY NAILS DONE AND GET A PERM for several days after the Hormone Treatment.

He said it should past in time.

[Verizon_Support]

Hi Friendly, as this appears to be resolved we have closed your Private Support Case. If you have any other questions or concerns with your account or services please feel free to make a new post and we will be happy to help.

-Adam_VZ

[Friendly]

Adam,

I got that issue figured out however almost immediately I know get error number 0x800ccc7d.

This entry is my own from another post, I have to leave so I am posting this not to be difficult only because I have to get going.

A great number of folks seem to be having this problem now that they dropped their servers and have signed onto Verizon as instructed.

"I had a Verizon tech set my ports etc however like others we keep getting Error 0X800CCC7D. I called Verizon Support and they doubled checked my settings, that they set up, and we still Error 0X800CCC7D after 5 or 6 emails.

I went to Microsoft's Forums and they pretty much say the same thing about Error 0X800CCC7D and that the only thing left that can be wrong is the ISP has some thing wrong, there are NO more options for the clients to do.

Verizon told us they are doing away with the Yahoo accounts and connections and now have their own email program that I have accessed. However before this we did not get Error 0X800CCC7D."

[dwgriffi2]

Hi Friendly, as this appears to be resolved we have closed your Private Support Case. If you have any other questions or concerns with your account or services please feel free to make a new post and we will be happy to help.

-Adam_VZ

Whoa, Adam, way too fast on the closing out trigger.  It's not resolved.   Solution is two steps forward and three back.  Error city.   

[LawrenceC]

Hi Friendly,

Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you. Please go to your profile page for the forum and look at the top of the middle column where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.

Under "My Support Cases" you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis, as the agent may be waiting for information from you before they can proceed with any actions. Please keep all correspondence regarding your issue in the private support portal.

[Friendly]

Lawrence,

Last night I was trying to work with the Techs you sent me to. Time and time again we would communicating then when I tried to go back I kept getting the screen to Open an Account for this Forum.

Finally I gave up, maybe you can let them know. One did not realized or know that for years we had been set up for Yahoo server by Verizon.

Our incoming account is and was set up by Verizon as incoming.yahoo.verizon.net. This tech insisted it had to be incoming.verizon.net and the same with outgoing.verizon.net.

Finally I was able to show him THE ACCOUNTS HAVE TO HAVE

INCOMING.YAHOO.VERIZON.NET ETC to work and OUTGOING.YAHOO.VERIZON.NET

If the tech did not know this simple thing with the accounts I have my concerns about how much they could help with the Security Certificates not be recognized problem.

If you can put me in touch with a tech I will try again. Last night it was frustrating I would try to send in the answers to their questions and instead I was sent to the setting up an account for this forum page.

[LawrenceC]

---

@Friendly wrote:

If you can put me in touch with a tech I will try again. Last night it was frustrating I would try to send in the answers to their questions and instead I was sent to the setting up an account for this forum page.

---

Are you able to access your support case today?