New FBL information

A couple new bits of information for folks interested in participating in feedback loops.
If you’re an ESP, you’ll want to sign up for the two new FBLs that were released this month. XS4ALL and Telenor are now offering complaint feeds to senders.
If you’re a mail recipient and want the ability to report spam, try the new browser/MUA plugins for reporting spam released by the French anti-spam grup Signal Spam
These browser plugins allow recipients to report spam directly from a button in the browser. Signal Spam reports:
The button is working for the biggest webmails around, such as yahoo!, SFR, gmail, outlook, AOL, laposte, free, and is downloadable for Chrome, Safari and Firefox with this links :
Chrome
Safari
Firefox
These plugins are currently in beta, but should be released by the end of 2016.
For those folks who use our ISP information page, I haven’t yet added Telenor and XS4ALL to the pages of available FBLs. Part of that is because we’re looking at options to improve data presentation and ease of maintenance. The perl script that magically generated the summary page from other pages was great, until it hid itself on some VM somewhere and can’t be found. There are other things we want to maintain as public resources, so we’re looking into options. (wikimedia was one of our early attempts… it didn’t do what we needed). Anyone have a public KB or wiki package they particularly like?

DoorDash gets it
Happy Holidays

Related Posts

Low complaint rates are not always good

Digging another old blog post out of the archives. In November 2011, I talked about how part of the Holomaxx complaint against Microsoft and Yahoo said that their complaint rates were below 0.5% and 0.1%. The argument was that if their complaint rates were low, then the mail must not be spam.

Read More

Beware the TINS Army

When consulting with clients, I spend a lot of time trying to help them better understand the concept of sender reputation. Spam reports, feedback loops, and other data that comes from a collection of positive and negative reputational feedback about a company sending email.
Certainly, the “This is not spam” action – moving an email from the spam folder to the inbox, or clicking the “not spam” button in a web mail’s interface, is a strong positive reputational action. Some webmail providers use this data to decide which bulked senders deserve being let out of the penalty box – which should have their mail once again delivered to the inbox.
A client recently theorized that a great solution to their delivery problems would be to do this “en masse.” Sign up for hundreds or thousands of webmail accounts, send my mail to them, and click on the “not spam” button for each of my own emails. That’ll greatly improve my sending reputation, right?
NO! ISPs have already thought of this. They watch for this. They’re really good at picking up on things like this. I know for a fact that Yahoo and Hotmail and AOL notice stuff like this, and I strongly suspect other webmail providers notice it as well.
What happens when Yahoo or Hotmail pick up on this type of unwanted activity? Well, if it’s at Yahoo, they’re likely to block all mail from you, 100%, forever. I’ve seen it happen more than once. Yahoo might even identify all of your netblocks, ones beyond the ones sending today’s mail or originating today’s activity. And good luck trying to convince them that you’re not a spammer – you have a better chance of winning the lottery two weeks in a row.
As for Hotmail – what would Hotmail do? Ask Boris Mizhen. Microsoft is currently suing him, alleging that he and/or his agents or associates engaged in this very practice.

Read More

Who pays for spam?

A couple weeks ago, I published a blog post about monetizing the complaint stream. The premise was that ESPs could offer lower base rates for sending if the customer agreed to pay per complaint. The idea came to me while talking with a deliverability expert at a major ESP. One of their potential customer wanted the ESP to allow them to mail purchased lists. The customer even offered to indemnify the ESP and assume all legal risk for mailing purchased lists.
While on the surface this may seem like a generous offer, there aren’t many legal liabilities associated with sending email. Follow a few basic rules that most of us learn in Kindergarten (say your name, stop poking when asked, don’t lie) and there’s no chance you’ll be legally liable for your actions.
Legal liability is not really the concern for most ESPs. The bigger issues for ESPs including overall sending reputation and cost associated with resolving a block. The idea behind monetizing the complaint stream was making the customer bear some of the risk for bad sends. ESP customers do a lot of bad things, up to and including spamming, without having any financial consequences for the behavior. By sharing  in the non-legal consequences of spamming, the customer may feel some of the effect of their bad decisions.
Right now, ESPs really protect customers from consequences. The ESP pays for the compliance team. The ESP handles negotiations with ISPs and filtering companies. The cost of this is partially built into the sending pricing, but if there is a big problem, the ESP ends up shouldering the bulk of the resolution costs. In some cases, the ESP even loses revenue as they disconnect the sender.
ESPs hide the cost of bad decisions from customers and do not incentivize customers to make good decisions. Maybe if they started making customers shoulder some of the financial liability for spamming there’d be less spamming.

Read More