Making Permission Assumptions

Do you know Romer? He's just this guy, you know. As he points out over on his WordPress blog, he's been in the anti-spam field for the last decade, doing a little bit of everything. Most lately, he's an engineer for a major anti-spam product.

I just noticed a very insightful post from Romer, where he talks about a recent email he received from Kodak.

The email from Kodak was just a plain old opt-out message. It explained that Kodak wants you to receive exciting emails and as such, we've just assumed that you want those exciting emails, so you are now opted-in. If you don't like it -- click on the unsub link.

It's the opposite of a permission pass -- and it's a heck of an assumption. Romer's take on it: Now, I don’t mind companies with whom I’ve done business asking me for permission to share my personal data. In some instances, I’ve been more than happy to allow it. But to assume that I will allow it, to require me to actively tell them that I do not want this, and to “update” my “permission status” without getting my permission first, is presumptuous in the extreme.

So Kodak just grew that list, but they did it in a way where an engineer for a major anti-spam product just made a face when ending up on that list. That's ... not a position I would want to be in. Do you think that bodes well for your deliverability when your practices catch the eye of somebody who controls the keys to the inbox?

This is why I occasionally raise the red flag about the emails I receive...if I notice these things, I know the spam filterers notice them, too.

(Update: Another spam filterer blogged about this as well. Click here to read.)