Resource hogging

Today on SFGate there was an article talking about how some Bay Area coffee houses were struggling to deal with workers who purchase one cup of coffee and then camp out all day using the free wifi. The final paragraph quoted one of the campers.

“We usually get one small coffee and stay for hours,” [Camilla Magrane] said. “Internet should be free.”

This type of resource abuse is obvious – customers can’t get tables to drink their coffee or have a quiet conversation with a companion. Less obvious is the type of resource abuse that ISPs have to deal with. Spammers avoid blocks by using botnets or frequently changing IP addresses (snowshoeing). ESPs open up tens or hundreds of connections at any one time. Delivery experts attempt to bypass published support channels and instead send direct messages to ISP employees hoping for a faster resolution to an issue.
All of these things use more than the sender’s share of resources and is very akin to buying a single cup of coffee and hogging up a table for a full day.

Related Posts

A series of warnings

Over the last month there have been a number of people sounding warnings about coming changes that ESPs are going to have to deal with. There has been mixed reaction from various people, many people who hear these predictions start arguing with the speaker. Some argue that our predictions are wrong, others argue that if our predictions are right then the senders will just start acting more like spammers.
I have put together a collection of links from recent blog posts looking towards the future and how things may be changing.

Read More

Blocking of ESPs

There’s been quite a bit of discussion on my post about upcoming changes that ESPs will be facing in the future. One thing some people read into the post is the idea that ISPs will be blocking ESPs wholesale without any regard for the quality of the mail from that company.
The idea that ESPs are at risk for blocking simply because they are ESPs has been floating around the industry based on comments by an employee at a spam filter vendor at a recent industry conference.
I talked to the company to get some clarification on what that spam filtering company is doing and hopefully to calm some of the concerns that people have.
First off, and probably most important, is that the spam filtering company in question primarily targets their service to enterprises. Filtering is an important part of this service, but it also handles email archiving, URL filtering and employee monitoring. The target market for the company is very different than the ISP market.
The ISPs are not talking about blocking indiscriminately, they are talking about blocking based on bad behavior.
Secondly, this option was driven by customer request. The customers of the spam filtering appliance were complaining about “legitimate” mail from various ESPs. Despite being reasonable targeted the mail was unrequested by the recipient. While ESPs use FBLs and other sources of complaints to clean complainers off rented or epended lists at ISPs, the option is not available for mail sent to corporations. Enterprises don’t, nor should they have to, create and support FBLs. Nor should employees be expected to unsubscribe from mail they never requested.
This option is the direct result of ESPs allowing customers to send spam.
Thirdly, this option is offered to those customers who ask for it. It is not done automatically for everyone. The option is also configurable down to the end user.
While I haven’t seen the options, nor which ESPs are affected, I expect that the ones on the list are the ones that the filtering vendor receives complaints about. If you are not allowing your customers to send spam, and are stopping them from buying lists or epending, then you probably have not come to the attention of the filtering company and are not on the list of ESPs to block.

Read More