3 ms·
1. They probably figure "the network is reliable" and therefore any failure that isn't short lived is permfail. I would disagree, but I imagine their own user b
by tedunangst 5y ago
1. They probably figure "the network is reliable" and therefore any failure that isn't short lived is permfail. I would disagree, but I imagine their own user base complains that they don't get bounces until days later. "That was a very important serious business email. How dare you not tell me it wasn't delivered promptly!" (And I imagine the old standard of a warning email that message hasn't been delivered but retries are ongoing isn't handled well by many people.)
2. I'd double check you didn't bring the server back online but misconfigured such that it rejected the message.
- _moof 5y ago> And I imagine the old standard of a warning email that message hasn't been delivered but retries are ongoing isn't handled well by many people. Can you expand on this? It's been a while since the previous century but I don't recall those messages ever being confusing.
- tedunangst 5y agoI assume there's a lot of overlap between yahoo users and people incapable of reading words on screens. The message can clearly say "Email has not yet been delivered, but I will continue retrying." And users will frantically email yahoo support what do I do, what does this mean, how do I fix it, have I been hacked? People refuse to read messages from computers because those could only be words that only computer nerds understand.
- londons_explore 5y agoThe fact the messages didn't have any consistent UI and frequently had lots of technical mumbo jumbo (ie. All the message headers) made them really user unfriendly. They also didn't localize to the user's language when sent by remote servers, and were frequently sent at 3am (did you want your phone going ding new email at 3am?)