Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Spam The Internet Your Rights Online Technology

Why Blacklisting Spammers Is A Bad Idea 396

Posted by timothy from the painting-with-machine-gun dept.
Roland Piquepaille writes "For the last two months, an eternity in Internet time, I was unable to reach -- and to contribute to -- Smart Mobs, the collective blogging effort around the next social revolution initiated by Howard Rheingold. Why that? Because an unknown customer of Verio decided it was a spamming site and asked the company to blacklist the site. Verio complied -- probably without even checking it -- and my problems started. It took me dozens of e-mails and phone calls and two visits to the headquarters of my french ISP, Noos, to fix the situation. More about this horror story is available here."
This discussion has been archived. No new comments can be posted.

Why Blacklisting Spammers Is A Bad Idea More

Why Blacklisting Spammers Is A Bad Idea

Comments Filter:

  • ORBS (Score:5, Insightful)

    by olman ( 127310 ) * on Sunday November 09, 2003 @05:19PM (#7430331)
    And other RBLs require usually multiple reports from multiple sources. And you have fairly straightforward way of getting de-listed, too.

    What's with the current boo-hoo over blacklists? Do we have some kind of spammer astroturf going here?

    • Overzealous users (Score:2, Insightful)

      by Anonymous Coward
      I use blacklists to mark probable spam, but still generally see it. Recently, some people had reported an email from GoDaddy (domain registrar) that was only sent to customers, and it was asking them to very information. If, say, my ISP was blocking email from them based on this, I'd never see it. ISP's should err on the side of caution, let users take more risks if they personally desire.

    • I don't necessarily think it's astroturfing; it's a legitimate problem, and will continue to happen. OTOH, there are possible solutions, not only to this problem, but others as well. DBP, anyone? [jpj.net]

    • Re:ORBS (Score:4, Insightful)

      by t0ny ( 590331 ) on Sunday November 09, 2003 @09:03PM (#7431411)
      This sounds more like a complaint about the potential for human error, rather than a complaint about the idea or technology itself.

      Rather silly, Slashdot. I suppose next we will have an article saying how security is evil, because some LUser gave his password to a hacker who phoned in posing as tech support. Or even that DNS is evil, because someone can hijack your listing (which was posted a few days ago...)

    • Re:ORBS (Score:5, Insightful)

      by PurpleFloyd ( 149812 ) <zeno20@attbi.cFORTRANom minus language> on Monday November 10, 2003 @01:26AM (#7432393) Homepage
      The current "boo-hoo" over blacklists can be mostly summed up by one word: SPEWS.

      They operate on the "nuclear bomb" method: list spammers, plus anyone using a "spam-friendly" mailserver (a definition that can be stretched to cover almost anyone) or anyone who is simply "suspicious." Oh, and you might also be listed if your new IP block was once used by a spammer. Don't worry, though. You can just wait a few weeks and lose massive amounts of buisiness because many customers can't recieve email from you and have no idea why - they just think you aren't responding. Or you can go onto NANAE and post a delist request, which will get you nothing but "Whiner! Eat your SPEWS, it's good for you!"

      To be sure, a large portion of the problem comes from ISPs implementing SPEWS incorrectly - silently dropping all IPs listed, not just tagging level 2 and dropping only level 1 (confirmed spammers), and the spammers have created this problem themselves. However, SPEWS' "list 'em all, let God sort 'em out" approach is irresponsible, particularly when they know that ISPs are applying the filtering with a wide brush.

      • you sir, are an idiot. (Score:3, Interesting)

        by RMH101 ( 636144 )
        your ISP has explicitly signed up to SPEWS because it works. it works because it encourages ISPs to be RFC compliant. it's for the greater good: i don't *care* if it breaks your email to your mom on a blacklisted ISP: it's your ISP's business decision to ignore spam complaints and become spam-friendly. natural selection says their customers get pissed off (step one: looks like it's working so far) and then jump ship to an ethical ISP. eventually the spamhauses go bust.

      • Re:ORBS (Score:5, Insightful)

        by Eggplant62 ( 120514 ) on Monday November 10, 2003 @06:15AM (#7433017)
        [SPEWS] operate[s] on the "nuclear bomb" method: list spammers, plus anyone using a "spam-friendly" mailserver (a definition that can be stretched to cover almost anyone) or anyone who is simply suspicious." Oh, and you might also be listed if your new IP block was once used by a spammer. Don't worry, though. You can just wait a few weeks and lose massive amounts of buisiness because many customers can't recieve email from you and have no idea why - they just think you aren't responding. Or you can go onto NANAE and post a delist request, which will get you nothing but "Whiner! Eat your SPEWS, it's good for you!"


        Incorrect characterization of SPEWS methods. From my own personal observations, a SPEWS listing starts out with the spammer's IP addresses based on spam received at multiple spamtrap accounts. Complaints are filed by the people who run the SPEWS list and, of course, they do not identify themselves as SPEWS operators in those complaints. Some time elapses (I'm not SPEWS, how should I know how much time exactly?). Either the spammer is removed (Yay! The listing drops off the list) or the complaints go ignored and more spam is received at the spamtrap accounts. The listing gets widened to the /24 in which the spammer space is included (this may happen immediately in the case of a spammer identified by Steve Linford's ROKSO (Registry of Known Spam Organizations) at spamhaus.org [spamahaus.org] (may be difficult to reach due to the Slashdot effect or DDoS by virus)).

        Lather, rinse, repeat the above until someone at the responsible ISP who received the original complaints wakes the fuck up and notices the situation, usually after their own customers are screaming at them, asking them to fix the problem that got them blocklisted. Then again, this is all laid out in the SPEWS faq [spews.org] in fairly clear, easy to understand language.

        If ISP's are dropping mail from both level1 and level2 listings, they've made their own bed and are now laying in it. Only an idiot would block on level2 listings as they are meant as an historical indicator of problems with an ISP and do age off after an indeterminate period of time, again outside my control or knowledge.

        SPEWS is the only thing thus far in the war against spam that actually has an effect at the ISP level to get some of these outfits to wake the fuck up and see what's happening in their own abuse@ mail accounts. ISP's think they can continue to shine on the spam problem, thinking they have no responsibility for their customers' actions. We, the users of SPEWS blocklist, say otherwise.

        If I decide I don't want mail from a corner of the Internet that has sent me nothing but spam, that's my right. If I decide to rely upon the opinion of another Internet service who tracks this kind of information for themselves and elects to share it with the public, that's my right also. SPEWS works for me and mine.

        • Yeah, whatever, moron (Score:3, Interesting)

          by MattW ( 97290 )
          You're good with the SPEWS line, there, but there's good reasons why any admin with a clue doesn't use that fucked up list.

          (1) SPEWS is ineffective. It might have some effect if your goal is to drive spammers away from a given ISP, or drive customers in general away from a given ISP. But it won't significantly reduce the amount of spam you get compared to using the lists with a philosophy that involves far less collateral damage. But by using SPEWS, you WILL block hundreds or thousands of times more legiti

  • Just (Score:4, Funny)

    by SargeZT ( 609463 ) * <pshanahan@mn.rr.com> on Sunday November 09, 2003 @05:20PM (#7430335) Homepage
    Break into the lobby of the ISP, guns in hand, and force them to remove the site from the blacklist. It's what I do when I'm pissed.

  • Why Blacklisting Spammers Is A Bad Idea (Score:5, Insightful)

    by wo1verin3 ( 473094 ) on Sunday November 09, 2003 @05:22PM (#7430343) Homepage
    This article should have been called...

    "Why it's important to have good policies and procedures in place when blacklisting spammers"

    • Re:Why Blacklisting Spammers Is A Bad Idea (Score:5, Insightful)

      by sweetooth ( 21075 ) on Sunday November 09, 2003 @05:27PM (#7430369) Homepage
      No kidding. The primary problem is the ISPs and thier upstream.

    • Better title (Score:5, Funny)

      by commodoresloat ( 172735 ) on Sunday November 09, 2003 @07:29PM (#7430919)
      "Why Blacklisting Spammers is a Bad Idea: It Takes Up Valuable Time that Could Be Spent Tracking Them Down and Killing Them"

  • Social what? (Score:2, Offtopic)

    by davie ( 191 )

    Yet another confusing explosion of tiny letters with a bad color scheme. Yeah, this is going to change the world. Or something.

    Hyperbole much?

  • Just to clarify (Score:4, Insightful)

    by Nachtwind ( 686907 ) * on Sunday November 09, 2003 @05:22PM (#7430346)
    "blacklisting" in this article refers to completely block an ip address. This is not a "bad idea", but complete nonsense. First time I've heard of something like that. This is not to be mistaken for using an open relay blacklist or similar, which only blocks mail from a certain address. I bet those "network administrators" clicked on some fancy "block site" button, not knowing what they were doing...

    • Re:Just to clarify (Score:3, Interesting)

      by arth1 ( 260657 )
      The manner of blocking must have been pretty special, if it gave a 404 error. That's an error that a *reachable* web server sends out when the content asked for isn't there.

      Did this guy misconfigure his web server application to fetch content from a remote server and present it, and it erroneously gave a 404 error when the connection couldn't been established?

      Anyhow, it's also quite uncommon that a single IP gets blocked. It's more common that a whole subnet is blocked, and this may hurt innocents who s

  • Pot/Kettle (Score:3, Funny)

    by AndroidCat ( 229562 ) on Sunday November 09, 2003 @05:22PM (#7430349) Homepage
    Verio blocking HTTP access to other people's spam pages? I have I wandered into another universe again?

  • Non sequitur (Score:5, Insightful)

    by ScottSpeaks! ( 707844 ) on Sunday November 09, 2003 @05:26PM (#7430362) Homepage Journal
    The fact that a strategy (such as blacklisting) can be mismanaged and that it is not invulnerable to abuse does not necessarily make it a "Bad Idea". It just means it needs to be managed more carefully, and better secured from abuse.

  • Improperly done blacklist (Score:4, Insightful)

    by DaEMoN128 ( 694605 ) on Sunday November 09, 2003 @05:26PM (#7430363)
    Why is the blacklist being done on a domain level. Spam is usually email....so block the email address. That is simple enough to do with intrusion detection systems, some application level firewalls, and if your really bored....an access list on a router. Whoever decided to block ftp or http to stop spam was not all there. They should have stopped smtp traffic from there instead and been done with it.

    Black listing of spammers is a good idea, we just have to make sure we are only blocking them and not innocent bystandards.

    • Re:Improperly done blacklist (Score:4, Interesting)

      by PReDiToR ( 687141 ) on Sunday November 09, 2003 @05:30PM (#7430381) Homepage Journal
      I'm still pissed that AOL won't let me send email to any of their customers, just because I run my own SMTP server.

      That sucks ass royally.

      • Re:Improperly done blacklist (Score:4, Informative)

        by l-ascorbic ( 200822 ) on Sunday November 09, 2003 @06:14PM (#7430570)
        I'm assuming that by "running your own SMTP server" you mean you're running one at the end of a DSL line or similar. If so, why don't you use your ISP's server as smarthost and relay through them? Avoids DSL/dialup/dynamic blacklisting, and reduces the strain on your server. Win-win, surely?

        • Re: (Score:2, Informative)

          by account_deleted ( 4530225 )
          Comment removed based on user account deletion

        • Re:Improperly done blacklist (Score:5, Interesting)

          by bigberk ( 547360 ) <bigberk@users.pc9.org> on Sunday November 09, 2003 @07:38PM (#7430963)
          If so, why don't you use your ISP's server as smarthost and relay through them?

          Why don't I use my ISP's mail server? Because:

          1. My ISP's mail server sometimes takes as much as 3 hours to deliver a single email
          2. Mail sometimes gets lost entirely, and without access to logs I have no clue what happened
          3. I have a host with TCP/IP abilities just like everyone else. Just because I'm not paying thousands of dollars doesn't mean I can't establish a port 25 connection to another host. I resent the drive by industry to segregate connectivity based on service class (consumer/business). TCP/IP knows no such labels.
          • Amen! This is a perfect example of one of many serious threats to end-to-end transparency in the Internet. Between greedy service providers like Verisign that would break end-to-end for their own financial gain and overzealous and ill-conceived antispam mechanisms like dialup blacklisting, the end-to-end principle that made the Internet great is now in very serious jeopardy.

            I don't know what can be done other than to find and promote better ways to fight spam at the endpoints, and to scream whenever an IS

            • Re:Improperly done blacklist (Score:4, Insightful)

              by bigberk ( 547360 ) <bigberk@users.pc9.org> on Sunday November 09, 2003 @08:11PM (#7431145)
              Amen! This is a perfect example of one of many serious threats to end-to-end transparency in the Internet . . . I don't know what can be done

              Unfortunately, these Windows viruses that make a broadband customer act as a spam relay are a big reason that ISPs are considering blocking mail from dialups/dynamics.

              If Internet communications gets divided between consumer/corporate lines, I will place the blame on spammers and Microsoft (no joke).

      • Yeah, I have a similar problem. I found that when I sent mail using my ISPs SMTP server (i.e., Comcast) it would go through fine. However, I also found that Comcast's SMTP server is unreliable: either it's down or it accepts messages and then eats them whole. Anyway, I set up a mail rule to route any AOL-bound messages through Comcast and everything else is routed directly to the destination host. That way I'm only dependent upon Comcast for mail going to AOL.
      • It's not just AOL. I hit this today sending mail to my webmail account at linuxmail.org - run by Outblaze. I get an SMTP 554 pointing me here [outblaze.com].

        I've been running my own SMTP server for a couple of years now, because it gives me control, because I get to learn how mail works hands-on, and because I don't have to rely on my ISP's mail server (they run Exchange) Looks like it's not going to be possible anymore.

    • Re:Improperly done blacklist (Score:5, Insightful)

      by spicedhamhawg ( 718466 ) <jbyrne@texaport.org> on Sunday November 09, 2003 @05:44PM (#7430450)
      Speaking as someone who fights spam for a living, effective blocking requires a combination of techniques. You need to filter on sender (both envelope and From:), sender domain, sender IP, and content filters.

      Your statement that whoever decided to block ftp or http was not all there completely misses the point, I think. If a site is known to spamvertise, blocking *all* traffic to/from that site is actually a pretty good idea. Why? Consider why spammers send spam: to generate traffic to a web site, an email address, a phone number, some way to contact that. Since they know any email address they use to spam probably won't last as long as fart in a room full of air purifiers, the contact link is usually URL, whether by domain name or IP address. If they spam and you put in a filter for that spam, they may never get that spam through again, but they may still get some buyers from among your (stupider) customers. However, if your policy is to block all traffic to/from that IP address, they get zero traffic and zero business from your netblock and you really hit them in the wallet.

      Verio's idea is good, but someone dropped the ball on implemenation in this case by not checking the facts before blocking.

      What I'd like to know, though, is why the author of the article uses an ISP as bad as Noos. They sound so bad they make even wanadoo.fr (gee, speaking of spam!) sound good in comparison. Someone at Verio apparently made a mistake, but if so many people at Noos weren't so incompetent (did the PHB character come from their, I wonder?) the situation probably could have been resolved in a day or two.
      • Your statement that whoever decided to block ftp or http was not all there completely misses the point, I think.
        Allow my to explain my self better. I meant that blocking FTP and HTTP just because a site is reported to spam is not a good idea. While I don't fight spam for a living, I do regularly write filters for email worms on my company's IDS though. We have to be careful that we only filter out the unwanted and nothing else. There should have been at a bare minimum,
        1. A check to guarantee that the

  • Horror story my arse (Score:5, Interesting)

    by pauldy ( 100083 ) on Sunday November 09, 2003 @05:26PM (#7430366) Homepage
    Use some common sense editors when presented with a story that seems unusually slanted please take it at face value. This is why corporations such as verio need to be made aware of their policies not working not that black lists do not. Blacklists are the only thing that works against spammers and they know it. So how do they fight back by using the blacklists against regular sites to try and disrupt users service so that people might think twice about using them.

    Instead this article should be title "Why Blacklist Do Work" and what spammers are doing to try and disrupt them.

  • That's what I'd call costumer care... (Score:5, Informative)

    by rune.w ( 720113 ) on Sunday November 09, 2003 @05:26PM (#7430367)

    Quoting from the article:

    1. Technical support people don't have access to Internet;
    2. They are not allowed to phone to customers;
    3. And they are not allowed to send them emails.

    Maybe it is a good time to change ISP?

  • Am I understanding this correctly? (Score:5, Insightful)

    by orthogonal ( 588627 ) on Sunday November 09, 2003 @05:29PM (#7430375) Journal
    From the article: My ISP has a partnership with Verio to handle its traffic in the U.S. When Verio blacklisted Smart Mobs, any request from Noos went unanswered -- sorry, there was the (in)famous 404 error.

    I want to be sure I understand this correctly. Verio wasn't (only) discarding mail from Smart Mobs, because they thought it was spamming site, they were refusing to pass through http (or other) connections to it?

    Discarding mail is one thing, but blocking an IP address is quite another. What's the justification for this? To prevent the (supossed) spammer from profitting from the spam, by preventing anyone from connecting to it to (presumably) buy the product touted in the spam?

    Discarding mail from a spammer can be justified, by, among other things, the argument that spam mass-mailings strain system resources. But connecting to sites happens all the time -- an ISP should should be set up to handle that traffic, and can traffic to sites touted in spam really increase the volume that much?

    To me, this seems like a dubious policy on Verio's part -- even without the problem of mis-identifying sites as in the case of Smart Mobs.
    • Discarding mail is one thing, but blocking an IP address is quite another. What's the justification for this?

      Null routing of address blocks with a significant number of known spammers has been done for years. This is hardly new so please do not act so shocked.

      -sirket

    • Re:Am I understanding this correctly? (Score:2, Insightful)

      by Anonymous Coward
      can traffic to sites touted in spam really increase the volume that much?

      It's not about saving bandwidth -- it's about taking away the spammer's source of income. If you block email from a spammer, you've wasted a minimal amount of his time, and he'll quickly move to another mail server. If you take out his web site, he can't sell anything online.
    • Discarding mail is one thing, but blocking an IP address is quite another. What's the justification for this? To prevent the (supossed) spammer from profitting from the spam, by preventing anyone from connecting to it to (presumably) buy the product touted in the spam?
      Bandwidth costs.

      When you can completely block a rogue IP/network/country/etc from accessing your network at all, you save that network cost.

      You also cut out the processing time that filtering would have used up, in a more efficient way.
    • Your missing the point that the most effective and cheaest to impement method of blocking an address is what we call null routing. Pretty much you inject routes into whatever routing protocal your using and have them go to the bitbucket. It's very fast and efficient as you can update all your routers automaticaly in seconds and it's very friendly to there resources as routing is what they do well not running ACL's etc.

  • Yup, I was RBL'd (Score:4, Insightful)

    by kwerle ( 39371 ) <kurt@CircleW.org> on Sunday November 09, 2003 @05:29PM (#7430377) Homepage Journal
    I left an HTTP proxy on on an open port - on the same machine that does SMTP. I didn't even know that spammers could relay via an http proxy using a PUT to the local SMTP server. mea culpa.
    I fixed it in 3 days (too long, I know).
    I contacted mail-abuse.org and submitted a removal request. It took them 2 weeks to take me off the list.

    It frustrates me that their site is so unresponsive to removal requests, and that they fail much of their process. They were supposed to send email at several stages, which they did not do. The email they did send was badly formatted (broken urls, urs that weren't relevent).

    I won't ever use an RBL because they just don't seem responsible.

    Yeah, I know - pot kettle black. But I'm not supplying a service to thousands of users.

    • Re:Yup, I was RBL'd (Score:4, Interesting)

      by sirket ( 60694 ) on Sunday November 09, 2003 @05:39PM (#7430428)
      First off, mail-abuse.org is notorious for their response times.

      That said, you left a relay open for 3 days, and potentially tens of thousands of spam emails, and you are going to sit their and complain that it took two weeks for you to be removed from the black list? What about all the individual admins that added you to their personal blacklists and just never bothered removing you?

      -sirket

    • Comment removed (Score:4, Insightful)

      by account_deleted ( 4530225 ) on Sunday November 09, 2003 @05:44PM (#7430452)
      Comment removed based on user account deletion

  • Had the same problem.. (Score:3, Interesting)

    by Chicane-UK ( 455253 ) <chicane-uk@ntlwor l d . c om> on Sunday November 09, 2003 @05:29PM (#7430378) Homepage
    Someone anonymously submitted our MS Exchange server (I don't blame em *grin*) as a spam relay, despite the fact that it is not. As said in the original post, they didn't even check the server they just blacklisted it.

    The first thing we know about it is when members of staff come to us and complain that they are getting error messages such as 'denied' when trying to email important people.

    Sigh.. in fact I have that very same problem waiting to be tackled when I get back on Monday morning. And its always such a ballache to get your mail servers removed from these block lists... :(

    • Re:Had the same problem.. (Score:4, Interesting)

      by sirket ( 60694 ) on Sunday November 09, 2003 @05:44PM (#7430454)
      I know of no blacklist that does not first verify that you are indeed an open relay. If you know which service did this, then please let the rest of us know so that we can be sure not to use them.

      -sirket
      • A fairly high-profile example of this was when (now defunct) ORBS announced that all of above.net was an open relay a few years ago (in response to above.net blocking network scans from ORBS). A mention of how it blocked the PHP mailing list is here [phpbuilder.com].

        6 months later, its proponents were telling people the same thing - "every entry was verified an open relay" (here [ornl.gov])

        Of course, these lists can be workable when combined with a system such as spamassassin, which uses them to weight whether or not a message mi

  • Hypocrisy (Score:5, Interesting)

    by sirket ( 60694 ) on Sunday November 09, 2003 @05:30PM (#7430384)
    First of all, the idea of Verio blocking spammers is laughable. They have always been a haven for spammers and everyone here probably already knows that.

    The real issue, however, seems to be this guys ISP. I mean honestly, what the hell is wrong with them? If I had called Speakeasy with this sort of problem, it would have been taken care of that day.

    -sirket
    • The real issue, however, seems to be this guys ISP. I mean honestly, what the hell is wrong with them? If I had called Speakeasy with this sort of problem, it would have been taken care of that day.

      Exactly, what kind of 2 bit ISP is he dealing with anyway? Why when this happened did he not instantly start shopping around and then demand to speak with a manager and tell them that unless they got a clue about the diffrences between protocals that he was leaving?

      I'm gonna mod his ISP as -1 Clueless and

      • Re:Hypocrisy (Score:3, Insightful)

        by sirket ( 60694 )
        Why when this happened did he not instantly start shopping around and then demand to speak with a manager and tell them that unless they got a clue about the diffrences between protocals that he was leaving?

        Actually you are right. The real problem is people willing to put up with shitty customer service. If enough people stopped putting up with it, and did switch, we might actually see some corporate changes.

        When my last ISP gave me crap about a similar problem, I immediately started looking for a new IS

  • incorrect title (Score:2, Interesting)

    by TekZen ( 611640 )
    The tite should read: "One of the many problems with spam blacklists" -Jaxn

  • My own slashdot horror story... (Score:5, Funny)

    by Sun Tzu ( 41522 ) on Sunday November 09, 2003 @05:35PM (#7430405) Homepage Journal
    I have an earthlink.net account and a couple of weeks ago I was issued an IP address in the dreaded slashdot BANNED! file. Pity poor me, getting the big orange screen telling me about the terms of use and how, as a BANNED! IP addy, I was unable to even read them. Fortunately, the evil orange BANNED! page quoted me a few of the offenses that might have gotten 'my' IP banned. I must have spammed the input queue or posted a PWP (page widening post) or somesuch.

    Of course, it wasn't me. It was some other Earthlink customer who, sometime in the past, was issued that same dynamic IP address and committed the unpardonable offense. That customer has moved on to a new IP, but /. never forgets.

    It was hell. I spent *hours* unable to access /. -- can you imagine the suffering that such a fate would cause *you*??!

    Eventually, I was issued a new IP address from earthlink and was back online as the ageless Sun Tzu once more. But I still live in fear that someday, perhaps when I least expect it, the evil orange BANNED! page will return to haunt me. This is the personal hell that I inhabit and it is here that I shall remain, until I get a clean static IP address of my very own. I live for that day.
    --
    Send us your Linux System Administration [librenix.com] articles
    • I dare you to try and contact the Earthlink Network Abuse department. At my work, we are a (legal) online betting site and were getting pounded by several Earthlink IPs grabbing our free odds.

      With megs of apache logs for each IP address, Earthlink network abuse must have taken the week off. 17 Emails and 8 calls. With NO answer, NO response on anything.

      We cannot just block all of Earthlink's dynamic numbers because of ten insipid users. I wish death on all the sysadmins at Earthlink and I curse th

  • User vs. Customer (Score:3, Interesting)

    by Buran ( 150348 ) on Sunday November 09, 2003 @05:37PM (#7430415)
    The last time I checked, being a user of an ISP or the company that carries the packets means you're a customer of that ISP/provider ... your money is used to pay for their services.

  • Answering the question. (Score:5, Insightful)

    by _Sprocket_ ( 42527 ) on Sunday November 09, 2003 @05:39PM (#7430431)
    So the question presented by this article would be "WHY is blacklisting spammers a bad idea?" Unfortunately, it doesn't answer the question.

    The blurb mentioned by the article submitter is the entire coverage of any such activity. The rest of the piece then goes on to complain about the user's ISP. Those who haven't RTFA'd can feel comfortable in skipping this one.

    I'm sure this submission will provide nice fodder for expressing annoyance over spamming and horror stories of "collateral damage". But then - we've had plenty of those before. It would have been nice if an article had provided some framework around this kind of conversation.

    This article doesn't.
  • There's nothing wrong with blacklisting as long as each customer can choose which blacklist they want to use (if any). That's the way most blacklists work: they are opt-in.

    What is wrong here is that the ISP itself makes the decision unilaterally and uniformly for all its customers.
  • I once tried to subscribe to a mead mailing list that I found on a web page with my rogers.com Address.

    I got a letter saying 'YOUR SPAM HAS BEEN REJECTED!'

    I wrote the guy who ran the web page and told him and he laughed and subscribed me.

    Still - to have the whole domain rejected because of BS is wrong, IMO.

    Interestingly enough, very shortly afterwards Rogers adopted a policy of having to have a password to get on the mail server, and my excellent mailer PMMAIL already had a new version that could handle
    • Still - to have the whole domain rejected because of BS is wrong, IMO.

      I agree, if by "BS" you mean dubious reports of spam-friendlyness. However, I have no problems with blocking mail or all IP traffic in general from known crime-ridden providers (such as Cogentco, Verio, Qwest or any ISP in South America).

  • Wrong. Not perfect != "bad." (Score:5, Insightful)

    by the_dreadnought ( 678956 ) on Sunday November 09, 2003 @05:47PM (#7430467)
    The good it does is far outweighed by the bad. Just like everything else in life, mistakes will be made. You can have a problem with the process to correct mistakes, but advocating RDNS blacklisting should go away doesn't make sense.

  • Blacklists and filtering only works so well. (Score:3, Interesting)

    by Chanc_Gorkon ( 94133 ) <.moc.liamg. .ta. .nokrog.> on Sunday November 09, 2003 @05:53PM (#7430494)
    The thing we all forget is that spammers are human. If a single address is being blocked, then they change the addresss. If they are spoofing, there's a chance you can incorrectly block a whole domain because of one idiot who setup an open relay. Case in point, at work, all e-mail on the .biz top-level domain is blocked because of the amount of spam taht is recieved from it. What if someone we'd like to do bisness with is on that domain? Alot of the typical comapnies you do musiness with have the .com tied up but if your starting a new business, sometimes the only one available might be the .biz. I personally have given up and try to filter as much as I can knowing that even that won't help.
  • This is totally off topic and I hope it gets modded as a troll or -1 Ignorant.

    But... the Noos web site really pissed me off. The fronsay is no big deal, je le parle comme tout le monde. But what is the deal with the animated text, the little blinking lights saying 'clickez ici, you big dumb user you', the text highlighting gizmo, and that terrible, terrible logo that looks like a genetically-modified O with extra ears.

    I mean... an ISP like that and you expect service? What the fuck?

    OK, I had to say it
  • Yep, I am tired of getting the dreaded pink slashdot screen (DPSS), after hitting several times F5 it loads the page correctly (weirdly developers.slashdot.org is the hardest to bypass)
    Why /. bans spain?
    Yep I know my evil "isp" hijacked the internet and put a transparent firewall but I CANT switch "isp" there is only one "real" adsl provider in spain Telefonica, the other ones are resellers of the same product. /. ban on spain lame
    (I tried once emailing /., one of the addresses listed in the DPSS, but to no
    • They're not related to teleline.es are they? The ISP that at least once (they've been blocked on my domains for ages) sent around an email saying 'don't worry if other ISPs have blocked you for spamming.. join us and we'll let you spam all you like'.

      I got that message and immediately blocked their entire subnet...
  • To get kicked from Verio, you have to burn down a network center or something like this. About 500 mails from users to abuse@verio.net for one spamvertized website netmails.com [google.de] and no action taken ==> They do nothing against spam. They tolerate spam.

    Check for yourself: Verio's Listing [spamhaus.org].

    I use blackholes.us [blackholes.us] to block (port 25) entire countries (cn, kr, tw) and ISPs (Verio, interbusiness.it...) that do not qualify (in my standards) for connecting to my mailserver.

    NSG

  • Gah (Score:2)

    by bruns ( 75399 )
    Gah, this story is not what it appears to be from first glance. This is a story about an ISP (a known Spam Supporting ISP at that) blocking access to a website through its network.

    Most times, a blacklist is used only for e-mail blocking and not website blocking. Alot of DNSbl maintainers specifically tell you that their list should NOT be used to block anything but e-mail.

    Its just stupid and pointless to filter out websites - unless you want to support censorship.

    Now, onto Verio blocking a spammi
  • I'd have to say this is pretty rare. That's just bad policy. At the ISP where I work it takes multiple offensives and the offending ISP has to either not respond to our multiple complaints for over 30 days or flat out refuse to do so. At such time we will blackhole them.

    Personally I see this more as an overzelous or undertrained staff at one ISP. I haven't heard too much of this happening myself. I think the biggest issue with blacklisting is when you end up blocking say a /16 or something because som

  • How was it blocked? (Score:3, Insightful)

    by Skapare ( 16644 ) on Sunday November 09, 2003 @06:34PM (#7430665) Homepage

    Based on this story, it seems Verio decided to block the presumed source of spam by means of the routers. That's a rather extreme measure. Doing such things in routers, whether by access list, or by blackhole routing table entry, is not nearly as easy, and does not scale as well, as blocking at the receiving mail server. But they may have wanted to do so because so many mail servers are run by clueless people that can't configure their way out of a paper bag.

    I block spam source at mail servers, not routers (except in very extreme cases, but there are current none blocked at routers). That gives me the option to whitelist specific senders and/or specific recipients. So I'd say the real issue he is not that blocking/blacklisting spammers is bad, but that blocking them in stupid ways that lose control is what is bad.

    Blocking spam and spam sources should be an end-point decision. There are risks in blocking, and different people have different needs and different sensitivities to that risk. Even your own ISP shouldn't block spam for you unless you agree to it with the understanding of how they are doing it. The best solution is for you to have total control if you wish, particularly in the ability to whitelist, and even blacklist, specific exceptions you want. Those who don't know the details of how this is done would have to delegate that to someone (such as their ISP).

    Even content based spam filtering can be broken. What if my girlfriend sends me mail telling me what she's going to do with certain parts when she comes over tonight. I sure would not want that to bounce. Of course I can whitelist her email address (and hope her computer doesn't get infected by some spamming virus).

    Blacklisting spammers is good ... when done right. Verio didn't do it right.

  • To me at least, is AOL's decision this year block mail from 'cable modem' address space. As someone who runs his own servers, I am now forced to smart-relay through my ISP...which adds all types of problems, their incompetence at properly configuring *THEIR* servers at the top of the list.

    Yeah, I'd like to say to the AOL users on my lists 'tough luck', but I cannot do that.

    • Re:Even more offensive (Score:3, Interesting)

      by taustin ( 171655 )
      There are only a couple of possibilities here. One, you are running your own server on a consumer account with a dynamic IP address, in which case you are likely in violation of your AUP, or two, your ISP is utterly clueless and has put their static IPs in the middle of their dymanic range.

      Either way, get a real provider, and your problems will disappear.
  • I understand the reasons for blacklisting ( I won't argue about the due process issues in which some people get wrongly blacklisted or find it hard to be un-blacklisted). Blocking evil senders of spam is good, even if some people are overzealous. But the situation here is the recipient was prevented from accessing data that they wanted.

    If I, the requestor and recipient of communications, want web pages, e-mail, etc. from a given domain, why shouldn't I be able to get them? Since when is the ISP in loc
  • A very similar thing happened to me. I run a reseller hosting account for myself and my clients on a machine with a few hundred other reseller accounts (and therefore probably thousands of domains). Somebody using the server either sent or was reported to have sent spam to somebody with an AOL address. It was reported, and AOL started refusing any email directed to any AOL account.

    This created havoc for myself and my clients (and everybody else on my server, and one other server run by my hosting provid

  • Um, Verio? (Score:3, Interesting)

    by CaptainSuperBoy ( 17170 ) on Sunday November 09, 2003 @07:35PM (#7430947) Homepage Journal
    Verio doesn't blacklist spammers. Verio HOSTS spammers. Verio is friends with spammers. Verio has a long and storied history of supporting spammers, so I think it's far more likely that Verio got blacklisted and not the other way around. This guy should have switched ISPs but he completely misunderstood what happened here - he thinks that Verio is blocking him from viewing some random web site. What actually happened is Smart Mobs' ISP blacklisted Verio, probably with good reason.

  • Proper spam blocklisting (for mail) (Score:4, Insightful)

    by bigberk ( 547360 ) <bigberk@users.pc9.org> on Sunday November 09, 2003 @07:50PM (#7431029)

    First, it's obviously a bad idea to block all IP traffic for an entire netblock (except under extreme circumstances -- attacks, for instance).

    Spam is a huge problem, and there are some very effective DNSBL's (DNS blocklists) out there that can let a mailserver reject mail coming from a certain IP address. There are many different DNSBL's out there, and each has their own policies on what IPs they will list, how they will de-list, etc.

    I don't like DNSBL's that list IPs based on non-spam related criteria. Examples include: country/continent of origin and service class (consumer vs. commercial). Blocks based on such criteria just divide the Internet, and don't even take into account where spam is coming from. I think it's a slap in the face of the Internet for a company to say, "I'm going to block all traffic from dynamic IPs, because they are not commercial connections".

    Then there are the blocklists that block IPs that send spam. I like this approach because the lists are designed to block what I don't want; spam. sbl.spamhaus.org blocks regions of the Internet that perpetually send spam. blackholes.easynet.nl similarly list established spam sources. relays.ordb.org and list.dsbl.org block open relays and proxies that were found to be points of abuse.

  • Newsworthy? (Score:3, Interesting)

    by fondue ( 244902 ) on Sunday November 09, 2003 @07:59PM (#7431091)
    So some bandwidth provider accidentally stuck a site on a blacklist. And then it got fixed. Is there some important angle I'm missing here?

    Don't tell me, because of this upset you missed meeting up with four thousand other bored office workers in a public place to do something 'wacky'? Boo freaking hoo.

  • some IP addresses blow spam (Score:4, Insightful)

    by chongo ( 113839 ) * on Sunday November 09, 2003 @09:22PM (#7431481) Homepage Journal
    While I feel sorry for those who are innocent victims of blacklists, I cannot also ignore the most of the spam comes from a only few IP addresses.

    Over the past 6 months, some 65% of spam (and spam attempts) that my ISP received came from less than 0.16% of the assigned IPv4 address space.

    Almost 2/3's of the spam we saw was sent over SMTP connections from one of 77 CIDR blocks (ranging from /16 to /30 in size). These 77 CIDR blocks represent less than 1/6 of 1 percent of the assigned IPv4 address space.

    BTW: The CIDR list growth factor is not much when you move from the 65% level to the 90% level.

    ... your stats may vary. :-)

    Spam is truly a world wide problem. Those 77 blocks, by national/region, break down as follows:

    1. 1 Australia
    2. 1 Belgium
    3. 8 Brazil
    4. 1 Canada
    5. 8 China
    6. 3 Dominican Republic
    7. 1 Spain
    8. 1 France
    9. 1 Israel
    10. 1 Italy
    11. 1 Japan
    12. 15 Korea, Republic of
    13. 3 Mexico
    14. 1 Poland
    15. 1 Russia
    16. 2 Thailand
    17. 3 Taiwan
    18. 25 US
    The above list is provided for the curious. I do not recommend that people block IP addresses based on the hosting country.

    "Yes, Virginia", a few IP address blocks do transmit most of the spam.

Slashdot Top Deals

"Trust me. I know what I'm doing." -- Sledge Hammer

Close