Thursday, 30 August 2007

Inadvertent Spamming: a Cautionary Tale

I learned today of a well-known software vendor whose business has suffered as a result of poor list management practices. It's not the first, and probably won't be the last. This sorry tale only goes to illustrate the importance of avoiding becoming an inadvertent spammer.

It appears that, although it had been legitimately sending mailings to its customers, the vendor had been ignoring unsubscribe requests. As I've said before, any unwanted bulk email sent by an organization after an appropriate unsubscribe request is spam -- an organization that fails to act on unsubscribe requests in this way is a spammer.

As a result of its failure to honour unsubscribe requests, complaints about the spam began to accumulate at the feet of the various organizations that track spammers' activity. Crucially, these include sender reputation services, such as DNSBLs (also known as IP blacklists). Inevitably, despite the fact that the majority of email it sent was legitimate, the vendor gained a negative reputation as a spammer.

This caused some recipients of its email to reject or otherwise filter these legitimate messages. Not only were legitimate direct marketing messages filtered, but also messages containing customers' license keys, technical support replies, etc.

This is indeed a cautionary tale: the lesson for senders is that the unsubscribe process is truly a mission-critical part of your direct marketing or transactional email workflow. Failure to ensure its integrity can not only cause legal problems, but damage your customer relationships and your business.

1 comment:

Mark Brownlow said...

Richi, great to see the word spread on these issues. This problem often occurs when email senders use a return address that isn't monitored. There are still plenty of people who unsubscribe by hitting reply and asking to be taken off the list. If nobody checks that email (or it's automatically deleted / rejected), the request goes unfulfilled and you have a spam situation...

Another related note is (where possible) to keep the sending infrastructure for business critical email separate from that for the kind of emails that can attract delivery problems. Like a newsletter list.

Even if the marketing emails are opt-in and totally above board, you can still slip onto a blacklist. So segregation means you can at least keep delivering the important email while you address the problem.

Post a Comment