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 *

  • ReturnPath on DMARC+Yahoo

    Over at ReturnPath Christine has an excellent non-technical summary of the DMARC+Yahoo situation, along with some solid recommendations for what actions you might take to avoid the operational problems it can cause.No Comments


  • AOL problems

    Lots of people are reporting ongoing (RTR:GE) messages from AOL today.  This indicates the AOL mail servers are having problems and can't accept mail. This has nothing to do with spam, filtering or malicious email. This is simply their servers aren't functioning as well as they should be and so AOL can't accept all the mail thrown at them. These types of blocks resolve themselves. 1 Comment


  • Fixing discussion lists to work with new Yahoo policy

    Al has some really good advice on how to fix discussion lists to work with the new Yahoo policy. One thing I would add is the suggestion to actually check dmarc records before assuming policy. This will not only mean you're not having to rewrite things that don't need to be rewritten, but it will also mean you won't be caught flat footed if (when?) other free mail providers start publishing p=reject.No Comments


Archives