Explore & discover

Helpful Links

Inbound.att.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x

Tutor

Inbound.att.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x

I am getting the following message using Outlook Express on Windows XP (SP3). 

The connection to the server has failed. Account: 'Adel Sakla ATT Mail', Server: 'inbound.att.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x800CCC0E.

Using MS Office Outlook does the same thing. My servers used to be: pop.att.yahoo.com and smtp.att.yahoo.com. They stopped working. Called ATT help line and they advised me to change them to inbound.att.net and outbound.att.net, but no luck there either.

Any help is appreciated.

1,508 Views
Message 1 of 13
Administrator

Re: Inbound.att.net

Greetings  @AASAKLA!

Welcome to the Community Forums! I understand how important it is to be able to have your email access. I can assist you with this issue!


In order to send e-mail from a mail client using a non-AT&T e-mail account on the AT&T network, you must first add and verify their non-AT&T e-mail address through their AT&T Yahoo! Web mail. You can see any of your email client error codes here.

1)      Access your Web mail, select Settings > Accounts

2)      You will need to know the POP server and the Port number for the other email account.

3)      The email address will then be in the From drop-down menu when composing an email in the Web Mail.

4)      You will be able to send and receive email from a different domain within your AT&T Yahoo! Web mail and be able to configure your client mail to do the same.


If you have any further questions or need and further assistance; please feel free to send us a private message to @ATTCares if you require further assistance. Please include your name, phone number, and any other account information you feel may be helpful in the personal message, so we can help to the best of our ability.


Thank you for reaching out today! I hope you have a wonderful rest of your day!


Shawn, Community Specialist


Need help?
Ask a question to get help from the AT&T Community or support from AT&T specialists. If this reply helped you please use Accept solution to mark it as an Accepted Solution.
*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
Message 2 of 13
Contributor

Re: Inbound.att.net

> In order to send e-mail from a mail client using a non-AT&T e-mail account on the AT&T network

 

ATTCares Shawn's response is not applicable. The error is WITH an ATT email account. A applicable solution is needed.

Message 3 of 13
ACE - Expert

Re: Inbound.att.net

The connection to the server has failed. Account: 'Adel Sakla ATT Mail', Server: 'inbound.att.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x800CCC0E.

I assume you are using some version of Outlook which I think is the only client that reports error codes in the form 0x800CCC0E.  Which Outlook (e.g., Outlook 2016)? 

 

The server settings are documented here and they really should be inbound.att.net/995/ssl for POP as you were told (and SMTP should be outbound.att.net/465/ssl).  Recheck those and your password setting (remember it's case sensitive).  You might also want to see if you can log into the webmail (through start.att.net) to make sure that password is valid.

 

I did a google search on your problem.  You might want to look over some of the results there.  Some talked about some repair tool for Outlook for this problem.

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 4 of 13
Tutor

Re: Inbound.att.net

Thank you _xyzzy_ (ACE - Master).

Yes, I verified that my password is correct through accessing my email at
www.att.net (receive and send). I don't like to use because of ads.

I also checked the settings that you mentioned (inbound.att.net/995/ssl for
POP3, and outbound.att.net/465/ssl for SMTP with PWD authentication).

The strange thing is that it was working ok on my Outlook Express 6.0 (that
comes with Windows XP), and it stopped working about couple of weeks ago.

I tried the same settings on MS Office 2003 Outlook that I had on the same
old PC with Windows XP, however, it gave similar errors.

I tried Outlook Express as well as MS 2003 Outlook on another PC with
Windows XP, and I had similar errors.

I tried the same settings on MS Office 2007 Outlook on another PC with
Windows Vista, and it worked fine.

I have come to the conclusion that ATT's servers have been altered to not
communicate with Outlook Express, Windows XP, or MS 2003 (or older) Outlook.
Message 5 of 13
Tutor

Re: Inbound.att.net

Hi d.w.b.:

Yes, I agree with you that ATTCares Shawn's response is not applicable.

I verified that my password is correct through accessing my email at
www.att.net (receive and send). I don't like to use because of ads.

I also checked the settings that you mentioned (inbound.att.net/995/ssl for
POP3, and outbound.att.net/465/ssl for SMTP with PWD authentication).

The strange thing is that it was working ok on my Outlook Express 6.0 (that
comes with Windows XP), and it stopped working about couple of weeks ago.

I tried the same settings on MS Office 2003 Outlook that I had on the same
old PC with Windows XP, however, it gave similar errors.

I tried Outlook Express as well as MS 2003 Outlook on another PC with
Windows XP, and I had similar errors.

I tried the same settings on MS Office 2007 Outlook on another PC with
Windows Vista, and it worked fine.

I have come to the conclusion that ATT's servers have been altered to not
communicate with Outlook Express, Windows XP, or MS 2003 (or older) Outlook.
Message 6 of 13
ACE - Expert

Re: Inbound.att.net

Yes, I verified that my password is correct through accessing my email at
www.att.net (receive and send). I don't like to use because of ads.

I'll just mention here my usual comment to those kind of statements about the webmail.  When or if you ever get your client to work (it really doesn't matter which client), so long as you use the yahoo servers, consider yourself cursed to visit the webmail at least once a month to see what legitimate mail may have been sucked up into your spam mailbox.  The yahoo spam filters have precedence over everything and I always sarcastically say "they know better than you what is and is not spam". Man Frustrated

 

FWIW, you can block the ads if your browser supports ad blocking addons/extensions. 

 

I tried the same settings on MS Office 2007 Outlook on another PC with
Windows Vista, and it worked fine.

 

I have come to the conclusion that ATT's servers have been altered to not
communicate with Outlook Express, Windows XP, or MS 2003 (or older) Outlook.

I'm inclined to believe it's the other way and blame the clients.  I suggest you post this over in the appropriate microsoft support forum.

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 7 of 13
Contributor

Re: Inbound.att.net

The version I have that is problematic is Outlook Express 6.00.2900.5512 (xpsp.080413-2105). I've verified settings per ATT/Yahoo. It's not a password failure because that is cached. For me, the email upload/download works occasionally. Closing and reopen it fixes it sometimes. Other times I can do that a dozen times or more and it doesn't. Strangely, last year I started seeing the following message.

Internet Security Warning: The server you are connected to is using a security certificate that could not be verified. The certificate's CN name does not match the passed value. Do you want to continue using this server? [Yes] [No]

Pressing No: A secure connection to the server could not be established. Account: 'ATT Yahoo', Server: 'inbound.att.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Error Number: 0x800CCC1A

It seems that I will not be able to upload/download due to the error if I do NOT see the message (or if I answer No). I must see that warning and press Yes then upload/download seems to work for the most part. The problem is, that does not always appear.

Message 8 of 13
ACE - Expert

Re: Inbound.att.net

Outlook Express 6 is an incredibly old mail client.  It is doubtless missing many necessary encryption features.  It isn't supported on Windows 7 or later, which means that your underlying OS is missing security features as well.  The OS is actually more likely the issue.  What OS are you running?

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 9 of 13
Tutor

Re: Inbound.att.net

I am using Windows XP.

The strange thing is that it was working ok on my Outlook Express 6.0 (that
comes with Windows XP), and it stopped working about couple of weeks ago.
My settings are: inbound.att.net/995/ssl for POP3, and
outbound.att.net/465/ssl

for SMTP with PWD authentication.
I tried the same settings on MS Office 2003 Outlook that I had on the same
old PC with Windows XP, however, it gave similar errors.
I tried Outlook Express as well as MS 2003 Outlook on another PC with
Windows XP, and I had similar errors.
I tried the same settings on MS Office 2007 Outlook on another PC with
Windows Vista, and it worked fine.
You may be right about the security issue and it looks like ATT's servers
have been

recently programmed to not communicate with Windows XP and any of its mail

browsers. I wish that ATT tell their customers about forthcoming changes
instead

of stopping abruptly.


Message 10 of 13
ACE - Expert

Re: Inbound.att.net

Yeah, you are going to find your XP system less and less useful.  The problem is that Microsoft has stopped providing new encryption support for it.  Thus, you won't be able to get to a lot of websites using IE, and/or any other browser that doesn't provide its own TLS/SSL encryption library instead of using Microsoft's.

Similarly, mail servers are now getting on board with more recent versions of encryption and since Outlook Express uses the OS's built-in library, it can't connect to machines that expect modern encryption protocols.  XP doesn't have any support for TLS 1.1 and TLS 1.2 and there are many who consider any version older than 1.2 inadequate.  XP also lags on cipher support.

 

 

 

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 11 of 13
Contributor

Re: Inbound.att.net

That may be but does not seem to apply to my situation which is intermittent. If software is now incompatible it would stop altogether. There is probably more to this that could be done.

Message 12 of 13
ACE - Expert

Re: Inbound.att.net


@d.w.b. wrote:

That may be but does not seem to apply to my situation which is intermittent. If software is now incompatible it would stop altogether. There is probably more to this that could be done.


The problem with this theory is that there are multiple mail servers that you might get routed to based on round-robin DNS and/or some other form of load balancing.  The servers are not equal, due to rolling upgrades, misconfigurations, etc.  Today you might connect to an older server that has a cert with a 128 bit key, tomorrow you might get one with 256.

 

 

 

 

Award for Community Excellence 2019 Achiever*
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.
Message 13 of 13
Share this topic
Share this topic
Announcements...

Are you having trouble logging in? Is your email password not working? Let us show you how to Reset your Email Password using myAT&T!

Additional Support