Tutor
•
6 Messages
inbound.att.net is not responding
I have a ATT/Yahoo email address. The inbound.att.net server is not responding. I have tried pinging it with 3rd party connection sites (is it down and web site down) neither can connect to it. Is it down says that it may be down for a week. Any one know what the problem might be.
Thanks
Pete
petercreasey
Scholar
•
235 Messages
5 years ago
0
0
ATTHelpForums
Community Support
•
2.7K Messages
5 years ago
Hi,
There could be an issue with the server that is keeping you from accessing your E-mail. We are usually really quick to fix these type of issues. If you still can't access your E-mails after 12 hours, try these troubleshooting steps.
David, AT&T Community Specialist
0
0
petercreasey
Scholar
•
235 Messages
5 years ago
Did you remove the SOLVED advisory as this problem is still occurring.
And, yes, we know that various options that might work but rarely do.
Please remove the SOLVED flag is you haven't already.
Thank you.
. . . Pete
0
0
OldZeb
Tutor
•
6 Messages
5 years ago
0
0
petercreasey
Scholar
•
235 Messages
5 years ago
Did you remove the SOLVED advisory as this problem is still occurring.
And, yes, we know that various options that might work but rarely do.
Please remove the SOLVED flag is you haven't already.
Thank you.
. . . Pete
0
0
lutronjim
Teacher
•
27 Messages
5 years ago
0
0
petercreasey
Scholar
•
235 Messages
5 years ago
@ATTHelpForums
David, please tell us why you have not removed the "SOLVED" designation for this thread.
The problem is still occurring.
. . . . Pete
0
0
Hotlynx16
Voyager
•
3 Messages
5 years ago
The problem is still occurring on my wife's POP3 email ,(windows 7,Seamonky email)I can log on to her web email but every time she tries to get her mail on her computer it says "server error try later" she only knows how to get her POP3 email. Has it been changed to Imap or something? I have a friend down the road and he just got ATT DSL windows 7 ,Windows live mail and is having the same problem.
0
0
cn6655
Contributor
•
2 Messages
5 years ago
There are actually two (2) different UNSOLVED problems.
1. As I documented earlier in this thread, by using a Linux DNS tool I was able to determine that inbound.att.net resolves to multiple (at least 3) different IP addresses. Which one you get depends on which one their DNS resolver chooses to give you. At least one of those server is bad, or at least frequently bad, and email clients simply cannot connect to it at all if the DNS resolver happens to hand you that one. It just isn't there. For myself, I fixed this by getting rid of inbound.att.net in my client settings, and instead hard-coding 74.6.106.29. 74.6.106.29 seems to be responsive most or all of the time.
2. The second problem is that sometimes you can connect to a server, but it gives the "server error try later" error. This is even with 6.4.106.29, and only certain email addresses. There is one of mine that goes out for hours at a time, while my other sub-accounts still work.
I really wonder if we should start two new threads, not marked "Solved", one for each of these issues. For me, these issues started in October or November 2017, and have been festering non-stop since.
0
0
petercreasey
Scholar
•
235 Messages
5 years ago
new one I created; however, it appears that AT&T has elected to not be
responsive with respect to these problems (which fact seems very
out-of-character for AT&T).
0
0