Monthly Archive for August, 2008

A whole year?

It is, in fact, one year today that I started blogging. My first real post came on August 30, 2007… discussing the e360 v. Spamhaus case. And look, here I am, a year later still discussing the e360 v. Spamhaus case. The end of that first post said:

Overall I think the ruling is generally what we could have expected. I’m quite pleased that the court affirmed that Spamhaus may legally list senders that comply with CAN SPAM. I am also eager to see what happens during discovery for damages.

I think the answer is nothing happened other than e360 repeatedly and painfully shot themselves in the foot.

Thanks for reading for the past year. And even more thanks for some great comments and discussions. Have a good 3 day weekend.

6 Comments

Spamhaus files for dismissal of e360 case

Spamhaus filed a motion today asking the judge to dismiss the e360 v. Spamhaus case for contempt. Mickey, as usual, has the docs up.

I have not posted much on the case recently, as there was only legal wrangling about discovery going on. The biggest problem being that e360 has dragged their feet, stalled and avoided discovery for the last 8 months. They have missed deadlines, turned over incomplete documents and ignored depositions. Since I last wrote about this case, discovery has been extended multiple times, the judge has compelled e360 to turn over docs and information and he sanctioned e360 for their failures to comply.

From my perspective, Spamhaus’ lawyers have been setting the stage for this motion for the last 4 - 5 months. Their interactions with e360’s lawyers, their motions to compel and their motion for sanctions have all formed a narrative of how e360 is stonewalling discovery.

This particular motion is only about 8 pages long, but references a 125 page exhibit. The very large exhibit is mostly documents that have been published before in the “Motion for Various relief due to Persistent Discovery Defaults” filed in July.

In the July motion, Spamhaus’ lawyers detail their repeated efforts to get discovery from e360, and the utter lack of cooperation. One of my favorite bits is that e360 responded (weeks late) to some of the initial interrogatories with (paraphrased), “It is too hard to write all this down, but we will tell you about it in the depositions.” My understanding of the law is that this is, in and of itself, a bit of a no-no. What really puts the icing on the cake, though, is that e360 then skipped 2 properly noticed depositions. They just did not appear, thus making their answers to the interrogatories utterly meaningless.

Spamhaus requested that the Judge impose sanctions on e360 for failing to appear at 2 depositions, not complying with the judge’s previous orders and generally being unable to actually produce any documentation that is complete or on time. Even better, when e360 did manage to produce a thumb drive it contained multiple email conversations between Mr. Linhardt and his lead counsel. This little oops happened because no one at the law firm bothered to actually examine any of the files before handing over the thumb drive. In fact, they only became aware of their error when opposing counsel notified them of the files. When e360 asked for the information back, Spamhaus’ lawyers refused pointing out that they handed over all the information willingly and that their failure to actually examine the files does not constitute an inadvertent disclosure.

The judge did sanction e360, although not with the severity that Spamhaus’ lawyers requested. He also ordered full discovery and documents turned over by August 15th. Based on my reading of the transcript (exhibit 4) the Judge sounds like he is tired of having to tell the e360 lawyers to do their jobs. The judge lectured e360 on their failure to get thing resovled.

You should have acted — your side, not you personally, but your side should have acted — sooner to get this resolved.

And it [sic] is no place in discovery that you say, “These are the only terms that we are going to agree to before a deposition goes forward,” and, then, not show up. You do not have that right or privilege. And you imposed on them and frustrated them in this whole proceeding.

So, that is how we are going to do business.

And there is going to be, in addition to paying for the court reporter, you have to pay $200 to the other side as fees for — as a sanction for — them having to present this motion and me having to resolve it. Okay?

So, that is how we are going to do business.

The judge then moved on to address the issue of sanctions.

So, I will not foreclose Linhardt’s future participation, but he needs to be deposed.

And if there is any problem in scheduling the deposition, I am going to issue even more sanctions. Okay?”

Finally, the judge made it very, very clear that e360 had to answer the interrogatories and could not fall back on producing documents (emphasis added).

Interrogatories, even if there is perhaps some duplication in the information-gathering process, interrogatories cannot be challenged because sometime later somebody may speak to those. That is not a fair ground for not answering otherwise legitimate interrogatories.

So, those need to be answered within the next two weeks. [...]

It is one thing to say, “Here, look at these documents and let the other side go fishing and searching for an answer. And it is similar to that where you may narrow the reference to a specific document and even to some general group of information on [sic] that document.

But, in this instance, I am going to require specificity in the answer because you have already overused your ability to say, “Here is what is responsive to the interrogatory, but not in answer form,” by giving them a bunch of stuff you are going to make them look through, try and search for an answer and be frustrated in the process.

You sacrificed your opportunity to use that legitimately. So, the idea you are going to reference documents and say. “It is in there,” and narrow the field that they have to look at, is not presently sufficient.

If the answer is in there — if you say the answer is in there responsive to their question — it does not take a whole bunch of extra work for you to take the document and write the answer down to the interrogatory.

There has been enough of this recalcitrance and being sufficiently precise and responsive to inquiries.

And for you to come back here all the time with this kind of stuff is taxing on my patience.

Sounds like an unhappy judge to me. One who is going to be even more unhappy when he discovers that e360 did not take the opportunity he gave them to recover from their multiple errors, but instead ignored this deadline.

I am amazed that the plaintiffs in this case just cannot seem to get it together and actually demonstrate they had any basis for a multi-million dollar claim against Spamhaus. At the July 30 hearing, the judge gave e360 another chance, but promised more sanctions if they did not follow through. Another month, more failures in follow through and another motion before the judge. The only question in my mind is: how far will the sanctions go? Will he actually dismiss the case? Or will he give e360 one more chance?

0 Comments

Data Integrity, part 2

Yesterday I blogged about eROIs contention that consumers should not be wasting the time of lead gen companies by filling in fake data. There were lots of good comments on the post, and I strongly encourage you to go read them if you are interested in different perspectives on the data issue.

One of the arguments I was making is that people are only going to give accurate information if they trust the website that is collecting information. I do, strongly, believe this. I also believe very strongly that websites collecting information need to do so defensively. It is the only way you can get good information.

This ties in with an earlier post about a website that collects email addresses from any visitor, then turns around and submits those addresses to webforms. Hundreds of mailing lists have already been corrupted by this group. They are a prime reason companies must design address collection process defensively. There are people who do bad things, who will take an opportunity to harass senders and recipients. This company is not the first, nor will they be the last to commit such abuses.

Taking a stand against abusive companies and people may be useful, but that will not stop the abuse. It is much easier to design process that limits the amount of abuse. For lead gen, in particular, confirmed opt-in is one way to limit the amount of bad data collected. As a side effect, it also results in less blocked mail, fewer complaints and better delivery.

1 Comment

Who is responsible for data integrity

Yesterday, Ken Magill wrote about his experience with the Obama campaign’s open and unconfirmed marketing list. Ken, to see just how open the Obama subscription form was, subscribed using a valid email address but the name of Stupid Poopypants. As expected, mail to Ken from the Obama campaign was addressed to Stupid.

eROI uses this as an example of people who ruin their ROI by filling fake data into forms and ends their post by addressing Ken as follows:

I think that as someone that covers the industry and espouses the things that make us strong, tear us down, threaten our industry, and lift us up… you of all people should be helping us out and not hurting us.

I have known Ken for a while, and done a few interviews with him over the years. He has never pulled punches. Ever. It is not what he does. His job is pot-stirring. In this case he is stirring this pot by pointing out the poor subscription practices of the Obama campaign.

From my perspective, the problem is not that Ken gave the Obama campaign Stupid Poopypants as his name, the problem is that the Obama campaign is not doing any data verification. Ken did give the campaign a valid email address, but there was no reason he needed to do so. Anyone could have signed up Stupid Poopypants and put in Ken’s address.

Ken was pointing out the poor data collection process with this experiment and based on their post the point flew right over the heads of the folks at eROI. People are going to put fake data in forms online and there is not any way to stop them from doing this.

This process is much more a reflection on data collectors than on the individuals signing up. Senders and marketers online have spent a lot of time collecting information and sending marketing to people. At this point in time people do not want more marketing in their inbox, or on their phone, or in their postal box. they do not trust that a company will respect their opt-in preferences. So they provide false data. The subscriber does not trust the collector to respect the subscriber, and so the subscriber takes protective action against the collector.

If what eROI says is true, “data integrity is everything to our industry” then people collecting data should be prepared to actually spend a little effort to not let subscribers pollute their data. If eROI lets any moron on the internet put information in their form, and then expects the data to be good then I just have one question to ask eROI: Are you new to the Internet or something??

hat tip: Box of Meat

Followup posts: Data Integrity Part 2 and Yet More Data Verification

14 Comments

Collecting information from subscribers

VerticalResponse Blog has a post up about collecting information from subscribers to mailing lists. Go check it out.

0 Comments

Interview with Matt Blumberg

Mark Brownlow posted an interview with Matt Blumberg, CEO of ReturnPath, about the merger with Habeas. It is well worth a read.

I have not yet commented on the merger and how this is going to affect the delivery industry because I am not sure how it will. Some of the effect is dependent on what ReturnPath does with the two companies and how their policies change. Here at Word to the Wise, we have known the folks at both companies for a very long time.

One thing that strikes me about this merger is that it means there are few direct competitors left in the delivery market. Everyone currently in the whitelist / delivery certification market seems to have a slightly different target audience and slightly different business model.

ReturnPath has SenderScore Certified and the Safelist. To get on these lists senders must meet criteria that, while filtered through ReturnPath, are set by the ISPs. Many senders find that they can get consistently high inbox delivery just by meeting the ISP standards, even if they are not SenderScore Certified or on the Safelist. However, certification does provide senders with an assurance that they are meeting standards.

Goodmail has their CertifiedEmail product. While certified senders must also meet criteria, they are also paying ISPs for delivery. I have always seen the Goodmail product as more focused on and more valuable for transactional senders rather than other senders. This slightly overlaps with ReturnPath’s target market, but the senders in this market do have different needs pressures.

ISIPP has their SuretyMail product. This provides a framework for senders to make statements about the email they send in a way that receivers can reliably query. This is a slightly different approach, in that ISIPP does not classify mail for their customers, but allows customers to self-classify. The benefit of ISIPP is that the ISIPP framework is trusted by their receiver-users and can push back on ISIPP if customers incorrectly self-classify.

Different markets, different business models, different approaches.

7 Comments

Challenge/Response

Christopher Breen at Macworld posts about a major pet peeve of mine.

Let’s suppose you’ve sent me a message asking for help with a Mac problem. I take time out of my day to find an answer and reply. I’m rewarded for my effort with an automated reply that begins:

I apologize for this automatic reply to your email. To control spam, I now allow incoming messages only from senders I have approved beforehand.

As someone who has multiple free resources up on the web and gets questions about them from random people who stumbled on them nothing annoys me more than spending time answering a question and having the mail bounce back to me.

Hat tip: Mickey

1 Comment

EmailAppenders

Al points out that EmailAppenders are possibly trying to change their online reputation. To bad their “suggestion” does not work.

4 Comments

SpamZa: corrupting opt-in lists, one list at a time

A number of ESPs have been tracking problematic signups over the last few days. These signups appear to be coming from an abusive service called SpamZa.

SpamZa allows anyone to sign up any address on their website, or they did before they were unceremoniously shut down by their webhost earlier this week, and then submits that address to hundreds of opt-in lists. This is a website designed to harass innocent recipients using open mailing lists as the harassment vehicle.

Geektech tested the signup and received almost a hundred emails 10 minutes after signing up.

SpamZa was hosted on GoDaddy, but were shut down early this week. SpamZa appears to be looking for new webhosting, based on the information they have posted on their website. 

What does this mean for senders?

It means that senders are at greater risk for bad signups than ever before. If you are targeted by SpamZa, you will have addresses on your list that do not want your mail. Some of those addresses could be turned into spam traps.

  1. Check your signups. If you see hundreds of signups coming from the same IP address over a very short period of time, treat them carefully. There are a number of things a sender can do to limit the impact on a list.
    1. Delete the addresses coming from a single IP
    2. Confirm the addresses coming from a single IP
  2. Implement confirmation. Start using closed loop opt-in (double opt-in) on new signups going forward. This will keep future incarnations of SpamZa from corrupting a list. It will also prevent lists from acting as attractive nuisances.
  3. Do not trust vendors. Senders who are are buying a list or using a co-reg provider must confirm all the addresses before mailing them. There are some suggestions that the SpamZa people are selling addresses. Senders must protect themselves and their assets.

The one thing a sender absolutely does not want to do is add any SpamZa collected addresses to a mailing list. This is not a problem that will go away, it is out there in the wild now. This is the time to start implementing protections, not after the horse has left the barn. Confirmation is one of the better ways to protect an asset against this type of interference.

Followup post: Yet More Data Verification

1 Comment

Blog Olympics - Passing on the stick

Given that it is August and a lot of people are on vacation and it seems to be a general low point in getting things done at work, I expect blogging to be light through the end of the month. Once everyone gets back in September, I will have a more substantive posts up more regularly. Happily, EmailKarma helped me with a somewhat fluffy post today. He tagged me into the Blog Olympics meme. The rules say I am supposed to pick 7 blogs I read and tag them forward. The rules also state that I have to link back to the blog that passed on the stick to me but I cannot add it to the list of my favorite 7 blogs.

I limited my picks to email related blogs. Now, in no particular order (vaguely the order they show up in my RSS feed, but nothing actually that specific):

Enjoy! No tags back!

2 Comments