Slashdot Mirror


Paul Graham Describes Dangers of Spam Blacklists

CRoby writes "Paul Graham posted an essay describing the danger and corruption of the main spammer blacklists today. It discusses MAPS and the SBL, the blacklist created to try to alleviate the abuses of MAPS, and suggests (maybe) another blacklist's creation."

611 comments

  1. $article_title by $blowhard by Neil+Blender · · Score: 4, Funny

    $idea will not help cut down on spam. In fact, it is detrimental. This has been know for $num_years years, but I feel I must prove that I am really smart by writing an article about it.

    1. Re:$article_title by $blowhard by 2names · · Score: 0
      Very funny sschtuff, man.

      Somehow, I think the guy thought it said "blackfist"

      --
      "I'm just here to regulate funkiness."
    2. Re:$article_title by $blowhard by Anonymous Coward · · Score: 0

      You are a hacker my friend!!!!! - Paul Graham

    3. Re:$article_title by $blowhard by Anonymous Coward · · Score: 0

      I blacklist articles written by Paul Graham.

  2. Definitely a bad idea... by nev4 · · Score: 3, Informative

    We've been blacklisted before and the sysadmins who run these things often WILL NOT remove you, no matter what. I'd take all the SPAM anyday vs. not being able to send legitimate emails.

    1. Re:Definitely a bad idea... by Triumph+The+Insult+C · · Score: 0

      then don't use MAPS or SBL on your mail servers. you will get all of the spam

      --
      vodka, straight up, thank you!
    2. Re:Definitely a bad idea... by Anonymous Coward · · Score: 3, Informative

      You really don't get it.

      The point isn't *me* using MAPS/SBL. The point is that others use it, thinking it makes a difference. Your netblock (that is, your ISPs netblock, or your ISPs ISPs netblock, etc) gets included in that list and *bang* you're a casualty of war.

      Get it yet?

    3. Re:Definitely a bad idea... by lawpoop · · Score: 1

      Does this blacklist have a name?

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    4. Re:Definitely a bad idea... by Triumph+The+Insult+C · · Score: 0, Troll

      Yes, I do get it. I have.

      What I do is get a new ISP that doesn't allow spammers.

      Simple. Problem resolved.

      --
      vodka, straight up, thank you!
    5. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 5, Insightful

      I'd take all the SPAM anyday vs. not being able to send legitimate emails.

      Except that blocklists don't stop you sending email, they merely allow others to decide whether to accept that mail. Or do you think other people should be forced to accept any and every email you send?

      --
      My next sig will be ready soon, but subscribers can beat the rush
    6. Re:Definitely a bad idea... by Seumas · · Score: 5, Insightful

      John Reid of the SBL told me this wasn't true-- that the SBL was still clean, and that they only blacklisted hosting companies' mail servers when they were spam hosts who took on innocent users as camouflage:

      He is right. That definitely is NOT how SBL actually operates. I have a site that is heavily trafficked (millions per month) and they blocked my email (from my own personal server) that has delivered mail for my site for seven years with absolutely no outgoing spam or relaying having ever occurred in its entire life.

      However, a spammer with false credentials faked his way into a hosting account with my colo provider and as a result, SBL blocked multiple entire submnets, rendering my entire site and service useless for almost an entire month (we deal with auctions, meaning nobody was getting closed notices, won notices, outbid notices, addresses to send payment, registration emails, lost password emails - and when they complained, I couldn't respond to help them and explain it to them).

      SBL couldn't have cared less. As far as they are concerned, if one IP is a source of spam, they all are. And they'll get to fixing it in their own damn sweet time.

      But the defense of SBL fan-boys is typically "well it's VOLUNTARY!".

      Yeah. Whatever. Fuck off.

    7. Re:Definitely a bad idea... by Skye16 · · Score: 1

      Wow. You have multiple choices of ISPs? I have 3, and one is AOL.

      Must be nice for you. :(

    8. Re:Definitely a bad idea... by Neil+Blender · · Score: 1, Flamebait

      Gee whiz. That's great for you and your little PHP blog that you use to write stories about your cat and host pictures of last week's bbq. However, that is not such a simple solution to someone who has 6 cabinets packed floor to ceiling with 1Us.

    9. Re:Definitely a bad idea... by Seumas · · Score: 2, Insightful

      Oh, NEAT. So you can afford the downtime of a service/site that must be available 99.999% of the time to find and move to another colo provider and deal with weeks of inavailability inbetween (due to the SBL block) every time SBL decides to block a slew of subnets around you just because some jerkoff decided to spam from it?

      I'm glad you're so flexible. In the real world, most of us aren't.

    10. Re:Definitely a bad idea... by Singletoned · · Score: 1
      "Except that blocklists don't stop you sending email, they merely allow others to decide whether to accept that mail. Or do you think other people should be forced to accept any and every email you send?"

      Well, someone didn't RTFA.

      The whole article is about blacklists that stopped people from sending mail, and the grandparent has a very good point.

    11. Re:Definitely a bad idea... by hawkbug · · Score: 2, Informative

      Right on - a company can't simply get out of an ISP contract for a lot of reasons. Technical reasons aside, imagine getting out of a 3 yr contract after 2 months. It's not going to happen.

    12. Re:Definitely a bad idea... by jdhutchins · · Score: 1


      What I do is get a new ISP that doesn't allow spammers.


      Your ISP may not allow spammers, but it really can't do a whole lot to stop every zombie before it sends any spam. A zombie from your ISP can send a couple of spams, and that could cause your entire ISP to get blacklisted. Your ISP doens't have to allow spammers for it to get blacklisted.

    13. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      Well, someone didn't RTFA.

      More like someone (ie you) RTFA but didn't understand it. Blocklists do not stop people sending. They are used on the receiving side. Receivers choose whether to use them or not. Of course, receivers need to understand the implications of that, and in particular, they need to understand what the policies of the particular list(s) are (and indeed, whether they have changed - Spamcop is a good example there).

      --
      My next sig will be ready soon, but subscribers can beat the rush
    14. Re:Definitely a bad idea... by caluml · · Score: 0

      The http://www.spamhaus.org/ SpamHaus lists seem to be very effective. I've yet to hear of anyone being wrongly listed. They list individual hosts, not netblocks. Couple that with Spam Assassin and Vipuls Razor, and I don't see much spam if any.

    15. Re:Definitely a bad idea... by ckaminski · · Score: 1

      I have one word for you: lawsuit.

    16. Re:Definitely a bad idea... by henrywood · · Score: 2, Interesting
      It's a very difficult problem. Being charged with implementing Spam filtering measures for my company I know how difficult a line it is to walk. When you're handling mail for 600+ users you do get a different perpective on the problem.

      We ended up by deciding to temporarily block mail from servers on certain blacklists (Spamhaus and Spamhaus XBL), sending a message back to the sender which allows them to release the mail. We also use SpamCop, but in a looser way; only if the mail comes from a SpamCop listed server and fails certain other tests do we, again temporarily, quarantine it. Otherwise we mark it as Spam, pass it through, and ask the recipient to tell us if it was Spam so that we can block it next time.

      In either case the original sender, presuming it's a real person, has the ability to release the mail. (Of course we check all released mail, and if it's Spam the sender goes on our own permanent blacklist!).

      I'm all too aware that this has the potential to add more useless mail to the system, but in practice most of these relase messages never even leave our server because the original came from a non-valid address. And it does work pretty well.

      These, and other, rules allow us to block most of the Spam, which amounts to about 2/3 of all the mail we receive. And I've had a lot of compliments from the end users, so they appreciate what we're doing.

      The moral is you can't trust the blacklists absolutely, but they have a very useful advisory role to play.

      --
      Something is happening here but you don't know what it is, do you, Mr Jones.
    17. Re:Definitely a bad idea... by cortana · · Score: 1

      Regardless of whether it was the right thing to do or note, you can't argue that the process didn't put pressure on you to switch hosting providers, or at least put pressure on your hosts to ensure that they never host another spammer again...

    18. Re:Definitely a bad idea... by Seumas · · Score: 2, Interesting

      The best solution is to not let your blacklist be the final word. I use SBL on my server (though I dislike them due to personal experiences when a network I was on had a spammer on it for a day and it took three weeks for my own mail from my own email server on my own rackmount to flow again) - but I don't block mail just because it's on the list. I count it in the final spamassassin score. So if you are on the list, but little or nothing about the content seems to be spam - no problem.

      If you are from a blacklist and your message has lots of chick-scratch in it or other spammer tricks and it generally looks like a piece of spam, it's more likely to be caught and blocked.

      But using the SBL alone and giving it the final decision over accepting mail is just giving it way too much power.

    19. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      It is voluntary, so people who participate or use providers who do are at fault. You should have had your users complain to their ISP or network admins for blocking your mail.

    20. Re:Definitely a bad idea... by Triumph+The+Insult+C · · Score: 1

      in the real world, we get protection against those things in our contract before signing the contract

      if the contract provides for a certain level of availability, and that availability isn't met, the the isp will have some explaining to do

      --
      vodka, straight up, thank you!
    21. Re:Definitely a bad idea... by henrywood · · Score: 1

      Spamhaus do not list just individual hosts. They certainly do list whole network ranges, in some cases an x.x.x.x/16 range.

      I agree that they are by far the most reliable of the blacklists, but they are certainly not infallible.

      --
      Something is happening here but you don't know what it is, do you, Mr Jones.
    22. Re:Definitely a bad idea... by Triumph+The+Insult+C · · Score: 1

      i found one that doesn't suffer from this problem. my previous one did suffer from this problem. i was tired of 1. having my mails bounce and 2. supporting a company that was doing nothing to alleviate the problem

      --
      vodka, straight up, thank you!
    23. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 0, Flamebait

      Yeah. Whatever. Fuck off.

      How charming. Yet you would deny the users of RBLs the chance to say "Fuck Off" to spammers? Here's a free clue for you - I will decide who gets told to "fuck off" on my own system. Whine all you like, it's my decision.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    24. Re:Definitely a bad idea... by Seumas · · Score: 3, Interesting

      Providers don't have a choice very often. It's incredibly easy for someone to use any number of credit cards (even stolen ones that haven't been reported) and various false identities to purchase hosting accounts. If a provider doesn't respond and just keeps letting the spammer have at it, that's fine. But if someone is cut off quickly, then restore their SBL credibility immediately. Duh.

      Anyway, they shouldn't be blocking entire blocks of IPs. That doesn't even make sense. What does one guy on one IP out of hundreds or thousands who spammed for most of a day before he got caught have to do with my server which has run clean and reliable and secure and in good faith (including SPF and everything else) for the better part of a decade?

      As Paul Graham already stated, this is just a strongarm tactic to harass as many innocent parties as possible. There's no other explanation for it. Are two spammers really worth denying tens of thousands of (in the case of Paul Graham) Yahoo customers?

      There are bad-actors; rogue hosts. It's pretty clear when you're dealing with one who isn't. And if you were quick to put people on the SBL list, then take them down just as quickly. It is unacceptable that it took three weeks after the incident for them to finally remove them from the list.

    25. Re:Definitely a bad idea... by FyRE666 · · Score: 1

      It's rubbish to say that it was impossible for you to email your users. You could easily have set up another account at another colo for a few bucks and set up a simple script to accept and relay the mail out.

      I think the SBLs are great, as the administrator of several relays, they save me a lot of work (along with URL BLs). They DO encourage hosts to ditch the scumbags in double quick time - I've been phoned by web hosts within minutes after emailing to inform them I was about to submit their domains/netblocks and spammy customers to the RBLs, with them promising to fix the problem if I hold off. In some cases the same netblock was spewing spam the next day, in which case they were straight on the RBL, but in some cases something probably got done.

      Yes, if my sites were BL'd, it might be a little irritating for the half hour or so it would take to set up a relay, but it's not the end of the world...

    26. Re:Definitely a bad idea... by LetterJ · · Score: 1

      And I have several for you:

      "Eighteen months of litigation and downtime."

    27. Re:Definitely a bad idea... by Seumas · · Score: 1

      You, however, will gladly assume the role of telling peopel to fuck off on behalf of your tens of thousands or millions of mail users on the boxes you administer, though. And that's the point.

      The shotgun approach is a terrible approach and the only people who act like dicks about it are those who have never been an innocent bystander victimized by it. Christ, a shotgun would at least be more precise.

    28. Re:Definitely a bad idea... by Seumas · · Score: 5, Insightful

      That's the point - it doesn't matter how fast you respond to a spammer. If you ditch the spammer instantly, you're still going to end up on the list indefinately. In the case I cited, the spammer was kicked off within hours. I'm sure he was off to some other unwitting place to spam from while the rest of us went weeks without being able to send from our servers.

      How is it an incentive for admins to be "responsive" when dealing with spammers if you're going to punish everyone within a certain radius for days or weeks even if the problem was terminated within hours?

      What exactly is so wrong with blocking an IP at a time? You do away with the innocent bystanders while still nailing the spammers. Anyway, the reason they block the entire subnet has NOTHING TO DO WITH PREVENTING SPAM. It's merely a way of pissing off enough legitimate people to force the bad person to be dealt with (even if they've already been dealt with or it was an honestly unavoidable situation or what have you).

      If you've identified chronically spam-friendly hosts and want to widen your net for them, that's great. But don't take out the entire neighborhood because of one bad neighbor.

    29. Re:Definitely a bad idea... by capilot · · Score: 1

      However, a spammer with false credentials faked his way into a hosting account with my colo provider Why didn't your colo provider just get rid of the spammer?

    30. Re:Definitely a bad idea... by ScuzzMonkey · · Score: 1

      Simple for you, maybe, not so much for the majority of subscribers. It's like whacking a dog for something your neighbor's dog did two weeks ago... there isn't going to be any connection in their head and they aren't going to know what to do about it anyway.

      --
      No relation to Happy Monkey
    31. Re:Definitely a bad idea... by afidel · · Score: 1

      I would agree with you Spamhaus is by FAR the best of the RBL's, with the most sane policies (that aren't likely to change). However they are still human, and humans make mistakes. But if they are truely mistakes and not systematic errors then I think they are worth using. Besides I greylist things to a space limited catchall to be able to grab incorrectly scored emails so someone being improperly listed isn't the end of the world, just means a little bit of work on my part if one of my users needs to get a blocked mail.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    32. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 2, Insightful

      Except that I have been listed. And I had to go through contortions to fix that situation, which did not occur because of anything I did. What were you saying about acting like a dick?

      As I already said, yes, I do assume the role of telling people to fuck off on behalf of my users. And I'm accountable for that. If I choose lists with inappropriate policies, or continue to use a list after its policy has changed for the worst, then I deserve to have my users demand change or my removal. No-one is pretending that RBLs are a magic bullet, or even that that they're a "configure & forget" solution. Of course there will be false-positive listings, malicious smear attacks (which is what this case appears to have been) and so on. My experience is that the damage arising from such cases is minimal when compared to the benefit of using RBLs. Simply put, RBLs work more effectively than just about any other technique (for today, at least).

      And frankly, on a practical level, what are you going to do about it? Do you think you can stop groups of people organising themselves and exchanging opinions on the activities of others?

      --
      My next sig will be ready soon, but subscribers can beat the rush
    33. Re:Definitely a bad idea... by cft_128 · · Score: 1
      Yes, if my sites were BL'd, it might be a little irritating for the half hour or so it would take to set up a relay, but it's not the end of the world...

      Works great for you... but not everyone has that ability (or the cash for it). If I'm just running a site off of yahoo's hosting service, do you think that I would know how to set up that relay? Should I know how? For some small companies, it might not be the end of the world but it could be the end of their business. And please don't use the "if they don't know how to do it they shouldn't be on the internet argument. I wish people used that logic for operating cars. What? you don't know how to change out your alternator? well, you shouldn't be driving your car if you cant do something like that.

      What if, as it is with me and a couple of friends I know, I'm just a guy who runs his own mail server on his static IP and my ISP gets BLed? What should I do, go get another ISP and set up a relay? How about the email fascists get their act together and not ABUSE THEIR POWER? Let's say my ISP had a spammer on them and it took them 6 hours to find, detect and kick them off, does that mean I should be blacked out for 30 days? Why does the SBL get to take a month to so what they expect an ISP to do in 10 minutes?

      --

      Underloved Movies and Pub Quiz: donotquestionme.org

    34. Re:Definitely a bad idea... by capilot · · Score: 2, Insightful
      We've been blacklisted before ...

      Was it for -- wait, let me guess -- was it maybe for spamming? Maybe next time you won't spam or let your users spam. Just a thought.

      the sysadmins who run these things often WILL NOT remove you

      Which sysadmins are those? Certainly that's true for my system. Once I drop a spammer into the system blacklist they're there for life. I don't have the time or energy to audit my block list, and what would be my motivation anyway?

      The major RBL's on the other hand, will remove you if -- and this is the important part -- if you stop spamming. In this sense, the RBLs are doing you a great service. If the RBLs list you before I get mad enough to block you myself, then you have a chance to eventually get unblocked. Would you care to name a major RBL that continued to list you even after you cleaned up your act?

      I'd take all the SPAM anyday vs. not being able to send legitimate emails

      Ahh, but you weren't really listed for sending legitimate emails were you? If you're willing to accept spam in exchange for the ability to send it, then that seems perfectly fine to me. All the sites that want to send spam, and are willing to receive it in return need merely not subscribe to the RBLs. Voilla! The system works.

      I, on the other hand, am perfectly willing to not receive spam in exchange for your inability to send it to me. The system works again!

    35. Re:Definitely a bad idea... by Jeff+Hornby · · Score: 1

      Sounds like you lost money so....

      Why not sue?

      After all, they listed you as a spammer in a public notice (libel) and you lost money and probably sustained damage to your reputation. IANAL but it sounds like a pretty airtight legal case.

      --
      Why doesn't Slashdot ever get slashdotted?
    36. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1
      We've been blacklisted before and the sysadmins who run these things often WILL NOT remove you, no matter what. I'd take all the SPAM anyday vs. not being able to send legitimate emails.
      If you are stupid enough to remain on a blacklisted network, you only deserve to have your mail blocked.

      When your ISP is blacklisted, he is selling you tainted goods. So the only logical course is to move to a more respectable ISP who doesn't get listed; the idea is to force innocent collateral damage to move out of spam-friendly networks.

      It's like a credit bureau: credit bureaus tell the lenders if you're trusty enough to be lent some money. When you are turned-down, it's not the credit bureau you blame but the lender. Blacklists are the same: they tell the receiving e-mail server that you are spammy or not. In any case, the "fault" isn't the blocklist but the receiving mail server.

    37. Re:Definitely a bad idea... by Pig+Hogger · · Score: 0
      However, a spammer with false credentials faked his way into a hosting account with my colo provider and as a result, SBL blocked multiple entire submnets, rendering my entire site and service useless for almost an entire month (we deal with auctions, meaning nobody was getting closed notices, won notices, outbid notices, addresses to send payment, registration emails, lost password emails - and when they complained, I couldn't respond to help them and explain it to them).
      Your ISP is entirely to blame for this. If he acted in a timely manner and disconnected the spammer as soon as the spamming complaints came in, he would never had been listed.

      But your ISP obviously routed the abuse mailbox to Dave Null, hence the blacklisting.

      Nothing forces you to do business with that ISP; you just move with your feet.

      What? Do I hear about a contract? Well, your ISP did break his contract of providing unbroken connectivity, so you're free to go, and, better yet, the ISP is liable for your moving expenses!!!

    38. Re:Definitely a bad idea... by jbolden · · Score: 1

      You should read the article, Paul Graham's point was not that these tactics aren't effective but that they amount to terrorism: trying to pressure a central authority by harming innocent people. Whether this sort of pseudo terrorism is justified in the war against spam is another issue. I personally would prefer any the technical or central signing authoritiy style email solutions.

    39. Re:Definitely a bad idea... by squiggleslash · · Score: 1
      Who?

      The ISP? The ISP hasn't done anything illegal. At best (and it's a poor argument), it's provided access facilities, probably unknowingly, to a spammer. The spammer has left, but the blacklists remain.

      The blacklisters? It's been done. You generally can't.

      The spammers? They've almost certainly already left.

      Lawsuits are as dumb as blacklists. In the end, my solution is pretty much the solution anyone should take - encourage those on ISPs who use blacklists that prevent them from receiving email from you (that they want to read, obviously) to switch to a different ISP. One or other will happen in most cases. The victims short term are always the customers, and long term both the idiot ISPs who misuse a discredited form of spam control and the the ISPs who are unfortunate enough to have a spammer sneak under the radar.

      --
      You are not alone. This is not normal. None of this is normal.
    40. Re:Definitely a bad idea... by XLawyer · · Score: 1

      Anyway, they shouldn't be blocking entire blocks of IPs. That doesn't even make sense.

      Can you suggest another effective way for an outsider to apply pressure to an ISP that hosts a spammer?

    41. Re:Definitely a bad idea... by squiggleslash · · Score: 1
      That's right. Because lawsuits solve everything!

      In fact, that's such a brilliant approach, I'm going to use it to cure cancer. It's quite simple: I'll get my friend to sign a contract saying he'll cure cancer next week. And then when he doesn't achieve it, I'll sue him. Bingo, cancer is cured!

      That's right, huh? Because if an ISP has a minimum service level promised in their contract, and they're suddenly unable to keep to it because one third party hates another third party that happened to be a customer, then the downtime required by a switch, or merely implied by the boycott itself, will not happen, correct?

      --
      You are not alone. This is not normal. None of this is normal.
    42. Re:Definitely a bad idea... by Gorm+the+DBA · · Score: 2, Insightful
      Except for one not so minor thing...

      Credit bureaus are *heavily* regulated. If they have a file on you you can get a copy of it every few months. If there is an error, there is a defined process to follow to clear it up, and they are forced by law to resend new reports to anyone who accessed your report during the time the error was present.

      "Blacklists" are not regulated at all. There is no accountability, no way to protest a listing if you believe it is incorrect. No recourse.

      If you can't see a difference...then I pity you and whatever school system you went to.

    43. Re:Definitely a bad idea... by syukton · · Score: 3, Insightful

      Actually, I'm with singletoned, and I think it's you that has a problem with understanding. Understanding something involves realizing implications which are not immediately obvious. Understanding is something that few people ever really do. Reading the facts isn't enough, you need to be able to manipulate those facts and draw provable conclusions from them. THAT is understanding.

      For example, in order to get revenge on people they believed were spamming, MAPS would blacklist the mail server of the company hosting their site.

      The problem with blacklists is that they're human controlled and extremely susceptible to egotistical vigilante-ism. If I'm getting spam from a server, I don't have to block just that server. I could block every server in the headers, for example. What I choose to add to my blocklist can be totally arbitrary, and that's the problem with blocklists controlled by individuals that can block huge IP blocks.

      And, in terms of preventing the "sending" of mail, you could consider a blacklist to be a postman who would, whenever he saw a letter from a given return address, he'd destroy it. Any time you got a New Scientist magazine? destroyed, at their discretion. How many companies use a blacklist without saying what's on the blacklist, or making the blacklist easily searchable and editable? Does a user ever get a message on a regular basis "Hello so and so, you've received 274 emails this week from addresses in our blocked address list (which contains mostly spammers; click here to make a change." ? No, they don't provide that helpful information with links to the relevant information.

      The mail is just blocked, it disappears into a void. By intercepting it before it reaches its intended recipient you are effectively preventing it from being sent. Because it's not the addressed recipient that decides whether or not to accept the mail according to the blacklist, it's an unnamed middle-man or middle-men. A blacklist allows any server in-between the sender and the recipient to say "no, sorry, your ass is blocked."

      I do think people should be forced to accept every email that I send. They shouldn't be forced to READ them all, but they should be forced to accept them. As email becomes more and more prevalent as a form of legally recognized communication (emails are used in court as evidence) it's important to recognize the implications of interfering with that communication without disclosing such interference. Would you like it if I were your postman and every time I saw your electric bill, I took it and destroyed it because I didn't like the electric company and I didn't think anybody should be subjected to their tortures? Would you like me totally interfering with your legal communication and then not telling you, not even sending you a friendly "the electric company is evil, go solar!" letter? Would you like the way that could impact your finances, your credit, your reputation? What happens when somebody adds an obscure credit union to a blacklist and people don't get fraud alert emails from the CU, just because one server in their datacenter was compromised and used to send 10,000 spams? Do you REALLY understand, now? I still don't think you do.

      The blacklist themselves aren't really responsible for breaking any rules, which they believe absolves them of acting responsibly. The fact of the matter is that blacklists are often implemented in the most infuckingcredibly ignorant ways possible, unfortunately. No e-mails as per my suggestion above, no way for the sysadmins that use the blacklist to audit/edit it, etc.

      We need a wiki-style collaborative blacklist that has a membership of thousands who all collaborate on this issue. It's just one more example of how giving one person too much power before they're ready to use it responsibly with proper discretion results in a disaster. A blacklist affects too many people to be implemented so willy-nilly at only a few peoples' (poor) discretion. We need a collaboration, a large committee who will not become corrupted by power (as none of the members will individually have any power) but will be a gathering of individuals who maintain their individual opinions and ensure that the system remains fair and balanced.

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    44. Re:Definitely a bad idea... by XLawyer · · Score: 1

      They almost certainly did *not* list him as a spammer. They said that a particular netblock had been used by spammers, possibly among others. The OP, presumably, was one of the others.

      What they said is neither defamatory towards the OP nor false, and is therefore not actionable.

    45. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1
      It's rubbish to say that it was impossible for you to email your users.
      He could also have phoned the blocklist operators...
    46. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1
      Oh, NEAT. So you can afford the downtime of a service/site that must be available 99.999% of the time to find and move to another colo provider and deal with weeks of inavailability inbetween (due to the SBL block) every time SBL decides to block a slew of subnets around you just because some jerkoff decided to spam from it?
      You mean that you were not competent enough to think of setting-up a backup plan in case of disruption? Something along the lines of a unlisted smarthost welllll outside of the tainted netblock your server farm is on?
    47. Re:Definitely a bad idea... by XPACT · · Score: 1

      Well, I have been blacklisted too, but it was because I am using a dymaic IP and probably someone else from that IP pool ot some zombie PCs have been used for sending SPAM. I have my own webserver and mailserver at home on headless linux box (AMD K6-2 450Mhz) Have you ever thought that there are a lot of people just like me? I dont wan't to pay an extra $50 bucks to SBC for static IPs. Everithing (my web e-mail) can work fine with dynamic IP and DSL for just $19.99 (with no taxes) I know they made it recently 14.95. My point is that these extra $50 for 5 static IPs can be given for my cell phone bill. And I like the idea of having my own mail server. Now I have to use SMTP forward for sending mail, but it is OK.

    48. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1
      Your ISP may not allow spammers, but it really can't do a whole lot to stop every zombie before it sends any spam.
      Au contraire, mon cher.
      It's very easy to pre-emptively block every zombie before it sends any spam. Just block port 25 at the router and voilà! Instant spic-and-span network!
    49. Re:Definitely a bad idea... by Anonymous Coward · · Score: 1
      "Stupid" huh?

      BTW, I wasn't aware that credit bureau's will blacklist someone for borrowing from a particular bank that happens to have a lot of bad creditors also borrowing from it.

    50. Re:Definitely a bad idea... by keraneuology · · Score: 3, Interesting
      this is just a strongarm tactic to harass as many innocent parties as possible

      You hit the nail right on the head. In fact, a fly on the wall related to me the entire conversation from the morning they decided to set this thing up:

      Person 1: I'm bored this morning, how 'bout you?

      Person 2: Yeah, me too, dewd. Let's start harassing as many innocent parties as we can!

      Person 1: Yeah, dewd! That'd be way wicked cool!

      Anyway, they shouldn't be blocking entire blocks of IPs. That doesn't even make sense. What does one guy on one IP out of hundreds or thousands who spammed for most of a day before he got caught have to do with my server which has run clean and reliable and secure and in good faith (including SPF and everything else) for the better part of a decade?

      Blame the spammers' money and the greed of the ISPs. It used to be quite common for a spammer to run under his pink contract from an IP address until people got fed up and blocked that specific IP. Certain ISPs would then assign the spammer a new IP address knowingly full well what they were doing with the explicit intent of allowing that spammer to bypass the blocklists from people who were obviously and explicitly taking steps to avoid the spam. Unfortunately as it turned out truly innocent customers were being assigned a dirty IP address that had been previously sullied by a spammer. The moment their email server came online they were already blocked because of what had happened there before. Talk about unfair.

      The spam-friendly ISPs forced the blacklisting of IP blocks: there was simply no other way to filter out the spam coming from those netblocks. Other users of that hosting service may be inconvenienced, but the system admin's right to take steps to prevent spam from gumming up the works of HIS OWN NETWORK outweights the right of anybody else to expect email originating from the same IP address used to send out three trillion ads for vgiara the week before to be received with open arms.

      Does this catch innocent people in the crossfire? Unfortunately, yes. But with 4,228,250,625 possible IP addresses those who maintain the blacklists can't be expected to personally review each and every email asking to be whitelisted and spend time and effort determining who is telling the truth and who is following spam rule #1.

      If widget.qqq has your domain blacklisted then your beef is with the admin of widget.qqq. Period. End of story. Beg him to whitelist you. Buy him a pizza. Send him some free (as in beer) beer. Serenade him at three in the morning. Send three billion statements of character witness. But his network, his gate, his key, his rules on granting admission.

      Let's look at this another way: If I am throwing a party and, on the advice of my friend who told me that people who wear Mickey Mouse shirts are boring, I deny admission to people wearing Mickey Mouse shirts from whom will you beg entry and who shall be called nasty names for listening to somebody else?

      Of course, that's the solution, isn't it? We must ban any and all people from publishing an opinion regarding the statistical probability that an email from a given IP address is spam.

      --
      If the g'vt kept the data on you that google does you'd better believe you'd be calling it "doing evil"
    51. Re:Definitely a bad idea... by fm6 · · Score: 2, Insightful
      ...you can't argue that the process didn't put pressure on you to switch hosting providers, or at least put pressure on your hosts to ensure that they never host another spammer again...
      Wrong on both counts. Blacklisters are so quick on the trigger, there are no safe providers. And how is a provider supposed to "ensure that they never host another spammer"? They can only act after a user has started spamming. Plus, they have to take some time to investigate spam complaints -- yanking someone's service without documenting their TOS violations is a good way to get sued. That delay always seems to convince blacklisters that the provider is "spam friendly".
    52. Re:Definitely a bad idea... by golem100 · · Score: 1

      The *BL's are reference resources. Some free, some by subscription. They block nothing. The blocking agency continues to be _your_ Email Administrator--as it is that individual who makes the determination which *BL to reference and how much weight to give to its pronouncements. As such, any "power" that an "*BL" has devolves from the opinion of its subscribers as to the value/validity of its judgments. They can be as rabid as they will--if the Email Admins who look to them devalue their judgments--the impact will be minimal. So--don't bother complaining to the *BL operators--have a chat with the Email administrators with the orgainization you echange Email with--if they agree that the *BL is not doing its job--they will lower the weight they give that *BL. [...or not--if they share the opinion that you view is not correct!]

    53. Re:Definitely a bad idea... by EvilStein · · Score: 1

      Go ahead, try that. Try that "You, the ISP, broke the contract" bit.

      See how far it gets you. How far will it get you? Absolutely NOWHERE. You've obviously never dealt with a colocation provider.

      That stupid type of comment always pops up in these threads (nothing against you personally) but in reality, it won't work. it'll cost you thousands of dollars in legal fees at the very least.

    54. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      isnt spamhaus exactly the list that was criticized as becoming like maps in tfa?!

      im confused

    55. Re:Definitely a bad idea... by Minstrel+Boy · · Score: 1
      I dont wan't to pay an extra $50 bucks to SBC for static IPs.

      It doesn't matter. I *do* pay the extra $50 to SBC, and have run my own clean, personal mail server for years. Just last night I had an SMTP connection denied 553 "Excessive spam from address 66.125.9." - so they blocked at least the /24 I'm on, which is all statically assigned "Pro" DSL space for SBC. That particular message was an attempt to get an instructor in contact with his student to answer some questions about the course material.

      The fascists' response is that I should forward all my mail through SBC's mailservers - hell, if SBC could deliver mail I wouldn't have started running my own mail server in the first place. *I'm* following the RFCs, if you choose to throw my legitimate mail away, fine, but don't tell ME how I "should be" sending it. That sword cuts both ways.

      Sure, they can say "we don't want to accept mail from anyone in DSL space", that's their call - but they shouldn't pretend no innocent parties are being affected, or that no innocuous mail is being dropped.

      KeS

    56. Re:Definitely a bad idea... by jaeson · · Score: 1

      He could also have phoned the blocklist operators...

      Oh Yeah, where _did_ I put that phone number for the SPEWS guys? Oh now I remember, they are totally anonymous. Fuck SPEWS and their "collateral damage". When you block sites like the Linux Kernel Mailing List (and many other legit sites too) your blocklist just became totally unusuable.

    57. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      You're either stupid or trolling. The article is about DNS blocking lists. Those are lists which, by using DNS as a query mechanism, publish a list of ip addresses. That's it. They usually have a website and a policy telling you what is supposed to be on that list, but they NEVER block mail. By publishing a list, they give a rating. Someone else takes action based on that rating. None of your mail goes through a DNS blacklist operator's mailserver. They are simply not in the position to block anything.

      To laymen (and dense people) it sometimes looks like the DNS blacklist operators are blocking mail because some ISPs use DNS blocking lists to automatically reject email. The effect is that the decisions of the blacklist operators cause mail to be rejected, BUT it is still the ISP who decides to block email. He could just mark it and let the user filter based on the score, for example. Or he could just not use DNS blacklists at all. Whatever he does, it is never the blacklist operator who blocks anything.

      The way this chain of causality is constructed usually prompts people to absolve the blacklist operators of any guilt. Paul Graham neither defends the blacklist operators nor does he accuse them (well, he does, but he recognizes that their overzealousness comes with the territory). It's the principle of centrally administered DNS blacklists that is at fault here, not the individual operator.

    58. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      Every SA whos been there has had to get removed from a RBL.
      In the early days one of my clients was put on one for who the f@#$ knows, but it took quite a bit of time to restore mail functionality, that kinda soured me on the whole idea.

      I think the RBL providers just need to be sued for loss of business, afterward a subpeona issued for another lawsuit to determine the person who put the innocent on the RBL list.

      This is why we have courts, the next time I end up on an RBL for not spamming I think I will sue.

      There are so many different ways to skin a cat here, and so many different types of damages involved, it could actually be fun.

      I take my job as a SA seriously, part of what I do is limiting liability for my clients and myself. This should merely flush out all the SAs who fail to operate as if the internet is a commercial medium.

      Yes, you can use the court system to sue organizations of people, what do you think a corporation is, or the gov't, or fuck just about any institution.

    59. Re:Definitely a bad idea... by syukton · · Score: 2, Insightful

      They usually have a website and a policy telling you what is supposed to be on that list, but they NEVER block mail. By publishing a list, they give a rating. Someone else takes action based on that rating. None of your mail goes through a DNS blacklist operator's mailserver. They are simply not in the position to block anything.

      Yes, I know that. They just make a list. I said that, I also said that they believe that "just making a list" absolves them from all responsibility. I also said that blacklists are implemented (by people who implement them, namely system administrators) very poorly. Were you paying attention? Do you understand?

      The implementation of a blacklist is how the ISP uses it. Do they notify the customers? Do they send a weekly "You got spam from these addresses..." message? Do they enable to customers to easily edit the blacklist so that illegitimately added hosts can be removed quickly? I really don't think you understood me. heh.

      It's the principle of centrally administered DNS blacklists that is at fault here, not the individual operator.

      I said that a few times. Are you sure you were paying attention when you read my comment? I said that having a list maintained by people who believe themselves to be absolved of responsibility and can edit the blacklist willy-nilly without vote or consensus is bad, and we should switch to something more wiki-style that more people would have a say in.

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    60. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      I guess the RBL's will have to follow the lead of the spammers and place their RBL servers in Siberia, or somewhere else to avoid legal repercussions.

    61. Re:Definitely a bad idea... by Fulcrum+of+Evil · · Score: 1

      And, in terms of preventing the "sending" of mail, you could consider a blacklist to be a postman who would, whenever he saw a letter from a given return address, he'd destroy it.

      Okay, let's use that metaphor. The postman has 50 lbs of mail for you every day. 45 lbs are fraudulent or advertising some sort of snake oil/porn site. Your mailbox holds 7 lbs of mail. The postmaster has a list of people who send mail to every email address on the face of the earth and a good number of addresses that don't exist. The postman takes those sending addresses and uses them to weed out roughly 40 lbs of mail, so your mailbox is only half full of crap instead of 90%. Unfortunately, you just lost 30% of your mail because it wouldn't fit.

      A blacklist allows any server in-between the sender and the recipient to say "no, sorry, your ass is blocked."

      Do you have a better idea?

      As email becomes more and more prevalent as a form of legally recognized communication (emails are used in court as evidence) it's important to recognize the implications of interfering with that communication without disclosing such interference.

      Irrelevant. Nobody expects that email is a reliable transport, and sending mail is no proof of receipt. The legal status of email is largely irrelevant to the question.

      Would you like it if I were your postman and every time I saw your electric bill, I took it and destroyed it because I didn't like the electric company and I didn't think anybody should be subjected to their tortures?

      Strawman. I have never had a legit receipt get blocked. Also, that is counter to how RBLs tend to operate.

      We need a wiki-style collaborative blacklist that has a membership of thousands who all collaborate on this issue.

      Yeah, that'll scale.

      It's just one more example of how giving one person too much power before they're ready to use it responsibly with proper discretion results in a disaster.

      Don't like it? Don't trust the RBL 100% - you can always use it as a scoring mechanism

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    62. Re:Definitely a bad idea... by Fulcrum+of+Evil · · Score: 1

      When a hosting provider provides services to a spammer, he is a spam-supporter (as well as the other clients who pay him), so it is only fair that the whole network be listed as the spamhaus it is.

      Yeah, because hosting providers always know who the spammers are and all the other clients can immediately jump ship. Get a clue.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    63. Re:Definitely a bad idea... by Tim+C · · Score: 1

      Once I drop a spammer into the system blacklist they're there for life. I don't have the time or energy to audit my block list, and what would be my motivation anyway?

      How about jsut not being a twat? IPs change hands; today's spammer is tomorrow's innocent victim of your tendency to be an arsehole.

    64. Re:Definitely a bad idea... by capilot · · Score: 1

      Actually, my blacklists are mostly keyword-based, although there are some IP blocks listed (mostly in China).

      All I can say is that the inconvenience caused to the new owner of a tainted block of IPs does not outweigh the inconvenience caused to me by spam.

      True, this means that there are huge blocks of IP addresses out there that have become poisoned by the spammers. It's like a piece of real-estate tainted by toxic waste from the irresponsible gas station that used to be located there. Sure, it sucks for the new owners of the land, but why is that my problem?

      Blacklists are not a perfect solution. If you think you have a better one, I'm sure we'd all like to hear it.

    65. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      Quoting you:

      "Actually, I'm with singletoned" (read what he wrote, he's simply not getting it)

      "that's the problem with blocklists controlled by individuals that can block huge IP blocks." (DNS blacklist operators NEVER, repeat NEVER, block anything.)

      "you could consider a blacklist to be a postman who would, whenever he saw a letter from a given return address, he'd destroy it." (No, you couldn't. You could compare an ISP to a postman who destroys letters because someone else, the blacklist operators, said the letters were spam. That is, you would use these analogies if you have a hard time understanding an issue without analogies.)

      I kind of lost interest after you tried to get that broken and misleading analogy across for another two long paragraphs.

    66. Re:Definitely a bad idea... by capilot · · Score: 1
      Well, I have been blacklisted too, but it was because I am using a dymaic IP ... Have you ever thought that there are a lot of people just like me?

      Sure; I'm one of them. My own IPs are blacklisted for the exact same reasons yours are. I sucked it up and started using my service provider's static mail host rather than trying to use direct-to-mx email. Yeah, it's a hassle, but well worth it to keep my spam load down.

    67. Re:Definitely a bad idea... by Tripster · · Score: 1

      You mean we just need to add "are you a spammer?" on the signup form and we'll always be able to tell if a client is legit?

      Exactly how do you figure a legitimate hosting provider is going to know BEFOREHAND that a new client is a spammer?

      Any hosting provider could inadvertantly host a spammer, heck I've been blacklisted because a client of mine was involved with spammers elsewhere outside my services and the client had not once used my servers as part of his spammer resources, how am I supposed to know that he is involved elsewhere though? I was never informed of it, just one day SPEWS has us listed and even has some of our secondary DNS servers listed, none of which had anything to do with propogating any actual spam.

      And yet somehow, magically, we are supposed to just know our client is a spammer.

      They never did explain to me why they didn't also list the guys cable company, his telco, his other utilities he used outside his spamming activities, I mean fair is fair, if you want to punish spammers just list every possible service company they deal with and be done with it.

    68. Re:Definitely a bad idea... by shiksaa-spamhaus · · Score: 2, Insightful

      Been blacklisted by whom, pray tell? You people who whine about Spamhaus have no clue what you're talking about. Spamhaus has editors around the globe and that means people who don't lie and who get their spam problems under control get removed - and get removed promtly. I defy any of you to show that Spamhaus has been non-responsive to anyone except spamming and spam-supporting liars.

      I will thank you to stop painting everyone with the same brush. Spamhaus isn't SPEWS nor is it any other list. You don't like being listed? I wouldn't either, but then I don't spam nor do I host spammers. Deal.

      And if you like spam so much, I have a metric buttload of it I'd be happy to forward to you each and every day. Send me your email addy if you've got the guts. I'm guessing you're all b.s. - IOW, you don't have the nuts or the guts to put your mailbox where your mouth is.

    69. Re:Definitely a bad idea... by DavidTC · · Score: 1
      You know, you're an idiot for suggesting email just vanishes because of blacklists. You have no idea what you're talking about.

      In fact, blocking via blacklisting is the only majorly-used spam fighting method that lets the sender receive notification their email was decided as spam.

      Every other method accepts the email and runs tests on it, and then maybe the recepient sees it, or not, or they have to go look for it in the 'spam' folder, or whatever. The only options are 'Pester the user with this or not?', and if they guess 'no' wrongly, the mail does vanish.

      Blacklisting does not accept the email, and thus the sender's mail server will turn around and say 'Hey, that message you just tried to send? They rejected it, giving this reason: Blah blah blah'. At least then someone knows something went wrong.

      Of course, there are milters and whatnot that can do actual content filtering in the mail server at that point, but those are complicated to set up and suck CPU because you have to do all that processing when the message is accepted, instead of whenever you feel like it. They works perfectly for personal servers, possibly work well for huge server farms, and suck ass for a 120-person company operating a mail server on a Unix box. (And the huge email guys don't seem to use anything like that, so I must assume they don't work.)

      And those have the fun issue that some mail servers are broken and don't accept rejections after they send the email. So the bastards will just try again and again.

      Whereas a DNS blacklist just causes SMTP server to do a quick DNS look up or two and not respond until it's done, which isn't 'quick' but at least doesn't suck CPU.

      And I have no idea what you mean by 'a blacklist allows any server between the sender and the receipient'...you are aware that no email is forward by random third parties anymore, right? And if you had someone SMTP forwarding your incoming mail, you better damn well be in charge of the spam filtering on them, and it should be right there in the contract. And outgoing smarthosts don't filter mail at all, that doesn't even make sense.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    70. Re:Definitely a bad idea... by shiksaa-spamhaus · · Score: 1

      You live in a ghetto, you suffer the consequences. Instead of whining about being a casulty, why don't you do something useful like ridding your neighborhood of the thugs or move to a better neighborhood? Nah, you'd rather whine about it.

    71. Re:Definitely a bad idea... by DavidTC · · Score: 1
      When a hosting provider provides services to a spammer, he is a spam-supporter

      I agree with you, but you are utterly wrong here.

      They are not spam supporters. They are SPAMMERS.

      'spam supporting' would be, like, washing their windows or doing their taxes.

      If you operate a network and knowingly allow spam to exit from it, you are spamming. Doesn't matter who clicked 'send'.

      We need to stop this double-speak. If you drive the getaway car for a bank robbery, you are a bank robbery. If you provide a network for spammers to use, you are a spammer.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    72. Re:Definitely a bad idea... by gregmac · · Score: 1
      Anyway, they shouldn't be blocking entire blocks of IPs. That doesn't even make sense.

      Can you suggest another effective way for an outsider to apply pressure to an ISP that hosts a spammer?

      What difference does it make? You block the IP, he can't send spam anymore (to people subscribing to the RBL). Blocking the whole subnet means blocking legitimate, unrelated mail. You wouldn't burn down your house because a fly got in, would you?
      --
      Speak before you think
    73. Re:Definitely a bad idea... by jacksonj04 · · Score: 1

      Port 25 *outbound* - If my ISP blocks 25 inbound they're going to have some explaining to do.

      --
      How many people can read hex if only you and dead people can read hex?
    74. Re:Definitely a bad idea... by DavidTC · · Score: 1
      Good point.

      Now find a single blacklist that blacklists ISPs without notifying them and waiting for them to remove the spammer.

      Oh, wait, there aren't any.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    75. Re:Definitely a bad idea... by eric76 · · Score: 1

      It is quite possible for an ISP to be blacklisted in spite of the fact that no spam has ever come from their network.

    76. Re:Definitely a bad idea... by XLawyer · · Score: 1

      Blocking the single IP gives the ISP an incentive only to move the spammer to a different IP. That doesn't deal with the recipient's problem.

    77. Re:Definitely a bad idea... by gregmac · · Score: 1

      It used to be quite common for a spammer to run under his pink contract from an IP address until people got fed up and blocked that specific IP. Certain ISPs would then assign the spammer a new IP address knowingly full well what they were doing with the explicit intent of allowing that spammer to bypass the blocklists from people who were obviously and explicitly taking steps to avoid the spam. ....
      The spam-friendly ISPs forced the blacklisting of IP blocks: there was simply no other way to filter out the spam coming from those netblocks.

      Maybe instead of being lazy, the list administrators should do it in a way that at least minimizes damages. If an ISP moves a blacklisted custmoer to another IP, flag them as possible spam-friendly, and investigate further: ask the ISP whats happening, check if it's REALLY spam*. If it happens again, or the ISP give an unsatisfactory response, then flag them as spam-friendly. At that point, you can blacklist the ISPs netblock. Even skipping the second step, and only listing the netblock if the site has moved IPs within the same netblock owner would be better than it is now.

      * I run a small shared server, and we've been blacklisted before for a legitimate opt-in newsletter. instead of unsubscribing, someone sends to abuse@whatever and suddenly, entire netblock is listed.

      --
      Speak before you think
    78. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 2, Insightful

      I'm with singletoned, and I think it's you that has a problem with understanding.

      He(?) claimed that RBLs prevent people SENDING. He is wrong. If you agree with him that RBLs prevent sending, you are also wrong.

      Reading the facts isn't enough, you need to be able to manipulate those facts and draw provable conclusions from them

      Snicker. Donny Rumsfeld in da house!

      I do think people should be forced to accept every email that I send.

      Then you are no different than a spammer. And it's clear from the rest of your drivel that you really don't understand what happens when an RBL is in use. Hint : legitimate email suffering an RBL false-positive doesn't disappear into a black hole. That's one of the reasons why RBLs are so effective, even in an environment where some false-positives are inevitable. Or to put it another way, if the "collateral damage" from RBLs were anything other than insignificant, compared to the benefit they provide, then world+dog wouldn't be using them.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    79. Re:Definitely a bad idea... by trelanexiph · · Score: 2, Interesting

      Casualty of war? I think they're saying they don't want your e-mail. The internet is an even peering system. My netblock is my castle, and if I don't want you to enter you and your SMTP traffic can sit outside in the rain. You are under the misimpression that SMTP is reliable, it isn't. DNSBL's don't make it less so, they make it more so by allowing administrators to reliably filter whatever they want, whenever they want, for whatever reason they want. And if they want to use SPEWS MAPS SBL, or the AHBL they can, because guess what it's their server.

    80. Re:Definitely a bad idea... by keraneuology · · Score: 1
      Maybe instead of being lazy, the list administrators should do it in a way that at least minimizes damages. If an ISP moves a blacklisted custmoer to another IP, flag them as possible spam-friendly, and investigate further: ask the ISP whats happening, check if it's REALLY spam*. If it happens again, or the ISP give an unsatisfactory response, then flag them as spam-friendly. At that point, you can blacklist the ISPs netblock. Even skipping the second step, and only listing the netblock if the site has moved IPs within the same netblock owner would be better than it is now.

      Feel free to set up a list that follows these steps. You may even get a few subscribers. Or a lot. I'll bet that you get sick of the administrative overhead after a month and you'll still have people chewing you out for blacklisting a netblock no matter what you do.

      I run a small shared server, and we've been blacklisted before for a legitimate opt-in newsletter. instead of unsubscribing, someone sends to abuse@whatever and suddenly, entire netblock is listed.

      And of course you were able to send the email the complainer sent as part of your confirmed opt-in process to be removed from the list, right? You were using confirmed opt-in, right? I have lots of spammers claiming that I opted in to their lists, even though they were clearly using harvested addresses used for nothing aside from posting resumes to monster-and-similar sites.

      Again, for emphasis, the people who run the blacklists don't care what you, I, or anybody else think, nor are they under any obligation to do so. You are not their customer, their friend, a supplier of free beer or a source of possible sexual encounters. Any complaints directed at them is like peeing into the wind, only somewhat less effictive at keeping your comfort level high. If your emails are being blocked unfairly your -ONLY- legitimate target of complaints is the network admin who has decided to block messages originating from your server. He may listen to you. Or not. His network, his gate, his key, his rules.

      If I bought 100% of the shares of eBay tomorrow then decided to block anybody with an IP address where the third octet wasn't either a prime or a sum of two cubes it would be entirely my right to do so. It would then be up to me to deal with the consequences of my actions. The math geek who wrote up the list of all prime numbers and sums of two cubes between 0 and 255 would have nothing to do with it as I would have made the decision to apply said list to my IP filters.

      --
      If the g'vt kept the data on you that google does you'd better believe you'd be calling it "doing evil"
    81. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      SpamHaus lists seem to be very effective. I've yet to hear of anyone being wrongly listed.

      Now you have. They will happily list every IP an ISP controls if they have EVER had a ROKSO on their network however unwittingly or even if they buy out and clean up an ISP that did. They then start blocking everyone within 3 degrees or so of seperation of anyone in your the ISPs whois info.

      They will block a whole netblock on the strength of a single complaint. They will not in any way share the abuse complaint that prompted the action (I could understand anonymizing the complaintant, but they won't provide anything) or even enough info from it to determine what customer might have spammed.

      They will make sure you know they expect their asses kissed thoroughly should you even need to contact them about an error (if they do you the supreme favor of responding, that is).

    82. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      Terrorist! Was that over the top enough? lets see, what else, other than "spammer" can I accuse you of that would fall in to that "he's not a human" category? Food for thought.

      More food for thought: too many bad mailserver admins use RBL's in piss poor ways. Those admins point the finger at the RBL's, who in turn point the finger at the users of the RBL's, who point to the bad mail admins, who point to, well, you get the idea. Add to that the fact that most of those running the RBL's have an attitude on collateral damage that is as bad, if not worse than the attitude of spammers, and you have a lot of angry people on both sides.

      Have you ever found anyone that got hit in the expanding scope issue that still relies on RBL's?

      One last thought:has anyone using RBL's to block mail in the US taken a good look at federal ISP Safe Harbor provisions? This might just push your mailservers outside of the bounds...

    83. Re:Definitely a bad idea... by shiksaa-spamhaus · · Score: 1

      If your ISP has half a clue and a functioning abuse desk, those pesky zombie problems get the boot in a hurry. OTOH, if your ISP is lacking either in ethics or manpower, either deal with it and stop whining or find one that cares about running a clean network. If you want cheap service, you very often get exactly that - cheap electronic swampland.

      You don't need a freaking Ouija board to find a decent non-spam friendly ISP - if you can figure out how to post here, you can surely do your due diligence by checking to see if they're listed by us or anyone else or if there are a few too many mentions of them in Google. Really, people, this is not rocket science.

    84. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0
      If you drive the getaway car for a bank robbery, you are a bank robbery. If you provide a network for spammers to use, you are a spammer.

      Right, and if the getaway mode is public transit, then I suppose the subway/bus/tube driver is at fault. No, no, obviously that's not right. No, because the whole public transit system is at fault. We must punish the providers of such systems. It all starts at the top; our local government officials should be tried for every bank robbery...

      Where exactly does it end?

      It's all well and good in theory, but how many draconian surveillance measures would you be willing to tolerate, such that the top tier network providers can police this problem down to the level of a single moron spammer?

    85. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      "Except that blocklists don't stop you sending email"

      Bollocks. You know exactly what he means, and what he says is true.

    86. Re:Definitely a bad idea... by sjames · · Score: 1

      That Paul Graham is terminally clueless. When a hosting provider provides services to a spammer, he is a spam-supporter (as well as the other clients who pay him), so it is only fair that the whole network be listed as the spamhaus it is.

      Because, of course, spammers NEVER lie when they sign up for service and good customers never get a spam virus. Ever notice how many blacklisters who bother to contact an ISP only provide options of "No action taken" (blacklist me forever and "Customer terminated", never "report was in error", "complaintant requested this email", or "virus killed"?

    87. Re:Definitely a bad idea... by sjames · · Score: 1

      Au contraire, mon cher. It's very easy to pre-emptively block every zombie before it sends any spam. Just block port 25 at the router and voilà! Instant spic-and-span network!

      That'll go over REALLY WELL with their colo customers!

    88. Re:Definitely a bad idea... by gregmac · · Score: 1

      Blocking the single IP gives the ISP an incentive only to move the spammer to a different IP. That doesn't deal with the recipient's problem.

      So, you block the new IP. And you do a check - have we blocked this domain before? Was it on an IP in a subnet owned by the same company? If yes to both, THEN you block the subnet. You're still probably blocking other legitimate traffic, but at least you give an honest ISP a chance without blocking their other customers.

      --
      Speak before you think
    89. Re:Definitely a bad idea... by Cramer · · Score: 1

      And thus is your own answer... If the ISP moves a known spammer to a different IP once they've been "found out", it's clear the ISP has no intention of properly dealing with spammers (i.e. kicking them out.) At that point, it would be marginally acceptable to blacklist entire subnets or the entire ISP -- but that's still a strongarm tactic.

      Blacklisting more than one IP when only one has briefly been a problem is stupid. Listing an ISP's /16 because one customer -- with a /29 -- did something wrong is going way to far (like swating house flies with nukes.)

    90. Re:Definitely a bad idea... by rodgerd · · Score: 1
      Person 1: I'm bored this morning, how 'bout you?

      Person 2: Yeah, me too, dewd. Let's start harassing as many innocent parties as we can!

      Person 1: Yeah, dewd! That'd be way wicked cool!
      That sounds pretty much how ORBS was operating before it flamed out.
    91. Re:Definitely a bad idea... by syukton · · Score: 1

      I'm with singletoned on the notion that you didn't read the article.

      I'm still convinced you didn't.

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    92. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1

      Usally, colo farm computers don't get zombied...

    93. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1

      That's because only spammers use the "report was in error", "complaintant requested this email", or "virus killed" excuses.

    94. Re:Definitely a bad idea... by Pig+Hogger · · Score: 1
      Any hosting provider could inadvertantly host a spammer, heck I've been blacklisted because a client of mine was involved with spammers elsewhere outside my services and the client had not once used my servers as part of his spammer resources, how am I supposed to know that he is involved elsewhere though? I was never informed of it, just one day SPEWS has us listed and even has some of our secondary DNS servers listed, none of which had anything to do with propogating any actual spam.
      Well, you were providing some service to a spammer, so that's the reason why SPEWS listed you because you did not terminate the service when SPEWS complained to you (of course, SPEWS complaints are NOT advertised as such, so you ignore your ABUSE inbox at your peril).
      And yet somehow, magically, we are supposed to just know our client is a spammer.
      There is nothing magic. SPEWS will allow you to host a spammer, and they won't list you if you promptly terminate the spammer when they complain about it. You got blacklisted because you IGNORED complaints about the spammer.
      They never did explain to me why they didn't also list the guys cable company, his telco, his other utilities he used outside his spamming activities, I mean fair is fair, if you want to punish spammers just list every possible service company they deal with and be done with it.
      When you got listed, you obviously didn't read the SPEWS FAQ. You got included because the network ownwer(s) above you simply did not remove their pet spammers in due time. You were most likely "collateral damage".
    95. Re:Definitely a bad idea... by syukton · · Score: 1

      Okay, let's use that metaphor. The postman has 50 lbs of mail for you every day. 45 lbs are fraudulent or advertising some sort of snake oil/porn site. Your mailbox holds 7 lbs of mail. The postmaster has a list of people who send mail to every email address on the face of the earth and a good number of addresses that don't exist. The postman takes those sending addresses and uses them to weed out roughly 40 lbs of mail, so your mailbox is only half full of crap instead of 90%. Unfortunately, you just lost 30% of your mail because it wouldn't fit.

      Then deliver 7 pounds of mail per day over a 7 (and some fraction) day period. This is totally irrelevant though, because if something won't fit in your mailbox, the postman will come to your door and tell you about the package or packages and require you to sign for them because they couldn't be transmitted to their legal receptacle (the mailbox).

      Irrelevant. Nobody expects that email is a reliable transport, and sending mail is no proof of receipt. The legal status of email is largely irrelevant to the question.

      Um, what?

      I did a google search on e-mail site:.gov and came up with tons of results. Here's one:
      http://www.doiu.nbc.gov/orientation/email.html
      This page describes the Department of the Interior's email policy.
      They say: e-mail systems are highly reliable for transmitting messages.
      They also say: Q4. If my outgoing message is a record, should I ask for a return receipt to make sure that the person I sent it to got it?

      A4. It is not necessary to ask for a return receipt or read receipt in e-mail any more than it is necessary in hard copy. We don't send all letters certified mail. If it is important to document for the record the time that a message was opened, then that receipt must be retained along with the message for as long as the message is retained. You also need to have some means of linking the receipt to the message so it is clear what outgoing message the receipt documents.


      So they acknowledge openly that the mail could be intercepted in transit, just as postal mail could, but they still consider it to be highly reliable.

      From a state government website (Kentucky):
      http://www.kdla.ky.gov/recmanagement/tutorial/emai l.htm
      Electronic Mail (e-mail) is an important communication tool for conducting government business in the Commonwealth of Kentucky. Increasingly, government agencies use e-mail systems to distribute memos, circulate drafts, disseminate directives, transfer official documents, send external correspondence, and support various aspects of government operations.

      Disseminate directives? Transfer OFFICIAL documents?

      The office of the attorney general in New York began accepting document service by email in 2003:
      http://www.oag.state.ny.us/serviceag/serviceag.htm l
      Except as set forth in paragraph 2, below, beginning January 1, 2003, the Attorney General's Office will participate in the Court of Claims' Filing by Electronic Means (FBEM) pilot project and will accept service by e-mail of the following documents

      Digging back into the internet stone age, is this article from the year 2000, Judge allows subpoenas delivered via email. If Y2K wasn't your bag though, 2002 saw a different judge uphold the validity of process serving by e-mail.

      Do I need to keep going to illustrate how totally wrong you are not only about the reliability of email, but of the perceived reliability of email? (I shouldn't have to, but this is slashdot, after all)

      As to the l

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    96. Re:Definitely a bad idea... by syukton · · Score: 1
      You know, you're an idiot for suggesting email just vanishes because of blacklists. You have no idea what you're talking about.


      Here we go again, another one that doesn't understand... I didn't suggest that email disappears as a result of blacklists. I suggested that infuckingredibly ignorant implementations of blacklists result in mail disappearing into the digital void.

      In fact, blocking via blacklisting is the only majorly-used spam fighting method that lets the sender receive notification their email was decided as spam.


      And what good does that do, exactly? What do you do to correct it? Mail the admin@whateverhost.com? How do we do that if our e-mail is being blocked? Hmm? Do these "your message has been blocked" e-mails contain a phone number at which you can call somebody to have your address unblocked? I have never, EVER seen a "your message has been blocked" mail that contained a phone number. So while it might be great that a blacklist will notify the sender that the message wasn't transmitted to its intended recipient, they seldom (if ever) provide a means for the sender to easily correct the problem. Again, it's about shitty implementation of blacklists and not the blacklists themselves.

      And I have no idea what you mean by 'a blacklist allows any server between the sender and the receipient'...you are aware that no email is forward by random third parties anymore, right? And if you had someone SMTP forwarding your incoming mail, you better damn well be in charge of the spam filtering on them, and it should be right there in the contract. And outgoing smarthosts don't filter mail at all, that doesn't even make sense.


      You can't talk about this in absolutes because you don't know how people use e-mail. E-mail is forwarded by third parties, still, to this day. There are instances in which mail does not go directly from point A to point B.

      Consider for example an autoforwarding filter that transmits mail from your work address to your home address while you're on vacation. Now the message hits at least two incoming mail servers, the one at work and the one at home. What happens if you're not at your computer at home and you've got the home computer set up to forward to your mobile device (pager, RIM, whatever)? Then there's a third server in the mix, the one your mobile device uses. What about people who have one e-mail address they use in plain text online (and which therefore receives a lot of spam) but they've got a filter set up that auto-forwards mail that contains [Job], [Friend], or [Urgent] in the subject line? What if the address the auto-forwarder points to just upgraded to some new version of a blacklist that blocks the address that received the mail originally (and is thus doing the forwarding)? Then the address that never gets checked because it's full of spam gets a "your message was blocked" message, which is totally useless.

      I think you're the idiot. You speak in absolutes and you do so without considering that there are other people out there who use e-mail in a manner that you personally do not. That's a mark of idiocy, as far as I'm concerned.
      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    97. Re:Definitely a bad idea... by syukton · · Score: 1
      Singletoned didn't claim that RBLs prevent people from sending. He did not make an all-encompassing statement like you did. He claimed that in a given instance, a blacklist was used to prevent the sending of mail. Perhaps "sending" isn't the right word to use, but intercepting mail in transit before it reaches the intended recipient and then not telling the intended recipient of the intercept is kind of getting in the way of sending the mail. I mean, if you put insufficient postage on a letter and stick it in the mailbox and then you get it back with an "INSUFFICIENT POSTAGE" stamp/sticker on it, do you feel like you've been prevented from sending the message? It doesn't matter that the message went out in the mail when you stuck it in the mailbox (or clicked "Send") because it came back before it reached its recipient. It's this not-reaching-the-recipient that would lead somebody to the conclusion that mail is being prevented from being sent. That the block is implemented on the "receiving end" (but not by the receiver, so I don't know how you can call it the "receiving end" as it's more like the "transmission stage" than anything, an in-the-middle place that is neither sender nor recipient) really doesn't matter, as the effect is that the message sent to a given recipient is not received as intended, providing the impression that it did not get sent properly.

      Or to put it another way, if the "collateral damage" from RBLs were anything other than insignificant, compared to the benefit they provide, then world+dog wouldn't be using them.


      So we have to wait until blacklists become significantly harmful before we'll change our ways? What ever happened to foresight? Just because they're having a small harmful effect now doesn't mean that will always be the case. Waiting until something is broken to fix it gives you massive power outages (Summer 2003, northeast USA, and in Russia recently), huge security holes (anything from Microsoft), and so forth. Don't wait until it's a problem to fix it, FIX IT NOW.
      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    98. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      Perhaps "sending" isn't the right word to use

      Erm, right, because this actually is about receiving, not "sending". Like I said. Before.

      You seem to be hung up on the fact that (usually) , the intended recipient of a message doesn't receive notification that a message was rejected. But the sender will get a non-delivery report from their own local system. The onus is on the sender to decide what to do about non-delivery. How can any recipient be under any obligation to ensure the delivery completes? To be forced to accept anything? To relinquish the ability to decide which traffic enters their own, privately owned equipment? That's absurd.

      Furthermore, notifications to the intended recipient are worse than useless : almost all of the time they will be spam rejection notices. A spam rejection notice in my inbox (or even filtered into a junk folder) is no different than the spam itself. (cf those braindead mail systems that notify intended recipients that a virus was not delivered; or even worse, those that send the same notification to the purported (spoofed) sender; or, the piece de resistance, the system that sends a non-delivery report to the spoofed sender, and includes a copy of the original, virus-infected message as well. The latter is ignorance bordering on negligence).

      So we have to wait until blacklists become significantly harmful before we'll change our ways?

      Actually, from my own experience and that of other postmasters I talk to, over the last few years RBLs seem to be holding up pretty well in terms of a benefit/harm ratio. If anything, the harm is decreasing as postmasters become increasingly clueful in the ways they implement them. My last true false-positive incident was almost two years ago. I'm never going to say that RBLs are any kind of solution to the wider problems we have with unsolicited bulk email; they're one more tool in the bag of tricks. But they do work at least as well as any other technique we currently have.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    99. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      Do they send a weekly "You got spam from these addresses..." message?

      What value, really, does such a notification have? I would say "little to none whatsoever". Most always, there will be no false positives listed, and that's assuming you can even be bothered to examine the weekly message. A notification that I didn't receive a spam, is itself spam. I simply don't care that messages were rejected, because false positives are so rare, and the payoff is so high, the tradeoff is unquestionably worth it. If you're going to go the trouble of sending notifications of rejected messages in order that a recipient can catch a false-positive, you may as well just deliver the original messages in the first place.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    100. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      I think the RBL providers just need to be sued for loss of business...This is why we have courts, the next time I end up on an RBL for not spamming I think I will sue.

      That would be a laugh, although not for yourself. Assuming you're not so naive as to believe you're the first cartoony to think of suing, you might want to consider why there haven't already been swathes of court decisions against RBL operators.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    101. Re:Definitely a bad idea... by henrywood · · Score: 1

      No, Spamhaus wasn't the list being criticized in tfa.

      Yes, you are confused.

      --
      Something is happening here but you don't know what it is, do you, Mr Jones.
    102. Re:Definitely a bad idea... by Fulcrum+of+Evil · · Score: 1

      Um, what?

      You heard me - no guarantee of receipt, easy to spoof, etc. Just because people percieve something as reliable doesn't make it so.

      Disseminate directives? Transfer OFFICIAL documents?

      Yes, because you can always send something again.

      Digging back into the internet stone age, is this article from the year 2000, Judge allows subpoenas delivered via email. If Y2K wasn't your bag though, 2002 saw a different judge uphold the validity of process serving by e-mail.

      Great - claim that somebody has a particular email and call that service. It's a joke, just like CA and their paternity system - they ask the mother who the father is and where he resides. Without any attempt to verify any of this, if you don't contest paternity within the time limit, you're a daddy.

      Your last link (I'm lazy - I didn't check all of them) refers to a case involving an online business, which is substantially different from general process service. Quotes from your cite:

      Specifically, the 9th Circuit noted that the parties had not presented any legal "authority condoning service of process over the Internet or via email.

      Do I need to keep going to illustrate how totally wrong you are not only about the reliability of email, but of the perceived reliability of email?

      Yes. All you've done is demonstrate that the very people who generally don't get technology percieve email as secure and reliable. It may be reliable within an org, but not in the general sense. It lacks the basic facilities to do that, so regardless of its preception, it is what it is.

      As to the legal status of email in terms of recognized communication, it is HIGHLY relevant. Interference in legally recognized communication can become a very tricky thing, because then it can potentially become interference in interstate commerce--something the government can and does regulate. (see also: war on drugs)

      Let's not deal with the WOD - it's genrally an egregious waste of time and violation of our rights. As far as interference goes, spam filtering is generally recognized and, when done properly, does not mistake legitimate mail for spam. I'm not really clear on this 'legally recognized communication', as you've cited an internet case and one where subpoenas were sent along with registered mail copies. The fact that some legal documents are recognized went sent by email in coms circumstances does not mean that all email is legally protected. If a judge were to rule that way, then it would be illegal to filter mail from the next email worm, which is clearly absurd. Face it, email isn't as reliable as you think, and sometimes it gets lost. Also, deleting an email is not illegal, at least not yet.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    103. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      Implementing a blacklist is what the blacklist operator does. He turns a concept into a real existing blacklist. That still does not encompass blocking anything. Consequently, "infuckingredibly ignorant implementations" of blacklists still NEVER result in mail disappearing. NEVER. Got that? NEVER! A badly implemented FILTER does what you describe, but that is conceptually, legally and organizationally separate from anything a blacklist operator does. Get it through your thick skull. You'll meet much less resistance once you start using correct terminology and stop mixing up concepts.

    104. Re:Definitely a bad idea... by dheltzel · · Score: 1
      Except that blocklists don't stop you sending email, they merely allow others to decide whether to accept that mail. Or do you think other people should be forced to accept any and every email you send?

      You've missed the point, at least in the business world. I've spent many hours explaining to end users at other companies that the decision that their IT dept or ISP made to use a blacklist is preventing some of their customers from contacting them. This conversation usually clear things up quickly with a several very polite emails or phone calls from their email admin to make sure it's working (at this point, he's probably hoping to save his job after making an ill-informed decision to use the list int the first place).

      The point is that in a business environment, wasted time is wasted money, and the block lists are dangerous for business use. Use them for your own personal use, but put your company on it at your own peril.

      Our ISP (a company who shall remain nameless, but the spell checker want to change it to "venison") is on several lists which have blocked their entire netblock as being dynamic. The creator of the blocklist is just an idiot who can't undertand whois records and so just blocks everything because it's the only way he can get his mind around tough concepts like subnets. We finally added another ISP and use them to send email. I don't care if anyone sets up a block list, I don't even care who uses them unless they want to do business with us, then they've wasted my time, and then I care.

    105. Re:Definitely a bad idea... by DavidTC · · Score: 1

      Um, duh. Why the fuck do you think I had the word 'knowingly' in there?

      --
      If corporations are people, aren't stockholders guilty of slavery?
    106. Re:Definitely a bad idea... by DavidTC · · Score: 1
      That's not 'implimenting a blacklist', that's using a damn blacklist, but that's already been addressed.

      I'm here to issue a challenge to you: Point to me one public spam filter that deletes mail based on a hit on a blacklist. Just one. Or one ISP or free mail service.

      Oh, that's right, there aren't any. Because all mail servers have such a check built in, and they reject it before delivery, and thus any tool to check mail against a single blacklist and delete it would be completely pointless.

      There are tools that check blacklists as part of scoring the message, and those tools may end up deleting the message, like spamassassin. As part of literally dozens of tests to figure out if something is spam, though.

      That's not to say someone couldn't code something that deletes against a blacklist and use it internally, but at that point you're arguing against hypotheticals. There's no reason to do that when you can just type the address of the blacklist into the mailserver.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    107. Re:Definitely a bad idea... by sjames · · Score: 1

      hat's because only spammers use the "report was in error", "complaintant requested this email", or "virus killed" excuses.

      Such as that notorious spam machine murphy.debian.org? It's been blacklisted before, probably because of AOLers finding it slightly easier to click the spam button than to follow the unsubscribe instructions (that would be "complaintant requested this email"). I have seen colo boxes get zombied, spam reports come in, and box gets re-installed (that is, "virus killed"). I have seen faked email headers meant to make the actual spam relay look like an innocent victim. (That would be "report was in error").

    108. Re:Definitely a bad idea... by DavidTC · · Score: 1
      And as for ' many draconian surveillance measures would you be willing to tolerate', the spam problem is a result of deliberate 'inattention' on the part of various ISPs.

      Everyone knows what IP the spammers are on, because, due, they got spam from there, and the ISP knows who had that IP at what time. It's not rocket science.

      So there's no 'surveillance' needed, although that might be a nice option for dynamic IP users instead of blocking port 25.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    109. Re:Definitely a bad idea... by squiggleslash · · Score: 1
      This nonsense has repeated so many times it's unbelievable those promoting the argument still have any karma left.

      It doesn't prevent a third party receiving an email. It prevents a sender from sending it. Just because the logic is implemented by the third party doesn't mean that the email can magically be sent. If an email cannot be received, it cannot be sent. It is not physically possible to send something for it not to be received.

      I used the term "third party" because while it's occasionally the receipient who would block the mail, 99% of the time it's their ISP or employer's system administrator, a third party in the transaction. Blacklists would be a lot less controvertial (and probably a lot less used by themselves with no systems to bypass for trusted senders given their implications!) if it were actual email receipients that choose whether to use them or not, on an individual basis.

      Speaking as someone who administers my own email, I might add that despite doing a lot of ecommerce (Amazon, eBay, banks, other online stores, etc), I rarely get spam. I've had two this year. All through the trivially simple process of assigning independent, turn-offable, incoming email addresses to each entity I do business with. No filters, blacklists, bayesian or Mail.app AI, or any other BS. Not a single false positive, and only two false negatives in a period of six months during which time I've received hundreds of email messages. There are systems that work, and there are systems that punish innocent third parties. Changing the definition of "not innocent" to include "someone who unknowingly signs up with an ISP that unknowingly also signed up another customer who turned out to be a spammer whose account was eventually terminated but not without tooing and froing from the various clueless PHBs who didn't understand the implications of that" doesn't help either, because even if you're so extreme as to accept that tortured logic, the customer of the ISP that blocks the email is as much a victim as the person trying to send it.

      Let's stop destroying email and let's tackle spam using appropriate, sensible, measures. If it generates false positives, preventing an email, send from one individual addressed to another, that the intended recipient wants to receive from being received, it shouldn't be under consideration.

      --
      You are not alone. This is not normal. None of this is normal.
    110. Re:Definitely a bad idea... by syukton · · Score: 1

      Earthlink.

      You need to select their "High" setting for spam control, but they have a blacklist and if you get mail from anything on the blacklist, it instantly goes away into the "known spam" folder and you're never told about it (ie, you only see the "known spam" folder via the webmail system, and mail sent to that folder is not delivered by pop3). I did in-home tech support for a while and I went to a guy's house who was having problems receiving email from a customer of his who had *just switched ISPs*. The man had set his spam control to high when originally setting up his e-mail the year prior, without realising the implications of doing so. See, there's also a "suspect email" folder where stuff that appears to be spam but isn't on the blacklist goes, and a weekly summary message is generated for these mails, which lists the address and subject and a timestamp for all "suspect" messages. The guy thought that this message was wholly representative of all the spam he was getting, and he never saw any valid messages coming in on it so he never fussed with it. But the "known spam" filter was eating (at least one of) his messages and not telling him...

      You only asked for one. There you go.

      (This was two years ago, but their support page still reads: "Known spam blocking detects messages from known spammers on EarthLink servers and intercepts them before they reach your inbox. These messages are automatically sent to your "Known spam" folder, where you can view the messages before deleting them. This level of protection works regardless of your email program.")

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    111. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      [...the old "it stops people sending" chestnut again...]

      So you believe the onus for ensuring delivery of any particular message lies with the intended recipient, not the sender? I refute that entirely. As long as I own my equipment, then I'll feel no obligation to accept any traffic that I don't want to. And your smokescreen about "third parties" is just that, FUD. By "receiver", I mean the system published as handling the mail for a particular domain, as specified in its MX record. The fact that other stuff may happen internally at the receiver after a message is accepted is irrelevent. Simply, the MX record says "mail for domain example.com is handled by mail.example.com". When a sender connects to that system, responsibilty for that particular message does not pass from sender to receiver until the receiver issues a 250 OK. You seem to want me to take responsibility for *all* messages, not just the ones I've 250'd. That makes no sense, sounds more like a charter for spammers, and it is also completely impractical to try to force that on me.

      Let's stop destroying email and let's tackle spam using appropriate, sensible, measures. If it generates false positives, preventing an email, send from one individual addressed to another, that the intended recipient wants to receive from being received, it shouldn't be under consideration.

      Firstly, let's not forget who are the real villains here : it is the *spammers* who are damaging the utility of email.

      So, you're in the camp who thinks false positives are not acceptable, ever. OK. Your system, your choice. But you have to recognise that this is not a cut & dried decision, and there will always be substantial numbers of others who are quite willing to suffer false positives, provided the rate is low. Hell, SMTP doesn't make any guarantees about delivery, and messages go missing or undelivered all the time, for reasons that have nothing to do with RBLs.

      Bottom line is, I'm not going to stop using RBLs until they stop being useful, and I'm far from alone in that. What are you going to do about it? Whine some more?

      --
      My next sig will be ready soon, but subscribers can beat the rush
    112. Re:Definitely a bad idea... by squiggleslash · · Score: 1
      So you believe the onus for ensuring delivery of any particular message lies with the intended recipient, not the sender?
      No, and you're making interpretations of what I said up that no rational person would read into it, which I assume means you have no argument. In any transaction, for an email to be sent, the sender has to try to send it and the receiver has to try to receive it, with those in the middle who have agreed with the receiver to perform the work of storing their email also agreeing to do their part. If one or other of the parties doesn't do this, then the email cannot be sent. Whichever party falls down on the job is entirely responsible for the email not being transfered.

      You can pretend it's the sender's fault as long as you like, but the sender is doing everything they're technically required to do. It is the third party that sits between the sender and receiver who's preventing the transaction from taking place. It is that third party that has consciously made the decisions that have prevented the email from being sent. They ARE to blame. Not the sender. The sender didn't do anything wrong. Not some spammer, the spammer's responsible for any problems he causes and no more. Not some ISP, the ISP is responsible for allowing a spammer to spam, and no more. The person who takes the technical measures he does to prevent an email from being sent out of ideology is directly to blame.

      Firstly, let's not forget who are the real villains here : it is the *spammers* who are damaging the utility of email.
      Oh bollocks. That was true ten years ago when spam started, when spammers tied up mail servers. It isn't true today. Spammers are not preventing emails from being delivered, and the obsessive, insane, methods adopted by a large minority of "anti-spammers" have only caused the problems they complain about to get worse, by encouraging spammers to increase their output more and more in the hope that, somehow, their messages will get through. And a quick look at, say, my Yahoo mailbox, shows that they're working. Because the measures the ideologues adopt are, 99% of the time, easily defeatable by simple changes to the methods used.

      The real villians are those who are intentionally disabling email in order to try to involve third parties who aren't spamming and have no connection with spam to get involved. They're deliberately, as a matter of policy, trying to cause damage to those collaterally effected in the hope that they'll put pressure on their ISPs to deal with a rather minor problem.

      These people are the villians. They are fucking it up for everyone. They eschew real anti-spam methods for computerized blackmail. I'm not about to support those who resort to extremist methods simply because I don't like one of the same groups of people they're fighting (one of, because they have three targets - spammers, ISPs that have had spammers as customers, and other, innocent, customers of ISPs that have had spammers as customers.)

      If my neighbour speeds in my development, he's an arsehole. If someone smashes the windows of his landlord, they're arseholes too. If that someone smashes the windows of my neighbour's landlord, and the windows of his landlord's other tenants, then the window-smashers are the villian.

      If you're part of this, you're the problem: if you are, stop looking at yourself as better than what you attack, because you're not. Spam is a resolvable issue. Anti-spammers don't promote systems that prevent spam, they merely promote systems that cause damage. They should be run off the Internet.

      --
      You are not alone. This is not normal. None of this is normal.
    113. Re:Definitely a bad idea... by squiggleslash · · Score: 1
      Anti-spammers don't promote systems that prevent spam,
      That, of course, is liable to be misinterpreted. In this case, I'm referring to the type of anti-spammer we've been talking about. As I've shown, I'm technically an "anti-spammer", I have systems on my own email to prevent spam from being sent. But I choose systems that do not result in false positives, that actually work and punish the spammers themselves.
      --
      You are not alone. This is not normal. None of this is normal.
    114. Re:Definitely a bad idea... by Vainglorious+Coward · · Score: 1

      You seem to be lumping me in with the extremists like the SPEWS people. I would have thought it was clear from my other postings that far from being dogmatic, I take a balanced approach to RBLs and other anti-spam measures. Nowhere have I said that RBLs are *the* tool for *everybody* in *all circumstances*.

      But you know, you can't have it both ways - you say this is destroying email, but then you also object to pressuring ISPs to deal with what you describe as a "minor problem". Well, which is it? Minor problem or the end of email as we know it? Nothing you've written has had the slightest effect on my view, because you're simply never going to convince me that I'm not permitted to choose what traffic I will accept on my own system.

      Spam is a resolvable issue.

      Go ahead Einstein, I'm all ears...?

      --
      My next sig will be ready soon, but subscribers can beat the rush
    115. Re:Definitely a bad idea... by Tripster · · Score: 1

      No contact was made directly from SPEWS to us, nadda, there was nothing to ignore because nothing arrived.

      And again, I had NO WAY of knowing this client was a spammer as he was NOT using my services to pursue that career goal he had and therefore he was also NOT in any shape or form breaking my terms of service.

      This brought up another problem with my NOC, how am I supposed to terminate a client when said client is NOT breaking my TOS?

      I am being asked to take SPEWS at their word that this person is a spammer, I was provided zero proof of such, said client was not using my services to spam nor were any of the domains he hosted with us tied to spam or any complaints of spamming, in fact he was a reseller and all the domains he had were in fact local clients in his home town.

      Of course I had no choice but to dump the client as my NOC forced the issue but we were not really obligated to do anything as this person had not broken any of our terms of service agreements as he was not using any of our resources for spam activities and this was meerly a side business he had.

      Basically SPEWS resorted to terrorism in this case becasuse while they claim spammers should get real jobs it apparently does not include them having legitimate hosting services on other networks.

    116. Re:Definitely a bad idea... by Tripster · · Score: 1

      And just to add to this .. our abuse@ address does work as we use a catchall for our main account.

      SPEWS went as far as blocking secondary DNS servers on a couple of different networks as well, for no reason other than an email address on our servers being used by this guy on one domain registration he did elsewhere, again, if he had used gmail.com, aol.com, hotmail.com or yahoo.com would SPEWS have listed their entire infrastructure to force their hand? Didn't think so, so why should we small hosts have to be treated like this when SPEWS don't have the balls to do the same to the large networks?

      I really can't believe that the guy would be breaking Gmail TOS by listing a Gmail.com email address in a whois record.

    117. Re:Definitely a bad idea... by Otto · · Score: 1

      And what good does that do, exactly? What do you do to correct it?

      You can get your ISP to stop letting spammers use their network, or you can switch ISPs and thus stop financially supporting spammers. That's the whole point.

      If you've ever actually been blocked by an RBL, you'd know this. It's very, very clear and simple to understand. "Message blocked because this IP is listed by RBL-name-here" or what have you. Go to any of their webpages and it's explained very clearly and simply.

      You can't talk about this in absolutes because you don't know how people use e-mail. E-mail is forwarded by third parties, still, to this day. There are instances in which mail does not go directly from point A to point B.

      No, there are not. Even if a mail relay is being used, it's being used inside a private network before making it out to the main systems. And RBL's would not impact these transactions because they would only be accepting mail from specific known systems in any case.

      But there is no case anywhere where you should be using the relay of some other unrelated party to send email. Period. Email should go from you to your ISP to the other guys ISP to the other guy. Why you'd stick a random relay in there I have no idea.

      And if you are thinking that setting up forwarding on your webmail account is "relaying", then you don't understand the discussion in the first place.

      Consider for example an autoforwarding filter

      Consider that this is irrelevant and NOT what an RBL does. If your home ISP is subscribing to a blacklist that blocks email from your work, as in your example, then WTF would you continue to use that ISP? You could complain to your ISP to fix the problem, or you could get the people at your work to switch to another ISP (the reason your work got blacklisted) or whatever.

      I mean, you're introducing so much bullshit into this that you're missing the whole point. RBL's don't block in that way, they block point to point transactions. An RBL won't block because of the email content, it blocks because of the IP of the sending machine. If an RBL is blocking work to home, it's going to block *everything* from your work to your home, not just stuff that you got forwarded through your frickin' email program.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    118. Re:Definitely a bad idea... by syukton · · Score: 1
      Consider that this is irrelevant and NOT what an RBL does. If your home ISP is subscribing to a blacklist that blocks email from your work, as in your example, then WTF would you continue to use that ISP? You could complain to your ISP to fix the problem, or you could get the people at your work to switch to another ISP (the reason your work got blacklisted) or whatever.


      You seem to lack understanding just as the others do. I'm not saying this would be a permanent occurence that has always been and would require switching ISPs, it is actually rather infrequent and somewhat "occasional" by nature. But just because it happens a little bit doesn't mean we should ignore the circumstance all together.

      It could be that autoforwards from work to home or home to mobile or work to mobile or etc, could have always worked. It could be that one day, they just... stopped, unexplained. Well, it would be explained if the end user knew that the IP had been blacklisted, but since they're away from work (in my example) they can't check their work email and read the rejection message.

      I'm supposing an infrequent and yet possible circumstance. Just because it's infrequent doesn't mean it's an unimportant side-effect; it's a FLAW with the use of blacklists and needs to be examined and corrected.

      I'm not introducing any bullshit and I'm not missing the point. Blacklists maintained by small groups can be arbitrarily edited and are prone to egotistical vigilanteism over time--that is the point. People who use email in a way that you don't (or don't understand) can be very detrimentally affected by such willy-nilly blacklist editing. What about somebody in communist China or North Korea trying to communicate with the outside world unhindered by using an anonymous open relay to send mail that the Chinese government consideres "sensitive." ? What happens when somebody else using that relay for spamming gets it added to a blacklist and "just switching ISPs" isn't as easy an option as you make it out to be, you ignoramus?

      The gravity of any given scenario is variable (hindering work, hindering freedom, etc), but the overall the ability to impact the end user as a result of this egotistical power-tripping vigilante approach to eliminating spam is significant, even if infrequent, amd must be treated seriously.
      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
    119. Re:Definitely a bad idea... by sjames · · Score: 1

      Usally, colo farm computers don't get zombied...

      Colo does get zombied. I'm talking about real colo where customer brings a box in and puts it intoi ISP's rack. Some have good admins, some not so good. Some run windows without updates.

    120. Re:Definitely a bad idea... by Anonymous Coward · · Score: 0

      Seems Graham was wrongly listed but the IP he hosts on was rightly listed... so, since the SBL lists IPs and not people, the listing was correct.

      And then you go on to use "EVER", "Everyone" "Whole", "not any", all absoulutes, a pretty sure way to tell when when someone is full of shit.

      Based on what I've seen and read, they are run in the most professional matter on any of these blacklists, past or present. The only people who rant about them seem to be the ones who've had email rejected due to being on a spammer hosting IP address - or, of course, the ones who are spammers.

    121. Re:Definitely a bad idea... by DavidTC · · Score: 1
      Earthlink are the idiots who implimented C/R. Earthlink's spam fighting is just braindead.

      However, I doubt that implimentation uses a third-party blacklist at all. They're just deleting mail from IPs they don't like.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    122. Re:Definitely a bad idea... by Pete · · Score: 1
      And what good does that do, exactly? What do you do to correct it? Mail the admin@whateverhost.com? How do we do that if our e-mail is being blocked? Hmm?

      You try sending from a mailserver that isn't blocked. At worst, use Hotmail. Or Yahoo Mail. Or Fastmail. Or GMail. Or any of the hundreds of other free webmail providers that make a conscientious effort to stay off blacklists.

    123. Re:Definitely a bad idea... by syukton · · Score: 1

      People who get burned by the bad use of blacklists are usually not the people that know how to fix the problem, and blacklist "message returned" emails are never very helpful with regard to fixing an erroneously blocked email address or IP. This boils down to shitty implementation of a list of blocked IPs created by a group that absolves itself of all responsibility for the validity of the reasoning for blocking those IPs.

      Consider for a moment Joe American, who doesn't know what a "mailserver" is and doesn't know that if he's having problems sending mail from one address, he may not have the problem from another address. If he hasn't been shown how to do it by his brother/cousin/friend/neighbor then he doesn't know how to do it, period. You could switch mail servers in an instance like this, certainly. So could I, for that matter. But Joe American is not going to know how to switch mail servers or even consider using hotmail unless he uses hotmail for his primary address.

      People keep throwing out these solutions like they're easy for everyone. Easy for US, the people who read slashdot, sure. But everyone else? They aren't so fortunate, and we need to have consideration for them, as they are the significant majority.

      --
      Reinvent the wheel only at either a lower cost, greater effectiveness, or your own personal enrichment and satisfaction.
  3. A few comments by alanw · · Score: 4, Informative
    From Paul Graham's original article http://paulgraham.com/spamhausblacklist.html
    any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam
    The primary use of the SBL is to allow sysadmins to refuse e-mail coming from listed IP addresses. The mail should be rejected during the SMTP header conversation, and the senders of genuine (non-spam and non-virus) e-mails will receive a non-delivery report from their outgoing MTA.

    I assume that what Paul Graham is complaining about must be SpamAssassin, or some other content filter, applying a score to articles containing URLs, which when looked up in DNS resolve to listed IP addresses. This is much less acceptable, since the sender has no way to know that their e-mail may have been classified as spam.

    The details of the listing can be found at http://www.spamhaus.org/sbl/sbl.lasso?query=SBL279 45. This is a /32 - i.e. a single IP address. I don't know why Paul Graham's web site (which has that IP address) has been associated with textileshop.com, which has a completely different IP address.

    The other Yahoo listing on the SBL is also a /32.

    I also note in another of Paul Graham's articles http://paulgraham.com/sblbad.html he claims

    The most notorious example is the MAPS RBL
    As any fule kno, the most notorious spam blacklist is SPEWS. ~
    1. Re:A few comments by slavemowgli · · Score: 1

      As any fule kno, the most notorious spam blacklist is SPEWS.

      ORBS, and its later reincarnation, ORBZ, also weren't exactly the nicest players on the field. I remember one incident where I couldn't send email to someone from a GMX account, because GMX - a webmail provider not unlike Hotmail etc., with several million users - had ended up on their blacklists (I'm not sure anymore whether it was ORBS or ORBZ at the point that happened, but it matters little, anyway).

      This articleon the death of ORBZ has some more interesting points regarding the controversy surrounding these lists.

      --
      quidquid latine dictum sit altum videtur.
    2. Re:A few comments by mercuryresearch · · Score: 3, Informative

      Seeing as how this exact situation happened to me this week, I can provide some light on the /32 IP address issue.

      In my case, I moved a server to a new colo facility. Most facilities have an IP block, and you get assigned an IP from it. Six months or a year ago that IP might have belonged to someone else. For me, it turned out in February a spammer installed a server at the colo, spammed from that server for a single day before the colo ISP turned them off. That IP got listed in Spamhaus; in the beginning of June I was assigned that IP.

      So, I ended up with a Spamhaus listing for my mail server's IP address -- and _I_ can't get it removed. Spamhaus expects the colo operator to contact them (which they did on my request) but even there, if the blacklist operator doesn't like the ISP/colo people, they can ignore the request.

      Fortunately Spamhaus listened and I got the record for my IP removed. But this showed me it was trivial for a non-spammer to inherit a blacklisted IP. I've added doing DNSBL checks on colo-assigned IP addresses for future moves to prevent any future issues.

    3. Re:A few comments by sloanster · · Score: 2, Informative

      I assume that what Paul Graham is complaining about must be SpamAssassin, or some other content filter, applying a score to articles containing URLs, which when looked up in DNS resolve to listed IP addresses. This is much less acceptable, since the sender has no way to know that their e-mail may have been classified as spam.

      Um, no. That's not how spamassassin works - spamassassin uses a wide spectrum approach - it can take into account whatever blacklists you want to consult, but an RBL hit in spamassassin does not automatically mark the message as spam. An RBL hit is just one of over a thousand factors taken into consideration when making the call as to whether a specific message is spam or not.

      Other methods used include central clearing houses of known spam messages (razor, DCC etc), time offsets, examination of header content, message content, weighted statistical analysis, presence of buzzwords, phrases, URL patterns and more.

      Using all of the methods available and making a decision based on the overall picture makes spam assassin a very effective tool, with far fewer false positives than a hard coded "RBL in the MTA" approach.

      On the other hand, SA does use more machine resources than does simply rejecting a message based on an RBL result, but that's the price of intelligent behaviour - it almost always requires more effort than a knee jerk reaction.

    4. Re:A few comments by Desert+Raven · · Score: 2, Insightful
      The most notorious example is the MAPS RBL
      As any fule kno, the most notorious spam blacklist is SPEWS. ~

      Actually, MAPS and ORBS are the most notorious in my book. Why? Because they got caught listing folks for reasons not specified in the listing criteria. (personal agendas) For that reason, they are the only two lists I know of to have lost legal challenges. MAPS cleaned up its act, and ORBS was shut down.

      As far as I'm concerned, listing all even-numbered IP addresses is valid, so long as it is clearly stated in the list criteria. That way, sysadmins can decide whether the list is practical for them or not.

      Love or hate SPEWS, they follow their own listing criteria to the letter. I have seen a few mistakes happen, but I've also seen them get cleared very quickly. Most of the folks claiming they are listed "by mistake", do fit the criteria for listing as stated in the SPEWS guidelines. Usually, because they are getting their service from an ISP that is knowingly harboring spammers. I have no sympathy for this, if you don't want to be lumped in with the spammers, don't support an ISP that allows spamming.

      And I'm here to say, it's NOT impossible to get off an RBL. I got caught in a SPEWS listing, because my ISP got lax and allowed a spammer to stay on their network. It took six months for that listing to expand wide enough to cover my addresses. When I found out, I raised royal heck with my ISP, and told them in no uncertain circumstances that I would pull my service if they didn't clean up. They kicked the spammer, the Spamhaus listings were gone the next day, and within a week, the SPEWS listing covering me had been reduced so that I was no longer affected.

      Having spammers on your ISP is like having a crack-house on your street. Can you blame folks for not wanting to come visit you?
    5. Re:A few comments by tempest69 · · Score: 1
      Actually I would suggest that you specify the blacklist issues with the colo in your contract. Go ahead and check it first by all means. But having a "will not be assigned a previously blacklisted IP address" clause in all of your contract from now on will save a whole lot of hassle.

      Heck I would have gone after my COLO instead of the blacklister, and explain that you were assigned "damaged" addresses, and to rectify the problem immediatly.. IE move you to a clean spot.

      Two things gained:

      1. The ISP knows that damaged addresses happen, and you wont take it.

      2. you have a clean IP address

      Storm

    6. Re:A few comments by Anonymous Coward · · Score: 0

      And yet it is still a burnt IP address. You don't know about all blacklists and you will never know when someone filters based on a blacklist or personal list without sending non-deliverable notices. For any serious stuff, don't accept an IP address which was blacklisted in the past few years (is there a service which checks this?) or is close to current blacklist entries, unless you're really really well known.

    7. Re:A few comments by derF024 · · Score: 1

      ORBS, and its later reincarnation, ORBZ, also weren't exactly the nicest players on the field.

      ORBZ.org and ORBS had nearly nothing to do with one another. When ORBS went away, an ISP Penguinhosting.net, which was completely unassociated with ORBS in every way, decided to sponsor a new RBL to protect its customers, ORBZ. The listing criteria was completely different; only functioning open relays and open proxies were listed, and it only ever listed individual IP addresses, never netblocks. ORBZ went away because people were upset by unprovoked system/network testing, not because it listed someone improperly.

      This articleon the death of ORBZ has some more interesting points regarding the controversy surrounding these lists.

      And it seems to have absolutely none of it's facts straight.

      "Cummins started to refer to the new site as ORBZ." Paul Cummins never had anything to do with ORBZ, nor did Alan Brown.

      " Laurie Akins, newly installed president of the non-profit anti-spam outfit SpamCon Foundation, said the code changes necessary to correct the bug was "trivial," but an error that Gulliver, for one reason or another, was unwilling to correct."

      The bug wasn't Ian Gulliver's to correct; It was Lotus's, and they corrected and released a patch for it nearly a year before the incident happened.

    8. Re:A few comments by Linux_ho · · Score: 1

      Mod parent up! RBL's are a critical component of any SpamAssassin configuration. No single RBL hit will trigger it to mark a message as spam, but RBLs are one of the most effective components of SA, along with the Bayes filter, the auto-whitelist, and the SURBLs. Yes, SA is relatively resource-hungry, but it's not THAT bad. I'm currently running it on a 1GHz Athlon with ~768MB RAM to process about 20,000 messages a day.

      RBLs are a tool, and a very valuable one. Like any tool, they can be used for both good and evil. Don't complain to the people running the RBL. Complain to the mail admins who set their servers up to blindly block messages based on one single known-to-be-unreliable factor.

      --
      include $sig;
      1;
    9. Re:A few comments by Zak3056 · · Score: 2, Insightful

      When I found out, I raised royal heck with my ISP, and told them in no uncertain circumstances that I would pull my service if they didn't clean up. They kicked the spammer, the Spamhaus listings were gone the next day, and within a week, the SPEWS listing covering me had been reduced so that I was no longer affected.

      This is great--IF you have the leverage to do it. If you're a large (six figures a year in spending and up) customer, you can get the ISP to jump at your command. Likewise, if you're dealing with a small local ISP, you have a significant amount of leverage even if your spending is low.

      On the other hand, if you're someone with a single DS1 being provided by someone like Verio, you have NO power to negotiate or threaten. Sure, you CAN leave, but for a small organization (perhaps one with minimal or even no IT support) this kind of move is difficult, if not impossible--and in any case, is going to be really expensive. And what happens when the next time (and there will be a next time) comes around? You get to go through it all again.

      RBLs (when used exclusively, instead of in some kind of weighted average ala spamassassin) are like a bad action movie--you know the ones, where the cops walk into a crowded theater and open up on the bad guys, while ignoring anyone else in the line of fire. It doesn't matter who gets taken out as long as we get our man--right?

      --
      What part of "shall not be infringed" is so hard to understand?
    10. Re:A few comments by sjames · · Score: 2, Funny

      For any serious stuff, don't accept an IP address which was blacklisted in the past few years (is there a service which checks this?) or is close to current blacklist entries, unless you're really really well known.

      That would be hard to check (by the ISP as well), and is increasingly rare. It'll have to be outside of 0.0.0.0/0

    11. Re:A few comments by Desert+Raven · · Score: 1

      This is great--IF you have the leverage to do it. If you're a large (six figures a year in spending and up) customer, you can get the ISP to jump at your command. Likewise, if you're dealing with a small local ISP, you have a significant amount of leverage even if your spending is low.

      I'm here to tell you, you don't have to be huge, and you don't have to be dealing with a mom-n-pop either. I lease a half-rack in a colocation facility, grand total of about $450/month. This same colo facility is a major peering point, with plenty of customers spending 5-6 figures/month.

      What it took was being loud, persistent, and absolutely willing to pull my equipment if they didn't clean up their act.

      As for being "difficult, if not impossible" to move? No, it's not. I've had to do it several times over the years for various reasons. It's a pain in the butt sometimes, but it's not a good reason for continuing to pay money to a spammer-supporting operation.

    12. Re:A few comments by Anonymous Coward · · Score: 0

      >"I don't know why Paul Graham's web site (which has that IP address) has been associated with textileshop.com, which has a completely different IP address."

      I will tell you: because Paul is a known spam-fighter. The real problem with spam is that spammers can (and are willing to) use all the dirty tricks, because there's money to make.

      If you think about it, you will realize that only whitelist can work (maybe, most of the time).

      But in any case, you'd better rely on something under your own control.

    13. Re:A few comments by Zak3056 · · Score: 1

      As for being "difficult, if not impossible" to move? No, it's not. I've had to do it several times over the years for various reasons. It's a pain in the butt sometimes, but it's not a good reason for continuing to pay money to a spammer-supporting operation.

      Since you're contributing to this discussion in a meaningful way (and you mention leasing half a rack at a colo) I'm going to take it for granted that you have at least a moderate amount of IT experience. Moving, for you, would be a pain in the ass but not something particularly strenuous and would probably take you little more time or cost much more than is involved with moving the equipment from one colo to another.

      However: say you're in a position where you lease your CPE from the provider. Say you're locked into a multi-year agreement with the ISP. Imagine going through such a move when you have no in-house IT support (say you're a four or five person garage operation?) Now moving is not so easy, nor is it inexpensive. Your business is esentially being held hostage by the RBL with the intent of forcing a third party whom you do business with to change its policies.

      I'm as anti-spam as the next guy who has to admin mail servers (not to mention getting massive amounts of spam in my personal mailboxes) but somewhere along the line we've forgotten that the purpose of an email server is to deliver mail to users. Anti-spam is a tool that is supposed to make delivering mail easier (by reducing cost and overhead caused by spam) but turning it into a political statement by which we refuse to deliver legitimate mail misses the point entirely.

      Imagine if you will if the US Post Office decided it was no longer going to accept mail from entire zip codes, because bulk mailers lived there. The idea is absurd!

      --
      What part of "shall not be infringed" is so hard to understand?
  4. Re:In soviet russia by TeacherOfHeroes · · Score: 2, Funny

    In Soviet Russia; old, tired, worn-out joke tells you

  5. Paul is just pissed because... by SSpade · · Score: 3, Informative

    ...his website is hosted on the same IP address as a spammer (textileshop.com) was on yesterday, and because of that he's seeing some of his mail blocked.

    There's certainly a need for thoughtful and hopefully positive criticism of blacklist behaviour. This article is not it.

    1. Re:Paul is just pissed because... by DikSeaCup · · Score: 2, Insightful
      Is he making an accusation that Spamhaus isn't taking the IP off of the SBL? If so, maybe it's because they won't accept his word in the matter, only the word of the people who actually admin the box. Too bad - *I* wouldn't accept the word of a hosted person that the spammer is gone, only the word of the *hoster*, who, if he ends up lying, should rightfully end up with a more permanent ban. Yeah, this sucks for the hosted people, but hey - move your site. Your hoster sucks and doesn't deserve your business.


      Or maybe he needs to realize that it can take some time for stuff to happen. I know so many folks who have become accustomed to immediate feedback.


      Anyone know anybody who has something to do with Spamhaus? From what I understood, they were anti-spam pitbulls (this is not always a bad thing) but were also rather good at avoiding false blocks ...

    2. Re:Paul is just pissed because... by SpeedyG5 · · Score: 1

      what paul seems to be oblivious to, is "spam friendly" ISP's. There are a ton of them out there. They do nothing to stop these folks and in fact work to help them, additionally some businesses become ISP's so they can facilitate there Spam Activities. These folks offer cheap hosting to people like Paul who don't really care who they do business with as long as its cheap. Then they wanna whine about it when they are shown to have made a bad choice. Blacklists can be effective, peronally I would like to see a system based on a trusted whilelist, but you'll only get a bunch of whining spammers complaining about that!

    3. Re:Paul is just pissed because... by SSpade · · Score: 3, Informative

      Actually the IP address that's listed is store.yahoo.com.

      Yahoo hosting is riddled with spammers, and store.yahoo.com is where most of them live, and where they accept credit cards for their purchases.

      The SBL lists IP addresses that are involved in spam. 66.163.161.45 is involved in a lot of spam. It's not been removed from the SBL because, well, it's still actively being used by spammers.

      Because countless spammers register domains on a daily basis, yet point them at the same IP addresses some people choose to resolve the URLs in incoming email and bounce the mail if any of them resolve to particularly filthy IP addresses.

      66.163.161.45 is filthy. Blocking mail that has URLs pointing there will stop a fair amount of spam. Not an approach I'd use myself, but certainly a lot more effective (in terms of spam caugh and false positives) than many, many other approaches in widespread use.

      Paul chose to host his website there, despite supposedly knowing a lot about the spam issue. That was probably not a good call.

    4. Re:Paul is just pissed because... by l2718 · · Score: 1
      ...his website is hosted on the same IP address as a spammer (textileshop.com) was on yesterday

      I'd say this neatly demonstrates the problem with blacklists. I agree that the style is marred by the emotional state of the author, but then it's an essay on the guy's personal page.

      If you want some analysis, start with a personal exmample of mine: an ISP in Israel my parents used to use would occasionally get blacklisted. Since I'm behind company-level spam filtering there was nothing I could do about it (no personal white lists).

      What went wrong? The problem is exactly that not all mail from a domain/ip address is spam, and yet MAPS/SBL only give you 1 bit of information: in the list or not in the list. This bit can be very useful as an ingredit of a Bayesian filter (certainly mail coming from that ISP is more likely to be spam than mail coming from whitehouse.gov). However, letting that bit dictate the classification of messages by itself is probably not a good approximation to the true correlation between the two events "mail was sent from domain in the SBL list" and "mail is spam".

    5. Re:Paul is just pissed because... by Joe+U · · Score: 1

      So, the best way to ruin the SBL is to get some $10 domains from every hosting service you can and spam from them, then repeat in 2 weeks.

      Everyone gets a "more permanent ban" and the SBL is now worthless.

    6. Re:Paul is just pissed because... by deacon · · Score: 4, Insightful
      66.163.161.45 is filthy. Blocking mail that has URLs pointing there will stop a fair amount of spam. Not an approach I'd use myself, but certainly a lot more effective (in terms of spam caugh and false positives) than many, many other approaches in widespread use. Paul chose to host his website there, despite supposedly knowing a lot about the spam issue. That was probably not a good call.

      Let me reword your justification of of this behaviour so others can see the flaw in it more clearly:

      [66.163.161.45 is a filthy neighborhood. Lots of criminals live there. So, a group of vigilantes randomly started machine gunning people walking the street. Not something I'd do myself, I prefer to use a shotgun, but certainly more effective then using the court system. Paul chose to live there, and he should have known it's a bad area. If he gets shot at random, well, too fucking bad, he should have known better. Living there was probably not a good call.]

      Some days it's hard choosing between deleting 400 spams a day and dealing with the exsistance of "spam blocking" groups. Then I read a comment from an "anti-spam" person and I think I'll be safer choosing to work that delete key.

    7. Re:Paul is just pissed because... by Anonymous+Brave+Guy · · Score: 1
      Yeah, this sucks for the hosted people, but hey - move your site. Your hoster sucks and doesn't deserve your business.

      Spoken like someone who never administered more than his family home page.

      Businesses usually can't just up and move to a different ISP. It requires a lot of time and money to do that, and they could just get the same bad luck at the next one anyway.

      Your solution isn't.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    8. Re:Paul is just pissed because... by Anonymous Coward · · Score: 0
      the IP address that's listed is store.yahoo.com...Paul chose to host his website there, despite supposedly knowing a lot about the spam issue. That was probably not a good call.

      Perhaps he made that decision because he wrote the Yahoo Store.

    9. Re:Paul is just pissed because... by Anonymous Coward · · Score: 0

      Wrong - this is more like choice - free market choice.

      Although some of the contracts you are meant to sign may leave you having to pay to move, if joining a spamming host who gets blocked turns out to be a bad business move, you take your business elsewhere.

      Just like if you set up a shop in a bad high street - which got regularly robbed and took flak during cop/crim shoot outs - it is probably better you take you rent elsewhere and pay some other better located shop.

      Costs of letting the spam through my network are high - so I will block their network - if that costs them too much in lost customers moving to other hosts because they cannot do business or email people in my domain - tough. Free market economy - governments arent going to do anything - fine - my company choose to opt into a list.

      There are no high street banks in Leyton - because they kept getting robbed. People living in that area now have to travel to get cash or do branch based banking. I see this as no different.

    10. Re:Paul is just pissed because... by Anonymous Coward · · Score: 0

      Or you actually serve to effectively proove exactly how many domains have absolutely no spam controls.
      If a single mailer is sending more than about 100 emails with the same content, or are faking/forging mail headers, or generate an unusally high number of bounces, or simply receive more than a few spam complaints - then kick then ASAP - and make sure the SBL is aware of that fact.

      Reaction is the key - a few of the conditions above could be checked before the mail is even transfered by the MTA - and the user then blocked until they confirm in some way the legitamacy of their mails.

      Your strategy may actually result in a number of hosters tightening things up - a very good thing. This might result in an arms race, but it will certainly make spamming a lot less economical than it is now.

      Spammers are leaches!

    11. Re:Paul is just pissed because... by Vainglorious+Coward · · Score: 1

      [...hopelessly flawed analogy elided...] I read a comment from an "anti-spam" person and I think I'll be safer choosing to work that delete key.

      Fine, that's your decision. But don't try and force me into that same decision. Or, more accurately, you can't stop me making my own decisions on this. All the whining in the world won't change that.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    12. Re:Paul is just pissed because... by bluGill · · Score: 1

      Bahh. Hire a new ISP, setup servers and mirror your website. Then point your DNS servers to the new ISP. One week latter (or however long it takes for DNS to update) notify the old ISP that you are gone.

      I wouldn't call it trivial, but it is easy. Yes it costs money. The point it to make it cost them money to use the old ISP, ideally more money. There will be no bad luck if they write their contract with the new ISP correctly. Maybe the cost of switching to a different ISP will actually teach them to write the "you won't host spammers" into the contract with the new ISP, which prevents this problem. (Or at least gives them their costs to move to the next ISP back)

    13. Re:Paul is just pissed because... by Anonymous Coward · · Score: 0

      So, you'll buy a second rack of servers, find a way to keep the two copies of your database driven site in sync and eat the loss of users who happen to be using broken DNS servers with excessive cache times -- every time a spammer gets an account in your vicinity for half a day? ARE YOU NUTS?

    14. Re:Paul is just pissed because... by dr.badass · · Score: 1

      Paul is just pissed because......his website is hosted on the same IP address as a spammer (textileshop.com) was on yesterday, and because of that he's seeing some of his mail blocked.

      Is there some reason someone shouldn't be pissed about having his legit mail blocked? Does it make his criticism less valid?

      There's certainly a need for thoughtful and hopefully positive criticism of blacklist behaviour. This article is not it.

      Sorry, but there's just no way to say "blacklists are broken, please stop using them, you're destroying email" in a positive way.

      --
      Don't become a regular here -- you will become retarded.
    15. Re:Paul is just pissed because... by Dasein · · Score: 1

      Let's reword it this way. Paul send all his correspondance through a courier service. The courier service charges the recipient of any message 5 cents. I notice that 9 out a 10 times I accept a message from the courier, it's of no value to me. 1 out of 200 times, it's a mailbomb. So, I decide that I'm not going to accept messages from Paul's courier service anymore. Seems okay to me.

      Now, let's assume that I'm a Mailboxes, Etc. Is it okay for me to refuse delivery from Paul's courier service for my clients? Well, I happen to think so, after all there's a chance there's a mailbomb in there. Also, the 5 cent charge is a problem because Paul's courier service wants to deliver 300,000 messages to my clients a day.

      --
      You are not a beautiful or unique snowflake -- but you could be if you got off your ass.
    16. Re:Paul is just pissed because... by jgoemat · · Score: 1
      Let me reword your justification of of this behaviour so others can see the flaw in it more clearly:

      [66.163.161.45 is a filthy neighborhood. Lots of criminals live there. So, a group of vigilantes randomly started machine gunning people walking the street. Not something I'd do myself, I prefer to use a shotgun, but certainly more effective then using the court system. Paul chose to live there, and he should have known it's a bad area. If he gets shot at random, well, too fucking bad, he should have known better. Living there was probably not a good call.]

      Now let me reword your anti-justification so people can see it even more clearly:

      [66.163.161.45 is a filthy neighborhood. Lots of criminals live there. Therefore I CHOOSE not to go into that neighborhood. My friend that lives there will never have a visit from me because I don't want to get gunned down on the street outside his house, like three people were in the last week.]

      How the hell did blocking someone's email ever get associated WITH MACHINEGUNNING PEOPLE TO DEATH?!?!? Jesus Christ.

    17. Re:Paul is just pissed because... by jbolden · · Score: 1

      Your analogy is wrong because you are assuming a neighborhood that is two places with the same central governing authority. If the government were actually doing anything about spam we wouldn't have these problems. A fair analogy is closer to war.

      66.163.161.45 allowed armed groups inside their country to maurade in our country. Not all the people were involved but important subgroups and their government doesn't care. So our army has closed the borders to everyone and there isn't going to be anymore trade or travel between our two countries.

    18. Re:Paul is just pissed because... by nytmare · · Score: 1

      Machine gunning? You're wrong. The machine gunning is coming OUT of the filthy neighborhood, not going in. The blocklist is a WALL that goes up to stop the bullets. Innocent parties within the filthy neighborhood suddenly can't drive the shortest route to their friend's house on the other side of town. In your warped world you'd rather someone only erect walls that match the exact paths of each specific bullet trail. Or no walls at all.

  6. Vigilante it ain't by Rosco+P.+Coltrane · · Score: 4, Insightful

    The problem was, as vigilantes so often do, the guys at MAPS got carried away

    For some reason, journalists keep calling blackmail lists "vigilantes". But there's something they don't understand: nobody forces email system administrators to use those lists.

    These lists are provided by people for free. They decide to list bad email servers, but they may as well include any server they want. After all, who's to force them to provide quality of service?

    The real problem, of course, is that blacklists are needed in the first place. If ISPs did their jobs a little better (aol, hotmail and the likes), the amount of spam would already decrease significantly. And don't speak to me about chinese ISPs, since most spam comes from the US.

    --
    "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    1. Re:Vigilante it ain't by danheskett · · Score: 1

      AOL actually does a good job filtering SPAM. I can't imagine AOL being used to send any significant amount of SPAM at this point, and it does a fine job of filtering incoming SPAM.

    2. Re:Vigilante it ain't by Rosco+P.+Coltrane · · Score: 1

      blackmail lists

      I meant blacklists of course...

      --
      "A door is what a dog is perpetually on the wrong side of" - Ogden Nash
    3. Re:Vigilante it ain't by Maestro4k · · Score: 4, Insightful
      For some reason, journalists keep calling blackmail lists "vigilantes". But there's something they don't understand: nobody forces email system administrators to use those lists. No, but the non-spamming sites that end up on it would certainly disagree with you, they didn't do anything to merit the block.

      You seem to be confused about what a vigilante is, dictionary.com gives me this: "One who takes or advocates the taking of law enforcement into one's own hands." Note it doesn't say anything about them forcing others to agree with their views or take part in them. If you decide to take legal actions in your own hands, then you are, by definition, a vigilante. So it does apply here, just because they don't force anyone to use their lists doesn't change that.

      These lists are provided by people for free. They decide to list bad email servers, but they may as well include any server they want. After all, who's to force them to provide quality of service? TFA's point was that these lists start out listing just IPs/hosts/sites they know are sending spam, then later the power corrupts ("power corrupts, absolute power corrupts absolutely") them and they start using the power they've gained by their blacklist being used by many people to start trying to force ISPs to comply with them by blocking bunches of innocents at the same ISP. That indeed has happened, although I'm really not sure if it's happened here or not. The risk of it occuring is pretty high, humans are, after all, only human and it's hard to resist that temptation, especially when you're a strong enough anti-spam advocate to run a blacklist. The real problem, of course, is that blacklists are needed in the first place. If ISPs did their jobs a little better (aol, hotmail and the likes), the amount of spam would already decrease significantly. And don't speak to me about chinese ISPs, since most spam comes from the US. The real problem is human nature in all of this. In spam existing in the first place (greed), in ISPs not blocking things they should (laziness, lack of knowledge or time), in people actually buying from spam (greed (getting something cheaper than legal means would allow), sexual desire (gotta have a longer penis!) or just simply a criminal desire to purchase illegal goods (prescription drugs for example)) as well as humans becoming corrupted by power when their blacklists get to be popular.

      So basically if we can solve how to get people to stop being, well, people and giving in to baser instincts we can stop spam. Of course we'd also stop crimes of all sorts as well and we've not managed that in hundreds of years so I'm not holding my breath for it to happen.

    4. Re:Vigilante it ain't by Mike+Markley · · Score: 2, Insightful

      This argument is horseshit. It's been horseshit for years and it will always be horseshit. The blacklists exist for the sole purpose of allowing other people to block mail based on the data contained therein. The blacklist operators don't get off the hook for having some frickin' responsibility just because they're not holding a gun to anyone's head. They publish this information with precise knowledge of what it will be used for, so this argument is basically just the administrators trying to weasel out of personal responsibility for what they list.

      In case you're wondering, I do use a couple of blacklists. I use them to reject mail, as intended. I like to think that the ones I use are operated by folks who take seriously the fact that people like me are using it for that purpose.

    5. Re:Vigilante it ain't by hesiod · · Score: 3, Insightful

      > If you decide to take legal actions in your own hands, then you are, by definition, a vigilante

      What law enforcement activities do the blacklists take into their own hands?

    6. Re:Vigilante it ain't by hesiod · · Score: 1

      And I'll point this out before you tell me that spam is illegal...

      So is theft. Is it vigilante if a company sells a mail sorter that automatically removes junk mail from your mailbox? Only if it depends on the physical address it came from? Another businesss could move into that address... Or is it only vigilante if it makes a mistake once in a while?

    7. Re:Vigilante it ain't by Anonymous+Brave+Guy · · Score: 1
      What law enforcement activities do the blacklists take into their own hands?

      Gee, I dunno... Preventing spamming, maybe?

      Seriously, it is actually illegal to send UCE in many jurisdictions, and has been for some time.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    8. Re:Vigilante it ain't by Anonymous Coward · · Score: 0

      Unfortunately, most of us aren't email administrators. So we get stuck using whatever blacklists that our ISP decides they should use. And the average user has no idea they're even being used, so when their mail gets blocked they assume it is the sender's fault.

    9. Re:Vigilante it ain't by hesiod · · Score: 1

      You didn't read my followup post, which is understandable, because I just posted it, so you probably loaded the page between posts...

      Here

      > it is actually illegal to send UCE in many jurisdictions

      But not all. If (as has been claimed and disclaimed time & again) most spam comes from other countries without those laws, what then? You can't prosecute a Thai citizen (random example) from inside the U.S. because he sent you spam.

    10. Re:Vigilante it ain't by Andronoid · · Score: 1

      The real problem, of course, is that blacklists are needed in the first place. If ISPs did their jobs a little better (aol, hotmail and the likes), the amount of spam would already decrease significantly. And don't speak to me about chinese ISPs, since most spam comes from the US.

      I think that the most effective way to filter spam (in terms of maximum hits and least false postives) would be to have individual messages marked as spam. For example when a message is received a user can mark it as spam. The message would then be sent to some central server that would find statistical regularities (so that slight variations of the same message are also marked as spam) in the messages and block the message from being received by other users. (Doesn't Gmail already do this?) Heck individuals you could could SET the hit/false alarm ratio (based on how the algorithm has worked in the past) to whatever they think is optimal. Of course this means that some people will have to receive the message first but after spammers see a dastric decrease in the amount of return they may stop spamming as much. Of course the spammers might try to counter the filter by having clever algorithms that generate unique messages or by hiring super poor people to compose a variety of different spams but I seriously doubt they'll be able to keep up with the awesome power of Google!!!

    11. Re:Vigilante it ain't by Buran · · Score: 1

      You can't prosecute a Thai citizen (random example) from inside the U.S. because he sent you spam.

      If you do business in a country or state, you have to abide by its laws. That's part of the basis of do-not-call lists.

    12. Re:Vigilante it ain't by sethb.nyc · · Score: 1

      Are restaurant and movie reviewers also vigilantes in your eyes? How is a review saying "That movie sucks; don't waste your time" different from a blocklist saying "Too much spam comes from that part of the Internet; don't waste your attention"? Either way, I can choose whether or not to pay any attention to someone else's opinion.

    13. Re:Vigilante it ain't by Anonymous Coward · · Score: 0

      If it's preventing spamming, then it's working. Surely.

      No, there is no law enforcement acivity going on because saying to someone "that area is dangerous. stay away at night" is not enforcing law.

    14. Re:Vigilante it ain't by Experiment+626 · · Score: 1

      You seem to be confused about what a vigilante is, dictionary.com gives me this: "One who takes or advocates the taking of law enforcement into one's own hands." Note it doesn't say anything about them forcing others to agree with their views or take part in them. If you decide to take legal actions in your own hands, then you are, by definition, a vigilante. So it does apply here, just because they don't force anyone to use their lists doesn't change that.

      Law is force. This is why you hear phrases like a measure "having the force of law" or police "enforcing the law". The actions of vigilantes also involve force, such as some type of violent retribution against a criminal. If someone was compelling others to use their lists, that would also be a form of force. You concede that they are not doing that, but miss the importance of the distinction.

      If I went around seizing other people's money by force, that be unlawful. If I put up a Web page asking for people to donate money of their own volition, it wouldn't. Likewise there is a big difference between just disseminating information to those who willingly choose to make use of it ("207.46.199.30 are a bunch of spammers, you might want to dump emails you get from them"), and kidnapping / executing / whatever anyone who dares have contact with that IP. Spam lists are suggestions, whereas laws have consequences for not following them, like fines or incarceration. If the spam list providers aren't punishing those who decline to adopt their lists, the label of vigilante would appear to be going too far.

    15. Re:Vigilante it ain't by flonker · · Score: 1

      If preventing spamming is a vigilante activity, then are you suggesting nothing be done about spam, except by law enforcement?

  7. A Paradox? by LegendOfLink · · Score: 3, Insightful

    A blacklist for a blacklist for a blacklist...

    Personally, I find the need to disable more and more RBL's, because today a user might come thru OK, tomorrow, they're stuck in SORBS and considered a HIGH risk.

    1. Re:A Paradox? by smittyoneeach · · Score: 1

      Yep. Turtles all the way down.
      I forsee a split between the www 'wild, wild, west' and private networks that you pay real cash money and have a smart card with certificates on it to play (or some variation on the military theme you see here), just so the wheat is available, and you can surf the chaff if you want to.
      One wonders if some marketing twit won't tie these ideas to IPv6, as a forcing function to sell that technology to an otherwise indifferent market.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    2. Re:A Paradox? by legirons · · Score: 1

      "Personally, I find the need to disable more and more RBL's"

      Perhaps you could compile a list of the RBLs which are known to list non-spammers. After all, you're only writing a list, so there are no possible consequences of that.

      Make it automatic somehow, so that email systems can easily parse your list, dropping support for any RBL listed on your list.

      Some RBLs might complain about this, but then (a) you've only got a list, nobody's forcing anyone to use your list, and (b) if they stopped listing non-spammers, then you would remove their list from your list. Possibly. After a few months.

      If you wanted, you could block whole groups of RBLs just because one of them put non-spammers on their list. For example, if SPEWS listed non-spammers, you could blacklist all the RBLs operated by people in the same city as SPEWS. Again, there's nothing wrong with that because people are choosing to use your list of lists.

  8. Not like people get all radical about it... by dmorin · · Score: 4, Interesting
    Actual quote I have heard on the subject of spam blacklists: "I don't care that you're not a spammer. Your ISP allows spammers in their midst and therefore you all go on the list. Get a new ISP."

    Oh, ok. Nothing like over reacting a bit.

    1. Re:Not like people get all radical about it... by Uruk · · Score: 4, Interesting

      No, the principle is that if ISPs know that this kind of overreaction will occur, they will make quite sure that they don't have spammers in their midst. In essence, it's an attempt to incentivize ISPs to police themselves.

      What's the alternative? Having some centralized, international spam cop whose job it is to clean up every ISP on the planet? If ISPs get a completely free pass on spam and don't have to care whether their subscribers are abusing other people or not, where is their incentive to prevent the abuse? The way you avoid the tragedy of the commons is by getting people to see their individual stake in the issue.

      Certainly the quote that you're pointing out isn't the most diplomatic or effective way of putting it, and I doubt this kind of thinking is behind that quote - it probably is the knee-jerk reaction that you're identifying it for. Still, the idea might have some merit.

      --
      -- Truth goes out the door when rumor comes innuendo. -- Groucho Marx
    2. Re:Not like people get all radical about it... by Kynde · · Score: 1

      Actual quote I have heard on the subject of spam blacklists: "I don't care that you're not a spammer. Your ISP allows spammers in their midst and therefore you all go on the list. Get a new ISP."

      Oh, ok. Nothing like over reacting a bit.


      Harsh as it may seem, it also seems to be just about the only affective way to pressure ISP to cut the spam from where it originates. It's a hell of a lot easier to block it there than in the receiving end and the paying customers are just about to only ones that can demand policy changes from their ISPs.

      Will it cause some inconveniences? Yes.
      But will it lead to less spam driven net? It just might in the long run.

      That's a hell of a lot more than any of the other approaches I've heard so far.

      --
      1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
    3. Re:Not like people get all radical about it... by Just+Some+Guy · · Score: 1
      Harsh as it may seem, it also seems to be just about the only affective way to pressure ISP to cut the spam from where it originates.

      Harsh, stupid, and ineffective. My IP is in a couple of blacklists because my ISP's ISP's ISP has a customer who has a customer that used to send spam, so some ridiculously huge netblock (/16?) is listed because of them.

      I cannot switch ISPs. They're the only one in my small city that provides the hosting-friendly services I need. My ISP probably can't switch to a wholly different upstream, either, since connectivity to my city is somewhat limited.

      SPEWS and their ilk taught me a lesson, alright: they're a bunch of power freaks who truly don't care about any of the damage they do.

      --
      Dewey, what part of this looks like authorities should be involved?
    4. Re:Not like people get all radical about it... by RovingSlug · · Score: 1
      ... the principle is that if ISPs know that this kind of overreaction will occur ... What's the alternative?

      When innocent mail is blocked by a blacklist, the innocents have two options:

      • Apply pressure to remove the spammers (by analogy "regime change")
      • Apply pressure to remove the blacklists (by analogy "kill the terrorists")
      By intentionally blocking more than spam, they are just as likely diminishing their overall influence, which helps nobody while inflicting suffering the innocents.
    5. Re:Not like people get all radical about it... by PGillingwater · · Score: 1

      It's not over-reacting. Whilst I have been inconvenienced by this myself, it's clear that the *only* way to put pressure on ISPs who host (or tolerate) known spammers is to attack them indirectly, which is through their other (legitimate) customers. Once a significant fraction of customers complain, the ISP will take the correct action -- otherwise, they will continue to contribute to the SPAM problem.

      Disclaimer: it's been more than 12 years since I ran an ISP, but my attitude to SPAM has certainly hardened over the years. MAPS was right.

      --
      Paul Gillingwater
      MBA, CISSP, CISM
    6. Re:Not like people get all radical about it... by Anonymous Coward · · Score: 0

      Oh, ok. Nothing like over reacting a bit.

      Well, you're paying an ISP who is allowing spammers to pollute the net. Does that mean you're part of the problem or part of the solution? Guess.

      Hanno

    7. Re:Not like people get all radical about it... by Hurga · · Score: 1

      "I don't care that you're not a spammer. Your ISP allows spammers in their midst and therefore you all go on the list. Get a new ISP."

      Oh, ok. Nothing like over reacting a bit.


      Well, you're paying an ISP who is allowing spammers to pollute the net. Does that mean you're part of the problem or part of the solution? Guess.

      Hanno

    8. Re:Not like people get all radical about it... by Pig+Hogger · · Score: 1
      Harsh, stupid, and ineffective. My IP is in a couple of blacklists because my ISP's ISP's ISP has a customer who has a customer that used to send spam, so some ridiculously huge netblock (/16?) is listed because of them.

      I cannot switch ISPs. They're the only one in my small city that provides the hosting-friendly services I need. My ISP probably can't switch to a wholly different upstream, either, since connectivity to my city is somewhat limited.

      Your ISP would not have been listed if he had read his ABUSE mailbox, and ditched the spammer as soon as complaints started to flow-in. Eventually, when clients like you will get tired of being blacklisted, they will move to a spam-unfriendly ISP, leaving the spamhaust to wither and die.

      What? He's the only ISP in town? You poor sucker. That's the price to pay to live in hicksville... No wonder they were spam-friendly...

      Well, though noogies then. Either endure your blocking, or smarthost your mail.

    9. Re:Not like people get all radical about it... by Just+Some+Guy · · Score: 1
      Your ISP would not have been listed if he had read his ABUSE mailbox

      You wouldn't have bothered to answer if you'd read my message. My ISP has never hosted a spammer, as far as I know (and I did my homework). Their upstream provider isn't directly blacklisted, either. However, their upstream ISP did provide service to another ISP that hosted a spammer.

      I'm at least 4 degrees removed from the spammer, but I'm still on the stupid blacklist. Care to explain how that makes sense, or what possible influence I could exert on my ISP?

      --
      Dewey, what part of this looks like authorities should be involved?
    10. Re:Not like people get all radical about it... by Pig+Hogger · · Score: 1
      I'm at least 4 degrees removed from the spammer, but I'm still on the stupid blacklist. Care to explain how that makes sense, or what possible influence I could exert on my ISP?
      By moving out and stopping giving him your money, maybe???
    11. Re:Not like people get all radical about it... by Kynde · · Score: 1

      Harsh, stupid, and ineffective. My IP is in a couple of blacklists because my ISP's ISP's ISP has a customer who has a customer that used to send spam, so some ridiculously huge netblock (/16?) is listed because of them.

      Abusing the idea of pressuring ISPs with blaclists in shitty manner proves squat. Ofcourse bad blacklisting is bad, but that's totally different from wether the idea works or not. DNS is not blamed for bad dns administration.

      Blacklists should really be well administered and equal amount of effors should be put into removing ip blocks from the lists.

      But the bottom line for me is that I cannot see any other, even remotly possibly, effective approach against spam. Blacklisting attacks the roots of the problem, i.e. ISP allowing it's customers to send spam (wether they're end users or other ISPs makes little difference). In this day and age I see absolutely no reason for the rest the Net to allow such ISP to send email. Period.

      --
      1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
    12. Re:Not like people get all radical about it... by Anonymous Coward · · Score: 0

      Hang on, if they are vigilantes, then the second option must be

      (by analogy, kill the policemen).

    13. Re:Not like people get all radical about it... by Anonymous Coward · · Score: 0


      It's not over-reacting. Whilst I have been inconvenienced by this myself, it's clear that the *only* way to put pressure on ISPs who host (or tolerate) known spammers is to attack them indirectly, which is through their other (legitimate) customers. Once a significant fraction of customers complain, the ISP will take the correct action -- otherwise, they will continue to contribute to the SPAM problem.


      What's more, the ISPs which spam make money on the spammers; the good ISPs don't. The good ISPs will be undercut in the market by the bad ISPs, because they accept less revenues; and the customers of the bad ISPs will reap the benefits in reduced prices.

      So, the customers of the bad ISPs profit from spammers, and you and I get an inbox full of spam.

      Think of that the next time you're worried about the impact of blocking a bad ISPs emails: if these so-called "legitimate" customers aren't punished for their support of a spam-friendly ISP, they'll continue to reap the benefits of spam, and the spam in your inbox will get worse and worse.

      Disclaimer: it's been more than 12 years since I ran an ISP, but my attitude to SPAM has certainly hardened over the years. MAPS was right.

      I was there when Cantor and Seigel first posted the Usenet spam posting, and went on to write a book on spamming called: _How to Make a Fortune On the Internet_, advertising to the entire world how to buy a $100 Green Card lottery application; useful only to prospective US immigrants, and available for free anyway.

      In retrospect, I wish they'ld been punished by having a Usenet group dedicated to organizing a phone-in protest: every minute, one person would phone in to their business number, complain loudly about a posting to one of the 3,000 newsgroups for a full minute, and then hang up. Then the next scheduled person phones in, and so on. Weeks or months later, after everyone on the list internationally have registered their complaint for the first posting, they'ld start into the complaints about the second newsgroup. And so on, until those weasel lawyers all went bankrupt; I bet they wouldn't have written their spammer's handbook then!
      --
      AC

    14. Re:Not like people get all radical about it... by Anonymous Coward · · Score: 0

      And I'm sure not giving money to an ISP that has nothing to do with spam (read the parent. And the great-grandparent, for that matter) will have a huge effect.

    15. Re:Not like people get all radical about it... by kevcol · · Score: 1

      Ahh yes- move out of your home; makes no difference if you own the home you live in or anything like that:

      Move to a new city- anywhere, just as long as you are able to placate SPEWS.

      Your bulb certainly burns bright and the elevator clearly stops at the top floor, young man.

    16. Re:Not like people get all radical about it... by jbolden · · Score: 1

      Apply pressure to remove the spammers (by analogy "regime change")

      The analogy here would be a change in the law. Leave the ISP would be emigrate / regime change.

  9. today? by BitwiseX · · Score: 0, Interesting

    an essay describing the danger and corruption of the main spammer blacklists today.

    today? Articles linked are from 2000 and 2002!

    I don't know how many times you can use the word "vigilante" in one article :/ Vigilante is a very strong word IMO.

    1. Re:today? by suitepotato · · Score: 1

      Which only means we need Paul Kersey (Chuck Bronson) to go out and deal with the spammers. For the squeamish, our vigilante can use humiliation instead, like tranquilizing them, stripping them down and painting them pink and blue and putting them on a 3am bus to Grand Rapids. I'd of course prefer something stronger like repeated tasering...

      --
      If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
    2. Re:today? by Joe+U · · Score: 3, Interesting

      "Vigilante is a very strong word "

      You're right. The correct words are 'overreacting assholes'.

      Most RBLs are run by assholes who have no concept of how to properly manage something as complex as a RBL.

      And no, I've never been blocked by one and I weight RBL positives very low.

    3. Re:today? by Anonymous Coward · · Score: 0

      I live in Grand Rapids you insensitive clod.

  10. Pure and simple... by jellisky · · Score: 4, Insightful

    I had the unfortunate "joy" of being blocked by some of these draconian blacklists. My sister requested some information from me for a trip that she has upcoming via my yahoo.com account. After it bounced from her ISP saying that I was sending it from a "spam-hosting" ISP, I sent it from my mac.com account. Same schtick. After a couple other choices, I finally got it sent from my .edu account.

    Her ISP uses SpamBag for their blacklist. SpamBag? ScamBag is more like it.

    No wonder my sister is disenchanted by email. Her yahoo account got spammed to no end, then she can't get emails from most of her friends since they get bounced back by her ISP's stupid blacklist.

    Blacklists are fine and dandy in principle, but practice has shown them to be useless. IT managers, just drop them. They're more annoying than anything.

    -Jellisky

    1. Re:Pure and simple... by Megor1 · · Score: 0, Troll

      Lol for fun look up the picture of the guy that runs spambag and then ask yourself if you want him telling you who can send you mail (It's a Jem)

      --
      Everyone that disagrees with me is a paid shill
    2. Re:Pure and simple... by NitroWolf · · Score: 1

      SpamBag is run by Sam Varshavchik, the author of Courier. A singularly most unpleasant and moronic individual.

      I had the misfortune to cross his path a number of years ago about an issue with Courier I believe or something else, I can't quite recall, and I will never forget it. He is one of the most vitrolic, annoying, moronic individuals I have ever come across. I'm amazed he was able to produce something as nice as the Courier MTA package, but I guess idiot savants like him can do good things. It's just unfortunate he has the social skills of a diseased whore.

      Anyone that uses SpamBag as their RBL is a dumbass in the extreem. Then again, anyone that uses ANY RBL as the final arbitrator of email delivery should be beaten to begin with.

    3. Re:Pure and simple... by Anonymous Coward · · Score: 1, Interesting

      Speaking of blacklists not working, the company I work for had an open relay. We discovered this when we started getting Blacklist replies one December. Management wouldn't do anything, because our admin wanted to spend $20k upgrading our server to fix the problem. By May our server would crash daily, usually with 10k messages in the queue.

      The only reason we actually fixed the problem was because the boss couldn't get his email on the road (the server had crashed again). Incidentally, I was the only one available to actually do the fix, and I did it with Linux/qmail and an old box over the weekend. $0 spent.

      Maybe if we had been blacklisted to the point of not being able to send any email, they would have paid more attention. Instead most of our mail was still going through, so we were allowed to be a menace to the net.

    4. Re:Pure and simple... by Anonymous Coward · · Score: 0

      Look up the neck beard that runs BLARS.

    5. Re:Pure and simple... by Anonymous+Brave+Guy · · Score: 2
      Speaking of blacklists not working, the company I work for had an open relay. We discovered this when we started getting Blacklist replies one December. Management wouldn't do anything, because our admin wanted to spend $20k upgrading our server to fix the problem.

      I would have thought firing the admin who left the relay open and hiring someone competent to fix it instead might have been a good thing to do. What on earth was the $20k suppose to be for?

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    6. Re:Pure and simple... by Anonymous Coward · · Score: 0

      The open relay was probably a quick fix so that the boss could send his email while on the road. :)

    7. Re:Pure and simple... by Pig+Hogger · · Score: 1
      No wonder my sister is disenchanted by email. Her yahoo account got spammed to no end, then she can't get emails from most of her friends since they get bounced back by her ISP's stupid blacklist.
      Yahoo mail: you get what you pay for.
    8. Re:Pure and simple... by EvilStein · · Score: 1

      Hrm, I'm on the courier-users list and have never seen him act that way. in fact, it's been exactly the opposite.

      Now, check out the dumb shit that blocked the server that does nothing but host the *Postfix Users* mailing list..

      Google for "camomile.cloud9.net listed on SORBS"

    9. Re:Pure and simple... by TCM · · Score: 1

      Postfix-users mail is normally filtered into a special folder - based on
      the sender, return, to and cc addresses. For the last 3 days I have had
      the unfortunately 'pleasure' of having to use Windows rather than linux,
      consequently that filter is not automatic, so all postfix mail was
      sorted by hand.

      Now, when I receive UCE and UBE, I quickly verify it's not real mail and
      move it to the special folder - the system takes care of it from there.
      In this case the message is spam and there was no information to
      indicate it was via the postfix mailing list without viewing source
      (which I don't do routinely), so the message was submitted as spam.


      WTF. I'd say this moron isn't aware of his responsibility and the consequences of his actions.

      "Oh, looks like spam *clicketyclick*" "You just blacklisted a major legitimate relay" "Whoops, stupid windows, go file a delist request"

      What an asshole.

      This story makes a good point about some of the amateurish procedures these lists are run with. Apparently it's really hard to pick a good one and in no way should you let it have sole authority over the finaly decision to block mail.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    10. Re:Pure and simple... by EvilStein · · Score: 1

      That's pretty much what happened. But this isn't just some list.. this was *SORBS* - a pretty big list. They admitted that a lot of the mail (if not all) is automated?
      No apology from the guy and it took them a while to remove it. Completely unacceptable in my book.

    11. Re:Pure and simple... by DavidTC · · Score: 1
      You can tell the writer of Courier is an asshat just by looking the install.

      Why? Well, the lack of providing an RPM, which is just annoying, and the delibrate inability to compile the RPM as root.

      Total asshat clue, right there. 'Let's force people to set up an RPM compiling area as a normal user!'

      The first person to say 'You shouldn't be doing things as root' gets a punch in a mouth. I'm installing the damn thing as root, aren't I? I rather obviously trust the code, why wouldn't I trust the compile?

      Well, no, I'm not it as root, I'm installing postfix.

      But I am using maildrop, because I couldn't get the postfix built-in delivery agent to use mysql right. (It's probably fixed now.)

      It's weird, qmail's author seems to be a jerk too. Is there some sort of school producing MTA-writing jerks?

      The only sane choices for MTAs out there seem to to be Postfix and exim. (Sendmail is not written by a jerk, but...gah, can we just kill that thing already? Whenever I think of sendmail, I imagine a giant mechanical framework around a dead horse, moving its legs so it's appearing to walk.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
    12. Re:Pure and simple... by Anonymous Coward · · Score: 0

      What do you recommend as a replacement for courier-imap?

    13. Re:Pure and simple... by aaronl · · Score: 2, Interesting

      Yes, fun isn't it? Trying running your own email server from a Charter business link. Then try sending email to Juno or NetZero customers. Their mail server will give you a 550 denied. Proceed to have the ISP's ignore you, and the RBL jerks ignore you.

      The reason for the block? All Charter IP addresses have been put into a "residential" blocklist by one RBL nut that decided such a list was a good idea. Everyone knows that you should have to buy a T1 to send email. This is because people who really need to send email have the budget to pay 800$/mo for it, apparently. Unfortunately, Juno and NetZero both seem to agree.

    14. Re:Pure and simple... by DavidTC · · Score: 1
      Oh, heh, I forgot I had to use that also. I know of none other that can use mysql.

      Or, really, none other at all. The 'standard' one, cyrus, has the same baggage as sendmail, although at least it's not that old.

      Courier-imap is nice and clean and usable and works. It's just ultimately packaged by a jerk. (You can kinda tell that by the inability to run it from inetd. Not that I want to, but I can't.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
  11. Paul Graham's book by pHatidic · · Score: 0, Offtopic

    I just finished his book Hackers and Painters last night, and I highly recommend it. It has given me a much better understanding of economics, and has made me understand the conservative economic point of view much better. Of course I am also in the process of starting a startup, which is exactly what Graham recommends as the fastest way to wealth (for the most talented 1%, but indulge me here for a bit), so I may be a bit biased. But I do this that it is worthwhile for everyone to read, both for the life/economic advice as well as his technical insight into programming languages. Of course you should give it to your boss to read after you finish with it, as it is really in large part to help non-nerds understand nerds.

    1. Re:Paul Graham's book by Brando_Calrisean · · Score: 1

      Of course you should give it to your boss to read after you finish with it, as it is really in large part to help non-nerds understand nerds.

      Except that non-nerds aren't nerdy enough to read books about nerds.

      --
      Don't call me a cowboy, and don't tell me to slow down!
    2. Re:Paul Graham's book by Momoru · · Score: 1

      I wouldn't listen to his ideas about start ups...he doesn't even have the level of experience in this area as even say a Mark Cuban (who i think it equally lucky, but at least had two other companies)....Paul Graham had one idea that happened to come during the crazy dot com days that yahoo paid a fortune for. It was basically just luck and nothing more. If he were to start again from ground zero today with no name recognition or his millions of yahoo dollars, i really doubt he would succeed.

    3. Re:Paul Graham's book by ScreamCity · · Score: 1

      That might be true, but first, many people had successful startups yet not that many of them write about how did they managed to be successful and second, Paul Graham is an excellent writer. His essays are just a very good read (and very convincing too). I, for one, believe in what he writes.

  12. Whiskey. Tango. Foxtrot. Over. by Skye16 · · Score: 5, Insightful

    So...it's okay if he goes to Federal Pound-Him-In-The-Ass penitentiary just because he rented a car from a place that also rented a car to a crack dealer?

    Huh?

    Sorry, but that's still bullshit. He states it clearly in his article: You can't screw over innocents just to make the guilty pay. Does the your government put a neighbor family through torture just because you got a parking ticket? No. It's YOUR fault and YOU should be punished. Not some innocent bystander.

  13. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  14. I'm sure this seemed like a good idea at the time. by the_rajah · · Score: 1

    but five minutes later they should have recognized the likelihood of unintended consequences and looked for a better solution, much as our fine lawmakers always do....oh, wait....

    --


    "Do the Right Thing. It will gratify some people and astound the rest." - Mark Twain
  15. Happens to all blacklists by m50d · · Score: 1

    All blacklists get corrupted over time. On the other hand, new ones won't be very effective because they don't have enough spammers on them. You have to choose what false positive level is acceptable to you.

    --
    I am trolling
  16. Pay and you get removed by tmk · · Score: 4, Interesting

    I have found an interesting offer: pay 50 bucks and you are removed immediately from the spam list. Have a look here.

    Interesting: The company won't say who they are. They say this was approved by local authorities, but this is bullshit. Local authorities can not brake federal law in Germany.

    1. Re:Pay and you get removed by Reverend528 · · Score: 1

      That's a great idea! There's certainly no incentive to be corrupt when they're only getting $50 to remove ISPs from the blacklist.

    2. Re:Pay and you get removed by Malc · · Score: 1

      A bit like this self-important prick. He states:

      "If you would like a site be added or removed from BlarsBL, you may hire Blars at his normal consulting rates (currently $250/hour, 2 hour minimum, $1000 deposit due in advance for non-established customers) to investigate your evidence about the site. If it is found that the entry was a mistake, no charge will be made and the entire deposit will be refunded. Send Blars email from a non-listed account to verify current rates and arrange payment."

      One of our work IPs is listed on this list (I found it via dnsstuff.com). No idea how we got listed, that's his problem. He's so insignificant he's not affecting delivery of our outgoing mail. He obviously thinks he's important though. I looked at his web page... and yes he's quite sad and pathetic. If he were running a major RBL, the attitude in that one paragraph would ensure that we would definitely go straight to our corporate lawyers rather than contact him first.

    3. Re:Pay and you get removed by hesiod · · Score: 1

      That's not entirely honest of you... If you DON'T pay the money, you just have to wait 7 days. and regardless of whether you pay or not, if spam is found from your site again, you get added again. Sure, you can pay again, but it'll get expensive real quick.

  17. Oblig. Simpsons Reference by Mr.Progressive · · Score: 3, Funny

    Blacklists have a structural flaw: there is no one to watch the watchers.

    Lisa: If you're the police, who will police the police?
    Homer: I 'unno, Coast Guard?

    --
    Okay, so a philosopher, a philologist, and a philatelist walk into a bar...
  18. Who watches the Watchers? by redelm · · Score: 3, Insightful
    ... the Watched, of course! Ruel enforcement isn't a heirarchy but a loop.

    Blocklists are made by people for others to use if they see fit. When they become unusable, they're no longer used. Personally, I use none. The cost to me of one false positive is greater than 1000 spams that leak through. No list is that good.

    1. Re:Who watches the Watchers? by Anonymous Coward · · Score: 0

      Ruel enforcement isn't a heirarchy but a loop.

      Ruel dictoinaries help yuo write in inglish.

  19. Dont quite understand by jmkrtyuio · · Score: 1

    " This is, strictly speaking, terrorism: harming innnocent people as a way to pressure some central authority into doing what you want " -the harm is inflicted, often intentionaly, by those who CHOOSE to use a blocklist -Innocent is at best debatable " As of this writing, any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam. Why? Because the guys at the SBL want to pressure Yahoo, where paulgraham.com is hosted, to delete the site of a company they believe is spamming. " I was under the distinct impression that the SBL is an IP blocklist. And I see absolutely no evidence here of motive. Merely his say so.

  20. Paul Graham updates his blog by a7244270 · · Score: 2, Insightful

    OK, so PG wrote some code in the past, and is generally a smart guy, and to be honest, I actually like his writing. I like it enough that I'll even read his stuff despite the fact that he uses an excessively narrow column width for his text which makes it very annoying to read. However, there are many blogs out there written by smart programmers, some with far, far, far more geek cred than PG.

    Why exactly is this a Slashdot story ?

    1. Re:Paul Graham updates his blog by slavemowgli · · Score: 1

      It's a Slashdot story because Slashdot needs to have a certain amount of stories each day to keep readers happy - because if readers go away, so will advertisers (i.e., the money). :)

      On a less cynic note, it seems to be true that while Paul Graham has written some very insightful articles on spam, this blog entry does leave you with the feeling that the topic wasn't explored in-depth at all - that, rather, it was merely written out of frustration after finding himself as an (innocent) victim of one of the blacklists.

      That *is* rather unfortunate, and I would certainly have preferred a better article, but it's still an interesting discussion starter at least, and personally, I'm quite happy to see that the dangers of blacklists are being pointed out again to the general (Slashdot-reading) public.

      --
      quidquid latine dictum sit altum videtur.
    2. Re:Paul Graham updates his blog by Anonymous Coward · · Score: 0

      Because PG blew Taco before you could get to him.

    3. Re:Paul Graham updates his blog by Anonymous Coward · · Score: 0

      I like my answer better than yours, even though yours is much more accurate. /props

    4. Re:Paul Graham updates his blog by bugbear · · Score: 1

      Sorry. I didn't expect this to be slashdotted and am a bit embarrassed that it has been. This isn't a proper essay, and I don't expect it to be interesting to the average reader. This is just a page I added to the part of my site for people working on the spam problem.

    5. Re:Paul Graham updates his blog by a7244270 · · Score: 1

      I'll forgive you if you autograph my copy of Hackers & Painters. :)

    6. Re:Paul Graham updates his blog by legirons · · Score: 1

      "However, there are many blogs out there written by smart programmers, some with far, far, far more geek cred than PG."

      I think this might be an appropriate time to ask for links. I'd be interested if you know a few columns that are better than PGs (as I haven't found many so far)

      (And no, Joel Spolsky definitely doesn't count. Although Phil Greenspun might)

    7. Re:Paul Graham updates his blog by a7244270 · · Score: 1

      You want programmers writing about software, or programmers writing about random stuff ?

  21. Been considering... by danheskett · · Score: 1

    I've been considering going to a whitelist only system.. Everyone I know gets on a whitelist, and my personal website/webpage will have a CAPTCHA and a way to suggest your name onto my whitelist.

    Pratical for me? Yes, but I wonder how well it would apply to other users.

    1. Re:Been considering... by Just+Some+Guy · · Score: 1
      Don't do it, man. Really, don't do it. On several occasions, a non-subscriber has posted an urgent question to a mailing list I'm on. When others and I try to respond, we've been hit with challenge-response messages. There is no quicker way to get someone not to help you than by deliberately making yourself inaccessible.

      I have never, ever replied to a whitelist invitation, nor do I expect to. Based on conversations I've had, I don't think I'm in the minority.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Been considering... by Infinityis · · Score: 1

      Actually, a whitelist system would be interesting...I mean, it worked (or still works) for Google. Think about it...the way they validated the relevance of an email was based upon how many links to that page existed. If there were a way to rank email sources based upon the ratio of emails received received by that address divided by the number of emails sent from that address, then that gives a decent metric of the realistic use of that email address. If the number is at or near zero, then either it's a spammer or a mailing list. If the mailing lists could be user-authorized, then all the user should receive is email from "real" email addresses and the user-authorized mailing lists.

      Granted, there will be problems down the road because some spammers will email each other a lot to build up their ratios, and but that's basically the equivalent of what Google deals with already in terms of links from SEOs. But it's a start.

      I suppose the missing element right now is the ability to keep track of emails sent/received for a given email address, but maybe someone more knowledgable than I knows a way...?

  22. Re:Whiskey. Tango. Foxtrot. Over. by Cylix · · Score: 1

    In the age of the internet...

    It's not like it's difficult to register a domain. With cars... it's a little more expensive and there are several registriations that take place.

    So two discern two cars in a particular rental agency is not the same as two domains on the same ip/subnet.

    Your comparison is fundamentally flawed.

    --
    "You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
  23. *PLONK* by Anonymous Coward · · Score: 0
    In 1997, a group of anti-spam vigilantes called MAPS started a blacklist of mail servers... This is, strictly speaking, terrorism


    His other stuff on spam also missed the mark.

  24. Re:Whiskey. Tango. Foxtrot. Over. by Skye16 · · Score: 1

    Not in the slightest. You're basically saying "It's too hard otherwise". I'm basically saying "That's too goddam bad". You can't fuck over those who are innocent just to punish those who are guilty. If that means you can't win, then fine, you can't win. Deal with it.

    Or, of course, you can keep doing it, but you're still a prick. (General you, not specific you - I don't know you, so I wouldn't dare make that claim right off the bat :] )

  25. Corruption does exist by geekwithsoul · · Score: 1

    I work for an organization with ties to many different ISPs and I've heard many horror stories about large blocks of addresses getting blacklisted for the actions of a few, and when the ISP has either already gotten rid of the offending customer or tried to get incorrectly blacklisted blocks off the lists, they've been told "Pay me $xxxx and I'll remove you."

    I guess some blacklist managers have not taken to heart the adage "With great power comes great responsibility." I'm also sure many users of the data these blacklists provide are not even aware of the practices of these folks.

  26. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  27. Re:Language by PitaBred · · Score: 0, Offtopic

    Because white is the color of sunlight, generally regarded as pure, and black is the color many wounds turn when rotting and bad... I'm failing to see the problem?
    Methinks you're finding ghosts because you feel like being oppressed.
    Besides, isn't it african american, not black?

  28. There is a problem with blacklists by WebHostingGuy · · Score: 5, Insightful

    We deal with this all the time. Leaving any IP on a blacklist for any period of time doesn't help. Most spammers nowdays spam and run. They unload from a hacked account through a broken formmail script or a zombie computer. After 36 hours they have dumped their million emails and moved on to another IP. Blacklists generally don't get this though. They just make a bigger and bigger list. The problem with this approach is that they already missed the spammer. One time we dealt with someone who was running a blacklist and when we asked why an IP was on the list they said because it spammed years ago. When we said we have controlled the IP for the past three years they said it doesn't matter. It's like give me a break...

    The solution to blacklists is to use an AOL model in which dynamic IP blocking is used. When spam is noted from an IP that IP is automatically blocked for 24-36 hours after the last spam comes in. That way the innocents are not being blocked and the spammers email doesn't make it through. There are a couple blacklists which do this but more should.

    Compare this to the opposite blacklists like BLARS which requires a thousand dollars for "him" to investigate whether an IP should be removed. I have never seen an IP which is not listed with BLARS.

    --
    Quality Hosting e3 Servers
    1. Re:There is a problem with blacklists by kaarlov · · Score: 1

      Practically nobody uses BLARS, so I wouldn't worry about it. Among other things, BLARS lists /16 netblocks which are allocated to different providers in different countries as one listing. But I wouldn't worry about it.

      About spam and run. Yes sometimes it is just quick spam and run. But sometimes they use the same ip-address for months. While ago I received a lot of annoying spam to different role accounts from one ip-address, which wasn't blocked by any blacklist I use (It was blocked by SPEWS because of the same spammer), and I placed a manual block on it. I periodically check all my manually blocked IP's because I don't want to keep them listed forever. That one went on for months, though it was finally listed by SBL too.

      Spammers use different methods to get by different types of blocking. And AOL-style dynamic blocking isn't very effective for smaller providers or smaller companies. Unless someone creates a trusted network of admins and good infrastructure to collect enough spam to judge which ip's should be dynamically blocked.

    2. Re:There is a problem with blacklists by Anonymous Coward · · Score: 0

      I remember having my server blacklisted on BLARS blacklist.

      At the time I didn't know who he was. Sure enough, when I emailed him, along came the demand for the USD$1,000 came along I thought who is this giddy creep?

      I'm sure there are some suckers he defrauds into paying him, but it was quite a feeling of helplessness (and anger) until I realised that no-one bothered with his "blacklist" or takes him seriously.

      However, one day he's going to piss off the wrong person and get sued for blackmail or extortion - I'm sure some creative attorney could frame a case around his demand letter...

    3. Re:There is a problem with blacklists by argent · · Score: 1

      Leaving any IP on a blacklist for any period of time doesn't help.

      Then you should have no problem with SBL. They automatically delete listings after six months, even for known spam gangs (though of course they get back in again if they're still being used).

      And some spammers really do spam from the same address for years. I've got several addresses that I've had in a hardcoded block list on my mail server that are still spamming me after two or even three years. And the SBL is effective: I use my own dynamic block lists and greylists and dynamic IP lists, and the SBL still blocks a huge number of messages after all that.

    4. Re:There is a problem with blacklists by mabu · · Score: 2, Insightful

      Spamcop's RBL does exactly what you're suggesting. Their automated system automatically "retires" IP addresses from the RBL after set amounts of time. It goes one step further though, and determines the suitability for longer-term inclusion on the list based on the IP's history of spamming. It works exceptionally well.

      I have been the victim of the formmail exploit, and been RBL'd as a result. It was not difficult to get un-blocked. Yes, it was a hassle, but I suspect those that complain about being RBL'd, are the people that send nasty, vicious, "take me off or i'll sue you f'ing jerk!" e-mails and then wonder why they weren't removed. If you're polite with the RBL maintainers they're more than happy to cooperate. Anyone who's running an RBL that isn't reasonable, won't have anyone using their list so it doesn't matter.

    5. Re:There is a problem with blacklists by Anonymous Coward · · Score: 0

      One time we dealt with someone who was running a blacklist and when we asked why an IP was on the list they said because it spammed years ago. When we said we have controlled the IP for the past three years they said it doesn't matter.

      What I have seen on news.admin.net-abuse.email (NANAE) a lot is people who get some rush of power from refusing to remove IPs from spamlists. Rather disgusting, actually.

  29. What IP is the originating mail from? by isn't+my+name · · Score: 2, Informative
    # dig paulgraham.com MX

    ; <<>> DiG 9.2.4 <<>> paulgraham.com MX
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53349
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;paulgraham.com. IN MX

    ;; ANSWER SECTION:
    paulgraham.com. 3600 IN MX 10 milter1.store.vip.sc5.yahoo.com.

    ;; AUTHORITY SECTION:
    paulgraham.com. 3600 IN NS st-ns1.yahoo.com.
    paulgraham.com. 3600 IN NS st-ns2.yahoo.com.

    ;; ADDITIONAL SECTION:
    st-ns1.yahoo.com. 154169 IN A 216.136.225.202
    st-ns2.yahoo.com. 134882 IN A 216.136.225.203

    ;; Query time: 228 msec
    ;; SERVER: 192.168.1.23#53(192.168.1.23)
    ;; WHEN: Thu Jun 16 14:30:43 2005
    ;; MSG SIZE rcvd: 150
    Looking up the IP for his mail server, we get:
    # nslookup milter1.store.vip.sc5.yahoo.com

    Non-authoritati ve answer:
    Name: milter1.store.vip.sc5.yahoo.com
    Address: 216.136.232.238
    A Multi-RBL check on that IP shows absolutely no black-listing in any of the many RBLs.

    Is it possible that it's his outgoing cable-modem IP address that is the problem?

    Is it, as the parent suggests, spam-assasin filtering?

    I'm more than happy to get on the wagon of unresponsive RBLs. The only way they can actually get the response they want is if cleaning up your act results in de-listing.

    However, Mr. Graham makes some big claims with nothing to back it up--and attempting to investigate on your own shows that his claims don't seem to check out.
    1. Re:What IP is the originating mail from? by kaarlov · · Score: 2, Informative

      MX records don't always tell where the mail is sent from. In fact it is good idea to have separate server for sending mail. For example if your MX in some situation sends bounces to forged aol-addresses, it gets very easily blacklisted temporarily by AOL. But sending mail directly from server which hosts multiple webpages in same ip is not a good idea. But I don't thing Graham does that either.

      From TFA and from parent article I got impression that he suffers from people having spam filters which run URL's in the email body through blacklists. And I think that spam filter which gives too much points for that is more broken than the concept of DNSBLs.

  30. Re:smart you ain't by Anonymous Coward · · Score: 0

    Spam is a crime (legally and ethically IMHO). Therefore spam blacklists could be considered vigilante operations.

    I've seen small ISP's and web hosting companies with some of the most dedicated, proactive, and talented security officers fail to stop all if not a good chuck of out going spam from their networks. So saying "Oh ISP just need to do their jobs a little better!". Spam is big business on both side of the fence.

    Lots of spam blacklists get drunk on their own power and DO make some bad calls. SPEWS in my opinion has been one of the worst to deal with. I can't say I trust any organization who is accountable to no one but themselves.

  31. Re:Language by Vainglorious+Coward · · Score: 1, Offtopic

    Besides, isn't it african american, not black?

    Who said anything about American?

    On a practical level, "block list" and "accept list" are just much better descriptions of what such lists actually do.

    --
    My next sig will be ready soon, but subscribers can beat the rush
  32. Ooh, blackholing is TERRORISM now! by Medievalist · · Score: 0

    Graham writes: For example, in order to get revenge on people they believed were spamming, MAPS would blacklist the mail server of the company hosting their site.

    Wrong. "Revenge" is completely off the menu. Paul's being a crybaby and refusing to look at anyone else's point of view.

    The truth is, MAPS blacklists the mail server of the company hosting the spammer because MAPS subscribers are willing to give up their ability to recieve mail from some innocent bystanders if that will break spamhosters' profit model. That is the choice of those who use the blacklist.

    Graham also writes: This is, strictly speaking, terrorism: harming innnocent people as a way to pressure some central authority into doing what you want.

    Now Paul's really gone over the top. Allowing MAPS subscribers to block email is "harming innocent people"? Get a sense of proportion, man! Terrorism has a definition, although some dispute the details and this isn't it. Where's the terror? Are you living in fear that your email might be blocked, because you use a spamhoster? I don't think it's MAPS fault if you are terrorised; I hope you are not, but if you think you are, you need to see a psychiatrist quick.

    Once you get past the hyperbole in the first few paragraphs, Graham makes at least one valid point (his site has been wrongly blacklisted) and asks at least one pertinent question (who watches the watchers? answer: subscribers). But this article is mostly just a hysterical anti-blacklisting rant.

    1. Re:Ooh, blackholing is TERRORISM now! by Dynamoo · · Score: 1
      Oh there's nothing like a kook who gets annoyed because they host with a spam-friendly outfit like Yahoo!

      Take for example hostingprod.com, which is Yahoo's most bulletproof and spam-friendly hosting outfit. Check out that spam! When this person (who seems to have his own fan club, heck I expect there are some kooks amongst them too) stops bleating and moves his hosting to a less spam-friendly hosting outfit then perhaps that will be a small victory. But the bottom line is that if you host your site with bottom-feeding scummy spammers then you can expect some blowback.

      But it gets worse. He clearly has zero idea about the SBL and this concept of "power corrupting them" sounds like the petulant complaining of a teenager. The SBL makes a positive contribution to the daily lives of hundreds of thousands of internet users. That's far more use than the pathetic drivel you see on Paul Graham's site.

      --
      Never email donotemail@WeAreSpammers.com
    2. Re:Ooh, blackholing is TERRORISM now! by Anonymous Coward · · Score: 0

      You don't understand. He HAS to call them terrorists. Everyone knows that if you call them NAZIs, then you have already lost the argument!

      Also, who says his site has been wrongly blacklisted? Go to SBL and look at the evidence before repeating Graham's claim. Do you believe everything you read on the net?

  33. What's the real story? by argent · · Score: 3, Insightful

    People switched from MAPS because the other lists were free, not because MAPS was too aggressive.

    "As of this writing, any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam."

    Whisky Tango Foxtrot? *BLs block IP address ranges, not URLs.

    "Because the guys at the SBL want to pressure Yahoo, where paulgraham.com is hosted, to delete the site of a company they believe is spamming."

    1. Given that Paul's mixing up URLs and addresses of mail servers, I'm not prepared to take at face value the statement that SBL is blocking Yahoo's mail servers to pressure Yahoo to drop a "site", rather than (say) mail services Yahoo is providing the spammer.

    2. If Yahoo is providing services to a spammer and Yahoo refuses to deny those services to a spammer, than Yahoo is being "spam friendly", no matter what their reputation is, and they may well be depending on the many legitimate lists they're hosting to avoid responsibility for their actions. That's exactly the situation that John Reid is referring to in Paul's quote.

    I don't know what alleged spammer this is referring to, but what Paul's written is clearly not anywhere near the whole story.

    1. Re:What's the real story? by Russ+Nelson · · Score: 1

      DNSBLs block IP address ranges, not URLs.

      Actually .... since the one thing you can count on in spam is a working URL pointing to the spammer's advertising, some people are now parsing email, and checking the IP of all URLs. If any one of them is listed on a blacklist, then the email is rejected. Works pretty well, actually.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:What's the real story? by argent · · Score: 1

      some people are now parsing email, and checking the IP of all URLs. If any one of them is listed on a blacklist, then the email is rejected.

      So Yahoo's running outgoing SMTP from the address of Paul's webserver?

    3. Re:What's the real story? by Russ+Nelson · · Score: 1

      No, no, this is a blacklist containing the IP address of webservers advertised via spam.
      -russ

      --
      Don't piss off The Angry Economist
    4. Re:What's the real story? by argent · · Score: 1

      So he's running on the same machine as this spammer?

    5. Re:What's the real story? by Anonymous Coward · · Score: 0

      Wow, it takes Russ to compress-down all this /. BS and speculation to what really happend. Graham didn't have his SMTP blocked, he was probably nailed by someone using the URL lookup feature of Spamassassin3.

      And yes, it works VERY well. Spammers can find new trojan-zombies to spam though, but finding hosting is a bit harder, the "A" record of the URL stays the same for longer. If it's IP is in a list, 550, "get this stuff out'a here!"

      Problem is, old Yahoo is a piss poor "ISP" when it come to shutting down spam sites. They are a bit better with phish sites, but it's probably because the cops are on their backs about it.

    6. Re:What's the real story? by Russ+Nelson · · Score: 1

      Yes. The technical term is 'human shield'. Yahoo knows that the spammer is on that IP address. To protect their revenue, they put other non-spammers websites on the same IP address.

      John Levine has written up a description of the problem on his blog, Taugh Networks.
      -russ

      --
      Don't piss off The Angry Economist
    7. Re:What's the real story? by argent · · Score: 1

      Then that's Yahoo's responsibility, and Yahoo is who Paul should be complaining about.

  34. Easy answer to this... by Anonymous Coward · · Score: 0

    I knew it when I started reading that posting. He must have got listed somehow by one of them.

    Well talk to your provider and get them to get rid of the spammer. If they won't correct the problem then leave. That's the whole point of an RBL anyway.

    Customers get blocked and complain to their provider. The provider fears loss of further business and removes the offender. Of course this is only a theory cause it's rare someone does confront the provider.

  35. DUL by egburr · · Score: 1

    The DUL is another very annoying list. Earthlink reports all of its cable modem customers to DUL because we are forced to use "dynamic" addresses with DHCP. My address is so dynamic it has changed once since I because a customer, and that change occurred three years ago. For DSL customers, Earthlink offers a special service: a static IP address for only $15/month extra. Cable subscribers don't get that option. I really have to wonder how that static address could possibly cost them any more to maintain than my current dynamic address. In my case, the only difference it would make is whether I am on the DUL or not. (I use dyndns.org to have a dynamic domain point to me and now have a regular paid-for domain pointing directly to my IP address which I will manually update should my address ever change again.)

    --

    Edward Burr
    Having a smoking section in a restaurant is like having a peeing section in a swimming pool.
    1. Re:DUL by mabu · · Score: 1

      Don't run SMTP in DUL space. Simple as that.

      If you insist, use a proxy server that's outside of DUL IP space. Problem solved.

      Your ISP sucks because they haven't started filtering port 25 traffic outside of their authorized SMTP relays. I figure eventually all ISPs will do what AOL has done and restrict this activity and make the Internet a better place. It might even create a new marketplace for proxy mail services for people that do want more control.

      But for right now, I am fully in support of all DUL IP space being flagged as unauthorized for SMTP traffic. It sucks if you're doing something legitimate, but until your ISP controls their idiot users, it must be done, and it's the only way to get idiot ISPs like Earthlink, Verizon and Comcast to get off their lazy asses and fix their shit.

    2. Re:DUL by egburr · · Score: 1
      Don't run SMTP in DUL space.

      I am not in "Dial-Up" space. I am in "always connected" cable modem space where my address changes very rarely.

      Your ISP sucks because they haven't started filtering port 25 traffic

      I picked my ISP because they do NOT filter traffic without a good reason to filter it (such as verified reports that I am sending spam).

      It sucks if you're doing something legitimate, but until your ISP controls their idiot users, it must be done

      Yes it sucks, but "it must be done" is wrong. I am doing something legitimate. I run my own mail server. I do this for multiple reasons (in order of importance):

      1. Previous ISPs have had very unreliable mail servers (I don't know about Earthlink's); I know how reliable mine is and have logs I can check if/when something goes wrong.
      2. I get tired of identifying and notifying everyone when my email address changes when my ISP gets bought out or goes under or I move.
      3. I have my own web-based mail client (from www.horde.org) to use, so I can access my mail from anywhere and on any platform with a web browser that supports SSL instead of needing to install or configure a custom client whereever I go.
      4. for the experience
      5. because I can

      DUL makes sense for dial-up connections where the address changes every few hours because you have to dial in again. It does not make sense for "always on" connections like mine where the address has not changed in almost three years (December 2002 when an ice storm killed power for 10 days; the last change before that was when I relocated to a new state).

      I have never received any reports about spam coming from my server, either directly or relayed. I have never found my address listed by any of the blacklist sites except the DUL.

      Although I have done nothing wrong, I have been blacklisted because my ISP truthfully reports that I have a dynamic IP address served by DHCP. No consideration is given by the blacklist maintainers that my address has not changed in years, that my server is secured against relaying, that I have done nothing to earn being blacklisted. In fact, there is no way for me to get off of the DUL. At least with the other blacklists, there are ways I can attempt to prove my innocence of charges.

      --

      Edward Burr
      Having a smoking section in a restaurant is like having a peeing section in a swimming pool.
  36. Re:Language by Vainglorious+Coward · · Score: 1

    Would that be an editor that is modbombing this thread? I'd be flattered by the attention, if I had the slightest respect for them (-1 Flamebait)

    --
    My next sig will be ready soon, but subscribers can beat the rush
  37. Calling a spade a spade by Valdrax · · Score: 2, Insightful

    For some reason, journalists keep calling blackmail lists "vigilantes". But there's something they don't understand: nobody forces email system administrators to use those lists.

    To be honest, I like his other analogy for blacklist maintainers -- terrorists. It's much truer to the point. Vigilante in my mind at least implies an attempt to go after the bad guys and protect the innocents thanks to the pop culture influence of TV, movies, and superhero comics.

    This doesn't describe blacklist maintainers.

    Blacklist maintainers are cynical, bitter, little men who care nothing for the people they hurt so long as they get a spammer. They deliberately target innocents in the hopes that the innocents will complain to the higher power to get rid of the things that bothers them. This leaves little to distinguish them from terrorists other than the fact that they don't kill people. Their deeds are less dark, but their tactics are the same as the Madrid bombers who hurt innocent people to push them to choose a government more favorable to their wishes.

    Sure, nobody forces email admins to use those lists. Nobody forces people in the Middle East to contribute money to Hamas either. I don't care if you think you're funding hospitals and charity for Palestinians or if you think you're fighting to keep spam off the web -- you're paying to see people get hurt too. Stop it.

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    1. Re:Calling a spade a spade by 3nd32 · · Score: 2, Insightful

      Oh, come on. Do we need a new version of Godwin's Law? Blocking a website and blowing up innocent people are not comparable.

    2. Re:Calling a spade a spade by Anonymous+Brave+Guy · · Score: 1

      On the other hand, blocking a web site and blowing up the building hosting your company can have pretty close to the same effect on your business. That's pretty much the biggest problem here.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    3. Re:Calling a spade a spade by Valdrax · · Score: 2, Interesting

      Welllllll.... maybe. I did try to clearly deliniate that I did not see murder and extortion as morally equivalent, but I figured that I'll draw some flamebait mods anyway.

      The point is still a good one. Is it morally reprehensible to target innocents for the purposes of shaping institutions of power? Is this not fundamentally the definition of terrorism? If you agree on both counts, then MAPS is an opt-in terrorist network dedicated to the destruction of spammers.

      --
      If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    4. Re:Calling a spade a spade by brpr · · Score: 1

      This leaves little to distinguish them from terrorists other than the fact that they don't kill people."

      So you mean, appart from the fact that they lack the defining characteristic of terrorists, these people are just like terrorists. This is a bit like saying "This leaves little to distinguish them from thieves other than the fact that they don't steal anything".

      --
      Freedom is not increased by mere diminuation of government. Anarchy is freedom for the strong and slavery for the weak.
    5. Re:Calling a spade a spade by 3nd32 · · Score: 1

      I will agree on the first point. However, I am not convinced the blacklists are targeting innocents. I would see it more an indifference to innocents. They are targeting spammers, and have deemed others as "acceptable casualties". The collateral effect does have benefits for them also, but that isn't their goal.

      On the second point, assuming they were targeting innocents, it still isn't terrorism. There is no terror involved. It is far closer to an embargo than terrorism.

      I am in agreement that blacklists are not the best approach, but felt comparing it to "terrorism" was drastically overreaching the truth.

    6. Re:Calling a spade a spade by Pig+Hogger · · Score: 1
      Blacklist maintainers are cynical, bitter, little men who care nothing for the people they hurt so long as they get a spammer.
      Blacklist maintainers are just tired of having their networks clogged by spam.
    7. Re:Calling a spade a spade by Valdrax · · Score: 2, Insightful

      So you mean, appart from the fact that they lack the defining characteristic of terrorists, these people are just like terrorists.

      No. That's the defining characteristic of murderers. There are other ways to commit acts of terror. Kidnapping (without murder), rape, sabotage, etc. all can be acts of terrorism if intended to shape someone's opinion or vote. Really, the place where the analogy fails is that terrorism is inherently violent, where spam blacklists are not.

      However, the core issue of spam blacklists deliberately targetting innocents to get them to demand change puts them in the same philosophical camp in my mind.

      --
      If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    8. Re:Calling a spade a spade by Valdrax · · Score: 1

      Perhaps it is overreaching. After all, terrorism inherently requires violence which blacklisting doesn't involve.

      However, I'll dispute that innocent clients of target ISPs are mere collateral damage. Angering them enough to force them to abandon their ISP or to force their ISP to change is the whole point of the blacklisting whole ranges of IPs that many blacklists engage in. It IS their goal to target innocents. It has been stated before, as others have commented in this article.

      --
      If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  38. Re:Good riddance by Anonymous Coward · · Score: 0

    The major backbone providers are all spam-friendly. If you use the internet, someone, somewhere who supports spammers is getting your money.

  39. Abuse my hind end by Arker · · Score: 0, Flamebait

    I really get sick of this sort of whining.

    Yes, innocent users get hurt when their ISP chooses to host spammers. There's no way around that, unfortunately, except for users to become more choosy about their ISPs.

    But when an ISP gets blacklisted for hosting spammers, this is not abuse or corruption - this is exactly what a blacklist has to do to be effective, and exactly what those of us that use blacklists expect and desire for them to do.

    You can play whack-a-mole with spammers day in and day out for years, and have zero or very near zero effect on them. I know, I've done it. By the time you report a spamming IP, the run is done. The spammer isn't going to come back there, he's going to come back from a different IP for his next run. If you want to have any significant effect at deterring spam, you have to do more than whack-a-mole, you have to get them where it hurts. They can send out a million emails from one IP, then never use that IP again. But they have to have someplace more stable to take the money from the handful of morons that go ahead and click on their links.

    If an ISP allows spammers to host on their network, they should be blacklisted. I don't want to carry their traffic. And if that means I'm turning down traffic from their other, non-spamming customers, that's a shame, but so be it. Maybe if their customers complain they'll get rid of the spammers. If not, I suggest their customers vote with their wallets, and find a new ISP. That is, if their purpose in having an ISP is communication with those of us that don't want spam. If they're happy being able to connect only to the fraction of the internet that welcomes spam, that's fine too. But it's up to them to make a choice.

    All the blacklists do is allow those of us that DO NOT WANT traffic from spam-friendly networks to implement these blocks. Trying to spin an informational service as 'vigilantism' and 'abuse' and 'corruption' because it doesn't work the way the spammers and spam-friendly hosts want it to is abuse of the language, and insulting to the readers intelligence, IMOP.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Abuse my hind end by jamie · · Score: 4, Insightful
      Obviously you feel very strongly about spam. You feel that spam is so important that websites which offer to sell spam software should be blacklisted, along with many other innocent websites hosted at the same ISP.

      What else do you feel strongly about?

      There are websites, I am sure, that describe in detail how to commit murder and get away with it. Some readers may find those sites, and using that knowledge, go commit violent crimes -- just as some readers of spam sites may purchase email harvesting software and then go commit the crime of sending bulk email. I assume you would support blacklisting ISPs that host violent-crime advice, since surely everyone agrees that murder is worse than spamming.

      There are ISPs that host neo-Nazi propaganda calling for the murder of all non-whites. Do you think that's better or worse than offering spam software for sale? Should those ISPs be blacklisted?

      Escort services? Simulated rape porn? "The Anarchist's Cookbook"? A list of abortion providers' addresses? Al Qaeda recruitment and propaganda? I want to know which of these you think is equally as bad as, or worse than, hawking a CD with a million email addresses on it. How many things do you think merit blocking all of an ISP's innocent websites?

      You have your list. Others have their own lists -- and, frankly, there are a billion people who think porn is vitally important and your fixation on spam is stupid. Do you really want the internet segmented? Do you think advancing your pet cause is worth walling off the internet into warring quarters? Do you really want to wield a censor's black pen?

    2. Re:Abuse my hind end by Anonymous Coward · · Score: 0
      Your point of view, though interesting, is naive. Put yourself in a hosters position. The hosters primary concern is making money, not pleasing some RBL. The hoster could care less about the RBL. And more MTAs then you'll want to admit DO NOT use RBLs for fear of missing email from business associates, customers, and potential customers. If a hoster loses a few legitimate customers, there are plenty of spammers around to fill the void left by their departure.

      Want to assign blame somewhere? Blame greed. IT'S what drives spam.

    3. Re:Abuse my hind end by Arker · · Score: 1

      There's a big difference between someone putting up a web-site you personally find objectionable for the content matter, and a website which promotes itself by thievery.

      You want to post your propoganda? Fine. Whether I like it or not, it's no business of mine.

      But when you start stealing from me in order to push it, that crosses the line.

      And make no mistake, that's what spam is. Theft.

      Now, beyond that, if a group of people decide they want blocks on their service to keep out porn, or nazi propoganda, or whatever, they're within their rights to do so. In fact, many people do just that, and several companies are making money selling that service - look at netnanny and that genre. I don't agree with their point of view, and I find them objectionable - but they still have a right to provide their service to subscribers that want it, no question about that.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:Abuse my hind end by jp10558 · · Score: 2, Interesting

      However, you seem to think it's easy to change ISPs. I can't. I have ONE broadband ISP where I live. ONE. I cannot switch.

      If you suggest I move... that's rediciulous. Let's all just up and move to a different town each time a spammer comes by. Sure. Maybe if you're Bill Gates.

      It is NOT easy to change ISPs, nor is it necessarily even possible. Oh, it's my fault for living here. Well excuse me - get the hell off your high horse. It's people like you making e-mail unuseable.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    5. Re:Abuse my hind end by Anonymous Coward · · Score: 0

      ISPs hosting neo-Nazi propaganda: It isn't shoved in my face.

      Escort services: It isn't shoved in my face.

      Simulated rape porn: It isn't shoved in my face.

      Anarchist's Cookbook: It isn't shoved in my face.

      Abortion providers: It isn't shoved in my face.

      Al Qaeda: It isn't shoved in my face.

      Spam: Shoved in my face, at work and at home, wasting hours of time. Yes, hours. This past week, it's taken me approximately thirty to fourty five minutes each morning to sort through mail, determining what spam is and isn't.

      Yeah. It takes that long, and each piece of mail must be manually verified. We can't afford to say, "Oops! Sorry, we didn't get your message because you live in Asia and your message looked like Engrish spammer talk!"

      Fuck spammers. Fuck the people who profit by it, may their entrails be strewn about like party streamers.

      How about I bust into your house each morning, wasting your time while I insist you need to buy some wholesome vi4gra or ci . al1s? Freedom of speech, right? Yeah?

      Freedom of speech means that you can say whatever you want - it doesn't mean you have the right to force people to listen.

    6. Re:Abuse my hind end by Monkeyman334 · · Score: 1

      Apples and oranges. Are people rabid about v14gra mailing lists? No, because you subscribe to mailing lists. You intentionally visit simulated rape porn sites. Spammers do their best to come to you and there needs to be a method to filter it out. It has nothing to do with content.

    7. Re:Abuse my hind end by Arker · · Score: 1

      BTW, you completely missed the point. I don't care if they're selling spam software (which I never mentioned but you acted like I had) or Viagra or fake rolexes or campbells soup. They can sell whatever they want. If they try to steal from me to advertise it, THEN we have a problem. And if their ISP doesn't see the problem, then I don't want to carry traffic from that ISP.

      Remember, the internet is a voluntary and coöperative thing. No one has any obligation to carry anyone elses traffic, absent contractual agreement. Where there is no contractual agreement, it's carried on the basis of generalised reciprocity and a basic assumption of decent behaviour. Decent behaviour does not include theft. And where there are contractual agreements, they almost always explicitly prohibit spam.

      If you want spam, that's fine, bully for you. But don't tell me I have to put up with it. I don't.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    8. Re:Abuse my hind end by Arker · · Score: 1

      I'm in the same situation - there is ONE broadband provider serving my residence. So don't think I don't understand your situation - I do.

      If they get blackholed, I'll be on the phone to them immediately. Why aren't you providing the service I contracted for?

      If someone on the far side of the planet writes them complaining about a spammer they're hosting, it may not get their attention. If 500 local customers call them up complaining that we're not getting the service we're paying for, that's a lot less likely to be ignored. Fact of life.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    9. Re:Abuse my hind end by Just+Some+Guy · · Score: 1
      The key difference, as I see it, is that none of spam lists are a reaction to a type of email that burdens the global email system. None of the other things you mentioned directly affect that system.

      It's not that I don't agree with you about blacklists (I do), but I don't think this is necessarily a reason you'd want to use in a debate.

      --
      Dewey, what part of this looks like authorities should be involved?
    10. Re:Abuse my hind end by argent · · Score: 1

      You feel that spam is so important that websites which offer to sell spam software should be blacklisted, along with many other innocent websites hosted at the same ISP.

      Anyone who uses a blacklist in such a way that they or anyone at their location or any of their customers can't get to a website because it shares the address of a server that's in a blacklist is (a) a fool, and (b) the person on whom responsibility for this abuse of that blacklist should fall.

    11. Re:Abuse my hind end by Anonymous Coward · · Score: 0

      so what? i dont have to visit the damn webpage now do I? I can leave the site if I come across it and never visit it again, wish I could do that with all those viagra emails!

    12. Re:Abuse my hind end by That's+Unpossible! · · Score: 1

      Look jamie, it's very simple.

      Put your opinions into the article submission, where they belong!!!

      --
      Ironically, the word ironically is often used incorrectly.
    13. Re:Abuse my hind end by Anonymous Coward · · Score: 0

      Want to assign blame somewhere? Blame greed. IT'S what drives spam.

      But it's greed that's the root of Paul Graham's bitching... how? Well, my ex-GF at Yahoo tells me he's not even on the books there, so he gets free hosting somehow.

      Guess he'd rather not pay to move elsewhere less spam friendly? Greed to keep the cash he's got! ;-)

      Hey, but I'll admit it, I'd do the same!!

      [adams family pinball] Greeeeeeeeeeeeeeed!!

      [Wall Street movie] Greed is good!!

    14. Re:Abuse my hind end by nytmare · · Score: 1

      I will explain it for you. It's like a nosy neighborhood watch lady being upset about a brothel or crack house opening up down the street. Real world problems that affect your real world neighborhood, and she'd prefer something be done about it. The neighborhood watch lady doesn't give a shit if some spammer lives in her neighborhood because his actions don't affect her neighborhood. You live in the same neighborhood and don't care about these new neighborhood blights, although you'll happily take any opportunity to put down the watch lady for her meddling ways, and bash her for not also going after spammers, wife beaters, corporate embezzelers, tax cheats, and drunk drivers -- all neighbors whose naughty actions don't affect the neighborhood itself.

    15. Re:Abuse my hind end by JuggleGeek · · Score: 1
      Do you really want to wield a censor's black pen?

      You are the one promoting censorship. After all, a RBL list is simply a list of IP's that the RBL recommends you not accept mail from. They don't force anyone to use it - they create a list and publish it.

      Some admins choose to partially protect their users from spam by refusing mail from listed sites - others don't. What gives you the right to say "They shouldn't be allowed to publish that list!"?

      You are the one advocating censorship. You are probably opposed to Consumer Reports, too. After all, it's essentially the same thing.

      Disclosure : No, my mail server doesn't bounce anything based on an RBL list, but I do use RBL lists as part of my filtering because the fucking spammers you don't want us to block would make email useless if no filtering was done.

  40. Re:Language by Anonymous Coward · · Score: 0

    >>I've always been a little uncomfortable with the underlying assumptions white=good, black=bad. I prefer to describe such lists as "blocklists" and "accept lists"

    >>Yeah, yeah, very PC of me; go ahead, shoot me down. Sometimes, these things *do* matter, and individuals have to stand up and say so.

    I think California has a law against this very thing. In fact, the words MASTER/SLAVE on an IDE drive or anywhere else is illegal in California government hardware.

    Now "that's hot." (TM)

  41. Guideline, not a rule by bitflip · · Score: 5, Interesting

    I use blacklists all the time. Rather than simply rejecting the mail, if the server is on a blacklist, the initial OK is delayed by five seconds.

    If you're sending a ton of mail, i.e., spam, little of it gets through. If you're only sending one or two messages, ie, likely legit mail, it goes through just fine.

    Combined with more specific stuff further back (bayes, et. al), it's been quite effective at reducing the amount of spam sent, and the amount of mail that gets scanned.

    The problem isn't blacklists, its how people use them.

    1. Re:Guideline, not a rule by angaram · · Score: 1

      Using blacklists in novel ways is particularly important as false-positives increase. Perhaps in conjunction with other suggestions here, there could be a meta-RBL that did not collect its own entries but instead was populated with the set of entries that was the intersection of of all of the actual lists. Or maybe populated with entries that appeared in at least 2/3 of the source lists. There would be the added benefit of domain admins. only needing to query one list: the meta-list that in turn collected from the source lists.

  42. Wrong by autopr0n · · Score: 3, Insightful

    What they do is allow others to block email between two diffrent people, simply because they run the mail servers that sit between them. If it was only individual users who were using these blocklists, it would be a diffrent issue. But it's not.

    --
    autopr0n is like, down and stuff.
    1. Re:Wrong by Pig+Hogger · · Score: 0, Troll
      What they do is allow others to block email between two diffrent people, simply because they run the mail servers that sit between them. If it was only individual users who were using these blocklists, it would be a diffrent issue. But it's not.
      I operate my OWN MAIL SERVER ON MY VERY OWN NETWORK. Those are MY PRIVATE PROPERTY, so I MAKE MY OWN GODDAMMED RULES and I DECIDE WHO CAN CONNECT TO MY NETWORK OR NOT. For this, blocklists are invaluable because other people do the gruntwork of discovering the IP addresses of others.

      In a nutshell, it's "MY NETWORK, MY RULES". Got any problem with that???

    2. Re:Wrong by squiggleslash · · Score: 3, Insightful
      You're why sysdadmins and blacklists have a bad name. Just because you can do it, doesn't mean you should or even that it's particularly intelligent to do so.

      If I can't receive email from a friend because my mail provider, who I pay money to, is as stupid as some of the BL-supporters here, you can bet I'll yell at them. They can whine as long as they like about how it's their equipment, *I* pay their wages.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:Wrong by Pig+Hogger · · Score: 1

      <morbo>We sysadmins have a vastly bigger intelligence than you, puny humans, so it is no wonder your puny little human brains cannot understand what we do. </morbo>

    4. Re:Wrong by Linux_ho · · Score: 2, Insightful

      If I can't receive email from a friend because my mail provider, who I pay money to, is as stupid as some of the BL-supporters here, you can bet I'll yell at them.

      RBL's don't kill e-mail, bad sysadmins kill e-mail. You're just demonstrating your own ignorance of spam-blocking techniques by saying "BL-supporters" are stupid. RBLs are an incredibly valuable tool. My systems, which process about 30,000 messages per day (60-70% spam), NEVER reject a message based on a single RBL hit. But if an IP is listed on three or more different reputable RBLs and doesn't have a very low Bayes score, that message is probably getting rejected. RBLs contribute a huge amount to my (currently > 99%) spam detection accuracy.

      --
      include $sig;
      1;
    5. Re:Wrong by Fulcrum+of+Evil · · Score: 2, Insightful

      You're why sysdadmins and blacklists have a bad name. Just because you can do it, doesn't mean you should or even that it's particularly intelligent to do so.

      When you're a sysadmin, you have to weigh the flood of penis pills and mortgage scams against one or two people not getting an email because the sender is hosted by someone who can't secure their mailserver. It's really an easy call. Before you start spouting on about giving users the choice of what to receive, there's also the sheer volume of spam - accepting too much email can put a serious strain on the servers and degrade the experience for everyone.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    6. Re:Wrong by Anonymous Coward · · Score: 0
      In a nutshell, it's "MY NETWORK, MY RULES". Got any problem with that???

      Hey, go for it. I even have a tip for you: block all the even-numbered IP addresses. Fully one-half of all spam come from those addresses!!

      In the mean time, the rest of us want to block spam, and only spam. Blacklists and other faulty spam technology have caused me headaches as both a sender and receiver. We need to find better methods of getting rid of spam.

    7. Re:Wrong by Anonymous Coward · · Score: 1, Interesting

      When you're a sysadmin, you have to weigh the flood of penis pills and mortgage scams against one or two people not getting an email because the sender is hosted by someone who can't secure their mailserver.

      Bzzt. You get the award for not RTFA today. The SBL added Yahoo, because out of tens of thousands of sites they host, two were accused of spamming.

      Yahoo represents a little more than "one or two people".

      Additionally, you missed the point he was making about blacklists in general, which is that they start out rejecting spam... and then the guys who run it go on a power trip and start blocking out whoever they feel like.

      He didn't say not to block spam hosts; he said that when they blacklist NON-spam sites by the truckload in order to pressure an ISP, they are specifically targetting innocent users in order to carry out their agenda.

    8. Re:Wrong by farnz · · Score: 1
      Blocklists is a bad choice of wording; these are lists of IPs that the list claims are spammy.

      It's up to the mail admin to choose what they do with them. Some mail admins block based on them; others choose to apply greylisting only to IPs on one of these lists. I happen to use several lists on the firewall that the mailserver lives behind to determine how fast your mailserver can send mail to my mailserver, using a CBQ setup. Unlisted servers are top priority, and can use all available bandwidth; listings in SPEWS level 2 and other unreliable lists are the next priority down, sharing 1MBit/s. Listings in SBL and other good blacklists force you down a level, and you now have to share just 10kBit/s.

      The result is that my use of blacklists doesn't drop a single mail; by throttling the rate at which blacklisted servers can send to me, I keep the load on my server under control, and there's no gain to you in having access to several servers, all on the same blacklist (as if two servers listed on the SBL send to me at once, they each get 5kBit/s, dropping to 1kBit/s whenever an unlisted server sends me something).

      Bad application of blacklists is wrong, but so's bad application of (for example) guns or cars. And, as with all things that someone else maintains, you need to check up on the blacklists you use regularly.

    9. Re:Wrong by Pete · · Score: 1

      Bzzt. You get today's award for not having read the informative slashdot comments, specifically this one - showing that the listing Paul Graham was bitching about covered only one single solitary IP address. As mentioned in alanw's comment, you can look at the Spamhaus record if you wish:

      Warned repeatedly, many times, that textileshop.com was spamming, Yahoo chose to continue hosting them. They spammed again. Via Haberstroh. Again. Textileshop has been kicked off other ISPs for spamming.

      News flash: Yahoo has more than one IP address. Hard to believe, I know. And very very very very very very very very few of Yahoo's customers/users would actually send email from that one blacklisted IP address.

      He didn't say not to block spam hosts; he said that when they blacklist NON-spam sites by the truckload in order to pressure an ISP, they are specifically targetting innocent users in order to carry out their agenda.

      Well, it's a good thing that in Paul Graham's case, Spamhaus was only blacklisting the one IP address used by the spammer. Excellent. So there's no problem, right? :-)

  43. spam blacklist blackmail? by matt+me · · Score: 2, Insightful

    Blacklisting is clearly just opening more oppurtunies for cyber-crime: spammers threatening to get companies blacklisted by major ISPs unless they pay up. Sending a few emails from fake addresses to the right places is a lot easier than organising DoS attacks from BotNets.

    Loss of email hurts more too.

    1. Re:spam blacklist blackmail? by Anonymous Coward · · Score: 0

      The nice thing is, this isn't possible. The way (good) blacklists work is by having secret "spam catch" or "spam trap" addresses.

      Also, do you think the experts in this get fooled by "fake addresses"? Doubt it or president@whitehouse.gov would be blacklisted all over*.

      NB

      * yeah, it may be, but for OTHER reasons! ;)p

  44. Best by bahwi · · Score: 1

    The best would be to make a new RBL that added headers to each email when a site is known to be using an RBL.

    SPF is the way of the future, blacklists have no place and should be actively discouraged. Until SPF is in full deployment, or even after, TMDA works great too, and is the wave of today. RBL's are old, outdated, too high on themselves, etc.... Time to move on to the next solution.

    1. Re:Best by taustin · · Score: 1

      More spam is SPF compliant than is legitimate email. Even the guy who created SPF says it won't stop spam.

  45. Re:Language by Anonymous Coward · · Score: 0

    Yes. Stop calling them blacklists. They're African American lists. :-)

  46. "Power-hungry weenies" by slavemowgli · · Score: 5, Interesting

    Interestingly enough, the owner of the acme.com domain who was recently featured in a story due to his getting more than a million spam mails (well, attempts to send spam) a day, agrees:

    DNS-RBLs - Domain Name System Realtime Black Lists. In theory the idea is fine. You have a set of sites that you blacklist, and you want to let other folks use the same list so you distribute it using DNS, which is a nice efficient de-centralized database. What's not to like?

    Well, I don't know why, but in practice every single DNS-RBL eventually comes under the control of power-hungry weenies. They start listing sites unreliably, and if you complain you find yourself listed. And there's usually no way to get off the list.

    A lot of people tell me I'm wrong about this. They say that certain DNS-RBLs are ok, with objective criteria for inclusion and simple procedures for getting off the list. The thing is, they give conflicting recommendations for which lists are good and which are bad. Some of these folks recommend lists which I know from personal experience are bad.

    This problem is really inherent in the way DNS-RBLs are set up. You cede control of your mail system to a third party, with no real possibility of checking how they are doing. The people running the lists get overwhelmed with bogus feedback from spammers and/or idiots, to the point where they assume all their mail about the lists is from spammers and/or idiots.

    If the lists you use have not yet descended into corruption and chaos, consider yourself temporarily lucky.

    Do not use DNS-RBLs.

    (from http://www.acme.com/mail_filtering/shame_frameset. html)

    --
    quidquid latine dictum sit altum videtur.
    1. Re:"Power-hungry weenies" by argent · · Score: 1

      Jef's a great guy, but he's not always right. For example, he also says "don't use qmail because it always bounces after receipt". I use qmail, and yet I somehow manage to handle bounces in the initial handshake.

    2. Re:"Power-hungry weenies" by slavemowgli · · Score: 2, Insightful

      He may be referring to an older qmail version - I assume that he made the observation when he evaluated different MTAs and then didn't bother checking newer versions after he decided on one.

      That being said, I think his comments about blacklists pretty much hit the nail on the head. Think about it: what you're ultimately doing is give some complete stranger near-complete control over what email is or isn't accepted by your system. Blacklists are something that might seem like a good idea in theory, but when you really think about them, they're not anymore. There's just too many ways they can be subverted in one way or another.

      --
      quidquid latine dictum sit altum videtur.
    3. Re:"Power-hungry weenies" by argent · · Score: 1

      He may be referring to an older qmail version

      No, the behaviour he's referring to would occur if one applied filters late in the chain. The thing is, he assumes that you HAVE to apply filters late in the chain. It's a common misunderstanding about qmail.

      Think about it: what you're ultimately doing is give some complete stranger near-complete control over what email is or isn't accepted by your system.

      I'm already doing that. I'm trusting my registrar, I'm trusting my ISP, and I'm trusting the people running my secondary DNS, and I'm trusting the people "near" me on the Internet.

      Blacklists are something that might seem like a good idea in theory

      Blacklists are something that is absolutely essential in practice. Without blacklists I wouldn't be able to run a mailserver at all.

    4. Re:"Power-hungry weenies" by Anonymous Coward · · Score: 0

      What a load of BS, the DNS-RBLs we use do the majority of the spam blocking load and produce the fewest false positives.

      This is like saying, "yeah, I had bad fish once and will never eat fish again because all fish is bad".

      When Jef states "A lot of people tell me I'm wrong about this" he should figure out there's a good reason a lot of people tell him he's wrong!

    5. Re:"Power-hungry weenies" by Smallpond · · Score: 1

      So I guess you wrote your own mail program? You wouldn't want to give Eric Allman control over your mail.

  47. Exactly by autopr0n · · Score: 1

    It's not so easy for people to "get a new ISP" on both sides of the blacklist. Blackhole proponents act like there totaly optional when there not. If your ISP decides to use a blackhole, there's really nothing you can do. You miss important email that you would have chosen to recive if you could have. But you can't, because some BOFH with a stick up his ass decided that fighting spam was more important then people talking to eachother.

    As long as the individual user makes the choice on the client side, it's great. When it gets to be the admin making choices for the users, it's not.

    --
    autopr0n is like, down and stuff.
    1. Re:Exactly by MikeBabcock · · Score: 1

      When an ISP is receiving and storing terabytes of E-mail a day of SPAM and wasting their resources doing so when almost none of their users want it, automatically blocking those messages and adding a statement to that effect to their SLA is perfectly legit.

      Get over yourself.

      --
      - Michael T. Babcock (Yes, I blog)
    2. Re:Exactly by Anonymous+Brave+Guy · · Score: 1
      When an ISP is receiving and storing terabytes of E-mail a day of SPAM and wasting their resources doing so when almost none of their users want it, automatically blocking those messages and adding a statement to that effect to their SLA is perfectly legit.

      As long as it's clearly advertised up-front, perhaps. If I found that my ISP, which has given me no such notification, had blocked even one mail from my inbox without my consent, I'd be gone within minutes. I've seen too many places hit by RBL idiocy, and I choose to do all filtering locally, thanks.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    3. Re:Exactly by jellisky · · Score: 1

      Collateral damage, though, to many email users isn't worth it. The only reason that mine got through to my sister was the simple fact that I have access to a large number of email addresses.

      What happens if I only used yahoo.com, for example? Am I supposed to just sign up for another free email address just to send that one important email? And what if that one is blocked, too?

      Blacklists are a terrible idea as soon as they prevent innocent users from communicating in an easy way. If it takes me four-plus different accounts just to send an email to someone, well... you can finish that thought.

      Blacklists are not a great idea for stopping SPAM.

      After all, it's not like I'm talking about joeblow.cn here... I'm talking about yahoo.com... mac.com... domains which have millions of legitimate and innocent users. Punishing everyone for a couple of abusive losers is draconian and stupid.

      -Jellisky

    4. Re:Exactly by DavidTC · · Score: 1
      That's nothing. If my ISP came by my house and beat me senseless with a baseball bat, I'd discontinue the service as soon as I could talk.

      Why we even have basebal bats is beyond me.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  48. Re:Whiskey. Tango. Foxtrot. Over. by Detritus · · Score: 1
    If you sleep with dogs, you get fleas.

    If you hang out with crack dealers, you run a much higher risk of getting arrested or shot. Collateral damage is a fact of life.

    --
    Mea navis aericumbens anguillis abundat
  49. Gosh darn terrorists by RickPartin · · Score: 2, Insightful

    From the article:
    This is, strictly speaking, terrorism: harming innocent people as a way to pressure some central authority into doing what you want.

    Can we please stop throwing the word terrorism into every sentence? Please? No? Damn.

    1. Re:Gosh darn terrorists by n0rm · · Score: 1

      But why, don't you know everybody who does something bad is a terrorist now?

      Terrorism: random violence against civilians.

    2. Re:Gosh darn terrorists by Anonymous Coward · · Score: 0
      From the article:
      This is, strictly speaking, terrorism: harming innocent people as a way to pressure some central authority into doing what you want.

      Can we please stop throwing the word terrorism into every sentence? Please? No? Damn.

      How dare you question my use of that word?! Doing so makes you a terrorist!!!!

      Gaul Praham

  50. Get real. by bananasfalklands · · Score: 1
    If your buying on the cheapest isp connectivity then jolly good for you.

    But I, and my company have no quams with blocklists. Yes I also block Korea, and China

    Any **sane** email admin person will know that some isps just love the money - I do not yet love spam.

    Blocklists work for the cluefull. When you isp responds to spam compliants then I will accept you email - if everybody else gets the idea to locally block (even worse than a bl), or use a blocklist then that is not our fault. We block, the bl only provides a list, which i could (should i want to want to white list)

    We are based in europe. American law (can-spam) does not apply so do not think that list you bought is to american citizens only. So dont believe your list (spammer) provider. If i really do have a desire for Viagra - im really sure that i can get it, and no you do not you have to spam me.

    So that email address list that you bought this year but was harvested from 1997 does not exist is that my problem no. its yours. If your isp is too greedy and feel that it is ok to ignore my spam reports why is that not an issue to us?.

    When your isp considers the report then I might change but until say chinanet do not give a stuff except for the money do yourseleves a favour Change isps end of matter.

    --
    Send Peter Clifford Francis Macrae comdoms to 23 Bedford St, St.Neots, PE19 1AX, England
  51. I remember you used to pretend to have a clue... by Anonymous Coward · · Score: 0

    If your IP address is dynamic, you have no business talking to other networks' port 25. Set define(`SMART_HOST', `smtp.earthlink.net') and shut up.

  52. Graham ignores the problem, becomes part of it. by RonVNX · · Score: 1

    His time would be far better spent asking Yahoo why they're so steadfastly blackhat about the spam that comes off their network. Graham here is functioning as an apologist for spam, and the fact that he chooses to use a blackhat provider. Shame on him.

    As for SBL, he's mistaken. It has long had a policy that allows the listing of corporate mailservers of spammers. If he wants to know their policy, he should talk to Steve Linford the Spamhaus founder, not John Reid.

  53. Re:In soviet russia by Anonymous Coward · · Score: 0

    I swear if Jim Thompson doesn't stop doing this crap, i'm going to be happy. Let him know how happy you are.

    703-382-0299

  54. Terrorists! by StinkiePhish · · Score: 1

    Oh! Oh! He used the "T" word! They must be stopped at all costs.

  55. OK, I'll go first: how is this legal?! by Anonymous+Brave+Guy · · Score: 1
    However, a spammer with false credentials faked his way into a hosting account with my colo provider and as a result, SBL blocked multiple entire submnets, rendering my entire site and service useless for almost an entire month (we deal with auctions, meaning nobody was getting closed notices, won notices, outbid notices, addresses to send payment, registration emails, lost password emails - and when they complained, I couldn't respond to help them and explain it to them).

    What I've never understood is how a human-run operation that blacklists based on human decisions, and which by blacklisting an organisation can interfere with both their business and their reputation, isn't breaking about half a dozen laws that would subject them to more-or-less open-ended damage suits. Can any lawyer reading this please explain why this doesn't count under things like defamation legislation?

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:OK, I'll go first: how is this legal?! by Seumas · · Score: 1

      Because:

      1) They're based in the UK.
      2) They're just "making a list".
      3) Implementing the list to block mail is "voluntary".

      You know - *cough* - It's sort of how it's okay to go around pointing fingers at people and shouting "CHILD MOLESTOR!" - because no matter how much you slander someone, it's up to the individual to believe it and the blame is on that person, not the finger-pointer.

    2. Re:OK, I'll go first: how is this legal?! by Phoenix+Rising · · Score: 1

      Defamation (slander/libel) is only valid if you are knowingly and publically stating false facts. MAPS (and apparently SBL - shame, I used to trust you...) are stating that the addresses they block are involved in some way with spam, and they are, if only indirectly. MAPS has always believed that a sort of Internet Death Penalty was valid against ISPs who refused to own up to their problems, and people who subscribe to MAPS seem to agree.

      And, since the service is voluntary, not necessarily the sole determining factor of spam, and not governmental, there are few if any laws that could apply.

      A spammer once threatened me with unfair business practices because I sent notices to his upstream provider due to repeated spam; he was kicked off the system. My ISP, being an understanding bunch, supported me and backed up my claims when I responded that he was illegally using my system to support his own business practices and was violating his ISP's use policy. And, yes, I was publishing a "blacklist" at the time - a voluntary filter written in Perl, that worked with procmail.

      He backed off - I haven't heard that argument in quite a while now.

      --
      Let us live so that when we come to die, even the undertaker will be sorry -- Mark Twain
    3. Re:OK, I'll go first: how is this legal?! by WarPresident · · Score: 1

      You know - *cough* - It's sort of how it's okay to go around pointing fingers at people and shouting "CHILD MOLESTOR!" - because no matter how much you slander someone, it's up to the individual to believe it and the blame is on that person, not the finger-pointer.

      No, actually people doing that could be sued for making a slanderous defamatory statement about whether a person has committed a crime. At least in the U.S. Does this apply to RBLs? I don't know of any lawsuits that haven't been settled out of court.

      --
      Here come da fudge!
    4. Re:OK, I'll go first: how is this legal?! by Otter · · Score: 2, Funny
      1) They're based in the UK.

      That makes a defamation / slander / libel suit much easier, not harder.

    5. Re:OK, I'll go first: how is this legal?! by Pig+Hogger · · Score: 1
      What I've never understood is how a human-run operation that blacklists based on human decisions, and which by blacklisting an organisation can interfere with both their business and their reputation, isn't breaking about half a dozen laws that would subject them to more-or-less open-ended damage suits. Can any lawyer reading this please explain why this doesn't count under things like defamation legislation?
      Truth is an absolute defense against defamitory statements. But, of course, a spammer with deep-pockets can expensively harass a blocklist operator into oblivion, so this is why more serious blocklists are safely located well outside of the reach of US law, like SPEWS, which is located in Siberia.

      Isn't it ironic that, in order to preserve one's free speech, one has to move to the old archvillain Soviet-Union???

    6. Re:OK, I'll go first: how is this legal?! by aramael · · Score: 1

      ... and when somebody cries "child molestor", you can always reply "bad speller"; this invariably puts them back in their place. People have been making lists since before The Mikado; if that's illegal then so is being human. But personally, being on a list -- good or bad -- makes me fret.

      --
      Be true and faithful like your dog; but don't eat vomit like your dog
    7. Re:OK, I'll go first: how is this legal?! by jbolden · · Score: 1

      Because the criteria used to make the list is public. Saying person X did one of things A,B,C...L isn't slander if he did thing D.

    8. Re:OK, I'll go first: how is this legal?! by drwho · · Score: 1

      Amazing that they can still operate in the Gulag.

      Though SPEWS may be out of reach, those that contribute to it may not be. Those that use it may not be.

      SPEWS is either vindictice slander/libel, or is poorly run, or both.

    9. Re:OK, I'll go first: how is this legal?! by Fulcrum+of+Evil · · Score: 1

      Truth is an absolute defense against defamitory statements.

      Not in the UK.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    10. Re:OK, I'll go first: how is this legal?! by Otter · · Score: 1
      I appreciate the moderation, but -- "Funny"?

      The UK has particularly low thresholds for libel and slander claims. If one wished to sue a blacklister, the UK is definitely the place to do it.

    11. Re:OK, I'll go first: how is this legal?! by Anonymous+Brave+Guy · · Score: 1
      Defamation (slander/libel) is only valid if you are knowingly and publically stating false facts. MAPS (and apparently SBL - shame, I used to trust you...) are stating that the addresses they block are involved in some way with spam, and they are, if only indirectly. MAPS has always believed that a sort of Internet Death Penalty was valid against ISPs who refused to own up to their problems, and people who subscribe to MAPS seem to agree.

      Leaving aside that what you say about defamation may not be true in all jurisdictions, we normally call a process that uses large numbers of machines to affect the ability of a system to communicate a denial of service attack, and there are laws against that sort of thing.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    12. Re:OK, I'll go first: how is this legal?! by Pig+Hogger · · Score: 1

      What part of "MY NETWORK, MY RULES" don't you get?

    13. Re:OK, I'll go first: how is this legal?! by Phoenix+Rising · · Score: 1

      You miss the distinction; individual ISPs and businesses choose to use blacklists; the publisher is not doing a DDoS, but rather each ISP is choosing to accept advice from that blacklist.

      If the ISP uses SpamAssassin, the blacklist is only part of a score used to determine spam-ness. If the ISP works like AOL or Yahoo, the blacklisted mail goes into a junk box for further user-based processing.

      At a minimum, the Betamax argument applies; it has a substantial non-illegal use, and so is legal. But more generally, it isn't a denial of service to refuse to accept e-mail - that is the receiver's perogative, as e-mail is a service just like Telnet; the computer's owner has every right to deny access to his own systems.

      --
      Let us live so that when we come to die, even the undertaker will be sorry -- Mark Twain
  56. What a clusterfuck by maynard · · Score: 3, Interesting

    blocking spammers via a central database just doesn't work. The spammers are constantly moving from zombie client to zombie client in huge waves of hundreds of thousands of infected systems, making the RBL always filled with obsolete and incorrect information. The problem - as everyone knows - is that the protocol is fundamentally broken. It's a tragedy of the commons played out in front of our eyes.

    By allowing the abuse it's outcome becomes a certainty. We're going to have to bite the bullet and dump open SMTP. And I think we're going to have to do this quickly. The levels of SPAM continue to rise. I often see ten to twenty times as many spam connections on my mail servers than legitimate connections, and this is a constant, flowing, amount of SPAM 24/7. Even with RBLs, spamassassin, etc, SPAM still gets through. The solution will not be found with another bandaid. It's time to dump SMTP and move to something that demands cryptographic authentication for users and hosts before allowing the transport session to complete. --M

    1. Re:What a clusterfuck by mabu · · Score: 1

      blocking spammers via a central database just doesn't work.

      If sure as hell does work!

      Jun 6 00:00:00, 12099
      Jun 7 00:00:00, 12747
      Jun 8 00:00:00, 12980
      Jun 9 00:00:00, 11971
      Jun 10 00:00:00, 11942
      Jun 11 00:00:00, 11251
      Jun 12 00:00:00, 10502
      Jun 13 00:00:01, 10528
      Jun 14 00:00:00, 10404
      Jun 15 00:00:00, 11037

      In the last ten days, on one of my smaller mail servers, my own homebrew relay blacklist stopped 115,461 spams. This is before I run checks against spamcop and other systems.

      In the past six months, I've had THREE false positives. That's it.

      You don't know what you're talking about. RBLs work. I have years of stats and many happy clients because of it, and I've saved tens of thousands of dollars in bandwidth and resources by using RBLs.

      DUL IP space, cable users, DSL and the like should be wholesale RBL'd. If you disagree, that's probably because you enjoy hanging a linux box off your cable connection, but you're stuck among a zillion zombied PCs and using an irresponsible ISP who isn't controlling unauthorized activity on their network. That's not my problem. You have work-arounds you can do using proxies. I see nothing wrong with blocking huge IP space and then whitelisting individual legitimate relays. It's the way to do it and it WORKS!

  57. Author of parent article is really confused. by argent · · Score: 1

    RBLs don't have anything to do with "adding headers to email".

    SPF is irrelevant to spam. More than half of the SPF records in use belong to spammers.

  58. Re:Wholehearted Agreement by Anonymous Coward · · Score: 0

    Dealing with zombies on dynamic IP blocks by using RBL's is liks shooting gnats with an elephant gun. There are better tools for the job that will do a lot less damage if they misfire. You seem to recognize this, so I'll ask--why do you have/use RBL's at all?

    For instance, reject mail from any sender that's not reverse DNS'able. Quick. Easy. Will get all the dynamic IP's without hitting anyone who's hosting a legit mail server (unless they're running a legit mail server without a PTR record, but frankly most people would view that as a bad configuration anyways).

    If you need more than this, look into greylisting. If you're more progressive, look into SPF records.

    Can someone please describe a situation where either using an outside or "in house" RBL is preferable to just using some common sense in your MTA configuration?

  59. Re:I remember you used to pretend to have a clue.. by Anonymous Coward · · Score: 0

    Why is that?

  60. 'Terrorism' my behind... MAPS' side of the story by mi · · Score: 2, Informative
    Although MAPS did, indeed, only blacklist the actual spammers at the beginning, they changed not because they 'got carried away' (Paul Graham's words), but because the spammers adapted.

    Here is the link, that responsible editors would've offered in a story like this...

    --
    In Soviet Washington the swamp drains you.
  61. So what by Vainglorious+Coward · · Score: 4, Insightful

    I reserve the right to block (or accept) any mail I choose on my own system. I also make that decision on behalf of my users, weighing the pros and cons, and especially the listing policies, of any RBLs. If I get it wrong, then yes, my users won't be happy. I'm all for doing what makes my users happy. Blocklists do make my users happy. They work. The fact that there's sqealing about the effect shows that they work. I reject utterly the contention that I should somehow be forced to accept anything I don't want to receive

    --
    My next sig will be ready soon, but subscribers can beat the rush
    1. Re:So what by Wolfkin · · Score: 1

      What? The fact that there are complaints about the harmful effects of X means that X works?

      Are you reading what you're writing?

      --
      Property law should use #'EQ, not #'EQUAL.
    2. Re:So what by Vainglorious+Coward · · Score: 1
      The people who are sqealing are not my users. In fact, my users are *delighted* at how effective my overall spam-prevention works (and of course, RBLs are but one element of that).

      You have to read my post with your eyes closed to get your meaning from it.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    3. Re:So what by drwho · · Score: 1

      Yeah, well I hope none of them pay you for email, because if I did and you were causing my email to be dropped, I'd cancel service. And if your rash and careless action had caused me to lose money because of dropped business mail, I'd sue you.

      But hey, if it's just email for you and your friends, then go for it. Because I am probably not going to be sending you email anyhow.

    4. Re:So what by nacturation · · Score: 1

      Yeah, well I hope none of them pay you for email, because if I did and you were causing my email to be dropped, I'd cancel service. And if your rash and careless action had caused me to lose money because of dropped business mail, I'd sue you.

      If you were careless enough to not do your homework and sign up with a provider that implements filtering and then you try to sue but you can't because the license agreement you accepted requires you to waive the right to any action, then you deserve to lose a few emails.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    5. Re:So what by nacturation · · Score: 1

      What? The fact that there are complaints about the harmful effects of X means that X works?

      Maybe English isn't your native language, but the full expression is to "squeal with delight", not "squeal in anger" or something.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    6. Re:So what by justin12345 · · Score: 1

      I really wonder how well such an agreement would protect anyone anymore. Don't you just have to convince a jury that the agreement is 51% unfair? IANAL BTW.

      --
      Cool art gallery, if you're into that sort of thing.
    7. Re:So what by Vainglorious+Coward · · Score: 1

      Actually, I *do* get paid. And typically, I specifically get paid to implement a range of measures, of which RBLs are just a piece. I explain the pros and cons to the client; I explain the listing policies of the RBLs I recommend, and the listing policies of those I do not recommend. And I also track how policies change over time (eg it's been some time now since I stopped recommending Spamcop). Sometimes, the client decides not to use RBLs. Most *do* use them to some extent (often weighted in with a number of other measures), simply because RBLs are currently very effective.

      Your chest-beating about suing over dropped mail is so naive it's touching. Have you ever even read the contract you've entered into with your ISP? Good luck getting a clause in there that guarantees email delivery.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    8. Re:So what by alexo · · Score: 1


      > I explain the pros and cons to the client; I explain the listing policies
      > of the RBLs I recommend, and the listing policies of those I do not
      > recommend. And I also track how policies change over time


      Since you are obviously very familiar with the subject, why won't you share your expertise with your fellow slashdotters and tell us what RBLs are currently recommended and which of them cause the least amount of collateral dammage?

    9. Re:So what by Chris+Burke · · Score: 3, Insightful

      I reject utterly the contention that I should somehow be forced to accept anything I don't want to receive

      And that means that you will readily accept someone else's decision on what you should and should not receive? You sound to individualistic for that, so I think you are probably missing the implications of these blacklists.

      What if you want to receive email from someone, but their block is in the blacklist your ISP uses? Can you call up your ISP and ask them to remove it? Can you get your friend to change their ISP so they are in a non-blacklisted block? In the past, I've seen people whose ISPs would block, for example, the entire University of Michigan. That made it pretty tough to communicate with them.

      You are absolutely under no obligation to accept anything. That's why I run a spam filter myself. But letting someone else's often arbitrary judgement control what you do and don't receive is contrary to the personal control that you (and I) want.

      Speaking of which, I'm glad I'm not one of your users.

      --

      The enemies of Democracy are
    10. Re:So what by Chris+Burke · · Score: 2, Insightful

      The fact that there's sqealing about the effect shows that they work.

      Um, no.

      The fact that there's squealing about the effect from non-spammers shows that they don't work.

      --

      The enemies of Democracy are
    11. Re:So what by Vainglorious+Coward · · Score: 1

      If the collateral damage caused by RBLs were not insignificant compared to the benefit they provide, then they wouldn't be so widely used. They're not perfect, of course. But they are indisputably the single most effective tool we have today.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    12. Re:So what by fmaxwell · · Score: 1

      Yeah, well I hope none of them pay you for email, because if I did and you were causing my email to be dropped, I'd cancel service.

      If you are that upset about not getting your ads for penis enlargement pills, viagra, and baldness cures, you're free to find another e-mail provider. But, if missing that kind of e-mail is a big concern, you've got problems far more serious than who provides your e-mail.

      And if your rash and careless action had caused me to lose money because of dropped business mail, I'd sue you.

      It's not "rash" or "careless" to employ blacklists. It's meeting consumer and business demand for e-mail services which block large amounts of spam -- even if that means the occasional, rare, blocked piece of non-spam. And it's normal within the ISP industry. AOL, MSN, Earthlink, etc. all employ spam filtering. Many, like pobox.com, advertise it as a primary feature of their service.

      Most businesses recognize that spam costs them money. It costs them money for bandwidth. It costs them money when their employees click on the link to buy V*1*A*g*R*A or see the h0t.C0EDZ. It can cost them a heap of money if an employee sues, claiming that the incoming pornographic spam made for a "hostile work environment" and that the company was negligent because it did not employ effective anti-spam techniques.

      If you need absolutely unfiltered e-mail because your "clients" send you e-mail through shady ISPs, open relays, and zombie residential PCs, then you're the one being rash and careless if you don't choose an ISP that specifically promises completely unfiltered e-mail. Of course, if you were running a real business, you would probably have your own e-mail server which you could run as you choose.

    13. Re:So what by Vainglorious+Coward · · Score: 1

      Speaking of which, I'm glad I'm not one of your users.

      I was going to respond that the feeling is mutual, but actually, that would be overstating my concern. Truth is, the only way you're likely to be a user on one of my systems is as an employee, in which case the question of whether you have any choice is moot.

      What's way waaaay more critical than whether a system is using RBLs (or indeed any specific anti-spam technique), is whether you have a postmaster who is clueful. Someone who is responsive to what's happening on their system, both in terms of supporting their own users, and in dealing with external postmasters. I'm not going to pretend that I've never had to add a particular IP to my accept lists, if even only temporarily. There have been cases where, *gasp* yes, I had to speak to people on the telephone to resolve a particular situation. But those few cases are dwarfed by the enormous benefit and resource-saving RBLs provide.

      And the answer to the question you're pondering, but would never ask unprompted, is "no, of course not".

      --
      My next sig will be ready soon, but subscribers can beat the rush
    14. Re:So what by ady1 · · Score: 1

      isn't it better that instead of deleting or boucing back emails; just add something like "possible spam" to the subject of the email and let it go to intended destination. the ISP has done its part now its user's choice. he/she can configure a rule which checks if the subject contains "possible spam" and configure it be deleted/moved to folder etc

    15. Re:So what by majikenny · · Score: 1

      I've most of my friends have had the same problem, from big places like Purdue to tiny little colleges all over. oh yeah, i almost forgot. ANN ARBOR'S A WHORE!!!!!

      --
      No bastard ever won a war by dieing for his country. He won it by making the other poor, dumb, bastard die for his.
    16. Re:So what by Anonymous Coward · · Score: 0
      You are absolutely under no obligation to accept anything. That's why I run a spam filter myself. But letting someone else's often arbitrary judgement control what you do and don't receive is contrary to the personal control that you (and I) want.


      Then dont use a blocklist. But just as you have every right to decide what you will or will not accept, so does anyone else. And they have every right to choose to take the presence (or absence) of a potential sender's IP address on a blacklist into account when making that decision.
    17. Re:So what by Chris+Burke · · Score: 1

      Then dont use a blocklist.

      It's about ISPs who use blocklists. Pay attention.

      --

      The enemies of Democracy are
    18. Re:So what by Chris+Burke · · Score: 1

      in which case the question of whether you have any choice is moot.

      Sure, just like I have no choice in whether I have to change my Windows password every three months. That doesn't make it cool.

      But those few cases are dwarfed by the enormous benefit and resource-saving RBLs provide.

      Okay, but I question how you can actually know how much the RBL is costing you. If an employee sends an email asking for product information from Companies A, B, C, and D, but only gets answers from C and D, is he going to call you up assuming there's a problem or is he going to assume A and B aren't interested? The fact that only people sending email to your users are affected, rather than your users being unable to send email, makes this a more difficult determination. Because you've only had to pick up a telephone occasionally doesn't mean that's the only cost.

      Clueful admins are of course the most important thing. But I've had clueful admins tell me the opposite of what you are saying, but I still get essentially zero spam. If clueful admins are the most important thing, and I have a choice in the matter, I'll take the clueful admin with no RBL, thanks.

      And the answer to the question you're pondering, but would never ask unprompted, is "no, of course not".

      I was in fact wondering whether you had a pair of hamsters in your shorts, but now I know. :) But seriously, I have no clue what you think I'm pondering.

      --

      The enemies of Democracy are
    19. Re:So what by Vainglorious+Coward · · Score: 2, Interesting

      Okay, but I question how you can actually know how much the RBL is costing you.

      Millions and millions of rejected messages versus the occasional manual intervention. It's a pretty easy judgement. I can even figure an average spam message size, multiply by the number received, compare that to my ham traffic, weight it against the cost of running my mail service and produce a dollars and cents figure of what RBLs save me (and that's before I factor in the costs associated with users having to deal with those spams if they were delivered). If I'm rejecting two thirds of all delivery attempts at the front door, I don't need to have mail systems that are three times the size and three times the cost.

      If an employee sends an email asking for product information from Companies A, B, C, and D, but only gets answers from C and D, is he going to call you up assuming there's a problem or is he going to assume A and B aren't interested?

      You seem to be conflating the case where I am using RBLs and the case where someone else is. If my employee attempts to send an email to a system that has us on their blocklist, my employee gets a non-delivery report from my system, advising him that the message was not delivered, including a transcript of the SMTP dialogue ("552 We don't like people with a "K" in their name"). Typically, he would then contact me and ask what was up, and I then deal with it in whatever way is appropriate. In the case where somebody elses employee tries to send to us, and we reject because of a RBL listing, that remote person gets a non-delivery report from their own system, and it is for the remote admin to deal with it as appropriate. I can only take responsibility for my own systems, I can't be postmaster for everybody else.

      Shorts are no place for a hamster.

      --
      My next sig will be ready soon, but subscribers can beat the rush
    20. Re:So what by Medievalist · · Score: 1
      I still get essentially zero spam
      You just admitted your viewpoint is too limited to comprehend the issue.

      I use blacklists (most of which I built and maintain myself, although I also use the ORDB) to turn away over 5000 spams and viruses daily. You seem to think I have an obligation to accept them. I don't have any such obligation; and I'm perfectly willing to throw away messages from Yama Dharma himself if his lordship is using a spam-friendly ISP. Only commercial pressure will force the ISPs to act, only disgruntled users can provide commercial pressure on the ISPs. That's *my* choice, to be part of the free market, and help the good ISPs prosper while the spam-friendly ISPs die from dissatisfied customers. I prefer this method to heavy-handed government intervention, which doesn't cross international borders and always contains exemptions for the rich and powerful.

      Incidentally, I don't block gmail.com nor do I block email to the postmaster and abuse addresses, so if anyone complains politely I give them a gmail invite.
    21. Re:So what by nacturation · · Score: 1

      I really wonder how well such an agreement would protect anyone anymore. Don't you just have to convince a jury that the agreement is 51% unfair? IANAL BTW.

      In a free market (non-monopoly) you are able to choose any provider you wish for your email service. If you choose one and agree to the terms provided in the service agreement, it is by its very nature a fair deal barring any terms and conditions which are unlawful. If you had no choice in providers, or if all providers implemented spam blocking uniformly, then you could perhaps argue that it's unfair.

      On the other hand, why would someone sue over this? If someone feels their provider is being unfair, switch providers. There are quite literally thousands and thousands of companies willing to provide email services with varying levels of spam and virus blocking, from none at all to very aggressive. Or someone could pick up a book, buy a computer, and get a raw internet feed and learn to do it themselves.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    22. Re:So what by justin12345 · · Score: 1

      Well my understanding is that you can sue anyone, for any reason, for any amount, unless specifically prohibited by law (this is what my bother-in-law told me). TOS and other contracts often wind up unenforceable (another thing he told me) in civil cases.

      --
      Cool art gallery, if you're into that sort of thing.
    23. Re:So what by nacturation · · Score: 1

      True, you can sue anyone, anytime, for just about any reason. Going through the paperwork is the easy part. Showing up in front of a reasonable judge and demonstrating the merits of your case is another matter.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    24. Re:So what by Chris+Burke · · Score: 1

      I still get essentially zero spam

      You just admitted your viewpoint is too limited to comprehend the issue.


      Um, no, I don't think I made myself clear. I, the email user, receive essentially zero spam because of the efforts of my mail server admins. 5000 spams and viruses a day is a pathetically tiny amount compared to what hits our mail servers. The point is that spam gets filtered out without needing blacklists. In other words, maybe blacklists are great, but they clearly aren't necessary to give me, the user, a life almost completely free of spam (and the tiny amount that gets through mozilla filtering has already learned to deal with easily so it doesn't clutter my inbox).

      Hope I've done a better job of explaining.

      --

      The enemies of Democracy are
    25. Re:So what by drwho · · Score: 1

      You don't get what I am saying: Yes, spam filtering is good. Even blacklists can work. But these systems that spread blacklists are not. They're open to abuse and error, and the results are disasterous.

      Here's something else: blacklist can be abused as a form of censorship: don't like what people are saying on a mailing list? Just add them to SPEWS! Good thing it wouldn't be very effective, because most sysadmins don't use spews.

    26. Re:So what by fmaxwell · · Score: 1

      You don't get what I am saying: Yes, spam filtering is good. Even blacklists can work. But these systems that spread blacklists are not. They're open to abuse and error, and the results are disasterous.

      Okay, I think that I get it better now. What you are arguing against is blacklists that list an entire block of addresses when one IP in the range sends spam. Is that right?

      Assuming that's the case, here are my thoughts on that:

      The blacklist should give the ISP a chance to resolve the problem prior to blacklisting. Only if the ISP is unresponsive should there be an entry into the blacklist.

      Blacklisting large blocks means that ISPs get massive pressure from their non-spamming users to do something about the problem. Some users will take their business elsewhere and others will be vocal about the need to address the problem. Without this kind of pressure, many ISPs would turn a blind eye to outgoing spam. They're getting money from the spammer, it's not affecting their "regular" customers, so they're happy. That's the entire basis behind "pink contracts" -- the ISP gets a higher than normal fee and they ignore complaints about the spammer's operation. And pink contracts are one of the reasons why blacklists sprouted up to block large address blocks.

      The more use there is of IP block blacklisting, the more concerned ISPs will be about outgoing spam.

    27. Re:So what by Pete · · Score: 1
      If an employee sends an email asking for product information from Companies A, B, C, and D, but only gets answers from C and D, is he going to call you up assuming there's a problem or is he going to assume A and B aren't interested?

      For a properly-configured sending mailserver that's had an SMTP connection refused, the person sending the email in question should receive a message back from their mailserver indicating that the email was refused.

      There should be no need for anyone to guess anything.

  62. Sorry... by Iphtashu+Fitz · · Score: 1, Interesting

    But this guy doesn't have a leg to stand on. After only the first few lines of the article I knew he'd been a target of a blacklisting.

    As an admin of a small mailserver hosting a handful of private domains I'm a very happy user of various DNS blacklists. I use some blacklists to reject ALL e-mail from countries like Korea & China due to the constant flood of spam from those countries. I also use other blacklists in conjunction with SpamAssassin to more accurately deal with spam. If you don't like the way I manage my mailserver then tough! I probably don't want e-mail from you anyway. If you have a LEGITIMATE problem with being blacklisted then e-mail me another way (like from gmail, hotmail, etc) and I'll consider whitelisting you. I've also got a few specific mailservers whitelisted exactly because I was asked (nicely!) to do so.

    Bottom line - my server, my rules.

    1. Re:Sorry... by prockcore · · Score: 1


      As an admin of a small mailserver hosting a handful of private domains I'm a very happy user of various DNS blacklists. I use some blacklists to reject ALL e-mail from countries like Korea & China due to the constant flood of spam from those countries.


      Why even run an SMTP server at all then? Just turn off mail.

  63. THe Internet is Fulfiliing its destiny of becoming by Anonymous Coward · · Score: 0

    Totally unusable

  64. IP, not ISP by tmk · · Score: 1

    No, 50 bucks is the fee for an IP, not for an ISP.

  65. That's not how it works. by khasim · · Score: 0
    We've been blacklisted before and the sysadmins who run these things often WILL NOT remove you, no matter what.
    Specifics, please.

    Which lists?

    Was this the first time you were listed or were you listed 3 or more times?
    I'd take all the SPAM anyday vs. not being able to send legitimate emails.
    That isn't the way it works.

    Am I willing to accept all that spam just so you can send email to me?

    The answer is ... no.

    If YOU want to send email without being on the spam lists, there are LOTS of options open to you. Sure, some of them are more expensive than others ... but that's what happens when your ISP subsidises your email account by taking on more lucrative spammers.

    This all comes down to money and time. I use blacklists and I like them because they save me time and money.
  66. RBL entries for zombies are correct. by argent · · Score: 1

    The spammers are constantly moving from zombie client to zombie client in huge waves of hundreds of thousands of infected systems, making the RBL always filled with obsolete and incorrect information.

    That doesn't actually matter, because there's virtually no overlap between legitimate mail sources and zombies. Infected desktop or laptop PCs are not also SMTP mail servers: if by chance someone is using a desktop PC as their outgoing SMTP server, AND they're using that same desktop PC for other purposes, AND they are unable to keep it from being infected, then they should be on a blacklist.

    1. Re:RBL entries for zombies are correct. by maynard · · Score: 1

      The point is that it will always be impossible to keep an accurate map of infected vs. uninfected systems when dealing with numbers this large. There will always be inaccuracies within the database, leading to some disenfranchised legitimate email users. While at the same time the SPAMMERS continue on, infecting new hosts with zombie bots and other malware, in order to send out SPAM. That this is a criminal enterprise is no matter. The fact that they can do this and that it remains profitable is enough to confirm that it will happen. The only solution is to transition to a new protocol that enables authentication so that it won't happen. Then we all turn our old sendmail servers off and tell the SPAMMERS to go fuck themselves. Yes, the confusion will hurt for a bit. But the outcome would (IMO) be worth it. --M

    2. Re:RBL entries for zombies are correct. by splint3r · · Score: 1

      Woah woah, you're making the assumption that we all have static IPs. I've never been infected, not once (not running Windows helps;) however since I have a dynamic IP (which is what almost all ISPs give in the UK), I've had to go through the pain of getting my current IP unlisted, or just reconnect and getting another IP.

      And let me tell you, those DSBL guys can be real dicks sometimes. My question of "have you guys started blacklisting all dynamic IPs" was met with the answer "your IP is blacklisted because spam came from it". Thanks guys, you freaking retards ;)

      Admittedly, the overlap between zombie clients and legitimate mail sources is low, but it is no where near non-existent as you claim.

    3. Re:RBL entries for zombies are correct. by argent · · Score: 1

      The point is that it will always be impossible to keep an accurate map of infected vs. uninfected systems when dealing with numbers this large.

      So? You don't need to maintain an accurate map of infected vs. uninfected systems. You just need to keep track of systems that have been infected "recently", for values of "recently" that can be days or even weeks long. Since SBL expires botnet entries in 48 hours they're not contributing to abuse from this cause.

      In fact you've given me a good idea for expanding my current bot tracker.

      The only solution is to transition to a new protocol that enables authentication so that it won't happen.

      The trick is to come up with a scheme that works, that people actually uses, and that doesn't put Microsoft or Verisign or someone similar in charge. Otherwise you wouldn't be able to convince people to turn off their old SMTP servers.

    4. Re:RBL entries for zombies are correct. by argent · · Score: 1

      you're making the assumption that we all have static IPs.

      If you want to send mail, you need a static IP.

      If you have a dynamic IP, then my mail server won't accept mail from you regardless of whether you're part of a botnet or not, because not only is one of the BLs I use simply a list of dynamic IPs, I also explicitly block hosts whose reverse lookup indicates they're in an un-RBLed dynamic IP space.

    5. Re:RBL entries for zombies are correct. by Anonymous Coward · · Score: 0

      And how is DSBL supposed to know that the address is dynamic? There's no obvious way that doesn't involve manual detective work and a judgement call. DSBL has very specific rules that it follows. The goal is that only facts, not human judgement, factor in a listing, in order to avoid exactly the accusation that Paul Graham leveled at Spamhaus.

      The guy who called you a retard was a jerk, but ultimately he got one thing right: it's just not practical to send mail from a dynamic IP address. It's not just the geeks posting here who block mail from dynamic IPs. Lots of companies do, and so does AOL.

  67. what the HELL with paul graham by Anonymous Coward · · Score: 0

    look, if i wanted to read every one of this know it all's essays, i would read them on his website.

    bloody hell, is there NO NEW THINKING in the world? dammit.

    1. Re:what the HELL with paul graham by Anonymous Coward · · Score: 0

      Paul is a well known blow-hard, and a legend (mostly in his own mind). Thank being said, about 1 out of 10 times he comes up with something interesting and good. ...yeah, this rant "cuz I'z bin bloxd" ain't one of them. Slow news day at the Slash?

  68. Blacklists are PART of the solution by ehaggis · · Score: 1

    The SpamHaus RBL / SBL / XBL has been quite reliable for us. However, it is PART of a total solution. Thunderbird spam control and Spamassassin certainly help.

    The greatest ROI was educating users on proper use of email addresses. Keep one address for work only, one address for personal and one for a throw away. The throw away is for registering, posting or whatever may end up in someone else's hand. It is not foolproof, but it helps. Since our users have held to this system, our spam problems have all but been eliminated.

    --
    One ring to bind them - should probably have more fiber and less rings in their diet.
  69. paulgraham.com is blocked by Anonymous Coward · · Score: 1, Interesting

    I agree that the block you listed is a single IP:
    66.163.161.45/32

    Now do a DNS lookup on paulgraham.com: 66.163.161.45

    The problem is that yahoo can host multiple sites on the same IP and the blacklists cant differentiate. The problem is the lack of granularity not, as Mr. Graham writes, an abuse of power by the SBL people

  70. Better solution to your DUL woes. by argent · · Score: 1

    Earthlink reports all of its cable modem customers to DUL because we are forced to use "dynamic" addresses with DHCP.

    So don't use your cable modem as your outgoing mail server. If your outgoing traffic volume is small, you can get a virtual colo with a low traffic cap. for much less than the $15/month your DSL peers are paying and make that your smarthost.

  71. Anonymous accusations by Anonymous Coward · · Score: 0

    What a great piece of shiti journalism. An anonymous e-mail from a potential spammer is all it takes to let this reporter conclude that SBL got corupted.

  72. The market is powerless to stop spam by Cid+Highwind · · Score: 1

    If not, I suggest their customers vote with their wallets, and find a new ISP.

    In the ideal world that free market idealists live in, that would work well. Unfortunately reality is a much harsher place. In most areas, internet access is provided by one or two near-monopolies. Don't like those companies spam policies? Tough. No internet for you.

    Even if there were a true alternative, most broadband providers and hosting companies require long term contracts. If you terminate your account at the first sign they're hosting spammers on your subnet, they still get paid in full. The balance of power in modern coproration-consumer relationships is so tilted in fovor of the corporations that expecting angry customers to have any influence at all on business decisions is totally unreasonable.

    --
    0 1 - just my two bits
  73. I have admined companies like this. by Anonymous Coward · · Score: 1, Interesting

    Posting AC so this does not taint my real-world karma:

    I once worked for a hosting company that hosted spam servers "on the side". As an admin it was a constant battle with the blacklists ... to stay off of them.

    Management never understood this (or rather, they understood it very well, the spammers paid $20X the hosting of regular servers...), indeed, they started a second company just to host the bad servers.

    I was ordered to lie constantly, and to shift IP's around etc, to make it harder for the black lists to get us. IMO, I think that the blacklists should have taken out the WHOLE hosting company.

    While 99% of my customers were legit, and I worked hard to keep spammers off of our "normal" list, I knew that we were hosting spammers on purpose. In fact, part of the reason I was let go was that I complained that doing this was immoral, and that it risked our hosting business as a whole.

    So, if they blocked your whole hosting company, I would suspect that the hosting company was playing games like this.

    (As an aside, when I was let go from that job I was estatic. Indeed my co-workers wished that they could be "let go" too. In the end, the turnover at that company was about 120% a year...)

    1. Re:I have admined companies like this. by Seumas · · Score: 1

      You are speaking of a different situation. Blocking a network that is repeatedly found to be spam-friendly is completely different than blocking an entire network based on one single complaint, one time about that company.

      I'm all for blasting chornic offenders, even if it takes out some innocents. But there needs to be some occasional leeway because even the best of hosts will wind up victims of a creative spammer every few years.

    2. Re:I have admined companies like this. by Anonymous Coward · · Score: 0

      You are speaking of a different situation. Blocking a network that is repeatedly found to be spam-friendly is completely different than blocking an entire network based on one single complaint, one time about that company.

      Good point - however, the juggling I did was such that when a complaint came in, the spam was shifted to a different domain/ip within the hosting company. This way it appeared to go away... Pity that the blacklists (at the time) did not seem to look at the ROUTERS that were serving the netblocks.

      Every time a complaint (from a blacklist) came in, the domain and the IP was juggled to a new section of our network. It would have been difficult to detect on the side of the blacklists - unless they looked at the routers serving the spam.

    3. Re:I have admined companies like this. by DavidTC · · Score: 1
      Well, see, that's where you've fallen for the lies. No fault of yours.

      On every blacklist that lists entire ISPs, that ISP hasn't been responding to spamming complaints for a hell of a long time.

      There is plenty of leeway. You get a spammer, you respond to complaints, you remove them, you never end up on a blacklist.

      Notice it's never the blocked ISP that complains, at least not anymore? It's always some random guy on that ISP. No ISP ever shows up and says 'We were unfairly blocked.'. Not one who's willing to state their name. Think about why that is.

      It's because they know they'd have hundreds of people immediately leaping on them, asking 'Why are you still hosting spammer X?'.

      In fact, they only time they do stand up is to say 'We've gotten rid of all our spammers and are still blocked!!' and the response there is usually 'You had spammers for two years, and removed them last week? Well, a large organization like you must recognize how slow things can be...I'm sure our staff can get around to it in a few months...'.

      No, they just have their customers go out and hassle people. Those customers, I'm sad to say, are collateral damage of the spam war, but not of the spamfighters. They're being held up as human shields.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  74. Maybe Paul Graham should look up "hyperbole" by otter42 · · Score: 2, Insightful

    This is, strictly speaking, terrorism: harming innnocent people as a way to pressure some central authority into doing what you want.

    No. No... No, there's just something not right about that. I'm pretty sure that the definition of terrorism includes the idea of terror somewhere...

    Ahhh. That's more like it: Terrorism: the unlawful use or threatened use of force or violence by a person or an organized group against people or property with the intention of intimidating or coercing societies or governments, often for ideological or political reasons.

    Yeah, violence should induce terror. Not being able to send emails to my girlfriend, as hair-raising an idea as that might be, just doesn't seem to be in the same league.

    And just in case Mr. Graham is too lazy to find a dictionary to look up hyperbole for himself: hyperbole - n : extravagant exaggeration

    --
    www.eissq.com/BandP.html Ball and Plate System. Amuse your friends. Crush your enemies.
    1. Re:Maybe Paul Graham should look up "hyperbole" by legirons · · Score: 1

      "Terrorism: the unlawful use or threatened use of force or violence..."

      So by that definition, why do we need "anti-terrorist" laws? Wouldn't they be circular reasoning or something?

  75. The problem is.... by /dev/trash · · Score: 1

    A) ISPs can't control a spammer who spams for 2 days and then leaves.

    B) ISP uses dynamic IPs, and if that IP was used as a spammer haven for two days then re-allocated to another customer after the spammer leaves, it'll cause problems.

    1. Re:The problem is.... by bananasfalklands · · Score: 1
      Most of our spammers for stocks, drugs, etc are kept by the same isp for several weeks for instance once reputable isp Saavis is a large sewage farm for us.

      Yes Windoze trojans are a problem for isps but if the isp just ignores the reports what should i do - just press the delete key, or unopt to get even more crap.

      If the isp cannot spot a trend, or if they can and then not act upon it why should i not block it? Local blocks are worse then lookups.

      the bl is like game theory - the more reporters or 'collaboration', the harder it is for people to say - 'i did not know about it'

      1 spam report maybe wrong but 1000 reports is hard to disagree with. With known spammers on an isp why I need abosultety no justification. If isp needs a spammers cash - then do they not deserve the block.

      --
      Send Peter Clifford Francis Macrae comdoms to 23 Bedford St, St.Neots, PE19 1AX, England
  76. Which Registrar? by Anonymous Coward · · Score: 0

    Well, if poster works for Network Solutions, it's because NetSol doesn't care if it's services are bad, they charged enough money during the .com bubble to coast on reputation for a few more years.

    If poster works for GoDaddy, it's because the owner is spending too much time on his own vanity, trying to start a cult of personality with his commercials and radio show rather than pay attention to the horrible technical limitations he has imposed on his customers.

    If poster works for Register.com, they don't have enough customers to care.

    Regardless, poster did say low-level management. You think anyone cares what technicians and technical management think? Big companies don't choose solutions based on sound technical advice; they buy the solutions that savvy salesmen present to them.

  77. non-mail server in SBL, what about mail server? by jdunlevy · · Score: 2, Insightful
    From TFA,
    As of this writing, any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam. Why? Because the guys at the SBL want to pressure Yahoo, where paulgraham.com is hosted, to delete the site of a company they believe is spamming.
    E-mail w/ the 'url "paulgraham.com"'? The SBL doesn't check URLs, it'd doesn't even check domain names, it checks IP numbers. paulgraham.com resolves to [66.163.161.45], which is listed in the SBL (details for SBL27945), but since this isn't a mail server, I don't see how e-mail from paulgraham.com gets marked as spam by users of the SBL. I note that the MX record for paulgraham.com is milter1.store.vip.sc5.yahoo.com [216.136.232.238], which is not in the SBL. He never mentions what he uses as his smtp server, but I'm supsecting it either not the SBL -- or it's in for a different reason than he thinks.

    Also, for what it's worth, I've found the SBL incredibly reliable (except recently, when I've found it's been increasingly unreachable at peak times), but I check it as one of many spamassassin rules -- I don't mark e-mail as spam just because it's in the SBL, though the way I have spamassassin score things, it doesn't take much more...

  78. Re:Whiskey. Tango. Foxtrot. Over. by /dev/trash · · Score: 1

    How is renting a car, hanging out with crack dealers????

  79. Great... another blacklist... by Raistlin77 · · Score: 0

    "...and suggests (maybe) another blacklist's creation."

    Great... another blacklist. Hey, let's just keep putting bandaids on top of bandaids on that cut. Eventually the bleeding will stop, won't it?

    1. Re:Great... another blacklist... by splint3r · · Score: 1
      Actually that's not at all the impression I got from that article. Mainly because of the last sentence;

      So if even they are going the way of the MAPS RBL, one has to assume that every blacklist will, eventually.
  80. Re:Vigilante it ain't-- clueless it is by Kazoo+the+Clown · · Score: 1

    It's true that the problem is with ISPs and not with those who create and maintain blacklists. This spam solution however, is contributing to the general unreliability of email. Consequently, I for one, refuse to utilize an ISP unless I can turn OFF the spam filtering for my email accounts. That is how I SELECT an ISP. Otherwise email is just too darn unreliable due to false positive blocking. I maintain my own filtering, so I can address problems with it immediately, and I don't lose emails as I keep a complete log and cache filtered mails for a limited time.

    While not everyone is prepared to take filtering into their own hands, DIY spam filtering may take another turn with the advent of better filtering add-ons to your own email clients. It's more efficient to filter further upstream, but unless ISPs start more generally making upstream custom filtering available to their users the reliability of email will continue to get worse as the spam arms race forces ISPs to institute more and more draconian filtering rules. But they've chosen to take on the problem, and if they're not very good at it users will look for better alternatives.

    IMHO, the problem of SPAM pales to the problem of the unreliability of email produced by errors in filtering. It's true though, I'm not an ISP-- but an ISP who uses filtering to solve it's internal problems at the expense of its users is out of touch with its user base and that presents an opportunity for its competition.

    Like DRM, SPAM filtering as applied by ISPs is not a solution to and end-user problem but a solution to a provider problem. End users are not particularly sympathetic to solutions to problems they don't have that actually cause problems. The customer is always right (many seem to forget that these days), and there's plenty of places to which the customer can walk if they're dissatisfied.

  81. Home Connectivity ISP != Your Domain ISP by billstewart · · Score: 2, Informative

    Maybe you only have three choices of broadband ISP at home, or live somewhere sufficiently rural that there are only three choices of dial ISP - that's entirely irrelevant to how many choices you have on where you get your email, send your email, or host your web servers. Sure, it's convenient to be able to run all those things from your home Linux box, but if you want to do that, you'll probably find that your cable modem company and some of the DSL ISPs that your phone company supports might not permit that. There are hundreds or thousands of companies that run POP/IMAP mailbox services, and probably more that will host web sites, and that's not even getting into options like virtual hosting.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Home Connectivity ISP != Your Domain ISP by Skye16 · · Score: 3, Insightful

      Right. So then, when those of us with a .nu domain name have to change ISPs constantly because, at any moment, someone else - that we have no control over - ruins the ability for our email to go to its intended recipient - we just get to suck up the 10$ a pop IP change for our DNS? And even aside that point - while hosting companies are a dime a dozen, good hosting companies aren't. When we do find one that is, we want to stick with it. It's not their fault someone else at the same colo decided to be a jackass.

      Basically, you're just saying "too bad, I'm tired of being screwed over by spam" and I'm saying "wtf, I'm tired of being screwed over by blacklists that can't keep their shit together". Put yourself in my shoes - when a blacklist service becomes worse than spam and the spammers who spam, what does that tell you about blacklists?

    2. Re:Home Connectivity ISP != Your Domain ISP by Anonymous Coward · · Score: 0

      Jesus Christ! You have to pay $10 to change your IP address??? WTF kind of scam is your registrar running? Get yourself a new registrar!

  82. Stopping spam is easy. by jellomizer · · Score: 2, Funny

    Just block the sub net 0.0.0.0

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Stopping spam is easy. by Anonymous Coward · · Score: 0

      A sub net of which upper net would that be? And yes, you should be blocking 0/8 on outer interfaces.

      What was your point?

  83. The "Dangers"? by Anonymous Coward · · Score: 0

    Woah there, you mean lives at at risk if legit networks get blacklisted? That's up there with copyright infringement being equated to murder and pillaging on the high seas!

  84. Yeah, WTF ... by khasim · · Score: 1
    So...it's okay if he goes to Federal Pound-Him-In-The-Ass penitentiary just because he rented a car from a place that also rented a car to a crack dealer?
    I must have missed the part where he's being anal raped.

    Maybe you or the mod's who mod'ed you up can quote that bit?

    I didn't think so.

    This isn't about going to jail. This is about some people not hearing what he's saying.

    No one's being raped or jailed or tortured. Some of his EMAIL is not getting to the people who asked for it because THEIR admins use the blacklists.

    How about a little perspective?
    1. Re:Yeah, WTF ... by Skye16 · · Score: 1

      I suppose you've never heard of analogies before? Rarely does an analogy contain the exact same quote AND the same context as the initial situation. I hope analogies, in general, make sense to you...

    2. Re:Yeah, WTF ... by Anonymous Coward · · Score: 0

      Apparently you didn't do well on that portion of the SAT I if you believe that's a sensible analogy.

  85. Spammer Record Dated June 10, 2005 by billstewart · · Score: 1

    Last week the spammer was at the address Paul's website is on. Now when I dig for the spammer's IP address, it's somewhere else. Assumin gthe spammer is no longer on Yahoo, Paul needs to get Yahoo to tell SBL they're gone.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  86. What a stupid article. by Pig+Hogger · · Score: 1
    The author of this article is obviously a spammer who got his peepee whacked.
    The problem was, as vigilantes so often do, the guys at MAPS got carried away. They started to include servers on the list that they knew were not sources of spam, to pressure whoever owned the server to do what they wanted. For example, in order to get revenge on people they believed were spamming, MAPS would blacklist the mail server of the company hosting their site.
    When the MAPS guys complained to the hosting company that their client was spamming, they took no action. They let their client spam.

    So, logically, the hoster, by letting it's client spam, is also a spammer, albeit indirectly.

    So, it's only normal and logical that the hoster be also listed by the blacklist!

    The idea of a blocklist is to cut spamming at the source. Very often, hosters will move spammers around, giving them a new IP address when the old one gets blocked. So it's normal that blocklist operators eventually tire of playing whack-a-mole and simply block the whole network.

    When anyone let spammers roam freely on his network, they are spam supporters and deserve to be blocked.

    And spam support need not be only letting spam e-mails out, but it can also be the provision of any kind of internet service to spammers, like DNS, domain registration or hosting of a spamvertized website.

    So, yes, it is only fair to also blacklist ISPs who, even though they don't let spam flow out of their networks, nevertheless provide spammers with valuable services such as domain registration, DNS or web-hosting.

    If no one would provide spammers those vital services, spammers would vanish quickly.

    So, until spammers vanish, rogue ISPs who provide spammer services will be fair-game for blacklists.

    1. Re:What a stupid article. by splint3r · · Score: 1

      Paul Graham is a spammer? Could you tell me exactly which variety and flavour of crack you're smoking?

    2. Re:What a stupid article. by be-fan · · Score: 1

      Paul Graham has a significant number of articles on fighting spam, and has done work on improving Bayesian spam filtering.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:What a stupid article. by Anonymous Coward · · Score: 0

      You're an idiot. Do cops go to your local Ford dealer when a Ford car is used in a bank robbery?

      Do you think little Grandma Smith understand or appreciates why she can't get email from Little Johnny because Johnny's parents use an ISP that is black listed? How exactly should Johnny's parents 'research' potential ISPs? Call up and ask "Excuse me, do you spam or allow spammers?" Of course the ISP tech guy will be like 'Uh, no way..' yet that doesn't stop them from getting on a black list somewhere for some reason. Blacklisting an entire range of IPs (and thus, thousands of customers on smaller ISPs) because someone with a free trial account sent some spam?

      The real problem with these lists is that has been shown, time and time again, how they purposefully abuse their power to blacklist people asking questions or (OMG) complaining simply because they can. THAT is the problem here.

    4. Re:What a stupid article. by Pig+Hogger · · Score: 1
      Paul Graham has a significant number of articles on fighting spam, and has done work on improving Bayesian spam filtering.
      Bayesian filters are a pretty ineffective way of fightting spam. It's just an automatic "delete" button, but you still have to pay for the bandwidth and computer ressource (storage, cpu cycles) your network uses to receive the spam (and worse, to run the bayesian filter and it's database - I know, I used to run one but when each fucking incoming email had to plod through 120 megabytes of database).

      Blacklisting is much more effective, because it stops the spam BEFORE it gets transmitted.

    5. Re:What a stupid article. by be-fan · · Score: 1

      That's not really the point. It's just obvious that Paul Graham is not a spammer.

      --
      A deep unwavering belief is a sure sign you're missing something...
    6. Re:What a stupid article. by Anonymous Coward · · Score: 0
      ...When the MAPS guys complained to the hosting company that their client was spamming, they took no action. They let their client spam. So, logically, the hoster, by letting it's client spam, is also a spammer, albeit indirectly. So, it's only normal and logical that the hoster be also listed by the blacklist!...

      Whats next, sue automakers for making something that can be used to kill people and damage property? Sue tool manufacturers for creating tools that can be used to kill people and damage property?

      Get your head out of the sand.

      NEWSFLASH: Hosters are in business to make money, not cater to RBLs. Its. That. Simple. Don't like it? DON'T USE EMAIL, then you'll cut off the spam problem.

      There is no quick fix to this, but one way would be for ALL ISPs to filter outgoing tcp:25, whitelisting their own SMTPs, and business customers SMTP IPs. THAT'd put a severe dent into the zombie spam senders, the majority from which spam is sent. If all the ISPs could coordinate in this way, the only avenue left for spammers would be to use their own accounts, or hosters networks, thus making it quite easy, and far more reliable for RBLs to do what they were altruistically designed to do, block legitimate spammer server IPs. Don't count on this happening though, greed always wins. Isn't unbridled capitalism just grand?

      And before you idiots flame me for using the word capitalism in a negative way, examine how your american dream (read greed) has eroded your countrys morality, its lack of social conscience (Social Security, unaffordable insurances, lack of business' commitment to its employees), and how american business interests are solely and unequivocally contributing to the downfall of humanity by placing humanities needs far below The Bottom Line.

      Go Greed.

    7. Re:What a stupid article. by Pig+Hogger · · Score: 1

      Well, despite that, he whines like a spanked spammer on NANAE.

    8. Re:What a stupid article. by Anonymous Coward · · Score: 0

      Except that MAPS is well proven to be loons of questionable ethis. Hell, I've been spammed by a MAPS employee, by their definition of spam.

  87. Collective Punishment by edibleplastic · · Score: 2, Insightful

    What you are promoting is the tactic known in the real world as "Collective Punishment". This is the situation where retribution is meted out to anyone in the vicinity of the concerned party (innocent or not) in order to pressure that party to change. In this case, you find it acceptable that innocent users could get hurt (innocent, probably non-tech savvy users who don't know much about other ISPs or SPAM, or anything) just so that you can put pressure on ISPs to change their ways.

    Now here's the fascinating part: you link to the site antiwar.com which has not 1, not 2, but 423 pages decrying the use of collective punishment.

    If that's not hypocrisy, I don't know what is. Sure email's not a life and death situation, but the principle is the same in both cases. Don't like it when innocent people get their homes destroyed? You should hate it when innocent people get their IPs blacklisted.

    1. Re:Collective Punishment by Arker · · Score: 1

      If that's not hypocrisy, I don't know what is.

      Then I guess you don't know what hypocrisy is.

      Sure email's not a life and death situation, but the principle is the same in both cases.

      No it's not. Not at all.

      I don't have a right to drop a bomb on you. I don't have the right to shoot you, or knife you, or torture you. Those things are assaults.

      Refusing your email is not an assault. Refusing your snail-mail, for that matter, would not be an assault. Refusing to take your phone calls, is not an assault.

      You have no right to force me to carry your traffic, period. I do it, by default, in the interest of the common good, but if you abuse that initial goodwill and use it to steal from me, I have every right to stop. And if you abuse people around the world by hosting spammers, and people start refusing to coöperate with you because of this, and your customers get hurt by it - it's YOUR fault. Not the fault of the people whose goodwill you abused and exhausted.

      If you can't see the difference between killing someone, and declining to receive email from someone, then I'm afraid not knowing the meaning of the word 'hypocrisy' is the least of your problems.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  88. Answer by RM6f9 · · Score: 1

    1. Publish your own list.
    2. Get sued for libel ("How dare you list my IP as a SPAMMER?").
    3. Counter-sue, showing proof that your list is honest/truthful/accurate ("Because this SPAM was in fact sent from it on this date at this time!").
    4. PROFIT!!!
    y'all please excuse me, this looks viable...

    --
    Take the 90-Day Challenge! http://rwmurker.bodybyvi.com/
    1. Re:Answer by Cheerio+Boy · · Score: 1

      y'all please excuse me, this looks viable...

      Or you could reverse it and try questionable billing practices like this guy:

      http://www.blars.org/errors/block.html

      The subnet I'm on, my ISP, and my corporate connection at work are all blocked by this guy but I refuse to pay his blood money to get off his list.

      --

      "Bah!" - Dogbert
    2. Re:Answer by RM6f9 · · Score: 1

      Oh, no, won't catch *me* goin' after money I might have to give back... I wish I owned an ISP, so I could sue these list-maintaining, self-elected, intarweb-trolling ogre-resembling wanna-be traffic cop/censors into oblivion.

      Far better, were one to create such a list, to at all times maintain the high ground, even to the point of providing the reason/evidence for listing a given IP to *any* requestor, and provide space for rebuttals - far more work involved, to be certain, but then, quality does occasionally require sacrifice.

      Is somebody with interest listening, or am I gonna have to follow through myself?
      (If the latter, interested volunteer assistants please email me: "I'm more an idea rat" - Ratbert)

      --
      Take the 90-Day Challenge! http://rwmurker.bodybyvi.com/
    3. Re:Answer by taustin · · Score: 1

      Keep in mind, Blars is pretty well known as a raving lunatic. So far as I can tell, the main requirement for him to list you is for him to become aware that you exist.

      I would consider it a blessing to be listed there, as anybody stupid enough to block based on his list is simply too stupid to be allowed to email me.

  89. RBLs *WORK* by mabu · · Score: 1

    The BOTTOM LINE is that RBL's work.

    I swear by them and I've tried every conceivable spam solution and continue to do so. I've been running large scale Internet servers for more than ten years.

    RBLs do one thing that no other solution addresses: They counter the theft of resources by spammers. All other anti-spam solutions require even more resources to stop spam and do very little to curtail spammer's theft of bandwidth. So ironically, ISPs end up spending more money and resources in the process of dealing with the flak from spammers' theft of bandwidth and resources.

    I've had to implement mail servers that are 4-5 times more hefty than my legitimate mail needs, just to maintain base services for my clients. That's bullshit, and that's because spammers steal resources. I'm sure as hell not going to spend even more money to stop spam when it doesn't put a dent in the real issue of spammers wasting bandwidth and network connections. RBLs shut spammers down quickly and keep them from wasting my system resources.

    Spammers hate RBLs more than anything else. It's the one solution that lets them know their crap isn't getting through. Nothing else does.

    Sure, I've ended up on RBLs, but it's not difficult to get removed. In the past, I've gone on rampages when things like this happen, but time has weeded out the irresponsible RBLs and made it easier. Anybody who complains about RBLs probably engages in questionable SMTP traffic on occasion. I've never met anybody who really had a problem with them unless they were violating the TOS of their ISP in the first place. This especially goes for broadband customers who throw up servers in DUL IP space and get their panties in a wad because they realize their homebrew SMTP server, however legitimate, is being RBL'd. Most of those people are violating their ISPs terms of service by doing so, and if they're not and they're caught in an RBL because they're intermixed among IP space held by moron, worm-infected broadband users, it's their ISPs fault, NOT the RBLs.

    You stop spam by:

    1. Enforcing existing laws on the books - almost all spammers are violating the plethora of existing computer tampering and mail abuse laws - problem is they're not being enforced.

    2. Whitelisting SMTP relays. Nobody wants to talk about it, but this is the future. It WILL happen, especially if we move to IPv6, which will create a huge nightmare in terms of tracking spammers. SMTP licensing and whitelisting will work, but it's a four-letter word people don't want to talk about until things get worse.

    3. RBLs are the next-best thing to whitelisting. You blacklist irresponsible IP blocks and refuse to allow SMTP traffic from them. It's the ONLY way to force bad ISPs and administrators to stop polluting the Internet.

    I was around when SMTP relays used to be wide open by default. There was a time when anybody could use anybody's relay, then the spammers came along and ruined it. Shortly thereafter, it was the RBLs that forced admins to close their SMTP servers - everybody hated it, but now it's the accepted practice. RBLs have done more to enforce responsible Internet use than almost any other service. They're here to stay.

    1. Re:RBLs *WORK* by Otto · · Score: 1

      :thumbsup:

      You, sir, are correct, and just got off my foe list for your wonderfully insightful post.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  90. Who's been shot? by khasim · · Score: 1, Insightful
    Let me reword your justification of of this behaviour so others can see the flaw in it more clearly:
    As long as you're up to the task...
    [66.163.161.45 is a filthy neighborhood. Lots of criminals live there. So, a group of vigilantes randomly started machine gunning people walking the street.
    Excuse me, but who's been shot?

    No one?

    Then your analogy is not accurate.

    Certain admins running certain email servers are rejecting/flagging his messages because they come from a "bad neighborhood".

    No one is being shot or physically injured in any way, fashion or form.
    Some days it's hard choosing between deleting 400 spams a day and dealing with the exsistance of "spam blocking" groups. Then I read a comment from an "anti-spam" person and I think I'll be safer choosing to work that delete key.
    And that is a valid option and a valid choice.

    But I'm the admin for a company of about 150 people. 400 messages a day x 150 people = a problem.

    So I use a few blacklists and deny the connections. No one gets shot, no one dies.

    There is always the phone and I do include my phone number in the rejection notice. If a person gets the reject notice, that person can call me or the person s/he was trying to email and I can make a specific exception.

    I've blocked over a million spam messages yet I've only had 4 calls (Bell South is staffed by idiots).

    I have 3 executives here who are 100% behind my anti-spam efforts. You might not mind manually deleting 400 messages a day, but they do.
    1. Re:Who's been shot? by jaydonnell · · Score: 1
      Excuse me, but who's been shot? No one? Then your analogy is not accurate.

      I do not think analogy means, what you think it means ;)
    2. Re:Who's been shot? by pdevor · · Score: 1

      "Excuse me, but who's been shot?

      No one?

      Then your analogy is not accurate."

      Are you retarded? It's an analogy. It's not supposed to be factually similar. It's supposed to be logically similar so as to illustrate a point. Deacon's analogy/em is correct.

    3. Re:Who's been shot? by Pete · · Score: 1
      Are you retarded? khasim was asking who matches up to the "has been shot" concept in the situation deacon was trying to analogise (if that's a word :)) - perhaps he was a bit generous when he thought that'd be inherently obvious from the context. Anyway, no one does.

      And no, deacon's analogy was not factually or logically similar. That's the problem. It's a horrendously bad analogy.

      It'd be (slightly) more appropriate if it was used for a situation where script kiddies were DOSing (making a denial-of-service attack against) IP addresses on a blacklist - then the DOS "attack" would match up to the vigilante machine gun attack (though the implications of a machine gun attack are somewhat different to those of a denial-of-service attack).

      But in the situation deacon was trying to analogise, one group of people had configured their servers to not accept email from a set of IP addresses in a blacklist. They're not interfering with or "attacking" those people using the blacklisted IPs. They're just choosing to not accept email traffic from those IPs.

      Any acceptable "real" world analogy would have to take that factor into account. Most specifically, no worthwhile analogy could involve the blacklist-users using any form of violence against the blacklisted.

    4. Re:Who's been shot? by pdevor · · Score: 1

      I guess the way I saw it was that the people doing the shooting were the network administrators. The logical parallel is that the network admins/shooters are indiscriminately punishing those who happen to be associated through no fault of thier own with those who are committing crimes. I think the main point of deacon's analogy is that it's unfair to respond in a way that harms the innocent bystanders.

      The "who has been shot" are the innocent bystanders--those people who are harmed by being put on a blacklist for something that someone else has done.

      Many analogies illustrate their point through exaggeration. To me at least, it's obvious that deacon is not equating the moral weight of having one's email blacklisted with that of being machine gunned.

      The definition of analogy according to wikipedia:

      "An analogy is a comparison between two different things, in order to highlight some form of similarity. Analogies are often used to explain new or complex concepts by showing the similarity between something familiar and something else."

      When you say "no worthwhile analogy could involve the blacklist-users using any form of violence against the blacklisted," you are wrong because it is the logically *similar* aspects of the analogy that are relevent. As deacon obviously was not making a point about the severity of the damage being done, the fact that he chose violence to illustrate this point is inconsequential. Any negative thing being done to the aformentioned innocent bystanders, violence included, illustrates the point that deacon was trying to make.

  91. Virtual Hosts - Many domains, 1 IP addr, Blacklist by billstewart · · Score: 1
    It's one thing for a blacklist to cover a large block of addresses because of one spammer. But there really is a limit to the granularity of a blacklist - it's checking on a single IP address. One reason that we haven't run out of IPv4 addresses in spite of the Internet explosion of the last decade is virtual host addresses in HTTP 1.1 and SMTP - multiple domain names can use the same IP address, and the web and email servers can sort out which requests are for which names. So it's possible that you can have a conscientious blacklist that's only listing the IP address used by a real spammer, but still affect multiple hosts. The blacklist could do something more complex, like return different codes depending on whether there are known to be multiple domains operating at the address and only one is known to be a spammer, but that's pretty tough (and if it were popular, the spammers would of course want to run multiple domains on the same IP address, including perfectly-innocent-example.com and annoying-spammer.com.)

    So what do you do about it? Not sure there's a good answer, other than the people who get hit with the collateral damage complain to their email/hosting provider to get rid of the spammer, and email recipients who want to avoid collateral damage can do things like use the blacklist as a SpamAssassin weight instead of total blocking, or use the blacklist to drive greylisting (e.g. tell BL'd addresses to come back in an hour, though spammers hosted at real ISPs are more likely to have real SMTP servers that get around greylisting, as opposed to zombies which usually don't.)

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  92. Spam the Blacklists by edibleplastic · · Score: 1

    Don't like blacklists? Start spamming them. Report spam as having come from every ISP you can imagine. Soon the RBLs won't be able to know legitimate sites from sites that actually have sent spam (moreso than at the present moment) and thus will become useless. They'll either start blocking too large a percentage of the net to be useful (people won't subscribe) or they'll have to start thoroughly investigating the claims.

    1. Re:Spam the Blacklists by Anonymous Coward · · Score: 0
      Luckily ill-informed morons like you are too ill-informed to do any damage. Submissions are checked before they are entered into the database. At least with the blacklists I use.

      Thank goodness for stupidity.

    2. Re:Spam the Blacklists by edibleplastic · · Score: 1

      According to the SBL:
      All SBL entries are backed up with evidence which has fully satisfied the Spamhaus Project team that the IP is under the control of a spammer, spam operation or a spam support service and that the IP or netblock represents an unwanted nuisance or threat to mail systems using the SBL.

      Yes, they're checked, but it takes *time* to check them. If you hate blacklists, slowing them down/hindering their work is probably in your best interest.

  93. Spam Blacklists Describes Dangers of Paul Graham by Lew+Payne · · Score: 1

    Someone should write an article about the dangers of Paul Graham. For someone who objects to the inevitable politics of opposing groups or businesses clashing together, he certainly seems to do a representative job of clashing with same.

  94. The answer to spam... by The+Woodworker · · Score: 1

    The answer to spam isn't going after the spammers. It's going after a) those who push their products via spam, and b) the morons who buy their products. That's why I support email viruses via spam. When people are afraid to open an email if they don't know what it is, the market will die. Kill the market and the spam will go away.

    --
    Give a man a fish and he'll eat for a day. Teach him to fish and he'll wipe out the species.
  95. misusing a black list is "terrorism"??? by Uzik2 · · Score: 1

    I would hardly think the threat of being blacklisted as a spammer would inspire "terror". It might be called criminal, or a conspiracy, but I don't think "terrorism" is very appropriate.

    --
    -- Programming with boost is like building a house with lego. It's a cool but I wouldn't want to live in it
  96. Impossible by Himring · · Score: 1

    We were a Lotus Notes shop back in the day with a mail gateway running 5.8 I think it was. We got black listed by orbz.org. I thought the concept was great and labored to resolve our open-relay problem. I finally discovered that it was an unfixable bug in the Lotus Notes mail server. Before it reached critical mass, orbz.org was sued by someone and the problem fixed itself.

    IMO, this experience taught me that blacklists, while well-intentioned, could be a bit draconian....

    --
    "All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
  97. Slashdot Language lesson by Anonymous Coward · · Score: 0

    You seem to be confused about what a vigilante is, dictionary.com gives me this: "One who takes or advocates the taking of law enforcement into one's own hands."

    Yes. Law enforcement: not civil agreements between ISPs to carry email traffic. It's not vigilantism when two parties negotiate an agreement over a legal dispute; it's not vigilantism when someone advocates not hiring people with a criminal record; it's not vigilantism when someone throws away postal mail is postmarked from a known stalker's house.

    Blacklist maintainers are not vigilantes: they aren't breaking any laws, nor are they advocating anyone break any laws. They're not opposed to due process, nor any other feature of the law, much less condoning "taking the law into one's own hands".

    They do advocate that people who break social conventions be ostracized by not dealing with them, and they publish lists of people they feel have broken those social conventions.

    Vigilantes are typically guys who do bad things, for what they feel are "good reasons". They are the guys who go out, and blow up buildings that belong to "corrupt" officials. They kill people who they feel are undeserving of life, but who the law doesn't condemn. Terrorists are one example of vigilantes; Robin Hood is another.

    The blacklist people don't advocate blowing up buildings, killings, or any other form of taking the law into one's own hands. Instead, they advocate legal use of financial and social pressure to prevent what they feel are abuses. Sometimes this inconveniences people who feel they should not be inconvenienced, and these people feel legitimately angry. They have a right to complain about the service they get from the people who provide it, and, if dissatisfied, find another provider.

    But nothing illegal is going on, nor are the people you condemn as "vigilantes" advocating any form of illegal act, so there are no vigilantes in this discussion.

    Understand yet?
    --
    AC

    1. Re:Slashdot Language lesson by DavidTC · · Score: 2, Informative
      Vigilantes don't technically 'have' to break the law.

      For example, in many places it's legal to do a citizen's arrest if you see someone actually committing a crime. If someone suspects a crime will be commited and hangs around armed with the intent of bringing the person in, that's vigilantism, and perfectly legal. Or even hanging around waiting to call the cops.

      Or if, for example, people keep getting attacked in a certain part of town, so you, who happen to have a blackbelt, wander through there, waiting to be attacked so you can fight back...

      It's usually not called vigilantism if it's legal, but if you are attempting to do the work of the legal system, it is being a vigilante.

      However, vigilantism requires enforcing a law, be it an actual law or just a made up one. Or punishing someone who already broke the law. (Or, as sometimes happens, you merely suspect broke the law.)

      Whereas spam fighting may be interacting with the results of a crime, it's no more vigilantism than picking up litter is, or rebuilding a house torched by arson. The crime already happened, no one's trying to punish or catch the criminals, they're trying to undo the harm caused.

      I guess you technically could call spam reporters 'civil vigilantes', by analogy, because they are reporting a contract violation between two third parties to one of those parties. Instead of taking criminal offenses into their own hands, they're taking civil ones. But that's getting a bit silly.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  98. Twisting your analogy farther by billstewart · · Score: 1

    He's not just on a bad street, and the vigilantes aren't shooting randomly with machine guns. He's got an office in the same building as a few mafiosi, and the vigilantes are very carefully using sniper rifles and only sniping at people who come out of that building's front door, and the front doors of a few other houses on the same street. They just aren't looking at *who* walks out the door.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Twisting your analogy farther by sethb.nyc · · Score: 1
      He's in a building with a bunch of muggers, and the local Chinese restaurant association listed his building as one that delivery people get mugged in. As a result, a lot of Chinese restaurants won't deliver to him in that building.

      Does the restaurant association have the right to tell the truth about what happens to delivery people in that building? Does an individual restaurant have the right to base its delivery policy on that report? Or do you believe he has a right to get Chinese food delivered from a particular restaurant because he wants it, even if the restaurant's owner or manager doesn't want to deliver it?

  99. Doesn't your knee hurt when it jerks like that? by schon · · Score: 1

    Does the your government put a neighbor family through torture just because you got a parking ticket?

    Dude. Whatever it is you're smoking, you need to cut the dose. Seriously.

    Comparing people who make a list of known spam hosts to governments torturing innocent people?

    Take a deep breath. Once you've calmed down and willing to stop the (absolutely stupid) analogies, then we can talk.

    1. Re:Doesn't your knee hurt when it jerks like that? by Skye16 · · Score: 1

      Why is it so hard for you people to not take things so literally? I don't understand why it's me who needs to calm down. it seems like you, rather, need to chill out and just absorb the essence of what I'm saying - NOT the literal truth. Really, I'm just pointing out a like situation. Whether it's worse or better than the current one is moot - it follows the same pathways to get from point A to point B, though points A and B are different between the two scenarios. If you refuse to use your brain (and I know you have one) to discern the pathways analogies are meant to illustrate, then I truly have no idea what else I can do for you.

    2. Re:Doesn't your knee hurt when it jerks like that? by Anonymous Coward · · Score: 0

      You're using a retarded amount of hyperbole in your "analogies" in order to create an emotional response in your favor. Your analogies are worthless because there's no equivalence relation between what's being done and what it's being compared to.

      Maybe you should try making analogies that aren't completely useless. How many people need to tell you that your verbal skills are shitty before you take the hint?

    3. Re:Doesn't your knee hurt when it jerks like that? by Skye16 · · Score: 1

      It's only emotional if the user lets it be. Really, if you can't manage to subdue your emotions and register the meaning behind the words, you're even less useful than my analogies. Excessive emotionality in a logical debate has no place. If you fall victim to that trap, then I'm sorry, but the argument obviously wasn't meant for you.

  100. Which ISP's block email? by khasim · · Score: 1

    I've been on several ISP's over the years and not a single one has EVER blocked ANY email to me.

    EVER.

    I get TONS of spam on my personal accounts.

    Can ANYONE give me the name of a single ISP that will block email so that it can be confirmed?

    It's far easier for an ISP to put a limit on mail box capacity and do smtp-time rejection based upon that.

    1. Re:Which ISP's block email? by MikeBabcock · · Score: 1

      We offer colocated corporate E-mail accounts to clients. We routinely reject blacklisted SMTP servers from a couple sources as well as our own internal spam source collection system.

      All of them thank us for how little spam they get.

      --
      - Michael T. Babcock (Yes, I blog)
  101. Wrong again by Otto · · Score: 1

    What they do is allow others to block email between two diffrent people, simply because they run the mail servers that sit between them.

    If you're a user who is getting mail from a mail server that has RBL's on it, then you either own/run the mail server or you pay money to somebody who owns/runs the mail server.

    Period.

    In the case where you're paying money to somebody, then you're either:
    a) For the idea, in which case you have no complaints or
    b) Against the idea, in which case you can stop paying money to the person who owns the mail server (the ISP) and switch to somebody else.

    If B was actually a significant proportion of users, then ISP's wouldn't use these blocklists. Free market economics at work.

    The fact of the matter is that B is not a significant proportion of users. The people complaining about this sort of thing are people who get mail they SEND blocked because the receiver is using an ISP that uses these blocklists. And you know, the sender of mail has no real say in the matter as to whether the mail they send gets delivered or not, in this case.

    The solution of switching ISPs to somebody who isn't spam friendly and thus won't get blocked never seems to be taken seriously. Again, free market economics are at work here.

    Because RBL's work. The concept of collateral damage works. If it didn't work, then ISPs would not use these lists. They don't have to. No system comes setup to use these RBLs enabled by default. ISPs have to enable them or set them up. And they do that because they work. It's real simple here.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    1. Re:Wrong again by Anonymous Coward · · Score: 0
      RBL's work except for us users that don't run mail servers. For instance, I no longer have a direct email link to my family and friends unless they are on aol.

      If they're on smaller isp's, either their isp is blocked, my isp is blocked, or my aol account is blocked at their isp.

      Sure it makes email admins jobs easier, but of course if you don't provide reliable email your job is going to be a cinch. Its real easy to run a low reliability service.

    2. Re:Wrong again by cdrguru · · Score: 1
      Absolutely. RBL's make email unreliable for confirming purchases. RBL's make email unreliable for sending any sort of mail which is required as part of a commercial transaction. RBL's make it impossible to rely on a email address getting an email.

      This is exactly the environment that many anti-spam, pro-BL folks want. No commerce on the Internet, period.

    3. Re:Wrong again by jaseuk · · Score: 1

      The fact that any idiot* can report a message as SPAM and get you blocked for 24-48 hours from large sections of the internet is enough reason to be seriously concerned about blacklists. If an idiot can get you listed, I'd hate to think what a malicious person could achieve.

      (* = handwritten e-mail sent to approx 20 people, person receiving e-mail had met sender in person several times in previous week and had signed up in pen and ink to receive info on further seminars, non-commercial and also sent from a .gov.uk)

    4. Re:Wrong again by sanosuke76 · · Score: 1

      Uh, yeah. AOL's probably the most aggressive anti-spam place out there. They were even rejecting mail from my laptop - not because of the IP it's using, but because the headers indicated that the mail wasn't coming directly from the laptop's IP, but being smart-relay'ed to my linux box (which was locked to only relay from the laptop's static IP).

      More recently, they blanketly ceased to accept email from any host which doesn't have a reverse DNS entry.

      AOL seems interested in blocking off access to itself as much as possible, so that 'AOL families' will push non-conforming family members to go AOL.

      --
      My 229 is all the Sig I need http://thegunwiki.com/
    5. Re:Wrong again by Anonymous Coward · · Score: 0

      As long as said sender did not then release email address to a number of "opt-in" lists for herbal viagra, and then blitz him, and his subnet with crap.

  102. DSL and dynamic IP hosts are the problem by msblack · · Score: 1

    My employer found that 90% of all spam and viruses originated from zombie PC's on DSL connections. We previously blocked any SMTP gateway whose reverse DNS entry resolved to a hostname that looked like a dyanic DSL/dialup address. We felt that a reputable business would ask their ISP to create a reverse DNS entry for their gateway.

    Alas, a number of small business owners or home experts wouldn't pay the fee for the reverse DNS entry (cheap bastards they are).

    --
    signature pending slashdot approval
  103. He doesn't suggest the creation of another list! by Azul · · Score: 1

    He never suggests the creation of another list: his point is that someone might create one but it would be pointless.

  104. I use several RBLs too. It's not enough. by maynard · · Score: 1

    You are missing the point. Just because the RBLs you're using have blocked some SPAM, and only blocked "THREE" false positives, does not mean that the process is viable. Look, I've got three RBLs configured in my mail server. On top of that I use per connection limits, and have set up RCPT throttling. On top of that I hacked the sendmail source (simple one liner) to hang up on connections that do too many RCPT requests in one session, to really stop the dictionary attacks. And you know what? The fuckers just upped the number of connections across varying IP addresses and continued with their dictionary attacks as before. I had set up a fork limit to sendmail until the SPAMMERS opened so many connections it actually blocked legitimate incoming mail. So where does this end? When folks regularly begin seeing sendmail consume a mail server's entire process table with inbound SPAM connections? Because they'll do it. They have enough zombie bot resources. Face it, there's no stopping these guys with an open protocol. It's that simple. --M

    1. Re:I use several RBLs too. It's not enough. by mabu · · Score: 1

      I've done most of what you've done as well.

      However, the best approach I've found is using RBLs. They are several orders of magnitude better than any other spam solution in terms of the resources they require for the results they deliver.

      Yes, this is a never-ending arms race. But RBLs are one of the few real "solutions". Everything else is an expensive band-aid that quickly becomes obsolete and costs more to maintain and doesn't stop resource theft.

    2. Re:I use several RBLs too. It's not enough. by maynard · · Score: 1

      The thing is, it doesn't stop resource theft. It might reduce resource theft on your server by cutting usage down to a decision within the smtp transaction instead of a complex baysian spam filter after the transaction. OK, that's good. But there's still network resources used with dns lookups, plus the infected zombies. I mean, OK - use an RBL for now. What else can one do? But this just can't continue. IMO: legitimate email has become worthless as a communications medium. I mean, I know people (professionals) who have just dumped email because of spam! We're hitting a tipping point here where email has hit that point where it's so much a PITA that its benefits just aren't worth the trouble. Which says to me - we need to do something drastic to fix this problem. --M

  105. This is ONE Single IP Address that's blocked. by billstewart · · Score: 2, Insightful
    There have been spam blacklists that worked that way; they mostly weren't worth using, except as SpamAssassin weights, and mostly nobody cares. And there have been Open Relay blacklists that blacklisted every mail server at an ISP to get their attention until they cleaned up open relays, even if only some of that ISP's customers had open relays.

    But this is different - this is ONE IP address - the SBL record identifies it as a /32. Virtual Hosting means that it's possible to have multiple domains all using the same IP address for their email or websites, and if you're going to blacklist based on IP addresses, it doesn't get more granular than one address (unless you want to do things like have different return codes for "address has one spammer and some non-spammers".) So if one IP address has 100 legitimate users and one spammer, and you receive email from them, is it more likely that the mail is one of the 10000 (100 users x 100 messages/day) good messages, or one of the 1,000,000 spam sent by the spammer? 99% likely that it's spam; sorry if it was Paul.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  106. How to stop UCE (Spam) by Kaenneth · · Score: 1

    Don't buy anything from it!

    Who the hell keeps giving these people money?

    I swear if anyone I knew bought anything from spam, I'd have to torture them to death.

  107. Worst. Analogy. Ever. by Otto · · Score: 2, Insightful

    Your analogy is freakin' terrible.

    Paul hasn't been shot. Emails he tried to send have not been delivered. Drawing a comparison between physical violence and the fact that a guy can't send email is rather disingenious.

    What's worse is that you still got the analogy wrong. Nobody has attacked Paul. His mail server is fine. HE CAN STILL SEND EMAIL. Other people, however, can CHOOSE to reject his email because of his IP being on a list. Nobody's touched his servers.

    To use your crappy analogy, nobody's shot anybody. Instead, they've put his address on a list and then people who want to know about where the bad parts of town are can read that list and think that Paul is bad because he lives there too. Then they can throw mail he sent them away based on that.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  108. Re:Whiskey. Tango. Foxtrot. Over. by Pig+Hogger · · Score: 1
    So...it's okay if he goes to Federal Pound-Him-In-The-Ass penitentiary just because he rented a car from a place that also rented a car to a crack dealer?
    Bad analogy. It's more like a pizza joint refusing to deliver to the block you live in because twice last week it's delivery boys were raped by the crack dealers who live upstairs from you.
  109. Re:Whiskey. Tango. Foxtrot. Over. by sethb.nyc · · Score: 1

    If I got mugged several times delivering pizza to other people in Paul's apartment building, then I'm probably not going to deliver it to Paul in that building. If he wants my pizza that badly he can hire someone else to pick it up and deliver it, that's not my problem.

  110. Innocent victims by Have+Blue · · Score: 1

    Assume we are having an argument about the effect of illegitimate use of a certain class of service on the service as a whole.

    [service] can be used for legitimate or illegitimate purposes. However, the presence of anyillegitimate use on a subsection of [service] is evidence that the entire subsection is polluted and dangerous to [service] as a whole. The subsection should be disabled and all its users forced to endure downtime until they can prove that they have cleaned up their act and are not longer transmitting illegitimate content.

    [service] can be used for legitimate or illegitimate purposes. However, the presence of illegitimate use on a subsection of [service] is the price we have to pay for the benefits of [service] as a whole and our obligation to preserve the use of [service] for legitimate users on the same subsection as purveyors of illegitimate content. We should be careful to only act against those individuals who are polluting [service] and minimize collateral damage.

    Which conclusions will you pick when [service] is "email"? Now how about when it's "P2P"? Because the situations and starting positions leading to the two conclusions above are pretty much identical.

  111. I've been saying it for years by dtfinch · · Score: 1

    You can't trust blackhole lists. Too many non-spammers are blocked. Businesses lose customers when their email is very silently blackholed.

    1. Re:I've been saying it for years by taustin · · Score: 1

      DNSbls do not silently block legitimate email, unless the server it was sent through is badly misconfigured. Legitimate email will generate a bounce message back to the sender when it is rejected.

      The only way for a DNSbl to silently block any message is for the sending machine to be misconfigured so as to ignore 5xx replies. This is virtually a guarantee that the sender is a spammer.

    2. Re:I've been saying it for years by Anonymous Coward · · Score: 0
      You can't trust blackhole lists. Too many non-spammers are blocked. Businesses lose customers when their email is very silently blackholed.



      Maybe you can't, but I can and do. Almost no non-spammers are blocked with the ones I chose to use, and there is no "silent blackhole", every rejected email gets a full SMTP reject message telling the sender why. It's the Brightmail, Postini, lame-Bayesian/keyword stuff that tosses things into the never read spam bucket that sucks for the sender, not DNS blocklists!

    3. Re:I've been saying it for years by Anonymous Coward · · Score: 0
      Yes, but I'm not a business. I own a domain for fun on a box in my basement that my whole extended family uses for email.

      For that, RBL is a perfect solution. It's like a grouchy bouncer at the door: if you can't get past him, and you still can't figure out how to reach us, we don't want to know you.

  112. You know why they do that? by EvilStein · · Score: 2, Interesting

    They tell people to "Get a different colo" which is just ridiculous. Or, they'll tell you to pressure your colo to stop hosting spammers.
    Mine *doesn't* host spammers, and I'm in a contract. I can't pressure them to stop hosting spammers if they don't host any.

    I stopped using RBLs/MAPS/SPEWS years ago and have never looked back. Even more interesting is that the volume of spam *did not* increase, but the complaints about being bounced/not getting through decreased.

    1. Re:You know why they do that? by prockcore · · Score: 2, Interesting

      Even more interesting is that the volume of spam *did not* increase, but the complaints about being bounced/not getting through decreased.

      That's the biggest problem with RBLs... you have *no* way of knowing how effective they are. Since mail gets blocked at the server, you can't tell how many false positives or true positives there are.

      How much spam are you blocking? How much legit mail are you blocking? You have no way of knowing.

      Randomly denying 6 out of every 10 emails delivered would probably be just as effective as using an RBL.

    2. Re:You know why they do that? by Cramer · · Score: 1

      As the end user, maybe, but as the admin, it's pretty easy to see the effectiveness of RBLs (daily reports.) In my experience as an admin, RBLs work very well. Yes, they will kick out some legit emails from time to time, but that's easy to deal with. And yes, they'll miss a fair amount of spam, too -- it takes time to add sites to the list(s).

      Over ~1.5 years, the mail server for my previous employer kicked out exactly three (3) legit emails. The sender calls the person they were emailing; they tell me about the problem, and I add an exception to the rules. So, one innocent email killed every six months vs. letting in hundreds of spams per day is a fair trade in my book.

    3. Re:You know why they do that? by Mr.+Roadkill · · Score: 1
      I use five different blocklists (NJABL Dynamic, Spamhaus SBL/XBL, DSBL ORDB, Spamcop) plus some local entries for known offenders and dynamic ranges that have been dumping large amounts of spam and virus traffic on us, and get maybe half a dozen reports of blocked messages per month. That's okay - we block between twenty and forty thousand messages per day this way on average. Every rejection politely invites the sender to contact postmaster@$WORKPLACE to discuss the matter in the event that the blocked message wasn't spam, and I'm happy to consider whitelistings where appropriate and to offer suggestions to the admins of the blocked sites about what they might be able to do to improve the general deliverability of their blocked mail and how they might get off the blocklists if appropriate.

      Sure, blocklists aren't perfect, but they work well enough to keep my users able to productively use email, keep the load on in incoming mail relays lower than it might be if they had to scan every virus spewed out by an infected home machine on a DSL connection, and help those with legitimate systems that are getting abused find out about it sooner. They all sound like good things to me.

  113. Re:Language by hoggoth · · Score: 1

    > I've always been a little uncomfortable with the underlying assumptions white=good, black=bad. I prefer to describe such lists as "blocklists" and "accept lists"

    That's ridiculous.
    You are putting racial overtones into something that has NONE. They aren't "African-American-Lists" and "Caucasian-Lists". They are black and white, as in NIGHT and DAYLIGHT. Since we've been huddled in caves a pitch black night has been dangerous. Predators hunt by night. Criminals work by dark.

    This is as silly as the feminist movement protesting the word "Chairman" and having it changed to "Chairperson". The origin of the "man" in "chairman" is the word "manipulate", "mano" (hand), etc. NOT male.

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
  114. You're a fucking idiot. by Anonymous Coward · · Score: 0

    If you're running a mail server on a dynamic IP, then you're a fucking retard who should be blocked for being so fucking retarded. Moron. Pay the extra $5 and get a static IP. Then you'll have something worth complaining about.

    1. Re:You're a fucking idiot. by splint3r · · Score: 1

      I pay £400 a year and have a server hosted somewhere. So my home machine isn't my mail server, it's simply my home machine. Sometimes it needs to send out mail for various reasons.

      I believe machines do that, you know, send out mail sometimes (and no I should not be forced into using smart relaying i.e. using my ISP's mail server, or my co-lo machine to do the actual delivery). It's a clean machine which sends out mail, it also hosts some web content and various other services.

      Please consider what you're saying before you hit submit.

      Nothing but love for ya! :)

    2. Re:You're a fucking idiot. by argent · · Score: 1

      my home machine isn't my mail server, it's simply my home machine. Sometimes it needs to send out mail for various reasons.

      Yep, so does mine.

      I pay £400 a year and have a server hosted somewhere.

      I don't pay quite that much, but it's in the same range. I'm also about to set up a backup virtual server for another $70 a year.

      So when my home machine wants to send mail. it does it over an encrypted tunnel to my colo.

      I should not be forced into using smart relaying

      Entirely true. You shouldn't be forced to deal with the results of spammers pissing in the pool. But until spammers are fined or otherwise sanctioned sufficiently to make spam the minor problem that it should be, having to arrange for a reliable smarthost is part of the cost of being on the net.

      Please consider what you're saying before you hit submit.

      I have, at length, and I stand by it.

    3. Re:You're a fucking idiot. by argent · · Score: 1

      Pardon, I thought "you're a fucking idiot" was referring to me.

      The anonymous coward who called you one was a sorry bastard, but he was right in saying that you're going to have to find a static smarthost for your outgoing mail.

  115. Distributed List by suwain_2 · · Score: 2, Interesting

    The problem with blacklists is that -- the guy who recently had a story on spam here, at acme.com, put it nicely -- blacklists start off good, but always turn corrupt and start blacklisting excessively.

    Suppose a "distributed" blacklist were created. I could blacklist the whole Internet, but I'd be the only one, so it wouldn't mean a thing. On the other hand, if 75,000 people have blacklisted an IP, there might be something there.

    It needn't be totally distributed, I don't think. A community-run site, where, whenever you get obvious spam, you post the originating IP, could work. You'd post it, and that IP would have, say, 10 "points." The rating would "decay" by one point a day, so a site listed, but that went clean, would quickly leave the list: in ten days, each rating would be down to zero.

    You could then simply query the site for a given IP, and it'd return the "points" a site had. This also allows you a lot more customizability: if you were obsessed with blocking all potential spam, you could block anything with more than 5 points. If you wanted to be careful, you might set it to, say, 1000 points.

    Unless the people running the site keeping track of the ratings begin blatantly making up ratings, this idea means that a blacklist is much less immune to being "bad." And it allows IPs to "fade" out of the list over time.

    --
    ________________________________________________
    suwain_2 :: quality slashdot p
    1. Re:Distributed List by Anonymous Coward · · Score: 0
      The problem with blacklists is that -- the guy who recently had a story on spam here, at acme.com, put it nicely -- blacklists start off good, but always turn corrupt and start blacklisting excessively.



      One can always tell a lie masked in stats, or opinion by the use of absolutes, like "all", "never" and in this case "always".

      Some blacklists go this route, others like the one in question have been around for years and seem to not go this way.

      If they do, people will just stop using them. But based on this lame story by the "plan for spam" guy, this one has not.

      And "terrorists"? Get real.

  116. Initial delays, Greylisting, DialUp Lists by billstewart · · Score: 1
    I'm really surprised how much spamware apparently doesn't implement SMTP cleanly - Jef Poskanzer's recent article said that rejecting any address that sends mail before waiting for the response to an initial HELO throws out a significant portion of spam. But Greylisting throws out a lot more - if somebody's address isn't trusted, give them a 451 and tell them to come back in 5 minutes; spammers usually won't bother. You could get fancy and give anybody on a blacklist a long delay time (e.g. come back in an hour.)

    Greylisting is especially appropriate for the DialUp List type of blocklists, that track dynamic IP addresses. They might be legitimate users running Linux at home, or they might be zombies, and greylisting usually keeps the zombies out.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  117. Apparently I understand them better than you do. by khasim · · Score: 1
    I suppose you've never heard of analogies before?
    Of course I have. I also know that there are "good analogies" and "bad analogies". Your analogy was "bad".
    Rarely does an analogy contain the exact same quote AND the same context as the initial situation.
    Okay, I think that YOU are the one that does not understand an "analogy".

    And analogy is a comparision between two pairs that have the same relationship.
    I hope analogies, in general, make sense to you...
    They do, which is why I asked who had been shot.

    Here's a site to help you: http://www.epcc.edu/faculty/joeo/sa_analogy.htm

    Your "analogy" is:
    bad IP address:blocking by email admin
    as
    bad neighborhood:vigilante shooting

    So, no, your analogy makes no sense in this context unless you somehow equate an email message being rejected as being similar to a person being killed.
  118. Private blocklists. by Pig+Hogger · · Score: 3, Funny
    There are many, many private blocklists that are not advertised anywhere.

    Here is my very own private /etc/mail/access blocklist which I use on my own mail server:

    #
    12.217.112 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.113 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.114 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.115 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.116 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.117 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.118 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    12.217.119 550 Mediacom. Heh. What a fucking spamming cesspool. So why not eat shit and die???
    24 550 Comcast, when you'll have cleaned your zombies, you can knock here. Not before.
    24.174 550 Chuck Jones must be spinning in his grave when he see he's associated with spam. Close port 25, fuckers.
    59.0 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.10 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.1 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.11 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.12 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.13 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.14 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.15 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.16 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.17 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.18 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.19 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.2 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.20 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.21 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.22 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.23 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.24 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.25 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.26 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.27 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.28 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.29 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.3 550 It's not surprizing that a country split in two like Korea would have a totally fucked-up "internet".
    59.30 5

    1. Re:Private blocklists. by Anonymous Coward · · Score: 0
      Dude, are you an Aryan/Nazi/Fascist lamer?

      Get professoinal help. Seriously.

      Fucking kids.

    2. Re:Private blocklists. by iocc · · Score: 1

      I firewall port 25 from .cn and .kr. They are all spammers and infected with shit.
      cn-kr iptables blocklist here.

      My DNSBLs:

      FEATURE(dnsbl, `bl.spamcop.net', `DNS-block-check-01. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `relays.ordb.org', `DNS-block-check-02. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `blackholes.easynet.nl', `DNS-block-check-03. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `cw.blackholes.us', `DNS-block-check-04. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `burst.blackholes.us', `DNS-block-check-05. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `bellsouth.blackholes.us', `DNS-block-check-06. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `rackspace.blackholes.us', `DNS-block-check-07. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `level3.blackholes.us', `DNS-block-check-08. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `he.blackholes.us', `DNS-block-check-09. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `verio.blackholes.us', `DNS-block-check-10. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `nigeria.blackholes.us', `DNS-block-check-11. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `sbl.spamhaus.org', `DNS-block-check-12. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `list.dsbl.org', `DNS-block-check-13. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `dnsbl.njabl.org', `DNS-block-check-15. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `dnsbl.sorbs.net', `DNS-block-check-16. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `psbl.surriel.com', `DNS-block-check-17. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `dnsbl.net.au', `DNS-block-check-18. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `opm.blitzed.org', `DNS-block-check-19. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `cbl.abuseat.org', `DNS-block-check-20. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `blackholes.intersil.net', `DNS-block-check-21. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `spews.org', `DNS-block-check-22. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl
      FEATURE(dnsbl, `dnsbl.ahbl.org', `DNS-block-check-23. Shut your fucking face uncle spammer. You are a relay raping chicken-boning server-fucker.')dnl

      I get very little spam that gets through. Oh, and I dont care if I block legitimate mail. If they wanna write to me they can use hotmail or something if its really that important.

    3. Re:Private blocklists. by Pig+Hogger · · Score: 1

      Thanks for the cn-kr block script. :)

  119. General rule of thumb regarding blog legitimacy by mabu · · Score: 0, Flamebait

    1. If the blogger doesn't allow comments, it's not worth reading.

    If you want to slap stuff up and not give anyone the opportunity to comment or correct your work, chances are you're not really interested in being truthful or accurate.

    Paul Graham's "essay" is a mean-spirited vengeful attack on RBLs because he's been caught in them. And ironically, he shows he's a total hypocrite by claiming the RBLs are abusing their power, all the while he abuses his own power and influence by writing a one-sided wholesale condemnation of RBLs.

    I agree, his lame diatribe probably isn't worth mentioning in ./, but at least on this forum we can comment on the dubious nature of his self-serving propaganda. He won't allow anyone to question his statements on his own site.

    Hear that sound? That's whatever's left of Paul Graham's credibility being flushed down the toilet.

  120. Spam Blacklists, Ineffective... by MadMorf · · Score: 1

    At least for us...

    According to our Anti-Virus, Anti-Spam gateway, only 1/2 of 1% of the messages being stopped by the gateway were being stopped because they were on an RBL...

    I stopped using it because I figured the overhead/bandwidth being consumed wasn't worth it...

    1. Re:Spam Blacklists, Ineffective... by mabu · · Score: 1

      According to our Anti-Virus, Anti-Spam gateway, only 1/2 of 1% of the messages being stopped by the gateway were being stopped because they were on an RBL...


      You're using sucky RBL's.

      My rate is somewhere around 97%

    2. Re:Spam Blacklists, Ineffective... by Anonymous Coward · · Score: 0

      Well, how about telling us _which_ lists you use then? Duh.

    3. Re:Spam Blacklists, Ineffective... by mabu · · Score: 1

      Well, how about telling us _which_ lists you use then?

      Right now we're using spamcop and SBL and an internal RBL we've been developing which is largely a DUL/Broadband list. We're still looking for a good community DUL list. I'd like to make ours public, but I am not going to put it online from our network for fear of attracting retribution from spammers.

  121. Censorship my hind end by Otto · · Score: 1

    If somebody wants to make a list which will let people block information about X, whatever X is, then I have absolutely no problem with it. They're making a list as they see fit.

    If people then want to use this list to block X from their systems, then I also have absolutely no problem with it. Their system, they can block anything they choose by any means they choose. Not my say.

    Now, if the people who make the list decide to block whole ISPs because they host information about X, you say I'm supposed to have a problem with it? Bullshit.

    It's their list. They can do whatever the hell they want to do with it. The people who use their list, well, they can do that too if they so choose. I don't see how I should have any say in how they run their list. If they want to block entire ISPs that host blogs of people who have political views they disagree with, then I may consider it dumb, and I certainly won't use their list, but I'm not going to say that they shouldn't make such a list.

    They can list any damn thing they please. The only choice I have to make is whether or not their list is useful for me to use or not.

    RBL's are useful to a large number of people. This is why they exist. If the notion of blocking whole ISPs works for the people who use that list, then so be it.

    If I was to get blocked, and I thought it was unfair, then I'd be angry, sure. I'd try to argue my end of it and I'd try to get removed from the list. But never, EVER, would I say that they have no right to list me on their list or that other people have no right to use that list to block me.

    Now, if they blocked me because I used a specific ISP that these people didn't like, then it would motivate me to decide whether using that ISP was worth being on that list or not. You pick your side. You support the ISP or not. That's it. Just bitching about it doesn't help anything, because what they put on their list and how other people use that list is totally out of your hands.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    1. Re:Censorship my hind end by jamie · · Score: 1
      Of course it's censorship. It's preventing person A from seeing the website set up by person B.

      The only question is whether censorship should be supported as a tool for helping eliminate spam, even in the case where person B's only error was signing up with Yahoo as their service provider. Personally, I don't think ends justify means, and if they did I think I'd start with an end like eliminating child pornography, or terrorism, or something. But some people think spam is more important than those things. If you think that way, fine. But don't fool yourself about the means you're supporting.

    2. Re:Censorship my hind end by Otto · · Score: 1

      Of course it's censorship. It's preventing person A from seeing the website set up by person B.
      Actually, it's preventing person A from sending email to person B, but I get your point. Whether it be email or web surfing, it's the same concept.

      But you missed my point. Person B is subscribing (paying money to) person C who runs the ISP/mailserver. If person B dislikes the service, they can switch providers to person D, who blocks nothing at all.

      Free market economics at work.

      Personally, I don't think ends justify means, and if they did I think I'd start with an end like eliminating child pornography, or terrorism, or something.

      If you want to set up a list to help people block this sort of thing, feel free. Maybe ISPs will subscribe to your list. There's nothing preventing you, or me, or anybody else from setting up such a list. There's nothing preventing anybody from using such a list.

      But don't fool yourself about the means you're supporting.

      What means? Individuals setting up lists? Individuals using those lists? What, exactly, is wrong with this means? I see absolutely nothing wrong with people choosing to block things that they don't want to see.

      Because you act like something is being suppressed without any consent here. This stuff ain't automatic. It ain't built in. Somebody chooses to block mail in this fashion.

      --
      - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
    3. Re:Censorship my hind end by Arker · · Score: 1

      No, Jamie, it's not censorship.

      If someone comes in with a gun, or the force of the police and courts, behind them demanding I use a certain list, then that would be censorship.

      If I voluntarily choose to use a list to filter what I allow on my network, that's nothing of the sort.

      When you try to blur the meaning of words like this, equating theft of services with free-speech and spam filtering with censorship, you're not only insulting those who suffer from real censorship, and those of us that have put our jobs on the line many times to oppose it, you trivialise the entire issue as well.

      You should be ashamed of yourself. You really should.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  122. SORBS = perfect example. by EvilStein · · Score: 1

    http://archives.neohapsis.com/archives/postfix/200 5-05/1770.html

    The postfix-users list wound up in SORBS because the admin was sloppy.

    Read the thread. That's the attitude that you get from blacklists. It's *never* "their fault" - somehow it's *your* fault. That's just bullshit.

    1. Re:SORBS = perfect example. by mabu · · Score: 1

      SORBS got carried away and overzealous, so we had to stop using them.

      There are good RBLs and bad ones. At this time, I'm not sure if SORBS is a good choice for commercial mail servers based on our experience. We started to get too many false positives and had to drop them.

  123. I am a victim, too by drwho · · Score: 1

    I was victimized too. Because someone hijacked some IP space that I used to provide ptr dns records for, somehow they feel as though my IP space is hijacked as well, SPEWS feels as though my IP space must be hijacked and I must be a spammer as well.

    And other spam-blocking lists use SPEWS info, so I am banned through them as well.

    The worst of this is, this is all heresay and libel and there's nothing I can do about it. I found that one non-profit ISP starting using SPEWS and my mail to that server bounced, but luckily I knew the guy and just called him up and told him and he got rid of SPEWS.

    The whole blacklisting idea is just bad. All you need is a few vengeful cranks to make the whole thing fall apart.

    Oh, the IP space in question is 205.159.169.0/24.

    So, there you go.

  124. Funny.... by Anonymous Coward · · Score: 0

    It is funny how people here whine about flawed analogies when it comes to things like "copy right infringement," but flawed analogies like this one are deemed not to be flawed and get a +5.

    What machine guns? You know what a boycott is, right? All they are doing is refusing to do any business or have anything to do with that neighborhood.

    Besides, it is more like they are reporting things to the proper authorities, and the proper authorities are refusing to do anything about it. Heck, sometimes the "proper" authorities know about these actives, are profiting from them, and are encouraging them. Thus they refuse to do business or have anything to do with this neighborhood.

  125. Re:Whiskey. Tango. Foxtrot. Over. by GlassUser · · Score: 1

    How is renting a car, hanging out with crack dealers????

    Crack dealer rents car. Crack dealer steals someone's stash, and escapes in said car. Crack dealer returns car. The next day, you rent said car. While driving out of the neighborhood, the former owner of the stash sees the car, decides he wants revenge, and guns you down.

    QED.

  126. Journalism is not Terrorism by Anonymous Coward · · Score: 0

    This doesn't describe blacklist maintainers.

    Blacklist maintainers are cynical, bitter, little men who care nothing for the people they hurt so long as they get a spammer. They deliberately target innocents in the hopes that the innocents will complain to the higher power to get rid of the things that bothers them. This leaves little to distinguish them from terrorists other than the fact that they don't kill people. Their deeds are less dark, but their tactics are the same as the Madrid bombers who hurt innocent people to push them to choose a government more favorable to their wishes.


    Nonsense. Blacklist maintainers are journalists; they document abuses, and where the trouble comes from.

    If someone wants to impose a trade embargo on the region where the abuses came from, that's their right. If that person fails to notice when a change of regime comes in, that's also their right. It's certainly not the fault of the journalist who documented the original abuses.

    Certain, innocent individuals in the region where the trade embargo has been imposed tend to get upset: but that's the point. That doesn't make trade embargos terrorism; and the journalists who document the abuses certainly aren't terrorists.

    Get your metaphors straight. Asking it's members to put financial pressures upon a corrupt ISP by blocking that ISP until it stops spamming isn't that unreasonable: it's profiting by spam, and until it's unprofitable, it won't stop.

    Worse yet, if a company can sell to spammers, and undercut it's competitors by it's lack of spam controls, then the customers who permit the spammers benefit financially at the expense of everyone else. So no, I don't mind "paying to see people get hurt", since those people were sitting back, and making money by letting others hurt me.

    If the truth hurts, then let it hurt. If you're buying milk from the Mob, and they can't deliver it to you because the supermarket won't sell to them now that they know what the Mafia has been up to, well, that's your fault for chosing Mafia Milk Delivery.

    It's not the fault of the journalist who pointed out that the Mafia threw some poor guy in a woodchipper. And the journalist is not a member o Hamas, and the supermarket is not a terrorist for pointing it out, and it's not their fault you can't get your milk: it's yours, for chosing an corrupt dairy service provider.
    --
    AC

    1. Re:Journalism is not Terrorism by Anonymous Coward · · Score: 0

      Your analogy is more tortured than a terrorist in Guantanamo Bay.

  127. Load of FUD by Paul Graham, competitor to Spamhaus by Steve+Linford,+Spamh · · Score: 5, Insightful


    Gentlemen,

    You do realize that Paul Graham is in the business of pushing Bayesian anti-spam filtering, which he claims as 'the best' solution to spam. For a long time Graham has been spreading FUD about other anti-spam solutions, in particular blocklists. We're well used to hearing utter bollocks about blocklists spread by him.

    Yesterday we listed on the SBL an IP of a spammer which as luck would have it is being shared by Paul Graham. We of course can not simply give the spammer carte blanche to spam our users because Paul Graham is also using the same IP. Graham has no concern for the fact he's sharing his IP with a spammer, and rather than contact his ISP to ask what a spammer is doing sharing his IP he simply sees a PR oppurtunity to bolster his "blocklists are evil, bayesian is good" campaign. I'm only surprized this actually made Slashdot.

    Steve Linford, CEO, Spamhaus

  128. What's the big deal anyway? by o-hayo · · Score: 1
    I don't even use these services and I still get a very small percentage of spam leaking through our filter. Maybe I'm not on the superscale but when I had the DNS lists turned on they didn't even capture a sizable percentage in the first place. Here's an example, my last 30 days of message categorization:

    Total Processed - 2,260,811
    New Senders - 0
    Total Spam - 1,915,404
    Keyword Checking - 4,818
    Header Checking - 5,283
    Blacklist - 21
    Bayesian Analysis - 35,248
    DNS Blacklist - 0
    SPF - 354,726
    Directory Harvesting - 1,515,308
    Spam URL Blacklist - 0
    Spam Percentage - 85%

    Anyone blacklisted by these services need not worry about getting in touch with me, unless they *really* are pushing spam. I say we all abandon these antiquated tools and move on that doesn't put all the power in the hands of the few and let the internet manage itself again.

  129. This thing totally sux by XPACT · · Score: 1

    I have my own CMS web site with forums, and some eastern european people from my nationality get there, I have a live chat too. I wanted my site to have registration, and the best way is with an e-mail. Then the problem starts. The confirmation e-mail is often blocked even by yahoo mail servers.So I have to use SMTP forward. My yahoo SBC account is perfect for that. I hope the yahoo smtp servers will not be blacklisted.
    My MTA is XMAIL server <URL:http://www.xmailserver.org/>

    I believe your MTA should support smtp forwarding and you can use the user name and pass for your DSL account, or I should say your PPPoE user and pass.

    Good Luck!!!

  130. Such a fresh argument, too by Thuktun · · Score: 1

    Agreed. This same kind of argument against anti-spam blacklists has been used for years, and have caused plenty of thousand-message flamewars, but never really produced any effective alternatives.

  131. Collective Punishment by Anonymous Coward · · Score: 0

    Collective punishment is a war crime. ORBS and the other irresponsible asses who level entire subnets just to squash a spammer at one address are not doing anyone favors. They are too lazy to create a listing system that is granular enough to properly address the situation they purport to 'help us' all by addressing.

  132. Re:Whiskey. Tango. Foxtrot. Over. by AK+Marc · · Score: 1

    He states it clearly in his article: You can't screw over innocents just to make the guilty pay.

    He's too cheap to pay for dedicated hosting. He saves money by sharing resources with a violator. Would you be offended if your roomate was a drug dealer and the cops were so rude as to search your room while serving the warrant to search the house? You are stupid enough to live with a crack dealer because the rent is cheap. So why would that make you "innocent" when the crack dealer is found out?

  133. Sounds like Star Wars by tivoKlr · · Score: 1
    There was this character early on, Anakin (John Reid in this case) and he started out with the best of intentions, but being corruptable like all people, John was tempted by the power and simplicity of the Dark Side, and eventually created the monster SBL (Death Star) by which entire ranges could be devestated by a single blow...

    The rest is history (or should i say present.)

    --
    Ocean is land, covered with water.
    1. Re:Sounds like Star Wars by Anonymous Coward · · Score: 0

      Wrong episode.

      "Episode 4"

      This John Reid is Luke Skywalker and the SBL is the rebel alliance going after the monster that is the ISPs who host spammers. It's their Death Star, manned by Storm Troopers (spammers) who wreak havok on the Galaxy (internet).

      but what do I know? I'm just a droid!

  134. A different approach to RBLs by ckuske · · Score: 1

    Not RBLs are equal...

    My company furnishes a RBL/IP4r database called MXRate. No subjective human analysis is used whatsoever, and we do not block any subnets. Everything is 100% automated.

    We average a .02% false positive rate, and the only time we edit records manually is if there is in fact a false positive. Otherwise, if a server stops sending spam, it falls off the list in a few hours.

    MXRate was specifically engineered to overcome these shortfalls that are present in other blacklists.

  135. Re:Whiskey. Tango. Foxtrot. Over. by Darth · · Score: 1

    that isnt a very valid representation of the situation. Here's a better one:

    You rent a storefront in a strip mall. The guy with the storefront 2 down from yours is selling drugs out of the back of his shop. The police raid him and shut down his store. Then they shut down all the other stores in the strip mall because the owner of the strip mall rented space to a drug dealer.

    does that sound reasonable?

    --
    Darth --
    Nil Mortifi, Sine Lucre
  136. Black Lists by Stan92057 · · Score: 1

    I am a normal homeuser,I subscribed to Comcast. Why isn't there an email client that allows me to decide whats delivered to my box instead of having to use a black list? I don't do business with any other country then the US so how can i block emails from all the other country's?. Thats where all the IPs are from in the spam i get. Why cant i have a choice of, this is spam, do i want to block this IP address not the email address sense 99% of spams email doesn't match the IP address. That should be my choice and also to have to choice of not receiving the email at all not just putting it in a spam folder and calling it a spam blocking program, because its not. I still have to look through the spam folder so whats the point, it doesn't save me any more time. If there was a good choice of something to use instead of a blacklist i would use it, but because none of theses ISPs don't want the end user to have that much control of there email sense they have partners they make money from allowing them to send spam....

    --
    Jack of all trades,master of none
  137. Slows some spam but doesn't stop the real stuff. by eodmightier · · Score: 1

    Anyone on a blacklist isn't a real spammer. They are either a clueless company with an open relay (blacklisting them is fine cause it gets them to fix it) or it is a newbie spammer, sending out from a known spamming source (and fine ban them).

    Thing is real spammers, spam and run via zombie machines, hacked wifi connections, etc. They move about, constantly switching their source.

    We need to stop thinking blacklisting is the only way. More people need to adopt SPF records.

    --
    -Eod
  138. Terrorism? Hardly. by ChaosDiscord · · Score: 2, Insightful

    Graham has written some insightful and well thought out stuff, but this is just sloppy:

    This is, strictly speaking, terrorism: harming innnocent people as a way to pressure some central authority into doing what you want.

    I find it amazing that blacklists which mail servers must opt-in to use are somehow terrorism. Are you suggesting that these innocent people have some fundamental right to contact my mail server and send mail? They certainly don't; it's my mail server. I can use any methods I like to filter out mail, including chosing to rely on one of the IP blacklists. This can only be terrorism if random people have some sort of human right to send mail to my machine. I hardly think that's a right.

    Come to think of it, apparently organizing against tangentally related people to stop another problem is terrorism? By that strange standard you could call advertiser boycotts terrorism: you're trying to influence some media outlet by negatively influencing advertisers on that outlet. They often have the same claim of innocence ("I didn't know that they would run that article! I just buy bulk advertising rates.")

    (Now there are problems with blacklists, perhaps most significantly that many ISPs use them without informing their subscribers or allowing them to opt out. Blacklisting unaware users who happen to share a machine with a spammer's website is definately a complex question.)

  139. Re:Language by Vainglorious+Coward · · Score: 1

    I totally agree that "chairperson" is clumsy. I much prefer simply "chair".

    And I note that it is *you* that thinks this is a race issue. I just said that I didn't get the black=bad, white=good paradigm, (detour via caveman analogies notwithstanding). I never mentioned race (other than to note that others would shoot me down because they would jump to that conclusion).

    As for the main point, as I pointed out in another post, on a practical level, "block list" and "accept list" are just much more meaningful in explaining what the lists do. Why would anyone choose to use alternatives that are less meaningful *and* may be be looked upon with distaste by some? The only reasons I can think of are (a) ignorance/laziness or (b) a deliberate "anti-PC" mentality. So which are you? Your surely won't attempt to claim that "blacklist" is more meaningful than "block list" will you?

    --
    My next sig will be ready soon, but subscribers can beat the rush
  140. Re:Spam Blacklists Describes Dangers of Paul Graha by Anonymous Coward · · Score: 0

    Paul Graham ate my balls.

  141. You have got to be kidding me by bruns · · Score: 1

    You have got to be kidding me. _This_ is news? Come on, this guy can't even get his facts right. First major glaring error I see:

    As of this writing, any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam. Why? Because the guys at the SBL want to pressure Yahoo, where paulgraham.com is hosted, to delete the site of a company they believe is spamming.

    How about you do some research Paul? The SBL does not block based on domains, only IP addresses. DNSbl lists are always IP based, RHSbl lists are domain based.

    I always found the SBL to be a very reliable DNSbl to use, and have never lost a legit e-mail to it before.

    But hey, what do I know? I'm just one of those evil anti-business DNSbl admins (AHBL anyone?).

    --
    Brielle
    1. Re:You have got to be kidding me by harlows_monkeys · · Score: 1

      Uhm...you sure botched that one. Yes, the block is IP based. That is why it is catching paulgraham.com, even though paulgraham.com doesn't spam.

    2. Re:You have got to be kidding me by bruns · · Score: 1

      He was saying that any e-mail with the URL paulgraham.com would be blocked.

      It doesn't work like that. Unless you use SURBL type lookups with an RHSbl, it doesn't care what is in the body of the message.

      Yes, his e-mail is being blocked, but NOT because of his domain being in the body. He is being blocked because his mail server's IP address.

      Yes, I know I'm being quite anal about how he worded things, but if you're going to be publishing articles, you should at least word things correctly.

      --
      Brielle
    3. Re:You have got to be kidding me by harlows_monkeys · · Score: 1
      Yes, his e-mail is being blocked, but NOT because of his domain being in the body

      He didn't say it was because of his domain being in the body.

    4. Re:You have got to be kidding me by bruns · · Score: 1

      "As of this writing, any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam."

      Where else would it be other then the body?

      I think your missing the point that I am trying to make - he is being extremely vague in his meaning, and obviously i'm not the only one who got the impression that he doesn't know what hes talking about.

      --
      Brielle
    5. Re:You have got to be kidding me by squiggleslash · · Score: 1
      So because he's not describing his problem using your preferred terminology, he's not having a problem, and shouldn't complain about it? Correct?

      If your attitude is typical, that's great news for those trying to convert "Grandma" over to GNU/Linux.

      "I can't get the Internet to work"

      "Are you stupid? The Internet works fine. I'm on it now on my computer. Duh. You really are a maroon."

      --
      You are not alone. This is not normal. None of this is normal.
  142. I'm tired of this shit by Anonymous Coward · · Score: 0
    I'd take all the SPAM anyday vs. not being able to send legitimate emails.
    Really? How would you like 10,000 SPAM a day? Is that better than not being able to send legitimate e-mails from your (apparently only) e-mail address? The worst possible case isn't receiving 10,000 daily SPAM messages, it's receiving 10,000 daily MAILER-DAEMON errors because a spammer has started using your e-mail address as the 'From' address in his SPAM, so every automated spam filtering program on the planet starts sending you e-mails saying your message has been discarded because it's SPAM.

    What kind of fuckwit sysadmin would leave this option on? Everyone knows spammers don't use their real e-mail address, so what possible purpose could it serve to send an e-mail to the 'From' address of the message telling them the message was discarded because it was SPAM?

    I have ZERO sympathy for ISPs who get blacklisted because they relayed SPAM. Get your shit together.

  143. P.S. by That's+Unpossible! · · Score: 2, Funny

    "A much better way to cut down on spam is to use $technology_I_created."

    --
    Ironically, the word ironically is often used incorrectly.
  144. Yes, Wrong by BlogPope · · Score: 1
    What they do is allow others to block email between two diffrent people, simply because they run the mail servers that sit between them.

    Fortunately your title perfectly captured the content of your post. The mail admin (MA) has ALWAYS had the capability to block those emails. What the black list is supposed to provide is a listing of mail sources that conform to criteria X, so that MA can decide whether to block those sources. The only reason MA can block mail between two people is because A) One of those people has trusted MA to handle mail for them, or B) One of them is a A**hole attempting to relay mail through my server. The second MA doesn't need a blacklist for, a properly configured server handles them.

    The problem addressed by TFA is that some Blacklist maintainers are going off mission and are blocking site for reasosn other than critera X. So while I might want to use an account that only blocks sources that have actively spammed a list of "seed" addresses in the last hour, I'd be quite pissed to find they were also blocking Walmart because they opened a store nearby.

    I do what I can to monitor my Blacklists, and weed out the ones that seem too aggressive. Some seem to suck far more than I would expect given their charters, I suspect they may have been up to this sort of monkey business.

    --
    My other car is a Popemobile
  145. Re:Load of FUD by Paul Graham, competitor to Spamh by jaeson · · Score: 1

    Hi Steve,

    I totally agree with your comment. Paul *should* be contacting his ISP to see what they are doing about the problem. He is choosing not to contact them to hyperbolize his problem (and thus advocate Bayesian filtering instead).

    However, I also think that Paul has a point when he writes, "I do think that whether an email comes from a server on a list of (supposed) spam sources is just one piece of evidence among many, and probably fairly unimportant evidence compared to the content of the email."

    Since the SBL has been quite good about listing individual spamming IPs (not whole "collateral damage" ranges a la SPEWS) people have decided to rely on it quite heavily. This is both a curse and a blessing. Of course, no single RBL is 100% bulletproof against false positives, and any good solution to blocking spam will be a comprehensive one.

    My $0.02,
    Jaeson Schultz

  146. A motion from the floor ... by Obfuscant · · Score: 1
    I move that whenever the topic of RBLs is brought up in an article, with the predictable result of this kind of long, religious flamefest, that /. simply link to the previous long drawn-out religious flame fest and save everyone the time of repeating their position.

    Barring that, can we please use the following codes to save bandwidth, sort of like the prison inmates who numbered the jokes?

    1. "It's hurting innocent people."
    2. "It's my right."
    3. "My users like it."
    4. "RBLs don't block email, bad admins do."
    5. "Nuh uh!"
    6. "Uh huh!"
    7. "So's your grandma!"
    8. ?
    9. Profit!
  147. no big deal by gnuguru · · Score: 1

    This guy does not host his own site, he does not care to take responsability for his actions, he uses cheap mass hosting.

    The simple truth is that he trusts a third party with his data who cannot be reason of scale, look after him.

    When he actually owns the equipment, rents the T1, and pays the upkeep on his gear, and buys his own IP range, he will have some control over over port 25, and maybe the rest of the world will give him the attention he deserves.

    Until then, he will get the attention he deserves.

    Everyone who cannot live without email from Paul please raise your hand.

  148. Speaking of blacklists by TCM · · Score: 2, Interesting

    Going away from SMTP, I am currently running a Squid HTTP proxy with a quite long blacklist of URLs and networks of "marketing" and "ad" companies.

    I find myself doing for example a lookup of ad.marketingscum.com followed by a whois lookup of the IP address. If I find that they own a larger network like

    NetRange: 216.73.80.0 - 216.73.95.255
    CIDR: 216.73.80.0/20
    NetName: DOUBLECLICK-NET

    I enter the complete network into my blacklist. Are there any realtime blacklists for this purpose? This would be quite useful, wouldn't it?

    --
    Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
  149. Re:Wholehearted Agreement by trelanexiph · · Score: 1



    Worst of all, many RBL's (including ours) pretty much block any dynamic IP pool as "dial-up zombie hell"--but a lot of these IPs get reallocated to broadband as DSL coverage grows, and we end up blocking genuine mail routers and SMTP relays instead.

    We have a process for requesting the unblocking of an IP, but about 30% of the time the answer is "tough luck, pal. You (or your client who is trying to reach you) is blocked and we aren't unblocking you." There is no appeal process; if one of our admins decides not to unblock your IP or IP range, you can't reach any of our customers via email.

    What, you don't maintain a local whitelist along with your blacklist? Exim Sendmail Postfix Qmail and others all support whitelisting. If it's blocked and you don't want it blocked, whitelist. You don't have to use the lists we supply verbatim.

  150. Anything by certel · · Score: 1

    I don't care what the result or future creation of any type of spam protection -- I just want something that consistantly works.

  151. Using blacklists incorrectly! by Anonymous Coward · · Score: 0

    Blacklists *ARE* very useful if used properly. While you shouldn't use a blacklist to reject unilaterally, it is a very strong indicator that a message is spam.

    You still get false positives & false negatives though, so don't use a blacklist as the only criterion.

    So, configure your spamfilter to rank the message a bit higher if the address is on a blacklist. Combined with lots of other spam characteristics, you can be very sure a message is spam.

    Spamassassin makes this very easy.

  152. Re:Whiskey. Tango. Foxtrot. Over. by DavidTC · · Score: 1
    Um, yes, it does.

    With the minor quibble he rented to a drug dealer and then refused to cease renting to him when it became obvious the guy was, in fact, a drug dealer.

    At that point, hell yes the police should shut down the whole damn mall, because something funny is going on there.

    Of course, this analogy doesn't work, because this wasn't the police, it was simply people refusing to visit the mall, because no one would do anything about the damn drug dealer.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  153. Best analogy so far by e_AltF4 · · Score: 1

    After reading lots of clueless "murder", "rape" and "terrorist" ones it's refreshing to see someone hit the point.

    There is no "clueless" moderation for "murder", "rape" or "terrorist", so please moderate "movie reviewers" and "pizza delivery" as insightful if you have any spare points left :-)

    Thank you.

  154. Re:Spam Blacklists Describes Dangers of Paul Graha by pyrrhonist · · Score: 1
    Someone should write an article about the dangers of Paul Graham.

    Someone did in a way.

    --
    Show me on the doll where his noodly appendage touched you.
  155. Re:Load of FUD by Paul Graham, competitor to Spamh by jmason · · Score: 2, Interesting

    hmm. What's the relationship between the user 'Steve Linford, Spamh' (who's never made any comments before this story) and 'Steve Linford' (comments made back in 2001)?

  156. My favorite RBL by tacocat · · Score: 1

    Is for identification of relays only. This can be easily tested and confirmed by remote queries on the SMTP server. It's not very aggressive, but it definitely captures a lot of potential spam.

    Sorry Paul has to start a public bitch session against SBL but he's mostly right. RBL's have a tendency to turn into evangelical power mongers who start attacking a lot of people who are more innocent than guilty and if proven wrong, simply blow them off.

    The concept of RBL is probably still valid. But it's so poorly managed...

    1. Re:My favorite RBL by mabu · · Score: 1

      RBL's have a tendency to turn into evangelical power mongers

      The market weeds out those RBLs that aren't responsible.

      However, RBLs are one of the few ways for victim networks online to put pressure on larger ISPs who are acting irresponsibly. Every single day, an RBL forces an ISP to clean up their act. That's more progress in the battle against spam than all the client-side spam-filtering software combined.

  157. Even when they are right it's wrong by CustomDesigned · · Score: 1
    One of our customers gets DSL service from a spam friendly ISP that is blacklisted by Spews. Spews is correct: the ISP is a spam friendly bastard. Unfortunately, it is also a monopoly in the area. There is no other broadband service available at any price (well, I suppose if you wanted to set up your own ISP...).

    Our solution is to relay mail through another MTA (via VPN) for recipients that check Spews. But this illustrates yet another reason why the "blacklist the entire ISP" strategy is not good.

    The solution to the IP abandoned by a spammer problem is simple: don't blacklist IP addresses. Instead, use SPF to validate the MAIL FROM, and base your blacklists on the MAIL FROM domain instead of the IP. Yes, spammers can also do SPF, and already have throwaway domains. But the namespace is *much* bigger, and their automated throwaway domains are not ones you would want anyway, (e.g. ajfkc.com).

  158. RBL advice by Vainglorious+Coward · · Score: 1

    Certainly. The answer, unfortunately of course, is "it depends". It depends on what your own tolerance of false-positives is, and what your current level and nature of spam is (where "you" also includes the users of your system - there's a world of difference between an ISP with tens of thousands of paying customers, a small organisation with a hundred employees, and a personal family/friends server).

    My best advice is to carefully examine the policies of the RBLs, and revisit that examination on a regular basis. Look at whether the process by which IPs are added to a list is automatic, or human-moderated. Are they using spamtraps? Do they allow just anybody to submit addresses for listing? Is the listing process openly specified, or a black box? What is the procedure for de-listing an address? Google around for others' experiences using the list. This Declude page is a useful starting point (I have no relation to Declude).

    Currently, I see the least collateral damage with the Spamhaus lists. My top recommendation would be the sbl-xbl.spamhaus.org list, a composite list consisting of known spammers plus a pretty good list of compromised/trojanned systems.

    On one extreme, SPEWS is hardcore - I would never recommend them to anyone who isn't very well aware of the implications of what they are doing. On the other end of the scale, open relay lists like relays.ordb.org and the like are very benign, but less useful, since there hardly are any more open relays these days. I used to really like Spamcop's lists, but I lost faith in them a couple of years ago when I experienced some inexcusable cock-ups. More recently, Spamcop changed listing policy and started listing systems that were sending "mis-directed bounces", which I personally find misguided (long story, see this discussion for a start). Also be careful about "multi-stage" or "multi-hop" lists. These can often end up listing major ISP servers, simply because one of their clients relayed a spam that way, typically caused by a trojan-type infection.

    I've also had trustworthy results with cbl.abuseat.org, and in a typical configuration I often also use relays.ordb.org (open relays) and list.dsbl.org.

    --
    My next sig will be ready soon, but subscribers can beat the rush
    1. Re:RBL advice by AaronLawrence · · Score: 2, Insightful

      Re Spamcop; The simple fact though, is that "misdirected bounces", though well intentioned, make the problem of spam quite significantly worse. It pushes the spam off to someone else. Sure, the system doing the bounces is not "spamming" but they are acting as a spam transfer system, a bit like open relays used to.

      Still you obviously have a reasoned and generally reasonable stance on blacklists. Congratulations ;)

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
    2. Re:RBL advice by Vainglorious+Coward · · Score: 1

      The simple fact though, is that "misdirected bounces", though well intentioned, make the problem of spam quite significantly worse.

      I don't disagree that that scenario, and the similar ones caused by anti-viral warnings, act to amplify the effects. The problem is that a blanket "no bouncing, ever" policy destroys some useful features of the email system. Much as Spamcop would wish it, it isn't always possible to know during the SMTP transaction whether the message will ultimately bounce.

      --
      My next sig will be ready soon, but subscribers can beat the rush
  159. Unsolicited Plug (from me) ... by Dr.Dubious+DDQ · · Score: 3, Insightful

    Considering how much my spam has been reduced by the SBL (anywhere from at least 50% up to 75%) I'd like to just say:

    The mail servers under my control have always subscribed to the SBL-XBL (well, more accurately, before the XBL was established it was the SBL and cbl.abuseat.org. The latter is dedicated to short-term [72 hours, as I recall] blocking of e.g. spammers operating on DSL or cablemodem lines who are likely to appear on an IP address once or twice and then get kicked off. The CBL is now also represented in the XBL). I have so far, in the last 3-4 years or so, only been able to confirm 1 and 1/2 "false" positives in that entire time - one was from a person in China who was using a confirmed spam-haven ISP, the "1/2" from a company that, after an informative response from the CBL people, I believe were listed for appropriate reasons. In any case, the latter case cleared itself up when they were automatically re-removed from the CBL [they'd been there before] and the email lost WAS an advertisement anyway...)

    I have noticed the numerous stories of overzealous blocklists, which are obviously a bad thing, but I can't think of a way to reasonably put the SBL in that category...

    Besides, bayesian filtering only works AFTER the spammer has been allowed to tie up my mail server's bandwidth (and then allows them to tie up your mail server's CPU time with the bayesian analysis). I prefer to cut off known spammers before that point whenever possible. THEN I pass the remaining messages through SpamAssassin. Back in the early days of spam, I used to actually go to the effort of picking apart the mail headers and looking up the abuse addresses for the ISP whence the mail came AND the hoster of the spammers website (and on one or two occasions, even the registrar for the spammer's domain name, when I could confirm that the information was falsified). It's been a long time since I was able to keep up doing that with the volume of spam coming in, but I still can't stand the thought of allowing spammers to take ANYTHING from me that I can prevent...

  160. Free markets, creative destruction by Senescent+Nerd · · Score: 1

    I'm free to filter my mail any way I want. That's good.

    A bunch of spam fighters who want to pool their statistics to fight spam more efficiently are free to do that. That's good.

    If they want to put their results online where everybody can see them, that's good.

    If my ISP wants to improve my email experience by letting me use the spam fighters' online database, that's good. (They do. I like it.)

    If an ISP thinks most of their customers wouldn't want to wrestle with the details of spam filtering, and would prefer to have the ISP make the filtering decisions, that might not be the service I want, but I'll defend their right to offer that service.

    If SBC has rented my daughter a damaged IP address, one with a bad reputation for spamming, that's bad: I nearly missed a message from her that went into my Spam folder. I hope my daughter can switch to a service that tries harder to keep its IP inventory clean. Absent that threat, I don't see why SBC would make any effort to reduce spamming.

    So, SBC is free to decide how vigorously to discourage spamming. My daughter is free to choose her ISP. I am free to use the information that spam-fighting groups share freely. Life could be far worse.

    But my daughter, having innocently rented this damaged IP address, must be having trouble sending email to people who filter their email with blocklists. That's bad. But aside from the spammers, I don't see whose freedom we should abridge to alleviate the problem.

  161. Another good article by krokodil · · Score: 1

    Another good article on the subject is: "The Spam Problem: Moving Beyond RBLs" by Philip Jacob

  162. Re:Whiskey. Tango. Foxtrot. Over. by AK+Marc · · Score: 1

    does that sound reasonable?

    No, that is not a reasonable analogy. They are separate addresses. One is Suite 100, another is Suite 200. They have separate walls. There are separate locks on the doors. There are no shared facilities, other than a parking lot. Yours would work well if they blocked IP/24 upon an infringement. But they blocked only IP/32. That means that they were specific enough to hit only the Suite 100. Suite 200 was not affected. However, the two vendors sharing Suite 100 were both affected, even though only one was a criminal.

  163. centrally adminned blacklists are not a good idea by Joseph_Daniel_Zukige · · Score: 1

    If you maintain your own black/white/grey lists, then you control what goes in which list. You can fix the lists if they break, as soon as you know about the breakage.

    If you share your lists with friends, then you are losing some of the control. But you gain a wider range of coverage, as well. It may or may not be good, but the key point is that you have reason to trust (or not to trust) any particular friend's blacklist, and you are still making the decision.

    Particularly, if the sharing mechanism uses some sort of rating system and allows you to tune the shared lists for yourself, you maintain control.

    But when you share the lists of people you don't know, you no longer have a valid basis of trust. The only basis of trust that remains is the basis of advertisement. You are essentially giving your freedom into the hands of the group with the best ads.

    Centrally administered blacklists are by nature in the latter category.

    Therefore, centrally administered blacklists are not a good idea.

  164. BHL's Work Just Fine by Flaming+Cowpie · · Score: 1

    I've been a SPAMCOP member for years and other than the odd time I've fouled something up, it's worked flawlessly. I'm subscribed to all the BH lists + spamassassin and it cuts my SPAM from 2000 + a week to less than 3 a day. Lists work. If you don't like them, get your ISP to fix their services. Spammers only exist because of loopholes and slacker admin policies.

    It's harsh that sometimes people get caught up in the crossfire, but there's a reason - usually a good one - why it happens. The author of the article knew what he was getting into, he should have built his house out of bricks - not straw. I trust the sysadmins that make the lists *more* than I trust users to take a hand in fixing their bot ridden boxes and stopping the problem.

    --
    Sigs? We don't need no steekin Sigs!
  165. Not collateral damage by Smallpond · · Score: 1

    paulgraham.com is 66.163.161.45. When I check IP on either side, they are not listed. Only that one IP address is listed. Paul Graham is not a victim of collateral damage of a wideranging netblock, his single IP has been blocked because it was the previous address of textileshop.com. Its in the sbl evidence file SBL27945.

    host paulgraham.com
    paulgraham.com has address 66.163.161.45

    host 66.163.161.45
    45.161.163.66.in-addr.arpa domain name pointer html3.store.vip.sc5.yahoo.com

    44.161.163.66.sbl-xbl.spamhaus.org not found: 3(NXDOMAIN)
    45.161.163.66.sbl-xbl.spamhaus.org has address 127.0.0.2
    46.161.163.66.sbl-xbl.spamhaus.org not found: 3(NXDOMAIN)

  166. Re:Whiskey. Tango. Foxtrot. Over. by jgoemat · · Score: 1
    Does the your government put a neighbor family through torture just because you got a parking ticket?
    Hopefully your government wouldn't torture you for getting a parking ticket either...
  167. Oh I get that. by /dev/trash · · Score: 1

    But how do you know who drove your car before you did? You don't.

  168. Terrorism? by fbg111 · · Score: 1

    This is, strictly speaking, terrorism: harming innnocent people as a way to pressure some central authority into doing what you want.

    Though calling everything "terrorism" is all the rage these days, it's not actually terrorism, rather it is extortion, blackmail, or something else along those lines. MAPS actions as described by Paul may have been completely reprehensible, but it's a far cry from striking fear into the populace's hearts by murdering some random selection(s) of them. Man, if techies can't limit the rhetoric, who can?

    --
    Flying is easy, just throw yourself at the ground and miss. -Douglas Adams
  169. You're so strange, I feel compelled to ask further by Vainglorious+Coward · · Score: 1

    Some postmasters are piss poor, period. But I'm not one of those, so forget the hypothetical finger pointing and deal with the actuality : RBLs work, and work well, even though they're not maintenance-free, and they're not a panacea.

    Have you ever found anyone that got hit in the expanding scope issue that still relies on RBL's?

    So little of your post makes any rational sense, but this bit is particularly perplexing. What on earth are you on about?

    Maybe I'm just missing your point. How exactly do the Safe Harbor provisions have any bearing?

    --
    My next sig will be ready soon, but subscribers can beat the rush
  170. crock of... by RMH101 · · Score: 1

    this is why you get people who know what they're doing to write contracts. you mean your SLA and underlying contract with your ISP doesn't mention availability and the like?

    1. Re:crock of... by hawkbug · · Score: 1

      Availability has nothing to do with being blacklisted. Also, I said TECHNICAL reasons, which no lawyer can help with. Imagine having to sit down and change all your dns records and router config every time you wanted to move. For a large corporation, this is not reasonable.

    2. Re:crock of... by RMH101 · · Score: 1

      is your service available to you if you're blacklisted? (and by "available" i refer to the definition of "available" in your underlying contract between you and your businesses' ISP? in a well-written contract, spamhaus ISPs will be in breach, and so you have a stick to hit them with. it's pretty simple when you think about it.

    3. Re:crock of... by hawkbug · · Score: 1

      Our service agreement says nothing about the ability of other networks to get our communications by their own choice - and also, my main point is that technically, changing entire class C's is not reasonable for a large company. It's a lot of work and overhead costs to make this happen.

  171. Re:Wholehearted Agreement by aaronl · · Score: 2, Informative

    That works fine for him to keep the mail coming in. The problem is when you combine the annoying "dynamic ip range" lists with an idiotic admin that thinks using one to blindly deny is a good idea. I mentioned in another post, but Juno and Netzero do this. Neither will pay attention to you when you complain. Of course they also RBL deny their postmaster account, which is a no-no.

  172. Re:Apparently I understand them better than you do by Skye16 · · Score: 1

    I thought my analogy was "they're both guilt by unknowing association, no matter what the end result is". Should I spell it out some more? I'll do so now.

    In our current situation, we have a guy renting a car at Enterprise. He deals crack.

    Later another man goes to Enterprise and rents a car. He knows nothing of the crack dealer out and about in the streets selling his wares. All he knows is that Enterprise has cars to rent and he needs to rent a car. So he rents the car.

    The crack dealer gets caught by the police. Since he was driving a car he rented by Enterprise, according to this particular blacklist's logic, every person who rents a car at Enterprise is now guilty. The police then go out and arrest everyone who rented a car at Enterprise, because they are also guilty.

    What's the core situation I'm describing, regardless of the details? "If someone does something wrong while using ServiceX, everyone at ServiceX gets punished. Even if no one using ServiceX knows any of the other clients there, regardless of whether they were also breaking RuleY, they get punished as well, just because someone they never met fucked up."

    That's how this "analogy" I've posited ties in with this situation. If I had spent more time developing an analogy, that would be fine. But I guess I expected the readers here to use at least a smidgen of their supposed IQs and figure this out on their own. It may not be pretty, but it does work.

  173. Re:Whiskey. Tango. Foxtrot. Over. by Skye16 · · Score: 1

    That, like my previous analogy, is a bit misrepresentitive of the situation.

    Would I be offended if I went to an establishment that specializes in rentals. I rented a carpet cleaner there because I have a cat that sheds excessively. I'm a repeat customer because the rates are good and the service is excellent.

    Someone else, whom I've never met, also rents carpet cleaners there. Except they use them to do all sorts of nefarious and unsavory things (imagine what you will). It becomes known where this person rents this carpet cleaner - the town is outraged at his actions - so they blacklist everyone who continues to rent at that store.

    Here's where we come to a possible branch in the road.

    Possibility A: Suddenly people stop talking to you because you rent there. Are you angry? Absolutely. Mostly because people are jackasses. But you still stop using that rental establishment because they do nothing to alleviate the problem.

    Possibility B: The rental establishment finds out - at the same time as everyone else - that their equipment is being misused and does not allow this person to rent from them again. Everyone who shops at this rental establishment is blacklisted anyway - not because the establishment has done anything unsavory on their part, but because the person making the blacklist is completely inept and power hungry. You, as a customer, are still being fucked over - not because of the rental establishment, but because of the person compiling the blacklist. What do you do? Do you leave your rental establishment, even though they're doing nothing wrong? Or do you beat the shit out of the person making the blacklist for being a cockbiting fucktard?

    And that's the problem here. When blacklists are updated in an objective and timely manner, they're great. But, as seems to happen over time, the likelyhood of that happening seems to deteriorate. Entirely too many respectible and honest colos and hosting providers are being fucked by blacklist maintainers who have lost their way.

  174. blocking is not the problem by radja · · Score: 1

    Spamblocks are not the problem, they are an attempted solution that is not perfect. the real problem is spam itself. spam has made email from a reliable medium into a marketing tool, used to force advertising on us at our own expense.

    --

    No one can understand the truth until he drinks of coffee's frothy goodness.
    --Sheikh Abd-Al-Kadir, 1587
  175. Not just IP addresses... by Evro · · Score: 1

    I once worked for a company whose mail started bouncing (including stuff like order confirmation emails) due to having a well-known spammer in the same /24 block! We complained to the blacklist (I forget which one(s)) and were told basically that we had to lean on our ISP to can the spammer. Since the spammer was paying them like $5k a month or something, and we were paying like $700, it was a no-brainer for them. There was nothing we could do. These guys are like the gestapo in that sense. On the one hand, yes it's all voluntary, but on the other hand they could at least pretend to care about the collateral damage they cause.

    --
    rooooar
  176. Reliability of email by Otto · · Score: 1

    Email was never designed to be a reliable system to begin with, and thinking that it was is a fairly foolish thing to do. It's a best effort system. Simple as that.

    Funnily enough, no RBL has ever stopped me from getting email from places where I've made purchases or what have you.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  177. Re:Load of FUD by Paul Graham, competitor to Spamh by squiggleslash · · Score: 1
    Actually, he should be contacting the ISP and other mail server runners with the configuration problem that's causing his emails to be blocked. Those are the #1 problem here.

    Whether Yahoo! happens to have a spammer today or not is largely irrelevent, no ISP has a fool-proof anti-spammer policy, and spammers are going to come and go no matter how much work ISPs can do to fix this.

    There are several guilty parties here. If I had to put everything by order of "This guy caused this email to be blocked", I'd say the order was:

    1. Destination postmaster (and their employer)
    2. Blacklist operator
    3. Spammer
    4. Yahoo
    These parties can reasonably be said to have had some role in blocking the message. The person who administers email for the person who wants to receive it but can't is the person clearly most responsible. The blacklist operators are too, for putting this "ingredient" (Yahoo is a spammer) in the drug they're trying to push, and for pushing it. The spammer is clearly at fault for being part of a group that caused a problem in the first place. And Yahoo might be at fault if they knowingly allowed the spammer to operate.

    But let's be reasonable. Complaints should start with the people who can fix the problem, not at dubiously related parties for not being a loud enough member of an ideological crusade.

    --
    You are not alone. This is not normal. None of this is normal.
  178. Re:Whiskey. Tango. Foxtrot. Over. by AK+Marc · · Score: 1

    so they blacklist everyone who continues to rent at that store.

    But that's not what happened. There wasn't indiscriminate blacklisting of everyone that used the store. There were "good" machines available, for a higher cost. There are the "shared" machines which are seedier. The person specifically picked the cheaper one with the higher risks.

    I think I finally came up with an analogy that makes my point better.

    An honest businessman is in town for a 6 hour layover. With lunch and travel time, he has time for a 2 hour nap. He passes by two hotels. One is a Holiday Inn. The rates are $200 per night. He also sees "Joe's Hotel" next door. Their rates are $50 per hour. He picks the hourly rate because it is cheaper. He may or may not be aware that hourly rate hotels are not as reputable. 24 hours later, a dead prostitute is fond in that room. The room is dusted, and with the poor housecleaning, all people there for the last week or so, including the poor innocent businessman, are rounded up by the police and held for hours in interrogation. His reputation is soiled by being picked up in a murder investigation.

    So, I'd think that he was partially responsible. Dedicated hosting/hotel room was available, and he chose the solution that resuled in cheaper prices and greater risk. I also think that the actions of the police/list makers were quite reasonable. There was proof that a "crime" was committed there. Anyone there around the time of the crime is suspect. The person in the next room is not inconvenienced. Not everyone at the hotel is inconvenienced. Just the people that were in that one specific room.

    Oh, as an aside I'm currently on a RBL. Why? Because I pay $5 per month for some crappy hosting. It is for a non-profit with few hits. So, I'm on a server with a bunch of other people. On of them got on the list (for what, I have no idea). So, I'm on the list with them. Do I care? No, not really. That's what I'd expect when getting a dirt-cheap shared service. When you aren't willing to pay for the service you expect, it is your own damn fault when you don't get it. He was an idiot that wants all the benefits of dedicated hosting for the price of shared hosting. Obviously, I have no sympathy for him...

  179. Re:Whiskey. Tango. Foxtrot. Over. by Skye16 · · Score: 1

    Sadly, that isn't what they do. My colo was slammed by Spamhaus a year ago because someone else there was spamming. The spammer was eventually booted - before the entire colo was blacklisted - but the person (whoever that was) that was managing this particular blacklist situation decided the colo wasn't helpful enough - and without any spam known to be currently flowing out their pipes - added them anyway.

    There went the business of many webhosts who rented dedicated servers there, as their clients could no longer count on their emails being received. If it were just one IP, that was fine, but they blocked the IP of every computer this colo owned (at that datacenter, at least). Hundreds of dedicated boxes were down, and that's just boxes - not the drastically large number of people who were screwed over.

    After a few months, things worked out. Spamhaus fixed the problem eventually, after daily emails back and forth between the colo and Spamhaus' contact.

    I should note that this is the information the colo filtered out to their clients. With that said, my dedicated box, with 5 IPs assigned to it, was blocked because someone else's box, with a completely different IP, was spamming and the tech at the colo didn't bow to Spamhaus's demands. Blanket blocking is ridiculous - it's one thing to block an IP, it's another thing to block the entire range of IPs.

  180. RBLs vs Filtering: Apples and Oranges by mabu · · Score: 1

    First, thanks very much Steve for your tireless service to the community. We've been using your SBL for a long time and it has helped tremendously.

    It really bothers me that people compare filtering to RBLs. They are really two completely different animals. RBLs *stop spammers from communicating with you* thereby keeping them from stealing bandwidth and system resources (which is the nucleus of the formula which has the capacity to make their unethical and illegal efforts economical and practical). Content-based filtering does not. It requires even more resources by the victim network and doesn't address the critical issue that is spammers' consuming a disproportionate amount of resources for the cost.

    For people who choose to employ content-based filtering, good for you, but know that your efforts are not at all contributing towards the reduction of spam -- quite the opposite. RBLs however, do. They cause spammers to spend more money and time to do their spamming by moving about in IP space trying to find rogue ISPs, infecting clients and other methods to get around RBLs. The only way you stop spam is by negating the economic formula that makes spamming practical, and the only solution that does this right now are RBLs.

    If Graham wants to plug filtering, that's his prerogative, but he shouldn't call himself any sort of champion in the war against spam. He's just a champion of sorting his mailbox folders.

  181. Paul Graham is a liar. by wkcole · · Score: 1

    Just to get the full disclosure thing out up front: I have known Steve Linford of Spamhaus professionally for almost a decade and was an employee of MAPS (Senior Consultant in their Consulting Services Group and later Director of Customer Operations) before their 2001 collapse. I've also been working with real-world mail systems and spam control since the early 90's. Whether those facts make me informed or biased or both is a judgment call...

    Graham's description of what happened at MAPS is not just inaccurate, it is dead wrong and appears to have been invented to draw a sort of inherent lifecycle picture of blacklists. It makes a cute story, but it is a pure fantasy. Yes, MAPS had a period where their listings and escalations were not as careful as they should have been. That would have been 1999 or so. By mid-2000 MAPS was careful enough with listings that some of the more fanatical folks calling themselves 'anti-spammers' (see news.admin.net-abuse.email) were calling MAPS 'soft' and even accusing Paul Vixie of being in collusion with some of the entities MAPS refrained from listing. MAPS collapsed *financially* starting in early 2001 not because its users went away but because it was a non-profit organization with a very bubble-sensitive funding base. MAPS' lists were free of charge and open to all users at that time, so losing users would not have been a contributor to the *finanical* problems that pushed them into irrelevancy. On top of that, multiple *spammers* (not innocent victims) sued MAPS over listings and pursued those cases in ways that imposed huge legal costs on MAPS for suits that never really moved forward towards trial. In 2001 MAPS effectively committed suicide, settling all the cases by de-listing the plaintiffs, shedding most of its employees, and making the use of its lists available only to paying customers. There are still a lot of users of the MAPS lists and I understand those lists still manage to help stop spam for those customers, but it is off of Paul Graham's radar and a lot of the public spam discussion radar because it stopped offering any free services almost 4 years ago and it stopped doing anything that the larger and better funded spammers cared enough about to keep suing.

    As for what Spamhaus is doing now that is having an impact on his mail, Graham is overstating the situation. The SBL listing details why the single IP address that Yahoo has assigned to his site was listed. It was being used for a 'store' for a longtime spammer. Yahoo uses a complex load-balancing system for hosting, so I can't say for sure when or how or why that address became the one that www.paulgraham.com resolves to, but now it does. The spammer's store now resolves to an address in the same /29 block, but when or why it moved thee is not obvious and the DNS TTL's and zone serial number indicate that it could be back on the listed address within an hour or so. The short version: Spamhaus listed a single address that was being used for a spammer's web store, the spammer's web store was moved to a different address, and Paul Graham's site was left in its place. That move may not have been in any way calculated by Yahoo, it may have been pure accident. This is not a case of Spamhaus listing all of Yahoo: that's not something they do. They listed a single IP address that was in use by a spammer, and is now in use by Paul Graham. The spammer's facilities remain at Yahoo on a different IP address.

    You can make your own judgment on what that says about Yahoo.

    Graham's description of the impact is worse. He claims that 'any filter relying on the SBL is now marking email with the url "paulgraham.com" as spam' and that is plainly false. Most mail servers that use the SBL use it as a classic DNSBL: mail coming from any IP address that is listed gets refused. Some mail server operators have chosen to take this a step further, and use tools like Spam Assassin 3.0 that look into the message data for URL's and resolve them to a server IP that is checked against th

  182. Analogies have 2 items, you have 3 (at least) by khasim · · Score: 1
    I thought my analogy was "they're both guilt by unknowing association, no matter what the end result is". Should I spell it out some more? I'll do so now.
    No, I didn't see that in there.

    A formal analogy is in the format a:b::y:z so you might want to try fitting your "analogy" into that format. That will show where you're wrong.
    In our current situation, we have a guy renting a car at Enterprise. He deals crack.
    Okay, so
    A = Enterprise?
    A = Renting car?
    A = Renting car at Enterprise?
    A = Dealing crack?

    Which is it? Remember, the analogy is about the relationship.
    The crack dealer gets caught by the police.
    And now you're introducing the police.

    A = police?
    A = caught by police?

    Or are you onto item B now?
    Since he was driving a car he rented by Enterprise, according to this particular blacklist's logic, every person who rents a car at Enterprise is now guilty.
    Oh, look, now you've introduced ANOTHER item, the blacklist.

    I guess in YOUR world, an analogy is ...
    A:B:C:D:E:F::Y:Z

    Maybe you shouldn't use the term "analogy" at all, okay?
    The police then go out and arrest everyone who rented a car at Enterprise, because they are also guilty.
    Again, you might want to review what an "analogy" is before you start claiming that you're stating one.

    Here's a BETTER analogy for you:

    (non-spammer on email blacklist)
    is to
    (message rejected)
    as
    (black man)
    is to
    (not picked up by taxi driver)

    See the relationship? See how there are only two items in each relationship? See how the relationships are compared?
    "If someone does something wrong while using ServiceX, everyone at ServiceX gets punished. Even if no one using ServiceX knows any of the other clients there, regardless of whether they were also breaking RuleY, they get punished as well, just because someone they never met fucked up."
    You might want to look at how many items you just mentioned and then look at my REAL analogy and see where you failed.
    That's how this "analogy" I've posited ties in with this situation.
    Only if you don't know what an "analogy" is, which, clearly, you don't.
    If I had spent more time developing an analogy, that would be fine. But I guess I expected the readers here to use at least a smidgen of their supposed IQs and figure this out on their own. It may not be pretty, but it does work.
    Again, analogies are very simple and very easy.

    But there are lots of people who don't have the education to understand what an analogy is. You seem to be one of them.

    Here's a link to help you (in addition to the one I've already supplied):
    http://www.datanation.com/fallacies/falsean.htm
  183. They don't target innocents. by Otto · · Score: 1

    However, the core issue of spam blacklists deliberately targetting innocents

    No blacklist out there delibrately targets innocents. Not one. They target "spam-friendly" ISPs and users of those ISPs because those users are paying money to those ISPs. These users are not "innocent". They are financially supporting an ISP that allows spammers to operate. They may not know this, but after they get blocked they usually find out pretty quickly.

    It is perfectly acceptable to go after these users as targets, because they are contributing to the problem whether they are aware of it or not.

    --
    - Give a man a fire and he's warm for a day, but set him on fire and he's warm for the rest of his life.
  184. Re:Load of FUD by Paul Graham, competitor to Spamh by Godeke · · Score: 1

    I don't call it FUD if he is actually experiencing the problem. Paul has near zero control over the allocation of the IP space he uses. Yahoo can remove the spammer after complaints, but the importaint issue is:

    ONLY AFTER THE DAMAGE IS DONE.

    The nondelivered mail remains non-delivered. It will remained undelivered until someone up the foodchain gives in to your demands. Interestingly, most blackmailers give their demands first and then execute consequences once those demands aren't met. Here we find the notification of demands is by rendering consequences *first* on a collection of randomly choosen innocent victims. Maybe they will figure out *why* e-mail isn't delivered, but we aren't going to actually give them any hints that could help them...

    "If those innocent would just complain and have the spammer removed" is what I usually hear... but that takes time, and during that time the consequences remain enforced. I noticed here it is a new day and the block remains.

    Sorry, it isn't FUD when you can point to the objective fact: Paul Graham is suffering from blocked e-mails based because of an accidental relationships with an IP address. Sounds like he has that "power corrupts" thing down just right to me based on what is said in your comment: "Graham has no concern for the fact that he is sharing his IP with a spammer". WTF? He seems awful concerned to me. What you really seem to mean is "Graham is GUILTY of the fact that he is sharing his IP with a spammer. If he won't bow to our will, well, we don't force anyone to use our block lists (just a lot of people do)."

    --
    Sig under construction since 1998.
  185. Re:Load of FUD by Paul Graham, competitor to Spamh by Anonymous Coward · · Score: 0

    You don't understand. Yahoo Store (yahoo-inc.com) was given plenty of warnings about the spammer hosted on the IP (one IP, not "all of Yahoo" as Graham tries to imply), Yahoo-in.com has ingnored all complaints about the spammer, they were repeatedly told the IP would be placed on the SBL if the spammer was allowed to continue spamming hosted on the IP.

    Paul Graham is not "suffering" as he pretends, Graham WORKS for Yahoo-inc.com - in other words he works for the very same firm ignoring the complaints for the spammer. He can actually remove the spammer himself, but it's more valuable to him to have the spammer on his IP.

    Check the Whois record for the domain:

    Domain Name: PAULGRAHAM.COM

    Administrative Contact:
    Graham, Paul (PG174) pg@YAHOO-INC.COM
    Yahoo!
    3420 CENTRAL EXPY
    SANTA CLARA, CA 95051-0703

    The deception is greater than you imagine.

  186. Re:Apparently I understand them better than you do by Pete · · Score: 1

    Skye16 represents his extraordinarily poor analogy as:

    If someone does something wrong while using ServiceX, everyone at ServiceX gets punished. [...]

    This is the only element I'm particularly pointing out, because it's one of the bits khasim missed (in his otherwise very precise analysis of your bad analogy).

    The thing to remember about blacklists like Spamhaus and SPEWS that list IP ranges is that the block is not aimed at the spammer so much as it is aimed at the ISP hosting the spammer. So the point is that it's the ISP being "punished", not the users of the ISP.

    So in your analogy, the users of ServiceX wouldn't be touched, just ServiceX itself. The only downside for the users of ServiceX is that they can't use ServiceX anymore - at least for whatever translates as email service in your (bad) analogy.

    While we're talking about analogies, the one I've seen most often used by supporters of wide-ranging email blacklists (including myself) is the pizza-delivery analogy. If you live in a known-bad neighbourhood, you may find that your local pizza-delivery chain won't take orders to deliver there ("won't take orders" == "won't accept email"). They might do that because they've had too many orders from that neighbourhood for which their delivery people aren't paid ("unpaid orders" == "email accepted which turned out to be spam"). So they decide it's just not worth accepting orders from your neighbourhood anymore.

    The only point where that analogy falls down is that it's actually much easier for a user of an ISP to change than it is for someone to change house out of a bad neighbourhood :). And of course it's much easier for someone to send their email through an external known-good relay than it is for someone in a bad neighbourhood to relay all their pizza orders through a known-good friend in another neighbourhood.

  187. Re:Whiskey. Tango. Foxtrot. Over. by Pete · · Score: 1

    It's inappropriate for a few reasons, but the one key reason that I noticed is as follows. Legally speaking, when someone rents a property (whether for living in or for running a store) they are in most key respects supposed to be treated as though it's their property. For example, the real owner is not allowed to intrude upon the property except very occasionally, and only for a brief inspection.

    But anyway, the difference with ISPs and their users is that their users are not necessarily recognised as having any sort of legal claim on any of the IP addresses of that ISP. So while the cops (normally) can't shut down independently-leased properties just because someone at a neighbouring property committed a crime, there's nothing wrong with a spam-free ISP refusing to accept email from the network space of a spam-supporting ISP.

    I'm not even going to discuss the difference between an active action, eg. shutting down stores, and a passive action, eg. an ISP refusing to accept email (or other kinds of network traffic) from another. :)

  188. Re:Whiskey. Tango. Foxtrot. Over. by Pete · · Score: 1

    Name one SMTP blacklist - just one - that tries to track non-spamming users of a spam-supporting ISP, and tries to maintain blacklists against those users when they move outside the blacklisted ISP.

    Having trouble? Of course you are. Because there are no blacklists that do that. None. Zip, zilch, zero.

    Next analogy please. If you keep trying, maybe eventually you'll hit on one that doesn't suck quite so badly :-).

    BTW - a good analogy is simple, with the absolute minimum distinct components. A bad analogy is (usually) more complicated... because someone using a bad analogy wants to obscure the fact that it's bad, so they make it as complicated and confusing as possible.

    Hint. Hint hint. :)

  189. Re:Whiskey. Tango. Foxtrot. Over. by Pete · · Score: 1
    With that said, my dedicated box, with 5 IPs assigned to it, was blocked because [...] the tech at the colo didn't bow to Spamhaus's demands.

    It's much clearer and simpler and straightforward and more honest if you put it this way:

    "My ISP took a spammer on as a client. The spammer spammed. The ISP received at least one and probably many complaints. They did not terminate the spammer's account. The IP address used by their spamming client got blacklisted. The ISP still did nothing. A wider swathe of IP addresses belonging to that ISP got blacklisted. The ISP's legit customers started complaining. The ISP finally got rid of their spammer and started trying to get themselves off the Spamhaus blacklist. And so I'm complaining about Spamhaus, because they're obviously the bad guys here."

    *roll of eyes, grin*

    That said, I am nevertheless rather intrigued by your assertion that you, a non-spammer, were trapped under Spamhaus' blacklist of your ISP for several months after your ISP was completely free of spammer scum.

    That sounds rather unlikely, from what I understand of Spamhaus' policies. Can you give any specifics (eg. ISP name, specific date ranges that your IP addresses were blocked, the range of your ISP's IP addresses that were blocked, a Spamhaus record about the incident?... Because if I can verify that you're actually telling the truth, my respect for Spamhaus will drop several notches.

  190. Re:Load of FUD by Paul Graham, competitor to Spamh by jemfinch · · Score: 1

    "In the business of pushing Bayesian anti-spam filtering"?

    Pardon me?

    From what product that uses Bayesian filtering is Paul Graham making money?

    What service is Paul Graham providing that benefits from the use of Bayesian filtering?

    To be "in the business of" something, a person must be "in business" making money from that thing. Where is your evidence that Paul Graham has some financial stake in the success of Bayesian filtering?

    As for myself, I've seen none. And I'm calling shenanigans on your attempt to make people believe otherwise.

    Jeremy

  191. OT to fmaxwell by js7a · · Score: 1
    I bet you got mod-bombed for saying the price-performance ratio of x86 is better than that of PPC. People don't want that to be true because they think there is a reason that it shouldn't be, and because they are afraid of a machine-level monoculure. It will be interesting to see whether Apple consumers show brand loyalty to PPC.

    What bothers me is the legacy support for segmented addressing and all the other legacy kruft. If I were Apple CEO, I would make sure that ARM is supported just like he made sure that x86 was supported five years ago.

    1. Re:OT to fmaxwell by fmaxwell · · Score: 1

      I bet you got mod-bombed for saying the price-performance ratio of x86 is better than that of PPC.

      I've got an "excellent" karma rating and it's not going to be changed by a handful of tricks like that. I'm just disappointed that childish stuff like that goes on here. Discussions should be modded on their merits alone.

      People don't want that to be true because they think there is a reason that it shouldn't be, and because they are afraid of a machine-level monoculure.

      It's a valid concern, but pretending that the PPC will remain a viable competitor to the x86 architecture won't make it so -- as I am sure you are well-aware. Steve Jobs knows that, too.

      It will be interesting to see whether Apple consumers show brand loyalty to PPC.

      I bet they won't. Apple consumers are brand-loyal to Apple. Sure, there are a handful of Apple fanatics who really care about what CPU is in the box, but most are concerned with the UI, applications, etc. As they should be.

      What bothers me is the legacy support for segmented addressing and all the other legacy kruft.

      Fortunately, it doesn't take much CPU real estate. I think that Intel got a lot of grief for the segmented architecture that was unfair. The 8086/88 was designed as an embedded processor. 64K was plenty of space for interrupt service routines, multitasking threads, etc. It was IBM that stupidly decided that was the CPU of choice for a desktop PC.

      If I were Apple CEO, I would make sure that ARM is supported just like he made sure that x86 was supported five years ago.

      ARM is a great embedded systems architecture, but does it really have the horsepower to make it in the desktop world? I don't know.

    2. Re:OT to fmaxwell by js7a · · Score: 1

      ARM is great if you give it a cache with the same geometry PPC or x86 desktops get.