Recent Posts

Opt-in is dead! Long live opt-in.

This week there has been an ongoing discussion on one of my mailing lists about spam, definitions, use of the this-is-spam button and permission. One small part of the discussion centers around the definition of spam. Is spam unwanted email or is it unasked for email? If a sender doesn’t have permission from recipients to send mail, but the sender manages to keep their reputation at major ISPs clean enough to get good delivery, is the sender doing anything wrong?
My own answers really sidestep the question. I believe spam as a term is so ill-defined as to be meaningless. I try not to use “spam” when describing any mail. Even mail that comes to my own personal spamtraps and spammer-created email addresses, if I’m describing it to people I try to be more descriptive than just “spam.”
Coincidentally, Ken had an article in his newsletter today pointing out that the term opt-in has been rendered meaningless. First, he points out that all lists should be opt-in. Marketers shouldn’t have to describe a list as opt-in, it should just be opt-in. He then goes on to tell a story about an email marketer, who bought or purchased a list with Ken’s email address on it. The marketer claims the mail is opt-in, but it’s not. Ken ends the article with some advice to marketers.

Read More

Google Apps – where's my abuse@

Most ISP feedback loops require you to demonstrate that you’re really responsible for your domain before they’ll start forwarding reports to you. The usual way that works is pretty similar to a closed-loop opt-in signup for a mailing list – the ISP sends an email with a link in it to the abuse@ and postmaster@ aliases for your domain, and you need to click the link in one or both of the emails to continue with the feedback loop signup process.
That’s mostly there to protect you, by making sure that someone else can’t get feedback loop messages for your domain. And it’s not too difficult to do, as you should already have an abuse@ and postmaster@ alias set up, and have someone reading the abuse@ alias.
But maybe you’re using Google Apps to host your corporate email, and that’s the domain you need to use for your feedback loops. So you go to create abuse and postmaster users, but it won’t let you – you just get the error Username is reserved for email list only. Uhm, what?
Google want to police use of domains hosted on their service, so they automatically set up abuse and postmaster aliases for your domain, and any mail sent to them is handled by Google support staff. You may well be happy with Google snooping on your abuse role account, but you really need to be able to read the mail sent to it yourself too.
So what to do? Well, the way Google set things up they actually create invisible mailing lists for the two role accounts, and subscribe Google Support to the lists. In older versions of Google Apps you could make those mailing lists visible through the user interface by trying to create a new mailing list with the same name, then simply add yourself to the mailing list and be able to read your abuse@ email.
But Google broke that functionality in the latest version of the Google Apps control panel, when they renamed email lists to “groups”. If you try and create a new group with the email address abuse@ your domain you’ll get the error Email already exists in this domain, and no way to make that list visible.
So, what to do?
Well, there’s a workaround for now. If you go to Domain Settings you can select the “Current Version” of the control panel, rather than the “Next Generation” version. That gives you the old version of the control panel, where all this worked. Then you can go to User Accounts, create a new email list delivering to abuse@ and add one of your users to the mailing list. You can then set the control panel back to “Next Generation” and have access to the mailing lists via Service Settings → Email → Email Addresses.
Hopefully Google will fix this bug, but until they do here’s the step-by-step workaround:

Read More

Subvert the dominant paradigm

I am very slowly getting back into the swing of work and reconnecting with colleagues and other delivery folks, both on the sending and receiving side. On the sending side, there are multiple discussions happening about how senders can best communicate with receivers how much spam blocking by ISPs impacts legitimate businesses.
This is one of those perpetual issues, popping up usually around the time of conferences where both senders and receivers pop up. Senders are frustrated by the amount of their mail that is blocked, receivers are frustrated by the amount of mail that isn’t blocked and by the complaints from their users. The sender solution is to attempt a dialog with receivers, where they can tell the receivers how much legitimate mail is blocked. Receivers respond by avoiding senders as much as possible.
The impasse annoys everyone and doesn’t do anything to get mail delivered. I challenge both senders and receivers to find a new way to relate to each other this year

Read More

MAAWG agenda published

For those of you who are MAAWG members, the agenda for the February meeting in San Francisco has been published. Who is planning on attending?

Read More

Legitimate list vendors

In this week’s Magilla newsletter, Ken provides a number of ways to identify a bad email list vendor. His suggestions are not only appropriate for list vendors, but are also a good way to screen mail partners, customers or even vendors.

Read More

Court rules for Reunion.com

Today a California judge ruled against plaintiffs suing reunion.com. Venkat has blogged about the case previously, and has an analysis of the ruling. The crux of the case is reunion.com requesting users provide passwords to email accounts and then sending mail claiming to be from the user to all the addresses in the users address book.
According to Mediapost:

Read More

e360 v. Spamhaus

Mickey has been posting new documents in the e360 v. Spamhaus case. I’ve not had the time to read them, yet, but have seen some of the excerpts. Spamhaus is moving for summary judgment and moving to strike Mr. Lindhart’s testimony.

Read More

RoadRunner FBL information

RoadRunner has decided to delay the launch of their new FBL until after the holidays. Sounds like a good idea to me, the launch is never quite as smooth as the ISP wants it to be. People are checking out and trying to troubleshoot the problems while also dealing with all the extra stress and demands of the holiday season is asking for trouble. The good news is that they are now planning on running the two FBLs in parallel for a few weeks, instead of ending one then starting the other.

Read More

Light blogging through 2009

There will be some light blogging here through the end of the year. We are headed out for our first vacation in years next week, then will be spending some time with family. I will be blogging before we leave and will try to get some posts written to trickle out while I’m gone.
I hope everyone has a happy and relaxed holiday season. I am looking forward to resting, recharging and returning ready to take on 2009.

Read More

Co-reg

Well over half of the clients who come to me with delivery problems admit at some point that one of the ways they collect subscribers is through co-registration. They typically have widespread delivery problems at the major ISPs as well as SBL listings.
John Levine posted over the weekend about his thoughts on co-reg.

Read More
Categories
Tags