Something blew up Yahoo!!'s mail server and the story doesn't get better.
It began getting glitchy on the 23rd and by 10AM the 24th it was blown.
Yesterday, their 800 number was too busy to take calls (but be sure to send an email and we'll respond!)
Yah, that works.
Today, one can get through to the 800 number, but after 5 minutes in queue, the line goes to a busy signal and drops the call.
During the wait, Yahoo!! apologizes. I wonder if their "monitoring for quality" includes monitoring for just cutting off phone calls.
Subscribe to:
Post Comments (Atom)
4 comments:
I've been in and out of Yahoo Mail (under my real identity) without issue for the last two weeks throughout the day and night. I don't believe there is any Yahoo Mail outage. There is something else going on for you. What error are you getting or what are you seeing?
Dad29:
This is what I fixed for L.E.
Appears to be YAHOO! eMail relay servers authentications problems. YAHOO! apparently doesn't like to be used as an eMail relay service ("take a back seat") by AT&T and other ISPs even though YAHOO! is charging and being paid handsomely for rental of their eMail servers as eMail server relays for other ISPs like AT&T, etc.
YAHOO! wants to be your primary eMail provider. I'm not so sure YAHOO! isn't doing this on purpose to force migration of and steal customers/consumers to YAHOO! primary "@yahoo.com" eMail addresses. I wouldn't put it past Marissa Mayer...desperate to fix the YAHOO! brand and company.
God forbid any one of these IT companies would humbly "take a back seat" to the other to best serve the customer.
Pay your monthly bill and we'll give you whatever service we feel like when we feel like it.
Also, no matter what "the experts" forum, it also appears to be DNS, load balancing, namespace translation recognition, and port problems at YAHOO! with YAHOO! infrastructure. This is why some browsers (eMail access via WWW browsing) and eMail clients (eMail access using local eMail software(s)) will work and others will not and even others will work sporadically.
Remember, YAHOO! is having major financial, personnel, and logistical/morale problems under Wausau WI native Google 13 year alum but questionable YAHOO! CEO Marissa Mayer. Internal strife always equals bad product.
In your LOCAL eMail client software/app (MSOutLook, ThunderBird, Apple Mail, Eudora, etc....whatever you use), NOT your web-based browser-accessed eMail software/app, configuration, try the following.
Make sure SSL is enabled at all times!
Leave your POP (incoming eMail) server ALONE!
Change your SMTP (outgoing eMail) server to (try 'til one works):
fmailhost.isp.att.net ,
smtp.att.yahoo.com ,
smtp.mail.yahoo.com ,
smtp.sbcglobal.yahoo.com ,
mail.yahoo.com ,
others.
Change your SMTP (outgoing eMail) server PORT to (try 'til one works):
465,
587,
25 (this port is what your eMail client software/app is probably already set to),
others.
Try other combinations of SMTP servers and ports here.
Do NOT use Google. Presently, Google is an NSA stooge.
Concurrent with using TOR and/or proxy server(s) for WWW browsing, using startpage and/or ixquick, use the keywords: +YAHOO +Apple +Mail +problems .
Apple Mail fixes apply to all YAHOO! eMail problems but return better and more detailed technical fixes.
Enough of this shit.
Back to 12 hour day rehearsals for tour auditions.
purple: my yahoo assploded, but my wife's did not.
Got it fixed today--after SBC referred me to Yahoo and after 3 days of line-drops, I got to Yahoo.
They sent me BACK to SBC. SBC knows all about it, reset the pwd, checked my outlook settings (didn't change a damn thing) and we're good to go.
For now.
Password = part of authentication process.
In this case, it appears pass-through authentication is used...SBC (which is really AT&T) to YAHOO!. Something appears to be getting f'd up in, during, and/or at either end of the pass-through.
Again, "...appears to be YAHOO! eMail relay servers authentications problems....". See my comment posting above.
The common denominator, that I see anyways, in all these problems, is YAHOO!.
Why you and not your wife?
From my comment posting above:
excerpt:
"...Also, no matter what "the experts" forum, it also appears to be DNS, load balancing, namespace translation recognition, and port problems at YAHOO! with YAHOO! infrastructure. This is why some browsers (eMail access via WWW browsing) and eMail clients (eMail access using local eMail software(s)) will work and others will not and even others will work sporadically....".
Of course, all that REALLY matters here is that the NSA is ecstatic that your eMail is back up and running. They're probably monitoring both the Dad29 blog and you personally.
Any "funny-isms" with your telephones during this period?
Welcome back...back to the future...1984.
For now.
Post a Comment