Recent Posts

The 5 stages of a Spamhaus listing

Courtesy of Spencer over at Experian.
The 5 Stages of Recovery

Questions about Spamhaus

I have gotten a lot of questions about Spamhaus since I’ve been talking about them on the blog and on various mailing lists. Those questions can be condensed and summed up into a single thought.

There’s been a lot of discussion about Spamhaus, spam traps, and blocking. Today, Spamhaus rep Denny Watson posted on the Spamhaus blog about some of the recent large retailer listings. He provides us with some very useful information about how Spamhaus works, and gives 3 case studies of recent listings specifically for transactional messages to traps.
The whole thing is well worth a read, and I strongly encourage you to check out the whole thing.
There are a couple things mentioned in the blog that I think deserve some special attention, though.
Not all spam traps actually accept mail. In fact, in all of the 3 case studies, mail was rejected during the SMTP transaction. This did not stop the senders from continuing to attempt to mail to that address, though. I’ve heard over and over again from senders that the “problem” is that spamtrap addresses actually accept mail. If they would just bounce the messages then there would be no problem. This is clearly untrue when we actually look at the data. All of the companies mentioned are large brick and mortar retailers in the Fortune 200. These are not small or dumb outfits. Still, they have massive problems in their mail programs that mean they continue to send to addresses that bounce and have always bounced.
Listings require multiple hits and ongoing evidence of problems. None of the retailers mentioned in the case studies had a single trap hit. No, they had ongoing and repeated trap hits even after mail was rejected. Another thing senders tell me is that it’s unfair that they’re listed because of “one mistake” or “one trap hit.” The reality is a little different, though. These retailers are listed because they have horrible data hygiene and continually mail to addresses that simply don’t exist. If these retailers were to do one-and-out or even three-and-out then they wouldn’t be listed on the SBL. Denny even says that in the blog post.

Filtering is not just about spam

A lot of filters started out just as filters against spam. But over the years they’ve morphed into more general blocks against dangerous or problematic email. There’s a lot of crime and bad behavior on the internet, much of it using email as a conduit or vector. Filtering is so much more than stopping spam now. It’s as much, or more, about stopping crime.
Email filters are essential to protect us from scammers. Sometimes I forget this, and then I read about a grandmother getting swindled by a Nigerian scammer and ending up dead.
There are real consequences to poor filtering and there is real crime facilitated by email. It’s easy to forget this as we deal with the email that gets caught in filters when they shouldn’t.
Filters are one of the first lines of defense against online crime.
Not only does filtering stop crime, but they also keep email working. An unfiltered mail stream is an ugly, unreadable, unworkable mess.

NJABL blocklist closed for good

The NJABL blocklist has shut down for good. The zone files are empty and are expected to stay that way for a while.
Anyone using NJABL, either for yes/no delivery decisions or as part of a scoring system, should remove that blocklist from their setup.

Censoring email

It seems some mail to Apple’s iCloud has been caught in filters. Apparently, a few months ago someone sent a script to a iCloud user that contained the phrase “barely legal teen” and Apple’s filters ate it.
The amount of hysteria that I’ve seen in some places about this, though, seems excessive. One of my favorite quotes was from MacWorld and just tells me that many of the people reporting on filtering have no idea how filters really work.

Thoughts on bounce handling

This week’s Wednesday question comes from D.

What are your thoughts on bounce handling
Read More

Opting customers in to new programs

Recently, I started getting “1 sale a day!” emails from buy.com. I’ve made purchases from Buy in the past and generally have been content to get emails from them. They’re not always relevant, but hey, it’s relatively non-intrustive marketing.
When they started this new program, they just started mailing: no warning, no introduction, nothing. So I decided to opt out of this mail.
Buy.com has a preference center, and while I was there, I opted out of all email marketing. Why? Because a company that is going to randomly add me to new (daily!) marketing lists is a company I don’t trust any more.
A lot of folks have complained about Amazon doing the same thing. Amazon started a daily deals program and opted in a lot of people without warning, without introduction and without permission.
I get why companies do this. It’s a lot easier to ask for forgiveness than permission. It lets them sell things to people who might never opt-in to that program. And in many areas of direct marketing, consumers have no rights to make the marketing stop. They have no tools to make the marketing stop.
Email is different from many direct marketing channels, though. Many consumers have the tools to make mail stop (filters, this is spam buttons, changing their email address completely) and they do take advantage of them.
Given a marketers job is to extract as much revenue from customers as possible, they can’t respect recipients. They have to treat them as money dispensing machines. But at least in email recipients have some ability to opt-out of the transactions.

Irony

Saw this on twitter today:

Oh, the irony of an append vendor using COI for a whitepaper download.
Read More

Earthlink opens up FBL

Earlier this week I was at MAAWG and one of the Earthlink postmaster folks stopped me to tell me that Earthlink was now accepting non-ISP applications to their Feedback Loop.
In order to apply for the Earthlink FBL send an email to fblrequest@abuse.earthlink.net with the IP addresses and the FBL email address.