Slashdot Mirror


Lawsuits Against Spammers

apc writes "Pretty good overview of the state of the law regarding spammers, and some stories about people who have sued them and won. Nice to see the topic getting mainstream attention." It talks about several different states and several different people who have won cases. I still think its fairly hopeless, but I also believe forging SMTP headers should be legally punishable by castration.

13 of 355 comments (clear)

  1. www.xns.org by Anonymous Coward · · Score: 4, Interesting

    This is why XNS (a next generation DNS replacement) needs to be adopted ASAP by the worldwide technical community. For example, here is the white paper on spam filtering. In a nutshell, if someone who is not on your acceptable email list wants to send you an email, they must first (and this is all automatically handled by the software) accept an agreement which dictates your exact privacy requirements. If it is a personal email with actual valid content, clearly they will simply accept the agreement and automatically be added to your list. On the other hand, bulk email spammers (hereafter referred to as "Dickwads") will probably not like the section talking about your fees for accepting bulk advertising. :)

    1. Re:www.xns.org by johnburton · · Score: 5, Interesting

      I like this.

      But I can't see any reasable hope of pursuading people to replace DNS. But I suppose people won't care what kind of name lookup their email software is doing.... Hmm...

      Or what about something like ICQ where you can say who you want to be able to receive communciations from. Anyone else you have to authorize before they can send you an actual message. I doubt spammers could be bothered to do this, they'd go find some other way to annoy people.

      How about doing this?

      Your email program looks at the headers of emails being received. If the message is from someone in your address book, or is from someone you sent an email to *recently*, or is from a recognised mailing list then you get the email.

      If it does not fit any of those conditions, it must first validate the sender. To do this it sends back a message to the senders From address with instructions saying under what terms you are prepared to accept the email, and a code to send back saying that you accept those terms. Your client would then accept one, and only one message from that address to be delivered to you. If you want to accept more in future you can add them yo your local address book.
      The fact that the "spammer" must explicitly accept your terms for accepting your email would give a lot more legal protection to filtering and blacklists of known spammers.

      Hmm. Must think about this some, and implement something!

      --
      Sig is taking a break!
  2. Put the ball in the court of the ISP by smack_attack · · Score: 3, Interesting

    The simplest reasons that spammers "get away with it":

    1) Forged headers (SMTP auth would alleviate)
    2) ISPs turn a blind eye or aren't as responsive as they should be. Many are repeat offenders which labels them "soft" on spam prevention.

    A lot of people have already commented on #1 so I'm going to skip that one.

    In short, the accountability should come to the ISP, because they are the ones you inevitably allow this to happen. @Home or similar could implement a per day limit on outbound emails, same for the fre services, Yahoo! and Hotmail. There needs to be a clearinghouse for spam notification, someone who tracks spam and spammers, period. Fines should be imposed on ISPs who allow bulk email to originate from their service. Their choice should be simple: don't let spam originate from your system or face the penalty (steep fines, this could be used to fund the clearinghouse). Leniency could be worked into this, an ISP may have X number of reports per day based on the number of IPs they have. X should shrink every year.

    The clearinghouse should also be audited on a yearly basis and the results made public (what ISPs spam the most/least, amount of fines paid, etc)

  3. RBL and SpamAssassin by Gothmolly · · Score: 4, Interesting

    I run my own mail server, running qmail with the rblsmtpd daemon, pointing at several "underground", i.e. not for pay, black hole lists. In addition, there are spam _content_ filtering tools out there such as spamassassin, which looks for common telltale fingerprints in email. WORK FROM HOME, MAKE MONEY FAST, etc. etc. etc.

    It can be done, with a little work.

    --
    I want to delete my account but Slashdot doesn't allow it.
  4. Re:Technical solution by cmowire · · Score: 4, Interesting

    I think a better resolution to the problem is to enforce a certain amount of purity in the mail headers.

    If you are spam, you should mark your message as being such. If you are a mailing list, you should mark your message as being such.

    And then we need to have a network of trust between the mail servers. Something lightweight enough that it works 90% of the time. Servers who are trusted are trusted that they will send out mail with proper headers. Servers who aren't trusted will get their mail bounced most of the time.

    Thus, spam can be dropped on the floor at the option of any mail server. And server admins who don't mark spam as spam are marked as untrusted servers. At the option of the country that the mail server exists in, this can be declared as fraud.

    I wrote up some notes on it on my webpage but I'm not sure how well it would really work in practice.

  5. The laws in iowa by autopr0n · · Score: 3, Interesting

    I was delighted the other day to find out that Iowa had an anti-spam law. I promptly requested 'remove' on all the 'psudo-opt-in' type spam (no, buying a list from someone does not mean that the people on it want your crap). Of course, under Iowa law I need to opt out before I can do anything, unless the spam is forged.

    One of the 'university diploma' spams was illegal under Iowa law (invalid return address), but, of course how do you sue for something like that? I tried looking on reverse phone number sites to see who owned the phone number advertised, but nothing showed up.

    Are there any ways to find out who sends these out without incurring a large expense?

    Hrm, I wonder how long before someone starts sending out "make money suing spammers, call today for your free kit." spam.

    --
    autopr0n is like, down and stuff.
  6. Are the lawsuits worth it? by btempleton · · Score: 4, Interesting

    I've sued phone spammers, the type who use a machine that calls people and plays a recording, which as been blatantly illegal for almost 10 years.

    I've won, but it takes more work than the $500 you win is worth even when you do win, and on average it's something you do only on principle and not for money.

    And thus few do it. When I have been in court the judges/commissioners have said they don't often (if at all) see these cases.

    Laws are not the answer to spam. In spite of what people say it is not just a question of "it's not a free speech issue it's a property issue."

    Spam involves rights in conflict. It's a free speech issue AND a property issue AND a privacy issue, all in one. The answers are not so simple as these laws suggest.

    --
    Has it been over a year since you last donated to the Electronic Frontier Foundation
  7. Laws define both sides by coyote-san · · Score: 4, Interesting

    The problem with a national law, with any law, is that it defines "safe turf" for both sides.

    If Congress debated such a law, I'm sure that the DMA would yell and scream and "compromise" that it is willing to make it illegal to send unsolicited email of a criminal nature. Outlaw the pyramid schemes, outlaw the cock&tit creams that don't have FDA approval, etc.

    Meanwhile, in the same spirit of compromise, it's now Federal law that companies can ignore repeated requests that you be removed from their spam lists because you have a bona fide business relationship. It doesn't matter that this "relationship" was a one-time purchase of a Christmas present a decade ago for a person who's long been out of your life - you might need another left-handed bacon turner some day and if they can't sent you reminders, you'll buy it elsewhere!

    Likewise the legislation would undoubtably protect affiliated businesses - the reason I briefly got investment solicitations from my car insurance carrier, until I made it clear they were about to lose the latter account. It will even protect attempts to woo you away from existing businesses - you drive, so therefore you should hear about Fly-By-Night insurance rates. And Bob's detailing shop. And on and on and on....

    I'm not saying that legislation would never be appropriate, just that it's too early to do it at the national level. Let's get a clear concensus that spam is a problem, then use the federal law *only* to normalize things like mandatory subject lines.

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
  8. another tactic? by Alien54 · · Score: 5, Interesting
    I saw this idea else where, and it looks promising enough that I want to share ....
    One could extend the SMTP protocol for mail delivery so that (non-favored?) senders were forced to jump through some computationally expensive hoop before mail to local users will be accepted.

    Currently SMTP looks like this:

    >>> 220 mailhost.domain.com ESMTP Sendmail 8.9.9/8.9.9; Fri, 11 Jan 2002 16:05:32 -0500 (EST)
    >>> HELO host.domain2.com 250 mailhost.domain.com Hello host.domain2.com [155.108.129.30], pleased to meet you
    >>> MAIL From: 250 ... Sender ok
    >>> RCPT To: 250 ... Recipient ok
    >>> DATA 354 Enter mail, end with "." on a line by itself 250 QAA00187 Message accepted for delivery
    >>> QUIT 221 mail.domain.com closing connection

    We could add something like (not real numbers):

    >>> 220 mailhost.domain.com ESMTP Sendmail 8.9.9/8.9.9; Fri, 11 Jan 2002 16:05:32 -0500 (EST)
    >>> HELO host.domain2.com 250 mailhost.domain.com Hello host.domain2.com [155.108.129.30], pleased to meet you
    >>> MAIL From: 250 ... Sender untrusted, please give prime factor of 34576184516935692342934759132 to continue
    >>> FCTR 345837413 250 Ok, you bothered...
    >>> RCPT To: 250 ... Recipient ok
    >>> DATA 354 Enter mail, end with "." on a line by itself 250 QAA00187 Message accepted for delivery
    >>> QUIT 221 mail.domain.com closing connection

    The beauty of this is, putting support in sendmail would mostly be sufficient, and it lets you effectively add a cost per message without any sort of micropayments scheme, or giving up anonymity. I'd be curious what your reader groupmind thinks about this, or if the idea has been tossed around before?

    - Mike Earl

    Personally, I do not know the feasibility of this angle, although I am sure some expert with be willing to point out the flaws.
    --
    "It is a greater offense to steal men's labor, than their clothes"
    1. Re:another tactic? by tomstdenis · · Score: 3, Interesting

      Well that will work, there are other schemes.

      I'm a student cryptographer and I'm working on a system which will provide authentication [signatures], privacy [via encryption] and at the same time make spam less feasible [you can do it but its easier to filter out].

      The basic idea stems from squaring modulo a composite. Say you're given N=pq where p and q are two huge primes.

      You can find

      R = K^(2^T) mod pq

      easily, but given R its hard to find K.

      So if you specifically construct K to follow certain rules, you can help filter out spam very easily.

      The basic scheme works like this

      1. Make up two primes p and q and get N=pq
      2. Choose a value of T [say 1024]
      3. Publish N and T with your email address

      The user wants to send you a message M so they make up

      K = random_data || HASH(M) || time

      They hash K and use that as a key for a symmetric cipher. Then they send R=K^(2^T) mod N [by squaring T times] along with the ciphertext.

      The trick is that finding K from R is easy if you know the factors and squaring T times takes time.

      You can sign K easily too ... anyways...

      --
      Someday, I'll have a real sig.
    2. Re:another tactic? by reynaert · · Score: 3, Interesting

      How would you decide how difficult the problem should be? Believe it or not, but there are people using email on XT's. Or take Arache, a graphical browser+email+... that works fine on a 386. Those people would in effect unable to send email.

  9. Try the police and the attorney general. by TheMCP · · Score: 3, Interesting

    Try calling your state's attorney general's office and explaining the situation to them. Sometimes they can be surprisingly helpful, particularly if you can do a good job of explaining yourself (like pointing out repeatedly that they're doing this *incredibly* *loathesome* thing in *your* *name* and that it's just *destroying* the good name of your business) and can come off as genuinely hurt and confused.

    If you got any threatening complaints about the spam, you could bring those up too, and claim that you fear for your life because of what this person is doing in your name.

    The police might be willing to help, too.

    You have public law enforcement resources. Use them. It's not just the RIAA and MPAA that have a right to call in the cops. You do too. Go for it. If THEY catch the spammer, and prosecute them for identity theft, defaming you, or whatever, the spammer will be in for a lot worse than having their relay shut down.

  10. Class action lawsuits by MillionthMonkey · · Score: 4, Interesting

    I think companies like MSN/Microsoft/Hotmail, yahoo, excite and @home should be doing the suing.

    Well, maybe, perhaps not. Companies will sue if it's in their interest. If their network becomes good enough to handle the congestion from spam, and the amount of spam doesn't vary too much as a customer moves from ISP to ISP, it's conceivable that the providers might begin to view spam as the customer's problem (as they pretty much do now). And even if they do start suing- who benefits from that directly? Besides the obvious value as a deterrent to spammers, there isn't much justice being done if the plaintiffs are all going to be large ISPs. The parties most damaged by spam are the end users and especially the smaller ISPs.

    I always thought class action lawsuits by the actual recipients of spam are the most logical way to counter spam if the approach is going to be via the courts. After all, have you ever received a single, individual spam that's caused you to consider taking the case to court against that particular spammer, with lawyers and court costs and all that hassle? With a judge that might ask "well why didn't you just hit delete?" And getting that single spam email message isn't really what you're suing over. It's the degradation of your daily routine, the tedium of having to delete a hundred emails a day year in and year out, the loss of almost a day of your life per year deleting countless messages about herbal Viagara and credit repair software and diplomas from prestigious non-accredited universities and hair loss and government grants info packages and an EZ way to consolidate debt and reducing all payments by 60% and frisky teens. Going to court over a single spam seems to miss the point. And it's expensive and inconvenient to sue as an individual, so a spammer might very well recognize that his individual spam probably isn't going to elicit a lawsuit if it isn't outrageous enough for a spammed plaintiff to choose as THE spam (out of the 10000 in his box) that he's going to go to court over. In fact, people tend to sue when the spam particularly offends them (e.g. when it talks about sex with minors, or has nude photos in it and is received by a minor). Unless things proceed to the point where every spam message sent out results in a lawsuit, a spammer that keeps his emails polite and sticks ADV in the header is pretty much safe from being sued. So you don't even get much of a deterrent effect.

    Unless we switch to using class action suits, which don't have these problems if someone with the resources starts consistently nailing all spammers with them. It's much easier than taking a case to court yourself. Someone is doing the suing for you and you get to hang on like a million other freeloaders and enjoy the fruits of your class action. I almost wouldn't mind getting spam if I knew there was a chance that I could stick it to the spammer for a few cents along with thousands of other people. If I even got a fraction of a penny on average per message, we could still be talking about some serious money. And it certainly wouldn't be too hard to set up. In fact (if this were 1999) you could probably build a dot-com out of it somehow, to coordinate the spam submissions, identify plaintiffs and defendants, litigate in court, hire collections agencies, and process the payments back to all plaintiffs. That's more of a business plan than many dot-coms had. I think that if there weren't so many jurisdictional problems with the idea in general (and if there were more spam laws) someone would try this.

    I mean now I think that Microsoft has something to do with bestiality. How do I know that it wasn't really from them??

    Strictly speaking, even if it turns out the email wasn't from Microsoft, it still doesn't prove that Microsoft has nothing to do with bestiality.