BLOG

Another reason not to use no-reply@

A story from someone handling support at a UK company that regularly sends out transactional email with no-reply@company in the From: line.

[A] guy emailed in and started off the RMA process on a motherboard that was dead.

A month later this guy rings up the store and starts yelling and cursing saying his motherboard has not arrived and that Nor Eply (the guy who he had apparently been corresponding with) was ignoring all his emails. As you can imagine, he was pissed.

So my friend looks into the logs to see who was designated to to reply to him and why he had’t been.

It turns out when the guy had submitted his RMA ticket, the shops mail bot sent out an auto reply stating you will hear from them when they have news etc etc. The address was the usual no-reply@*******.com

Yes, the man had been having a one way conversation with the the mail bot ‘Nor Eply’ for a month.

It’s not that uncommon for people to not notice the no-reply and try to respond to mail. Then get angry when the company isn’t responding to them. I know it’s a pain to deal with replies to emails, but that is a cost of doing business.

Comment:

Your email address will not be published. Required fields are marked *

  • HE.net DNS problems

    Hurricane Electric had a significant outage of their authoritative DNS servers this morning, causing them to return valid responses with no results for all(?) queries. This will have caused delivery problems for any mail going to domains using HE.net DNS - which will include some of their colocation customers, as well as users of their free services - but also will have caused reverse DNS to fail for most servers hosted by Hurricane Electric worldwide, so if any of your mail is being sent from HE hosted machines you may have seen problems. (We're HE customers so we noticed. Still happy with them as a vendor.)No Comments


  • 65.0.0.0/8 DNS issues

    If you're sending email from any address beginning with a 65 - in 65.0.0.0/8 - it's possible you'll see some delivery problems. Something appears to be broken with dnssec signatures for the reverse DNS zone, leading queries for reverse DNS to fail for anyone using a dnssec aware DNS resolver (which is almost everyone).1 Comment


  • Our green bar certificate is going away

    Later today we'll be switching from an Extended Validation ("green bar") SSL certificate to a Domain Validation certificate. This isn't exactly a planned change but I'm waiting for responses from Comodo before I go into it too much. I'll share some more details next week.3 Comments


Archives