Getting Send/Receive Error (0x800CCC0F) in Outlook all of a sudden

[Nells250]

Hello all, did a search and didn't find the error below listed here, sooooooo:

Yesterday afternoon I suddenly started to get this error when using Outlook to get my Verizon emails.  Oddly enough, this was just after the Stock Market came back online!  🙂

This is the error I am getting:

... Receiving' reported error (0x800CCC0F) : 'The connection to the server was interrupted.  If this problem continues, contact your server administrator or Internet service provider (ISP).'

Problem comes and goes, and effects different addresses at different times.  I didn't change any settings and everything worked just fine in the morning.  Wondering if it is just something happening with the Verizon servers?

[eljefe2]

I'm getting the same error ID and a similar message using Windows Live Mail:

Unable to send or receive messages for the 04Verizon (xxxxx) account. Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity.

Server: 'pop.verizon.net'
Windows Live Mail Error ID: 0x800CCC0F
Protocol: POP3
Port: 995
Secure(SSL): Yes

It's intermittent.  Sometimes the connection is normal.  Other times it isn't.   Same thing with different type devices and different ISP's.

I hope Verizon is aware of this issue and working on fixing it.

[scr100]

I'm also getting the same error ID and a similar message using Windows Live Mail at about 5:15 PM Pacific on 7-15-2015.

[nancyh1]

I am getting the same message for the past 48 hours.  How do I fix this?

[TomH121]

Hi nancyh:

Please read Rob C reply on July 7,2012 which is at this link

http://answers.microsoft.com/en-us/windows/forum/windows_vista-networking/windows-mail-error-code-0x...

[Nells250]

UPDATE:  as of this second, same problem, and intermittent as well.  Have required settings changed on us once again, or just still a server issue?

[eljefe2]

Update here:   I haven't seen the error message in 24 hours or so.  Maybe (fingers crossed) the problem has been fixed.

[Nells250]

Same here.  Must have been an issue with the server? 

[eljefe2]

Yep.  That's my assumption.