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?

Related Posts

Update on Yahoo and the PBL

Last week I requested details about Yahoo rejections for IPs pointing to the PBL when the IP was not on the PBL. A blog reader did provide me with extremely useful logs documenting the problem. Thank you!
Based on my examination of the logs, this appears to be a problem only on some of the Yahoo! MXs. In fact, in the logs I was sent, the email was rejected from 2 machines and then eventually accepted by a third.
I have forwarded those logs onto Yahoo who are looking into the issue. I have also talked with one of the Spamhaus volunteers and Spamhaus is aware of the issue as well.
The right people are looking at the issue and Spamhaus and Yahoo are both working on fixing this.
Thanks for the reports and for the logs.

Read More

Yahoo and Spamhaus

Yahoo has updated and modified their postmaster pages. They have also put a lot of work into clarifying their response codes. The changes should help senders identify and troubleshoot problems without relying on individual help from Yahoo.
There is one major change that deserves its own discussion. Yahoo is now using the SBL, XBL and PBL to block connections from listed IP addresses. These are public blocklists run by Spamhaus. Each of them targets a different type of spam source.
The SBL is the blocklist that addresses fixed spam sources. To get listed on the SBL, a sender is sending email to people who have never requested it. Typically, this involves email sent to an address that has not opted in to the email. These addresses, known as spamtraps, are used as sentinel addresses. Any mail sent to them is, by definition, not opt-in. These addresses are never signed up to any email address lists by the person who owns the email address. Spamtraps can get onto a mailing list in a number of different ways, but none of them involve the owner of the address giving the sender permission to email them.
Additionally, the SBL will list spam gangs and spam supporters. Spam supporters include networks that provide services to spammers and do not take prompt action to remove the spammers from their services.
The XBL is a list of IP addresses which appear to be infected with trojans or spamware or can be used by hackers to send spam (open proxies or open relays). This list includes both the CBL and the NJABL open proxy list. The CBL list machines which appear to be infected with spamware or trojans. The CBL works passively, looking only at those machines which actively make connections to CBL detectors. NJABL lists machines that are open proxies and open relays.
The Policy Block List (PBL) is Spamhaus’ newest list. Spamhaus describes this list as

Read More

7th circuit court ruling in e360 v. Spamhaus

Mickey has some commentary and the full ruling up on Spamsuite. In short the appeals court affirmed the default judgment, vacated the judgment on damages and remanded the case back to the lower court to determine appropriate damages.
There are a couple bits of the ruling that stand out to me and that I think are worthy of comment.
Spamhaus made a very bad tactical decision by initially answering and then withdrawing that answer. The appeals court ruled that action signaled that Spamhaus waived their right to argue jurisdiction and that they submitted to the jurisdiction of the court. Based on this, the appeals court upheld the default judgment against Spamhaus. Not necessarily the outcome any of us wanted, but that doesn’t set any precedent for future cases unless defendants answer and then withdraw the answer. Specifically on page 12 of the ruling the court says:

Read More