Timeliness of email

There’s been an interesting discussion in the comments from yesterday’s post about temp failing. My position is that email is not a 100% reliable medium for transmitting time sensitive information.
Two things happened today to reinforce that.

  1. Yahoo announced they were having incoming MTA issues again, causing them to non-specifically defer mail. This has been going on for almost a week, causing mail delays all over the net. Other ISPs are dealing with backups and delays. Bulk senders are also seeing problems across the board.
  2. Yesterday I received email from a local brew pub about their tapping party for a new beer. Usually these announcements come 10 – 12 days before the actual party so I mentally noted that the tapping party was “coming up.” Today we went to the same pub for lunch, and discovered the party was last night and we’d missed it. Well, bummer.

In one case email delays are technical, in they other case they’re user error. In both cases, they’re things that senders can’t really control, though.

Related Posts

Delivery delays due to congestion

Now that we’re deep in the middle of the Christmas shopping season, I’m seeing more and more complaints about delays at ISPs. Mickey talked about everything the ISPs have to consider when making hardware and buildout decisions in his post The hard truth about email on Spamtacular. When, like on cyber Monday, there’s a sharp increase in the volume of email, sometimes ISPs don’t have the capacity to accept all the email that is thrown at them.

Read More

Yahoo and Verizon

Mickey at Spamtacular has information about Verizon’s email system that will have relevance for anyone working in delivery.

Read More

Yahoo delivery problems

Al writes about a Yahoo delivery problem where they have identified a particular Yahoo MX that is falsely returning “mail blocked due to XBL.” The IPs in question are not on the XBL. Yahoo is aware of the issue and are working on a resolution. If you are seeing these bounces, Yahoo is aware of the issue. Exacttarget has worked around the issue by suspending deliveries to the affected MX.

Read More