Monetizing the complaint stream

What if ESPs (and ISPs, for that matter) started charging users for every complaint generated? Think of it like peak pricing for electricity. In California, businesses can opt for discounted power, with the agreement that they are the first companies shut off if electrical demand exceeds supply. What if ESPs and ISPs offered discounted hosting rates to bulk senders who agreed to pay per complaint?
I see pricing scheme something like this.

  • $5.00 per FBL message.
  • $50 for a hand written complaint.
  • $150 for a  report of a spamtrap hit.
  • $500 for an ISP temporary block.
  • $10K for a major blacklisting (SBL, other filtering company).
  • $5K per customer if the blacklisting affects other customers’ ability to send.

ESPs could give a threshold of complaints that are covered. For instance, every per-complaint customer gets 0.05% of their total volume in free FBL complaints. Hand written complaints they get one or two every billing cycle, not to exceed 12 complaints a year. 6 spam trap hits a year. There is a bit of grace in the handling. I can think of lots of ways to make this sender friendly.

Benefits to the Sender

Good senders benefit because they get lower rates and don’t risk much in the way of complaint related expenses. They don’t have to pay that hidden compliance fee that all ESPs customers currently pay.
Senders with more aggressive email programs benefit because they’re able to shoulder the risks associated with those programs directly. The ESP has less to say about buying or renting lists because instead of the ESP paying the cost of problems, the customer assumes that cost. Even better, the sender can pass the compliance cost back onto their list vendor. Imagine being able to tell a vendor they have to discount a list based on the number of complaints or delivery problems. Instead of the vendor selling a list with no incentive for that list to perform well, the vendor now has an incentive to make sure those opt-in addresses really are opt-in.

Benefits to the ESP

The ESP benefits because no longer is their abuse and compliance desk a cost center. With the right mix of clients it may even become a profit center. Plus, the compliance desk is guaranteed to be funded at a rate that covers the work needed to maintain a reasonable delivery rate for customers. The ESP can stop spending so much time telling customers they can’t do something and more time raking in the cash.
It’s a total win for everyone.
Monetize complaints. It’s the future of email.

Related Posts

Problems with Yahoo FBL

There are a couple problems I’ve been alerted to with the Yahoo FBL today.
The first comes from Michael Ellis and is about broken FBL reporting at Yahoo.

Read More

Spammers react to Y! DMARC policy

It’s probably only a surprise to people who think DMARC is the silver bullet to fixing email problems, but the spammers who were so abusing yahoo.com have moved on… to ymail.com.
In the rush to deploy their DMARC policy, apparently Yahoo forgot they have hundreds of other domains. Domains that are currently not publishing a DMARC policy. Spammers are now using those domains as the 5322.from address in their emails. The mail isn’t coming through any yahoo.com domain, but came through an IP belonging to Sprint PCS.
ymail_dmarc
This is just one example of how spammers have reacted to the brave new world of p=reject policies by mailbox providers. If only the rest of us could react as quickly and as transparently to the problems imposed by these policy declarations. But changing software to cope with the changes in a way that keeps email useful for end users is a challenge. What is the right way to change mailing lists to compensate for these policy declarations? How can we keep bulk email useful for small groups that aren’t necessarily associated with a “brand”?
The conversation surrounding how we minimize the damage to the ecosystem that p=reject policy imposed hasn’t really happened. I think it is a shame and a failure that people can’t even discuss the implications of this policy. Even now that people have done the firefighting to deal with the immediate problems there still doesn’t seem to be the desire to discuss the longer effect of these changes. Just saying “these are challenges” in certain spaces gets the response “just deal with it.” Well, yes, we are trying to deal with it.
I contend that in order to “just deal with it”, we have to define “IT.” We can’t solve a problem if we can’t define the problem we’re trying to solve. Sadly, it seems legitimate mailers are stuck coping with the fallout, while spammers have moved on and are totally unaffected.
How is this really a win?

Read More

Do you have an abuse@ address?

I’ve mentioned multiple times before that I really don’t like using personal contacts until and unless the published or official channels fail. I don’t hold this opinion just about resolving delivery issues, but also use official channels when reporting spam to one of my addresses or spam traps.
My usual complaints contain a plain text copy of the mail, including full headers and a short summary of the email address it was sent to. “This is an address that was part of a leak from…” or “This is an address scraped off my website. It’s been removed from the website since 2004” or “This address isn’t used to sign up for any mail.”
Sadly, there are a number of “legitimate” ESPs that don’t have or don’t monitor their abuse address. In some cases it’s an oversight or a break down of internal mail handling. But in most cases, it’s a sign that the ESP doesn’t actually handle abuse.
It’s frustrating to watch an ESP post long blog posts about “best practices” and “effective delivery” and “not spamming” and yet not be able to actually stop their own customers from spamming. It’s not even that I necessarily want them to disconnect their spamming customers (although that would be nice) but suppressing the address that I’ve told them was a spamtrap seems trivial. And yet, a month after my first complaint and weeks after escalating to a personal contact, I’m still getting spam.
The 5 things every ESP should do to handle spam complaints.

Read More