Slashdot Mirror


The Measured Effectiveness of Blocking Asian Spam

fadden writes: "I recently started blocking IP addresses in China and Korea that were sending me spam. Instead of a blanket ban, I only blocked the subnets from which spam was being sent. After my first week of scanning and banning, I wrote up a report on the effectiveness of the blocks." In related news, SSKennel adds that: "The U.S. Federal Trade Commission has discovered (prepare to be amazed!) that revealing your email address in chat rooms can get you spammed. It claims to have taken action against spammers who harvest email addresses and use them to send fraudulent spam." Shocker!

11 of 378 comments (clear)

  1. Blocking subnets? Use SPEWS. by smnolde · · Score: 5, Informative

    Subject says it all. I block so much spam by using spews.

  2. How I block Korean spam by Jim+the+Bad · · Score: 5, Informative
    I just have KMail redirect all HTML formatted mail into the spam bucket. I check it once a day for the odd false positive - this is easy, as message titles in English stand out amoung all the Hangul ones. Only takes me a few seconds.

    On the other hand, 15 or so spams a day (in a language I don't even understand) every day is a major waste of bandwidth, and as irritating as hell.

    What can we do about this nusiance?

    --
    -- And when Justice is gone, there is always... Force. --Laurie Anderson, "Oh Superman"
    1. Re:How I block Korean spam by Binestar · · Score: 5, Informative

      While it is true that just dropping HTML can cause issues, you can still capture alot of spam by filtering on HTML e-mail without a CHARSET.

      :0 f
      * ^Content-type: text/html
      * ! html; charset=
      * ! from hotmail
      | ${FORMAIL} -A"X-Spammers: text/html only message"

      The above has *NEVER* given me a false positive in over 9 months of use.

      Also, I use 3 rules that block Fake Netscape/Hotmail/Yahoo e-mails. Basically, if the e-mail has a from address from either of those but isn't really from thier servers they get tossed as well.

      # hotmail-specific
      :0
      * ^(From|Return-Path):.+@hotmail\.com
      {
      &nbs p; :0
      * ^From: ".+" <[a-z0-9_.-]+@hotmail\.com>
      * ^X-OriginalArrivalTime:
      * ^X-Originating-IP: \[[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+]
      * ^Received: from hotmail.com \(\/...
      * $ ^Message-ID: <${MATCH}.+@hotmail\.com>
      { }

      :0 Efhw
      | formail -A "X-Spammers: fake hotmail"
      }

      # yahoo-specific
      :0
      * ^(From|Return-Path):.+@yahoo\.[a-z]+
      {
      &nb sp; :0
      * ^Message-ID: <([0-9.]+\.qmail|[0-9]+\.[0-9A-Z]+)@\/[a-z0-9-]+\. yahoo\.[a-z.]+
      * $ ^Received: from .+by $MATCH
      { }

      :0 Efhw
      | formail -A "X-Spammers: fake yahoo"
      }

      # netscape-specific
      :0
      * ^(From|Return-Path):.+@netscape\.
      {
      :0
      * ^X-Mailer: Atlas
      * ^Received: from +netscape.*MAILIN
      * ^Return-Path: <\/[a-z0-9_.-]+@netscape\.[a-z.]+
      * $ ^From:.*$MATCH
      * $ ^Received: from $MATCH.*by [a-z0-9.-]+\.aol\.com
      * ^Message-ID: <[a-z0-9]+\.[a-z0-9]+\.[a-z0-9]+@netscape\.[a-z.]+

      :0 Efhw
      | formail -A "X-Spammers: fake netscape"
      }

      Those 4 rules save me a big headache.

      --
      Do you Gentoo!?
    2. Re:How I block Korean spam by Qrlx · · Score: 5, Informative

      If you're in a corporate setting, then you should be installing Office from an Administrative Installation Point and have configured your install to override Outlook's default to send HTML, and changed it to Rich Text or Plain Text.

      They can always go up to the menu bar and change it if they suddenly decide they need to send HTML emails.

      By the way, I really, seriously, very strongly doubt that HTML mail format is necessary for your marketing group or whatever. I find it excpetionally unlikely that they are WRITING EMAIL IN HTML and that this is as core competency of your sales dogma. Most likely they are attaching files to email, which works fine with plain text.

      HTML email actually IS evil. There's completely no point to it. And in fact it's part of the spam problem: Let's say a HTML email contains a ref to some JPG somewhere. You read the (spam) HTML email, your 'puter dowloads the JPG. Congratulations, now the spammer can check his web logs and determinie how many people got the message! If s/he's really crafty, you could even tell which recipients got it by cross-indexing the HTTP GET request with the virtual file name you've set up like 01010012001012712.jpg -> sucker1001@hotmail.com. Now you put that name on your "known good accounts" list and sell it.

  3. Asian Pacific network by TheFlu · · Score: 5, Informative

    I started blocking off all Asian Pacific networks about 6 months ago. I wrote a quick Sendmail tutorial about it right here.

    How well does this work? Extremely well. I've gone from receiving 20 pieces of SPAM a day to only 1 or 2 (which Spamassassin typically catches. I realize that this method won't work for everyone, but it has worked out quite well for me.

  4. Cloudmark - Outlook 2k/XP users by exhilaration · · Score: 5, Informative

    If you're running Outlook 2000 or XP - Cloudmark is a nearly PERFECT solution to Spam - and IT'S FREE (for now, at least).

    1. Re:Cloudmark - Outlook 2k/XP users by spongman · · Score: 5, Informative

      I have noticed that many spammers are adding random crap to the end of their messages. This tactic is specifically designed to circumvent products like cloudmark. If you're running Outlook, try spambayes, it uses some pretty complicated statistics to determine whether or not an incoming message is spam, and it works surprisingly well. It requires a certain amount ofo technical knowledge to set up, though.

  5. Re:blocking ip's isn't enough by jensend · · Score: 5, Informative
    Where is the onslaught of OSS Bayesian filters?
    At Sourceforge. (Where else would you expect it to be?) That includes Bogofilter, POPFile, and a whole bunch of less-active programs. Searching for 'bayes spam' (Sourceforge uses OR searching by default) ought to get you more projects than you really want to look at. Mozilla is also looking at getting a similar filter- see bug 163188 at bugzilla.mozilla.org.
  6. Re:Fraudulent Spam? by doomdog · · Score: 5, Informative

    Yes, there is a difference between regular spam and the fraudulent variety. Normal spam is sent by well known "bulk mailers" (as they call themselves, in a pitiful attempt to legitimize their business) on a contract-for-hire basis.

    They send email directly from their own systems to your mailbox. They do not fake their headers, use open relays, hijacked proxies or root'ed boxes of other people to send out their messages. They generally have contracts with their ISPs to not cancel their connectivity as long as they have some type of proof, no matter how vague, that the mail *might* be considered opt-in (and as long as the complaints aren't too frequent. These people do listwash their own lists, if only to stop spamming people who actually complain about it, and also to show to their ISPs that they have an effective opt-out system. Their spam is annoying, but currently legal.

    Fraudulent spam, on the other hand, is completely different. These are the people that hijack other people's machines to do the dirty work, rape open relays and consume all of their bandwidth during spam runs, actively probe for open relays and proxies, forge everything they can in the headers, study SpamAssassin and other filters in an attempt to craft messages that don't "look" like spam. These are the people that use their opt-out lists as a source of revenue (by selling the names to other spammers), and will frequently joe-job spam activists and others who complain too loudly and to the wrong people...

    The first type of spammer sends out insurance offers, cell phones ads, inkjet ads and such. The second type sends out virus/trojan laden messages, porno by the bucketload, ads for illegal drugs, etc.

    Both types of spam are annoying, but the "fraudulent" type is much more so because of its immoral content (and anyone who thinks that sending pornographic images to children isn't immoral should quietly remove themselves from the gene pool) and also because of the theft of services (bandwidth, hard drive space, etc.) from the relays and proxies that they abuse.

  7. Re:Blocking subnets? Use SPEWS. by Anonymous Coward · · Score: 5, Informative

    I hate spews. spews is everything that is wrong with anti-spam work.

    There is no way to get off of the SPEWS blacklist, and if they black your entire NSP for one of the NSP's customers... tough luck for you. You can post to a usenet group and beg, and they wont do anything other than tell you to break your legal contract and go elsewhere. 20 people will harass you, and you can't even know which one to listen to.

    SPEWS can rot in hell. A properly configured SpamAssassin will block 98% of spam and have 0.01% false positives (I haven't gotten one false positive in a year, but I will someday).

    SPEWS is NOT how one prevents spam. SPEWS is how one pisses off the people trying to mail them.

    I can't stress enough how much I hate SPEWS and how much it should die.

    Please, please don't support SPEWS. I beg you.

  8. This works well for me by laing · · Score: 5, Informative

    A few months ago my spam level reached the point that made me do something about it. After looking carefully at all the headers, I concluded that about 80% of the junk (mostly from Asia) came from IP addresses with no reverse DNS database entry. (The IP did not resolve back into a hostname.) Just about all reputable mail exchangers have a reverse DNS entry. (The ones who don't are run by the clueless.)

    I decided to use this to my advantage. You can too.

    If your sendmail daemon uses the tcpwrappers library, you can create a /etc/hosts.deny
    file with "sendmail: ALL" and a /etc/hosts.allow file with "sendmail: KNOWN". (Make sure "sendmail" equates to 25 in your /etc/services file.)

    Doing the above will cause your mail exchanger to refuse incoming mail connections from any host with an unresolvable IP address. It will cut up to 80% of your spam.

    For the clueless ISPs, you can add exceptions to your /etc/hosts.allow file. (e.g. "sendmail:66.187.232." will allow mail from RedHat.)

    I wish more people would do this.