Ok I do
For all those times that you have to enter an email addy knowing full well that it will only be used for SPAM and invitations of a certain kind from Russian Beauties.
Yahoo!'s email service tumbled off the interwebs in the past hour when it began spewing out a "temporary error" message to an unknown number of users in the UK. The Purple Palace, however, remained silent about the outage on its official Twitter customer care account. At time of publication, it was not clear how many netizens …
This post has been deleted by its author
This post has been deleted by its author
"It actually used to be quite good. At least up until gmail came along."
Yes, true, but that was, what ?, 10+ years ago ? I've used them myself but the GUI became terrible, and gmail was indeed ramping up with interesting services, like the POP/IMAP service to consolidate all your ISP-bound email addresses.
Not only do I have a yahoo email, I have had it for years (mid 1990s?) and it's been my primary email for most of those, and instances of email failures and rejection can be counted on the fingers of one foot.
It's also not been affected by any of the occasionally reported "major outages". But then I try to stay at least one version behind their latest webmail client, when I'm not using it via a proper email client.
YMMV.
Anyone who uses ISP-based mail is being very silly. I have no intention of using gmail for anything significant. Where else should I be looking, assuming I don't mind paying a *small* fee?
This post has been deleted by its author
One of the bizarre sides of Yahoo is they were involved in setting up DKIM standard to check if the mail server sending an email is legit. Yet they often forget to register their own mail servers correctly and end up with lots of mail bounces. Especially from their BTInternet.com hosting.
The thing about BT is that they are causing denials themselves with their CPcloud server acting as a mail forwarder. If you look at BT they are running THREE email services under the name of BTInternet.com, one of which uses the Yahoo! mail service. To direct to mail to the correct service the CPcloud server is stripping off the original header info and substitutes itself as the sender. A great way to get mail be labelled as Spam.
I have many higher ups that communicate with regular people daily, and when I hear:
VIP - "Is there something wrong with our mail system?"
Me - "No, everything seems to be working normally."
VIP - "Well I sent a contract to someone and they've called and still have not received the e-mail"
Me - "Did you receive a message back, a problem delivering the e-mail?"
VIP - Silence greets me... then "No, I didn't get any notification."
ME - "I can look in the spam filter, can I have the e-mail address?"
VIP - "Let me see again, oh yes, someone@yahoo."
Me - "I will check, but Yahoo is notorious for having issues delivering mail in a timely manner."
VIP - "I want that mail delivered, please contact Yahoo and sort this out!"
Me - Silently opening the drawer where the scotch is kept... as I face palm.
This post has been deleted by its author
This post has been deleted by its author
BTinternet mail was giving a similar error this afternoon from around midday onwards. Seems to be OK now. Interesting in that BT supposedly split from Yahoo 12 months ago, yet its still possible to use the Yahoo servers and software to get BT mail (especially important for Android as theres no BT mail app....)
But before that around 8:00 this morning mail sent to BT addresses was getting black-holed. Didn't start getting through to the recipients until 7pm this evening. No warning message to the sender - it simply vanished for several hours
That's actually a refreshing difference from the usual "only a small amount of subscribers are experiencing issues" that is usually trotted out.
Of course, in the case of Yahoo!, they'd have trouble talking about a small number of subscribers, since that's all they have.
AC for obvious reasons.
I did a spell for a well known ISP with some "added value" features.
Turned out the programmers who produced these didn't really have an in depth appreciation of SMTP.
When an email was ready to go then they just fired it into port 25 as one long stream and got on with the next one.
Every now and then the MTA would not be ready to accept the email and would complain (although the program wasn't listening) and the failed message would be side lined to an error queue.
Over time this queue became quite large.
Nobody was keen to go public with this so I wrote a little Perl ditty which fed the error queue into the MTA at a gentle pace.
Genuine errors were rejected again, transient errors were picked up and the message re queued.
Over time all the stuck emails were delivered (albeit a bit late) and the programme was updated to confirm acceptance by the MTA.
Quite likely there are similar black holes in a lot of ISP software.
Testing often doesn't catch transient errors.
TL;DR just because programmers work for an ISP doesn't mean they understand email.