Cannot Download Emails with Attachments - Outlook Error Number 0x800ccc13

[shipwrite]

Beginning on Monday, June 25th, I cannot download emails with attachments to my Microsoft Outlook 2000 email client. I receive the MS Outlook error number 0x800ccc13. I have verified the detailed email settings in Outlook match those specified by AT&T. This problem just started on Monday. Previously, I have successfully downloaded all emails to my Outlook 2000 email client. No changes were made on my PC.

[shipwrite]

I should add that I am on AT&T Dial service, not DSL or U-verse. 

[shipwrite]

To try and resolve the problem, I delete my email account details from my Microsoft Outlook 2000 email client software and reentered the detailed email account details specified by AT&T. Afterwards, I attempt to receive an email which contains an attachment - I still cannot download an email with an attachment.  Now, however, the error message is 0-x800ccc0f.

[ATTAlexCM]

---

shipwrite wrote:

To try and resolve the problem, I delete my email account details from my Microsoft Outlook 2000 email client software and reentered the detailed email account details specified by AT&T. Afterwards, I attempt to receive an email which contains an attachment - I still cannot download an email with an attachment.  Now, however, the error message is 0-x800ccc0f.

---

Welcome shipwrite and thank you posting an update.  You may want to try deleting your Outlook profile according to this solution and try creating a new one.

Additional resources...

Setting up an email client for AT&T email

Verify settings in an email client for AT&T email

As an alternative, you can use the AT&T Web Mail site to view the attachments.

Regards,

Alex

[shipwrite]

ATTAlexCM, I already deleted my Outlook profile and created a new one according to Microsoft's instructions. Further, I already read the two AT&T documents, Setting up an email client for AT&T email and Verify settings in an email client for AT&T email. Everything was done in Microsoft Outlook 2000 exactly as specified and recommended in these three documents. As a further test, I restored a full image backup I made back on May 27, 2012. On May 27th, before I made the image backup, I successfully downloaded a 5MB email memo. After restoring the May 27th image this past week, I resent the 5MB email to my AT&T account and found I could no longer download it. I receive the same Outlook error message, 0x800ccc0f. Since my image backup restores my computer to its EXACT state on May 27th, I conclude that the problem must reside on the AT&T/Yahoo server side. Further, I note that changes HAVE been made by AT&T/Yahoo since May 27th. Specifically, I read that for any AT&T email account created after June 11, 2012, a user will not be able to use an email client to access email. Only web access is allowed for AT&T email accounts created after June 11, 2012. All-in-all, I am VERY disappointed in AT&T's poor service and responsiveness is addressing this problem. Working in the IT industry myself, I fully realize that AT&T cannot support the various email clients. However, AT&T/Yahoo should acknowledge and communicate that they are revising and consolidating their mail servers and instituting new policies that may disrupt service. In reading the postings in this community forum, I see that many other users are also experiencing problems with receiving email via their email client software. This reflects very poorly on AT&T.

[territty]

Similar problem.  I can only send but not receive emails via the server to Windows Live Mail.  This started on 6/22/12.  Called ATT tech support and was told I could pay for their service.  No way.  Looks like a scam to me, especially when I was told it was a Microsoft problem but I could pay ATT to solve it for me.

[territty]

Thank you for your post.

I was trying to figure out what the problem was and why I could no longer receive emails to my Windows Live Mail. 

Tech support wanted me to sign up for their service.  Now it is obvious.  Your post was very informative. 

Looks like even paying for the service still would not solve the problem.