- edited 01-18-2018 7:45 PM
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.
Solved by: Go to Solution.
05-01-2018 12:21 PM
@_xyzzy_ >> I think there are multiple servers handling the traffic so it isn't too much a stretch to believe one can become problematic every now and then
x, I believe the ATT problem has to do with server overload. When it happens, the problem seems to occur toward mid-afternoon or later in the day. Sometimes, it takes a very long time for my enauk client to successfully check for ATT mail and other times it fails with the error talked about in this thread.
As I said before, I can't imagine ATT not knowing about the problem and its cause. For some reason, ATT is electing thus far to not address the problem (at least, so far as we can observe).
. . . . Pete
05-12-2018 12:14 PM
I'm not sure if I want to get into this, but the complaints made by the other respondents are valid. They are NOT imagining this nor are they technically incompetent. As Lutronjim estimated, the servers are down at least 20 to 30 percent of the time. I've been on the line with AT&T "support" (that's a good one) for HOURS, thinking that the problem was on my end. I've researched the Net thoroughly, trying every possible way to solve the problem, only to discover that it's the SERVER that's down, NOT my system, whatever the AT&T apologists on this thread might claim.
We have only two high-speed Internet suppliers in my area, AT&T and Comcast. The only reason I stick with AT&T is because I hate Comcast more, if such a thing is possible.
05-20-2018 10:26 PM
Hi, Jim and Pete -
Nope, there’s no hope. None. Zip. Nada. Lasciate ogni speranza, chi si abbona a AT&T. (Google Translate still works, even if AT&T email doesn’t.)
Per favore, excuse the over-capitalization that follows. I’m usually more restrained in my writing, but I’m on a well-justified rant here…
I have exactly the same problem that Jim has. My email works just fine for five days, then conks out for two days (or more). This is not due to my browsers, because the same thing happens with Chrome, Firefox, and Internet Explorer. (I’ve tried all three.) It is not caused by my email apps, because the same thing happens with Outlook, Thunderbird, and Gmail. (Again, I’ve tried all three.) It is obviously not to due to my email settings, because I got those straight from AT&T, and besides, digital settings don’t fade in and out like radio reception. BY COINCIDENCE THOUGH, every time my email folds, I find that I can’t log onto the AT&T email server EITHER. (Gee… do you think that there might be a connection in there somehow?)
Pete (who sounds like a very fair-minded man) stated in an earlier post: “It seems to me that AT&T would want to uphold a favorable reputation with respect to anything that has the AT&T name on it.” No, Pete, AT&T is NOT concerned about maintaining a favorable reputation with the public, because as a near-monopoly, it doesn’t HAVE to be concerned about it. After all, where else are we going to take our business? Comcast? (That’s a joke.) We could threaten to do just that and the folks at AT&T would politely try to suppress their laughter while they put us on hold for transfer to yet another “technical specialist” whose entire job consists of convincing us that it’s all OUR fault.
As far as getting AT&T to live up to its obligations, you might as well petition Congress (which is currently in merger talks with AT&T, I’ve heard.)
Which reminds me, we haven’t heard from our buddy _xyzzy_ lately. Wonder what he has to say about all this.
- edited 05-20-2018 11:28 PM
If I have nothing (further) to contribute I keep my "mouth" shut! Lucky I saw your reference to me at all since you didn't prefix it with the @ to cause me to get a notification (same way I just referenced you). I could have missed reading this thread. (I also mentioned this in post 29 of this thread too).
And I really don't have anything to say or suggest because I don't know why access to an account would be more-or-less "random". If just trying to log into the account fails without even involving email then something else is going on. But if that does fail, say for a password error, I would also expect email to fail too. None of this then has anything to do with email if it's truly an account validation problem. It just shows up in email apps more since they log in every time they need to access the servers (get mail, send mail, etc.).
05-21-2018 12:24 AM
I apologize for the syntax omission. I mistakenly thought that you were still following the thread.
Well, that's certainly fair enough, and we'll respect your decision to conclude the conversation. Before you sign off completely, though, there is a favor you might consider doing for us:
We still can't get AT&T Technical Support to admit that there even is a problem, much less that it's their problem. You seem very knowledgeable about the ways of AT&T. If neither Technical Support nor the forum can make much headway in resolving the issue, where would you recommend we go next? I'd like to think that AT&T has some other channel that would be receptive to investigating the matter.
We would be genuinely grateful (no, really!) if you could point us in the right direction. Besides, I'd hate to spend a perfectly good rant on an audience of just three people.
Thanks for your help.
05-21-2018 12:39 AM
@OmnesMendacium - Not sure where you could turn for help. Has anyone suggested the Digital Assistance Center (877-267-2988). Not sure they are much help either but I thought I would toss that out there if it hasn't already been suggested. I really don't have any other ideas.
By the way about preceding a user name with a @. It looks like you didn't select my id from the popup menu that occurs when you type the @. If you had selected me from that popup menu you would see it creating a link. It looks like you just typed @_xyzzy_ since that is not a link and won't create the notification which it didn't.
I look at a lot of threads. It hard to stay on top of all of them and some do slip through the cracks.
05-21-2018 5:35 AM
Got it right that time, I think. (Thanks for the menu tip.)
That's almost exactly what I had in mind: a route that lets us do an end-run around Technical Support. A fresh perspective on a problem sometimes works wonders. I'll wait for @petercreasey and @lutronjim to check into the thread again, and we'll take it from there.
Thanks again for your help.
06-06-2018 11:49 AM
I think that I MAY have figured out what's going on here, and a possible workaround. I'm absolutely astonished that ATT / Yahoo cannot figure this out, and I think that I have.
I noticed that if I repeatedly pinged inbound.att.net, I could get different IP addresses. Sometimes it "stuck" on one IP address for quite a while, and then it would suddenly start bounding around between three different IP address.
In Linux, I used dig to poke into this, and discovered that there are indeed three different IP addresses for inbound.att.net. Which one you get depends on which one the DNS server decides to give you:
ops@saturn:~$ dig inbound.att.net
; <<>> DiG 9.7.0-P1 <<>> inbound.att.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25016
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 13, ADDITIONAL: 5
;; QUESTION SECTION:
;inbound.att.net. IN A
;; ANSWER SECTION:
inbound.att.net. 523 IN CNAME pop-att.mail.yahoo.com.
pop-att.mail.yahoo.com. 300 IN CNAME fo-jpop.mail.att.gm0.yahoodns.net.
fo-jpop.mail.att.gm0.yahoodns.net. 300 IN A 18.104.22.168
fo-jpop.mail.att.gm0.yahoodns.net. 300 IN A 22.214.171.124
fo-jpop.mail.att.gm0.yahoodns.net. 300 IN A 126.96.36.199
In my e-mail client, I experimented for a while, and discovered that (for me at least, and today at least) if I replaced "inbound.att.net" with " 188.8.131.52", it consistently connected and worked. If I used "184.108.40.206", it consistently failed.
This is just one data point at one point in time, so it may be a red herring, but it certainly appears to explain what people are seeing. There might be bad server(s), and depending on what DNS dishes out, you may be trying to connect to a good server or a bad server. Hard-coding a good server that is working at the time my be the workaround.
06-07-2018 6:22 AM
c, what you observe makes perfect sense and is consistent with what we have surmised in this thread a few times probably explains the intermittent failures.
The fact that AT&T has not addressed the issue evidently is indicative of a lack of appropriate interest on their part in the integrity of their email handling.
. . . . Pete