email error windows live mail/server error 0x800CCC90

xgdude · 16 Feb 2013

Response to post 70: reference to post 60. (Item 1)
I checked the servers tab and made the change from log on using account name to log on using same settings as my incomig mail server.
This change did not affect the send/receive problem. Tested by test email sent from web mail.
(Item 2) Email protectionm is disabled in Avast Pro.
(Item 3) created a new account in live mail using manual configuration.
tested by sending email from web mail; receive still blocked at livr mail
Leave a copy on server is checked.
Alternative port 587 tried and had no effect, Port 465 restored.
Response to Davidw7ncus re posts 6,8 & 11
I double checked all my settings in the link "setting up an email client for ATT email"
ATT Email Updater finished with "all youremail accounts already comply with ATT settigs"
I am not interested in a work around like email forwarding; I could easily change to another client. Also, I use Avast Pro for anti virus and my Windows Essentials Live Mail version is
16.7.3305.912

Regarding the blocked off note regarding getting a free ATT.net email address after June 11, 2011
I do recall getting a email address from AT&T when I began to grow tired of Live mail failing and that would have to have been after June 11, 2011. I ran some tests by sending from my regular att account at live mail to the new att.net account signed in on webmail, and it worked at that time; however when I tested today I could not get it to work.

Question: If the new att email address I have obtained after 6/11/11 is the problem, should live mail on my bellsouth account work at all. Tell me how to test this out.

xgdude

xgdude · 16 Feb 2013

Well, I tried something and it worked; I took the att ID and password and pugged it in to a new account in windows live and it will receive messages sent from bellsouth webmail sent from my bellsouth account.
Windows live new account received it when the original account was still in the send / receive failure.
Got to test some more to see what I have.

xgdude

Slartybart · 16 Feb 2013

Thanks, good feedback - too bad nothing has helped yet.

Setting up or using a different free mail account (Gmail, AOL, other free pop3 access) is a good way to isolate a server or client configuration issue. It's only for testing.
If WEmail & the new test email pop3 work without a glitch, it's definitely a Bellsouth issue (I think we're all leaning this way), if however you experience similar issues with two pop3 servers, there's something in WEmail that neither pop3 server handles well.

So, you had an eMail acount with BellSouth, you had send/recv issues with that account, you got a new acount?? from ATT and it was after 6/11/11.

Was it a new account?? or just a new eMail id (i.e. Alias).

Yeah, it's not clear to me what ATT means about free eMail accounts after 6/11/11. I agree with you - should a client work at all? I wouldn't think it would, but.... ATT isn't clear on that. You might call or eMail (sorry) them.

Yoiu could try setting a longer timeout on the Advanced tab, usually though it doesn't require very long to pass the handshakes. Worth a shot.

How about the firewall question? If you use a third party firewall, it might get in the way. Windows firewall isn't known to cause issues - unless a user has defined their own rules.

With the new account in WEmail - you can send, but not receive? I guess I should ask receive where - on the original account in WEmail? Trying to narrow it down to send or recieve or both and if both the old WEmail account and WEmail new account have the same issue.

(Item 3) created a new account in live mail using manual configuration.
tested by sending email from web mail; receive still blocked at livr mail

Slartybart · 16 Feb 2013

Just a few notes - just mining for something that might provide a clue.

bellsouth.net takes me to att.yahoo.com, slow to resolve domain name
bellsouth.com takes me to att.com, quick to resolve domain name

DavidE · 16 Feb 2013

Slartybart said:

Just a few notes - just mining for something that might provide a clue.

bellsouth.net takes me to att.yahoo.com, slow to resolve domain name
bellsouth.com takes me to att.com, quick to resolve domain name

I just tried searching for bellsouth.net and bellsouth.com in a Google Search.
I get the same results as to where it takes me, att.yahoo.com or att.com.

For me there is no performance difference in clicking on a link to either of these sites.
They are both quick...

DavidE · 16 Feb 2013

I don't have an "att.net" email address.
My bellsouth.net email address is 10+ years old (since my dial-up days with bellsouth).

When I log in to at&t it shows "Your att.net mail inbox MyUserName@ bellsouth.net". (see screen print below)
I now wonder if you having an att.net and bellsouth.net email address isn't part of the problem.

I just looked into adding an alias for my account (online at&t) and the domain name is not editable and hardcoded to "@bellsouth.net" for the alias.

The reason for forwarding is to test if your WLM client program can work correctly with an email provider other than at&t.
If you can send/receive from WLM with a different email provider it shows WLM can communicate with an email server correctly.

The reason for trying Thunderbird is to test if another client program can work correctly with your at&t account.
If you can send/receive at&t email from Thunderbird, then we know it is something in your "WLM/at&t setup".

You don't have to create a new account to test with forwarding if you don't want to.
You don't have to install Thunderbird to test a different email client program if you don't want to.

These are things I would do if I was having this problem.

Screenshot showing what I see online regarding att.net / bellsouth.net

email error windows live mail/server error 0x800CCC90-attsp03.png

DavidE · 16 Feb 2013

Another consideration is you did have malware on your PC...
Can you test on a different PC that is known to be clean and always has been?
Maybe there is some "lingering malware remnant" on your PC causing your problem?

xgdude · 16 Feb 2013

Slartybart: I received your private message but was unable to respond to it. i attempted to create a sub account logged in both att.net and as bellsouth.net both using the ID and PW provided. Both attempts failed with a notification "your secret answer must be 4 - 80 xharacters long. Only alphanumeric characters are allowed. Spaces and specialcharacters are not allowed."

Don't know what its referrig to. Bot offlineand online security questions have answers that meet that standard. There is also a four digit Passcode which I selected at random whch did not effect the error message. I am clearly in over myhead.

xgdude

Slartybart · 17 Feb 2013

You can only reply to a PM when you're on the forum - click on User CP at the top of every page. If msgs aren't displayed, look on the left menu for List messages.

I think they're asking for a new security question for the new account. If that's true, just make one up, but write it down in case you need it. If that's wrong, you'll have to get ATT/BS to figure that out. The 4-digit passcode is probably more related to your account bundle than just your eMail.

We'll skip this for now. I think I've exhausted my list. David has a Bell south account and will probably be more help from this point forward. If I think of anything else I'll make a post.

Follow Dave's suggestions, report the results, and good luck.

Bill
.

Slartybart · 17 Feb 2013

Wait, I missed this post. Are you saying that it works? If that's true, use the new account.

xgdude said:

Well, I tried something and it worked; I took the att ID and password and pugged it in to a new account in windows live and it will receive messages sent from bellsouth webmail sent from my bellsouth account.
Windows live new account received it when the original account was still in the send / receive failure.
Got to test some more to see what I have.

xgdude