Slashdot Mirror


Spam Blacklist Targets Hijacked Telewest Customers

davidmcg writes "BBC.co.uk reports that UK cable firm Telewest has had almost one million email address blacklisted by an anti-spam firm. The Spam Prevention Early Warning System blacklisted the email addresses because a large number of the machines using them have been hijacked by spammers. Telewest have stated that they knew about the problem and have been working with customers to regain control of their machines."

337 comments

  1. Glad it's not my job... by Anonymous Coward · · Score: 3, Funny

    "Telewest blamed recent virus outbreaks for the sudden rise in the number of hijacked home PCs. "We are currently contacting affected customers to help them clean their PCs which, as you can imagine, is a time-consuming task," it said."

    I sympathise with them, I've tried banging my head against the wall before and it's not fun!

    1. Re:Glad it's not my job... by anagama · · Score: 3, Insightful

      Well, if banging your head against a wall doesn't work, how about shutting down internet access for affected machines. The machine owners would get the hint rather quickly. Secondly, make a liquidated damages clause in the user agreement. Something like, "if your machine is hijacked and you are found to have sent in excess of 25,000 email messages, you owe us $250 -- oh and BTW, here some tools to use to prevent becoming infected."

      --
      What changed under Obama? Nothing Good
    2. Re:Glad it's not my job... by BobTheLawyer · · Score: 2, Insightful

      A clause like that would probably be a "penalty" and therefore unenforceable under English law. In English law you can only recover for your actual loss; a pre-agreed amount is only enforceable if it represents a genuine pre-estimate of the loss. I suspect it would be very difficult, as a legal matter, to show a significant loss.

      There may also be a problem with enforceability to the extent you are penalising someone for the actions of a third party; okay the user would have been okay had they kept all their software up-to-date, but is it reasonable to expect the average user to know this?

    3. Re:Glad it's not my job... by Nogami_Saeko · · Score: 1

      Why they don't just block outgoing port 25 and have a web-interface that users can use to re-enable it if they have the need. Or they could re-route all their outgoing port 25s through an ISP mailserver that could look for spammers and automatically throttle outgoing 25 from certain IPs if they are used excessively.

      Just have something where the user would have to enter their username/psw, and type-in some sort of obfuscated verification code from the website to re-enable their ports.

      If the user re-enables the port and doesn't secure their system, they get automatically cut-off if their machine sends more than (some number of) messages per-day or per-week.

      N.

      --
      "Nothing strengthens authority so much as silence." - Charles de Gaulle
    4. Re:Glad it's not my job... by Taladar · · Score: 1

      It is reasonable to expect them to read the TOS for a service they pay for. And 250$ isn't that much in admin time.

    5. Re:Glad it's not my job... by Dogers · · Score: 2, Insightful
      is it reasonable to expect the average user to know this?

      Yes. Just because the users ARE stupid, doesnt mean they should be allowed to BE stupid.

      Try walking around town with a ghetto blaster playing some obscene music and see how quickly the police/someone from the public try to shut you up.
      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    6. Re:Glad it's not my job... by shades66 · · Score: 1

      i've been wishing that they would cut people off for months. Ever since the blaster worm (i think it was that) Telewest have done feck all about it.

      When I first got telewest the activity light on the front of the modem only lit up when I was accessing the net. These days the light never goes out as there are constant pings against my firewall all from the telewest IP range.

      Oh and don't bother sending abuse any info about possible IP machines that have been infected as they do nothing with them. A number of the IP addresses that I sent them months ago are still busy scanning my machine every so-often..

      --
      ---- There are 10 types of people in the world. Those that understand binary and those that don't
    7. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      Is it reasonable to have to just walk away with your head down in shame because the 'average user' wants his computer HIS WAY, and he thinks Bill Gates is a HELL of a genious, as well as a capitolistic hero? What are you supposed to tell them. "Not fixing your PC EVER again." is all I can think of.

    8. Re:Glad it's not my job... by BobTheLawyer · · Score: 1

      If the ordinary man in the street wouldn't think it reasonable to know this then a contractual provision penalising someone who doesn't is unlikely to be enforceable in English law.

    9. Re:Glad it's not my job... by Tsu+Dho+Nimh · · Score: 1
      The newer spam-bots send their mail through the ISP's regular mail server, just as if the user was sendingn it. The days of connecting to an open relay are gone.

      Your suggestion for monitoring and throttling traffic if it's excessive might work. Few non-business users send more than 50 emails a day. Or the ISP could run a spam filter on outgoing traffic, looking for links to commonly spammed sites and common terms like V*agra.

    10. Re:Glad it's not my job... by Rasta+Prefect · · Score: 2, Insightful
      In English law you can only recover for your actual loss; a pre-agreed amount is only enforceable if it represents a genuine pre-estimate of the loss. I suspect it would be very difficult, as a legal matter, to show a significant loss.

      I don't know about difficulty of showing a loss - Lost customers, admin and helpdesk time due to spam listings adds up in a hurry. That SPEWS listing probably won't go away soon - the amount of time to get delisted tends to reflect the severity of the problem, and if they blocked that large a range they feel it's a severe problem indeed.

      --
      Why?
    11. Re:Glad it's not my job... by Greyfox · · Score: 1

      If the average user wants to connect his computer to the Internet where he can affect other people then yes, I think it IS reasonable to expect them to know that they need to keep their software up-to-date and to take other reasonable steps to protect their systems. I don't foresee any issues enforcing clauses in the contract that state that the user is responsible for the security of his system. Who else is going to be?

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    12. Re:Glad it's not my job... by Dogers · · Score: 1

      Well, maybe.. I'd certainly agree that the users should be cut off, but a monetary fine would be a step too far, I guess.

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    13. Re:Glad it's not my job... by tomhudson · · Score: 3, Insightful
      So why the fuck don't they just give everyone a fixed IP? They CAN do this, on both cable and adsl networks (we've been offered a fixed IP for on adsl free at the office, years after they said it wasn't possible "for technical reasons".

      The real reason - they're just as lazy fucks/ignorant n00bs as their customers.

      They keep singing the same old song, but its their customers that are causing the problem. Police them. Fixed IP. You're a zombie - you're gone. Let them sing "The Monster Mash" for all I care.

      And the politicians/dickheads won't do anything because they are allowed to spam you (nice going guys - pass laws against spam, but include an exemption for yourself). Make politicians have a fixed IP (dr00l).

      The best part about fixed IPs - if we bookmark them instead of doing a dns lookup, we couldn't have to worry about dns outages. Or stupid domain name wars. We do it with 10-digit phone numbers and 4-digit extensions - wtf can't we do it with a n 8-to-12 digit number on the net? Because the average user is STOOPID!

      SPEWS did the right thing. Telewest fucked up.

      Now if SPEWS would BLACKHOLE AOL, I'd notice a lot fewer probes. And while they're at it, maybe, as a public service, blackhole any site containing crapfloods from Maureen O'Gara.

    14. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      > The real reason - they're just as lazy fucks/ignorant n00bs as their customers.

      Nothing like a good generilasition eh? Sir, you are an a***hole and I claim my UKP5.

      Now piss off.

    15. Re:Glad it's not my job... by Anonymous Coward · · Score: 0
      Er, excuse me but HOW IS THE ABOVE A TROLL? It makes perfect sense to me, even if worded a little strongly.

      It is not a troll and shouldn't be marked as one.

    16. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      Email Death Penalty. It's the only way.

      Make people who want to set up a mail server apply for 'certification' (or whatever the hell you want to call it) from their ISP. The 'certification' process is simply supplying a valid, verifiable address and phone number(s).

      After 'certification', the ISP provides a public/private key pair. The public one is actually stored on their (the certifiers) server, and the private one is used to encrypt a header in all email you send. When you send an email to someone, their server sees the encrypted header and queries your certifier for your public key, and stores it for future use (ie: querying your ISP happens just once). Then their server uses your public key to decrypt and verify the header. If it is verified, your email is handled as 'legitimate' (ie: probably passed on to the user, or at least flagged as good). The server (or this can be done by the client, too!) handles the other cases (no encrypted header, bad encrypted header) as it is programmed to.

      So- we now have a guaranteed method of tracing email back to the provider of the sender's internet service. If we get spam, we can alert the sender's ISP, and they can revoke the public key or even shut the spammer's access down. They can also make it a part of the contract that, if someone is found to be spamming, their personal contact information can be made public, and since that info was personally verified, everyone will know exactly who the spammer is, and other ISPs can refuse to offer him/her service.

      The 'Death Penalty' part comes in if the spammer's ISP refuses to act. Any ISP that refuses to cut off (or at least revoke the key of) a spammer has ALL (I repeat: ALL) their email black-holed until they offer proof they cut the spammer off.

    17. Re:Glad it's not my job... by anagama · · Score: 1

      Well, liquidated damages are specifically designed to meet those situations where showing actual cost is is very difficult. A liquidated damages clause is not enforceable if it acts as a penalty as you say though. Given the potential value of losing customers though or admin costs as pointed out by another person, or any other myriad factors, $250 isn't that much.

      --
      What changed under Obama? Nothing Good
    18. Re:Glad it's not my job... by Glendale2x · · Score: 1

      So why the fuck don't they just give everyone a fixed IP? They CAN do this, on both cable and adsl networks (we've been offered a fixed IP for on adsl free at the office, years after they said it wasn't possible "for technical reasons".

      At the ISP I used to work for as a network admin, we assigned static IP addresses to all of our ADSL accounts but told the customers they were dynamic. If they wanted "static" we simply added $5/mo to their bill, but didn't actually change anything. The difference was that if we ever started to run short on addresses in the DSL pool we would start rotating the "dynamic" ones since many people turn the DSL modem off when they turned the computer off, thus freeing X number of addresses.

      I don't work there anymore, but the $5/mo for pretend static IP was just the tip of the iceberg.

      --
      this is my sig
    19. Re:Glad it's not my job... by pv2b · · Score: 1

      Your post advocates a

      (x) technical ( ) legislative ( ) market-based ( ) vigilante

      approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

      ( ) Spammers can easily use it to harvest email addresses
      ( ) Mailing lists and other legitimate email uses would be affected
      ( ) No one will be able to find the guy or collect the money
      ( ) It is defenseless against brute force attacks
      ( ) It will stop spam for two weeks and then we'll be stuck with it
      ( ) Users of email will not put up with it
      ( ) Microsoft will not put up with it
      ( ) The police will not put up with it
      ( ) Requires too much cooperation from spammers
      ( ) Requires immediate total cooperation from everybody at once
      ( ) Many email users cannot afford to lose business or alienate potential employers
      ( ) Spammers don't care about invalid addresses in their lists
      (x) Anyone could anonymously destroy anyone else's career or business

      Specifically, your plan fails to account for

      ( ) Laws expressly prohibiting it
      ( ) Lack of centrally controlling authority for email
      ( ) Open relays in foreign countries
      ( ) Ease of searching tiny alphanumeric address space of all email addresses
      ( ) Asshats
      ( ) Jurisdictional problems
      ( ) Unpopularity of weird new taxes
      ( ) Public reluctance to accept weird new forms of money
      ( ) Huge existing software investment in SMTP
      ( ) Susceptibility of protocols other than SMTP to attack
      ( ) Willingness of users to install OS patches received by email
      (x) Armies of worm riddled broadband-connected Windows boxes
      ( ) Eternal arms race involved in all filtering approaches
      ( ) Extreme profitability of spam
      (x) Joe jobs and/or identity theft
      (x) Technically illiterate politicians
      ( ) Extreme stupidity on the part of people who do business with spammers
      ( ) Dishonesty on the part of spammers themselves
      (x) Bandwidth costs that are unaffected by client filtering
      ( ) Outlook

      and the following philosophical objections may also apply:

      (x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
      ( ) Any scheme based on opt-out is unacceptable
      ( ) SMTP headers should not be the subject of legislation
      ( ) Blacklists suck
      ( ) Whitelists suck
      ( ) We should be able to talk about Viagra without being censored
      ( ) Countermeasures should not involve wire fraud or credit card fraud
      ( ) Countermeasures should not involve sabotage of public networks
      ( ) Countermeasures must work if phased in gradually
      ( ) Sending email should be free
      (x) Why should we have to trust you and your servers?
      ( ) Incompatiblity with open source or open source licenses
      ( ) Feel-good measures do nothing to solve the problem
      ( ) Temporary/one-time email addresses are cumbersome
      ( ) I don't want the government reading my email
      ( ) Killing them that way is not slow and painful enough

      Furthermore, this is what I think about you:

      (x) Sorry dude, but I don't think it would work.
      ( ) This is a stupid idea, and you're a stupid person for suggesting it.
      ( ) Nice try, assh0le! I'm going to find out where you live and burn your house down!

    20. Re:Glad it's not my job... by Lost+Race · · Score: 1
      Now if SPEWS would BLACKHOLE AOL, I'd notice a lot fewer probes. And while they're at it, maybe, as a public service, blackhole any site containing crapfloods from Maureen O'Gara.
      AOL is a crappy ISP in many ways and may very well need blacklisting, but they neither spam (via email) nor support spamming or spammers. They are very aggressively anti-spam and well-clued in that department. SPEWS would not be an appropriate blacklist for them. Maybe aol.blackholes.us or something like that? O'Gara appears to have nothing whatsoever to do with spam, so she also would more properly be in some other blacklist.
    21. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      Your post advocates a

      (x) technical ( ) legislative ( ) market-based ( ) vigilante

      approach to fighting spam.


      Correct.

      Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

      (x) Anyone could anonymously destroy anyone else's career or business


      How?? Please explain the scenario in which this is possible.

      Specifically, your plan fails to account for

      (x) Armies of worm riddled broadband-connected Windows boxes


      Um, if the email is sent direct by the PC, then it will be unsigned, ie: marked as (possible) spam. If it is sent thru the ISP's email servers, it can be authoritatively traced back to them, and they can look in their logs to see who's account was used, and either freeze that account ar face the Email Death Penalty.

      (x) Joe jobs and/or identity theft

      Um, the whole first part provided for a pretty-much-foolproof way to trace the email back to the sending server. Faking the sender would not be possible.

      (x) Technically illiterate politicians

      Um, the EDP is not political.

      (x) Bandwidth costs that are unaffected by client filtering

      ISPs can provide this at the server (just like they provide spam filtering now).

      and the following philosophical objections may also apply:

      (x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical


      Does anyone have that famous quote about people never being able to fly that was made just a few years before Kitty Hawk??

      (x) Why should we have to trust you and your servers?

      You shouldn't. The EDP has nothign to do with "my servers".

      Furthermore, this is what I think about you:

      (x) Sorry dude, but I don't think it would work.


      Nothing ever works until someone tries it.

    22. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      Best...comment...ever. I wish I had mod points.

    23. Re:Glad it's not my job... by pv2b · · Score: 1

      To be fair, it's not original. It's an old chestnut *someone* has to bring out in every spam story.

    24. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      Does anyone have that famous quote about people never being able to fly that was made just a few years before Kitty Hawk??


      "Heavier-than-air flying machines are impossible." -- Lord Kelvin, President, Royal Society, 1895

      or

      I confess that in 1901, I said to my brother Orville that man would not fly for fifty years . . . Ever since, I have distrusted myself and avoided all predictions." -- Wilbur Wright, 1908

      or

      "Airplanes are interesting toys but of no military value." -- Marechal Ferdinand Foch, Professor of Strategy, Ecole Superieure de Guerre

    25. Re:Glad it's not my job... by pv2b · · Score: 1
      (x) Joe jobs and/or identity theft
      Um, the whole first part provided for a pretty-much-foolproof way to trace the email back to the sending server. Faking the sender would not be possible.
      The easiest way to get past a locked door is to get the key. Conversely, if I wanted to send spam under that system, I'd just exploit myself a nice Windows machine (doesn't matter who it is) with a properly set up e-mail certificate (which most all machines will have if that system is widespread.)

      Eh presto, untraceable e-mail. Well, traceable back to the fool whose certificate you stole.

      Now add a false sense of security, and the relative ease of stealing certificates... and you've got a train wreck of an anti-spam system. Sure, you'll be able to block mail from the compromised machine, but you can do that by blocking individual IP-addresses either. The same whack-a-mole still applies, just by whacking individual certificates rather than individual IP addresses.

      And then anti-spam servers will pop up that block all certificates issued from a certain authority... all of this is sounding very familiar.
    26. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      The easiest way to get past a locked door is to get the key. Conversely, if I wanted to send spam under that system, I'd just exploit myself a nice Windows machine (doesn't matter who it is) with a properly set up e-mail certificate (which most all machines will have if that system is widespread.)

      And the first spam that gets reported back to the ISP results in the public key for that user being revoked. Therefore, all other emails from that account will not be able to authenticate, and will be marked as spam. (There would also be a way to 'push' a new or revoked key to the recipients. Actually, the key won't be pushed, a request to re-get the key would be.)

      The legit user can then be contated by the ISP and the PC cleaned.

    27. Re:Glad it's not my job... by pv2b · · Score: 1

      And this is different from using IP addresses... how? Theoretically, a spam filter could just as well revoke all e-mails touched by a specific IP address -- they ARE listed in the headers you know. Adding this functionality, to purge e-mails *after* reception doesn't require certificates to work.

      Basically, I don't see anything in this suggestion that can't be solved using IP addresses. The ISP knows what user uses what IP address at all times anyway, and given a source IP and a time can track down a customer easilly anyway.

      The only thing I see this helping against, slightly, is against users disconnecting and re-connecting and getting a different IP address. Still, this is still just a spam *reducing* method. The spammers will just compromise a few more machines to send through instead. It's not like it's hard to build up a pack of spam-sending zombies or anything -- I highly suspect that the spammers have more zombies than they can use anyway.

      The real big loss here is that Joe Jobs will be the norm rather than the exception. If spammers are forced to use valid e-mail addresses to get through, you can bet that the poor schmuck whose e-mail address was abused is going to get a lot more hassle about it from technically incompetent spam recipients. Not to mention this will actually make some spam filtering *harder*, today you can filter based on rules applying to From-addresses. If this system becomes widespread -- you won't be able to stop any spam by inspecting the From: address.

      Finally, what about the bureaucracy of verifying identity's for issuing certificates? Who pays for that?

      Sorry. This idea is just... dumb. It adds another layer of complexity to the system and causes more problems than it solves.

    28. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      And this is different from using IP addresses... how?

      IP addresses change. DHCP, you know.

      If spammers are forced to use valid e-mail addresses to get through, you can bet that the poor schmuck whose e-mail address was abused is going to get a lot more hassle about it from technically incompetent spam recipients.

      Good. That'll teach the idiot to keep his box patched and clean.

      If this system becomes widespread -- you won't be able to stop any spam by inspecting the From: address.

      Why not? All current spam-blocking methods used now will still work.

      Finally, what about the bureaucracy of verifying identity's for issuing certificates? Who pays for that?

      The ISP. Just like they pay someone now to maintain their spam-filters. Besides, it's not as bad as it seems. It'll mostly be businesses that want to send email themselves, and not induhviduals, who'll be fine using the ISP's email servers. The ID check will vary by ISP, but will probably just mean confirming the contact information (Address, phone, email) and the method of payment (to avoid people setting up a business accoutn w/ a stolen CC). Of course, the ISP might choose to be safe rather than sorry, and do a better check. But that's their call.

    29. Re:Glad it's not my job... by pv2b · · Score: 1

      Right. This is only for businesses who want to set up their own mail servers. I get it. I didn't quite catch that part in your first post, I'm sorry.

      But, you then go on to say that IP adresses aren't a valid way to block, because IP addresses change with DHCP and what-not. Let me ask you: What in the world would a business who uses a dynamic-IP Internet connection do with a mail server that delivers directly to destination mail servers?!

      If they are that big that they want to handle their e-mail themselves, they'd probably use a connection with a static IP anyway. Problem solved. You can block by IP address, no need for that fancy-schmancy new-fangled certificate nonsense.

      If they are smaller, and want to use a dynamic IP address, and still handle outgoing e-mail with their own mail server, they're probably going to want to relay all their mail through their ISP:s mail server anyway. This is what we do at work, we have a dynamic IP ADSL connection, and we run a mail server. The reason we do this is not because port 25 outwards is blocked, but because a lot of e-mail servers won't accept e-mail from dynamic IP address pools anyway. (Ever heard of the DUL?)

      You might not like the DUL, (I don't really like the idea of it either), but if you want to send e-mail from a dynamic IP address, you really want to send it through your ISP's mail server anyway. So, as the ISP, you can just block port 25 outward for all dynamic pools in addition to many receiving mail servers doing the same. Problem solved again, without fancy certificates.

      Now tell me. If users of dynamic IP addresses are forced to send e-mail through the ISP:s mail server, due to the DUL blocking a lot of their mail delivery anyway, and static IP addresses are trivial to block without using certificates -- what possible benifit would certificates give you now again?

    30. Re:Glad it's not my job... by Anonymous Coward · · Score: 0



      If you block the email server's IP, then ALL email from the server is dropped. With my plan, only the email from un-authenticated senders is blocked. All other email gets thru. This will reduce the 'collateral damage' complaints.

      Unless the ISP refused to deal with the spammer, then the EDP goes into effect, and all email is dropped at that point.

    31. Re:Glad it's not my job... by pv2b · · Score: 1
      Uhh. This makes no sense at all.

      First of all, there are two typical types of collateral damage:

      • The case where the entire IP range of a colocation ISP is blocked, because the ISP itself hasn't responded to complaints, and simply allowed the spamming mail server to change IP addresses. This is not the case in the case of Telewest, but I'll discuss it for completeness. In this case, the ISP is behaving irresponsibly by not taking complaints seriously and simply just allowing the spammer to change IP addresses. What makes you think they won't just issue new certificates to the spammer if they receive complaints?
      • In the case of Telewest, the collateral damage was directed at broadband users sending e-mail through Telewest's broadband service. I already handled that case in the grandparent to this post. If the user has a dynamic IP address they can just shove it and send their e-mail through the ISP's mail server like a nice conformer. If they have static IP addresses, there won't be any collateral damage, unless the ISP is irresponsible. (And again, what's to prevent an irresponsible ISP from issuing new certificates just as in the case with the colo ISP?)
      In either way, the process you outlined seems to be only directed at business users, completely ignoring that the bulk of spam actually passes through zombies on home computers connected to broadband conenctions, and not through business connections -- and in the case of the Telewest blocking, the residential users would still not be able to send e-mail because they're not subject to the certificate process.
    32. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      And again, what's to prevent an irresponsible ISP from issuing new certificates

      Because then the whole ISP gets the EDP. Their upstream provider revokes their certificate, which automatically invalidates all the certificates they have created.

      the residential users would still not be able to send e-mail because they're not subject to the certificate process.

      I think you've mis-understood my plan.

      UUNET/Verizon/Joes_ISP_Reseller/SpammerCo/users

      UUNET certifies Verizon, who certifies Joes_ISP_Reseller, who certifies SpammerCo, who is resonsible for it's users.

      Complaints go to SPammerCo. If they don't cut off the spam sending user, complaints go to Joes_ISP_reseller. If they don't do something, Verizon gets a call. Etc. At each level, they face getting their email service turned OFF if they don't either revoke the spammers certificate or cut off their access completely.

      You say my plan is similar to the way it is done now with IPs. Well, FINE. Let's quit arguing and get the more important second part of my plan, the Email Death Penalty part set up. The First part is just to make sure of who the target is, to avoid mistakes. But if the needed information already exists, let's skip that part and get on with the EDPs already.

    33. Re:Glad it's not my job... by pv2b · · Score: 1
      You say my plan is similar to the way it is done now with IPs. Well, FINE. Let's quit arguing and get the more important second part of my plan, the Email Death Penalty part set up. The First part is just to make sure of who the target is, to avoid mistakes. But if the needed information already exists, let's skip that part and get on with the EDPs already.
      All right. We agree that the problem is not technical -- the tools to do what you propose already exists without requiring certificate technology, but administrative. Now we can move on from *how* an EDP is possible to whether it's a good idea.

      First of all, who do you propose should decide who gets EDP:ed and who not? You? A consortium of large ISPs? A group of random roaming anti-spam vigilantes? And who is to watch that the group doesn't overstep it's boundaries and not block an ISP for completely arbitrary reasons?

      A system similar to the one you propose already exists. There exist blacklists that individual mail administrators can use on an individual and voluntary basis. They don't block all e-mail on the Internet, but they block enough e-mail for ISP:s to be concerned when they get blocked. These people who run these anti-spam lists are hot-headed enough already, I sure as hell wouldn't want them controlling *all* the e-mail on the Internet.

      The problem with these systems is that they only harm the ISP and its customers, all because some of their customers don't know how to properly secure their Windows machines. They don't need to be hurt more than they already are to get the message. The spammers themselves aren't hurt. They just move on to zombies on another as-yet-unblocked ISP.

      So, basically, you're proposing to build another bigger and better black hole to encompass all traffic -- in order to reduce collateral damage?! This doesn't make sense. If you want to reduce collateral damage, you make your blocking less aggressive, not more aggressive.

      Apparently, the blackhole systems that already exist are doing their job by blocking enough e-mail to be a major inconvenience and cause the ISP to be more proactive in shutting down spam zombies. Don't be fooled though. This isn't a system to fight spam. This is a system to force ISP:s to fight spam, and it's working.

      The root of the problem is that there's only so much an ISP can do to combat the spam problem. Whacking individual zombies is never going to solve the core problem of shutting down spammers.

      What I suggest instead, to combat zombies, is to block port 25 outwards for dynamic IP users and force them to send e-mail through a central SMTP server. This SMTP server would then be set only to permit a certain number of e-mails per day from a single user. Say, 100. This would be enough for any normal user, but would make individual zombies so much less valuable and raise the cost of spamming considerably.

      Now, what about businesses that need to send out bulk e-mail? The ISP can provide them with the option of turning this limit off. No questions asked, except that they'll shut them down if they receive valid spam complaints. This would stop an ISP from having to play whack-a-mole with individual client machines, but would still allow bulk e-mail through for a small number of users who are easier to handle if something does go wrong.
    34. Re:Glad it's not my job... by Anonymous Coward · · Score: 0

      First of all, who do you propose should decide who gets EDP:ed and who not? You? A consortium of large ISPs? A group of random roaming anti-spam vigilantes? And who is to watch that the group doesn't overstep it's boundaries and not block an ISP for completely arbitrary reasons?

      A ATTworldnet user complains about spam. ATT complains to the owner of the email server the spam came from. THey say 'piss off'. ATT then updates it's list of 'bad' email servers. That list is sent out to other email servers as they connect to deliver mail. Kinda like the Fidonet of old, or Usenet of today.

      The problem with these systems is that they only harm the ISP and its customers, all because some of their customers don't know how to properly secure their Windows machines.

      Maybe the ISP will either do a better job vetting their customers or at least of monitoring them.

      If you want to reduce collateral damage, you make your blocking less aggressive, not more aggressive.

      Hence the idea to block individual email accounts at first.

      What I suggest instead, to combat zombies, is to block port 25 outwards for dynamic IP users and force them to send e-mail through a central SMTP server. This SMTP server would then be set only to permit a certain number of e-mails per day from a single user. Say, 100. This would be enough for any normal user, but would make individual zombies so much less valuable and raise the cost of spamming considerably.

      Now, what about businesses that need to send out bulk e-mail? The ISP can provide them with the option of turning this limit off. No questions asked, except that they'll shut them down if they receive valid spam complaints.


      Why not skip the middle step, allow everyone to send all the mail they want, and shut them down if they receive valid spam complaints??? WHy have the limit? Just enforce the 'no-spamming' rules to begin with.

    35. Re:Glad it's not my job... by pv2b · · Score: 1
      A ATTworldnet user complains about spam. ATT complains to the owner of the email server the spam came from. THey say 'piss off'. ATT then updates it's list of 'bad' email servers. That list is sent out to other email servers as they connect to deliver mail. Kinda like the Fidonet of old, or Usenet of today.
      I think we're talking about different things here. I'm talking about the huge amounts of spam coming from compromised home machines, which is what got Telewest in trouble. You're talking about spammers sending e-mail directly to their recipients from their servers connected to leased lines or in colo facilities. These are two entirely different problems.

      When it comes to blocking e-mail from spammers sending directly to recipients, you already have blackhole servers which solve that particular problem. You ignore complaints, you're added to blacklists of all servers filtering based on specific blackholes. What you're trying to suggest is that the entire follow the same blacklist. Not only is it arrogant to think that one group can somehow get all the world's mail administrators to agree to let them decide who to receive mail from, it's also undesirable and open for wide abuse. I think the current system of blackholing works great, since the filters are applied selectively by the recipients, and if you're not happy with the policy a certain RBL uses, you can always as a recipient choose another RBL. So in essence, this problem is already solved, and in a better way than you suggest. Some ISP:s housing these kind of spammers can even be (and have been) blocked wholesale. There is collateral damage of course, but if the ISP is uncooperative, the legitimate customers will just switch ISP:s.

      When it comes to blocking e-mail sent through zombies, that's a completely different problem, that I have outlined in my previous posts. The reason I want a limit on outgoing e-mails sent through *broadband* connections, is to stop the spam from being sent in the first place. It doesn't matter if the ISP responds timely to complaints, by the time the complaints are received, the e-mails are already away and the damage has been done, and by the time the zombie responsible is shut down, the spammers have already found new zombies to replace it. Blackholing zombies is futile in the long term, and the best RBLs can hope to achieve by doing it, is to encourage broadband ISPs to take better preventative measures, like the one I'm suggesting.

      In short, the Internet isn't one big happy familiy that can be controlled from above. At best, you can get groups of disgruntled sysadmins together cooperating on blacklists, which is what's happening already. This will stop a lot of spam sent through business lines, but in practice does nothing to the problem of spam through zombied broadband machines.
  2. SPEWS by trelanexiph · · Score: 4, Insightful

    odd that the ISP never made an issue of their "Efforts" to clean up their customerbase before ending up in SPEWS. Some people say wholesale blacklisting is ineffective, some whine about false positives, I bet these guys really want to get out of the spotlight so they stop looking incompetant. Well done spews, whoever you are. By the way this article makes a serious mistake:
    SPEWS does not exist (TINS (there is no SPEWS)). SPEWS therefore cannot make announcements of any sort whatsoever, though they do have the Lumber Cartel (TINLC) to speak for them.

    1. Re:SPEWS by godzer0 · · Score: 1

      Try http://spews.org/. It's real.

    2. Re:SPEWS by rich_r · · Score: 1

      Yeah, but anyone who claims to talk for them doesn't- try to find who they are, and you'll find that it's all a bit secretive!
      The GP obviously hangs out on nanae...

    3. Re:SPEWS by Anonymous Coward · · Score: 0

      Hm, i thought SPEWS posted under their name in nanae? I'm wrong here?

    4. Re:SPEWS by derfy · · Score: 1

      No, and anyone who claims to be SPEWS, or to speak on behalf of SPEWS is lying.

    5. Re:SPEWS by mflinquin · · Score: 1

      I don't know if this is a case of incompetence. I was a Telewest user at one point, and accidentally left an open proxy port open; they shut my connection down about an hour later after an automated port scan, so I called them up, dealt with the problem and they reconnected it after a verification scan. Very swish, and I wish more ISPs took this approach.

    6. Re:SPEWS by Anonymous Coward · · Score: 0

      Everyone knows that SPEWS is really the devil.

  3. Good luck calling around by xiando · · Score: 2, Funny

    Spam is a huge problem and any ISP may obviously be subject to blacklisting due to infected machines,Telewest is probably no worse than any other. What I find interesting, though, is that the article states they think 16,000 machines are infected. And the slashdot article claims "have been working with customers to regain control of their machines.". Good luck, I am glad it's not me who's job it is to call all those 16.000 users... (my humble, unimportant opinion is that the users themselves should be responsible for making sure their computers are safe, but .. I'm not important)

    1. Re:Good luck calling around by trelanexiph · · Score: 3, Interesting

      Telewest is probably no worse than any other.
      for a medium size ISP 16,000 machines spewing crap is a huge issue.
      my humble, unimportant opinion is that the users themselves should be responsible for making sure their computers are safe
      I run the AHBL and I am a firm believer in this. You are responsible for your car on the highway, you are responsible for the actions of your children if you have them, and you should be responsible for the damage your computer does to the public network. Currently in the open-proxy and comp-sys-ddos (obviously compromised machines) we have listed over 1.3 million machines. I honestly think that we can do better than to have 1.3 million machines which have been responsible for spewing crap since the inception of the AHBL 2 years ago.

    2. Re:Good luck calling around by dspacemonkey · · Score: 3, Insightful

      No need to call the 16,000.

      I expect the vast majority of telewest's customers are set up as per telewest's instructions as far as email goes i.e. they use telewest's smtp servers. If that is the case, their email is not blocked. It is only those who run an email server that will have a problem.

      Not really a problem either, just make postfix (or whatever mta you're using) send mail via telewest's smtp server itself (relayhost directive). Those who run an email server will notice soon enough and take appropriate action. If they can't work it out then they probably shouldn't be running a server anyway.

    3. Re:Good luck calling around by BrokenHalo · · Score: 3, Interesting
      and any ISP may obviously be subject to blacklisting due to infected machines,Telewest is probably no worse than any other.

      Yes, if that is what it takes to get their attention. Many ISPs adopt an "it's not my fault" approach to users abusing their networks, and anybody who runs any kind of mail server without taking steps to secure it is guilty of abuse.

      Similarly, in this day and age, there is no excuse for users not to know that their machines have been zombied. The simple fact is that unless they are running reliable firewalls or anti-virus programs, they already will have been zombied. I know it is possible to secure a Windows box, but most OEM installations are left totally insecure, and a majority of people never change their computer settings once the machine is on or under their desk.

    4. Re:Good luck calling around by sumdumass · · Score: 3, Insightful

      It would'nt be all that hard to clean this network up. Just block port 25 and allow specific requests thru. Notify email providers/server operaters about the decision a few days in advanced so they can get placed on the list and then put it to work. It would definatly be cheaper then someoen calling 1600 people or having to vewrify they meet with your requirments. Just shoot them an email and say thier service will be diconected if the problem isn't fixed or justified. Those that are infected will be stoped while those that are effected would have an out. If someone requesting an exception is actualy sending spam, it shouldn't be that hard t determin after that and remove them from service completlety. After the situation calms down, open the ports back up.

      In fact, i think it is sort of careless for ISPs to not at least monitor thier common ports for malicious activity. The added trafic from infections could be increasing bandwidth requirments as well as costing the ISPs more money in added equiptment. It just seems logical to try and keep costs down. Whats the chance that 1600 existing users are going to set up a mail server in about a month from each other and then flood the network with trafic that would appear to be comming from thousands of users? This should be spoted easily without some third party needing to get involved. My networks scan email and attachments comming and going at the server level and all it took was a couple of extra seconds to set up. Also snort lets me know of any wierd trafic pattern changes and i can check the difference in logs from several months ago if neccesary. It only take a couple of minutes a day. For this effort you get less people calling and complaining too.

    5. Re:Good luck calling around by Motherfucking+Shit · · Score: 1
      Currently in the open-proxy and comp-sys-ddos (obviously compromised machines) we have listed over 1.3 million machines. I honestly think that we can do better than to have 1.3 million machines which have been responsible for spewing crap since the inception of the AHBL 2 years ago.
      Are you saying that there are 1.3 million positive hosts in the AHBL right now, or that over the past two years, you've had a combined total of 1.3 million hosts? There is a world of difference between these two situations, but I can't tell from your statement which one you meant.

      1.3 million hosts over 2 years is only about 1600 hosts per day, which isn't a lovely picture, but doesn't seem all that bad. If you've actually got 1.3 million positives right now, I want rsync access to run a local copy!
      --
      "BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
    6. Re:Good luck calling around by SEWilco · · Score: 1

      Getting the message to them is no problem.
      Right now there are certain to be people emailing all the people on those lists to sell them antivirus and antispam tools.

    7. Re:Good luck calling around by bowloframen · · Score: 1

      That's not the point. Of course users, in an ideal world, should be responsible for their own machines. But the fact is, we dont live in an ideal world. Many owners are not responsible, and unfortunately, their irresponsibility has consequences for the rest of the world. That's why the rest of the world sometimes has to take actions to fix that breach in responsibility. Same manner of thinking for why the developed nations often help the undeveloped nations with money, food, etc. Not all of it's PR or some "inherent" sense of duty or morality. The greater reason is that helping the poorer countries contributes at least somewhat to a stabler political arena.

    8. Re:Good luck calling around by Anonymous Coward · · Score: 0

      Telewest is probably no worse than any other.

      I'm not sure about that. I've been a telewest cable internet subscriber and a Pipex ADSL over phoneline subscriber. The Telewest connection my firewall a lot more excercise.

    9. Re:Good luck calling around by advocate_one · · Score: 1
      In fact, i think it is sort of careless for ISPs to not at least monitor thier common ports for malicious activity.

      Why are the ISPs responsible for cleaning up the poop left by infections in MS Operating Systems???

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    10. Re:Good luck calling around by Anonymous Coward · · Score: 0

      I have a machjine that is clearly hijacked by something called "istbar". I remove the thing with adaware every time I start the PC, and the next time, it is back again. I dont know what it does, but it uses all the bandwidth on my ADSL connection to do it.

      I have posted before on /. saying WTF can I do to get rid of the beast, but up til now the only workable answer is "run Linux" - I normally do. I even run netBSD on my laptop. This is a machine I only use when I *HAVE* to run Windows. It is running Win2000 professional edition, with all its patches up to date.

      I know many of my relatives have the same istBar sh*te on their machines. I don't know of anyone who has managed to remove it for good.

      A re-install removed much of my legit licenced applications, some of which are not supported on XP, and the machine was re-infected within the hour.

      The consequenses are so horrendous that I expect it will lead to people abandoning Windows, AND THE CRIMINALS REPONSIBLE FOR THIS ACT LIVE IN AMERICAN JURISDICTION so dont blame it on the Chinese or anyone else. How come MS does nothing about this?

      Users can only do so much. We sure as hell cant fix windows to make it secure, cos it isnt open source, and if /. cant tell you how to remove this kind of infestation, then its unlikely anyone else can.

    11. Re:Good luck calling around by Dogers · · Score: 1

      One simple fix- block outgoing 25 to all but the ISP's mail servers and see who, if any, complains.

      These are home accounts, they shouldnt need external mail servers for *sending* mail. Yes, someone will probably complain and say they have a server at home which sends their email, thankyouverymuch, but I think a few people running servers on their home internet accounts is a good sacrifice for cutting spam..

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    12. Re:Good luck calling around by lorque · · Score: 1
      I have a machjine that is clearly hijacked by something called "istbar". I remove the thing with adaware every time I start the PC, and the next time, it is back again. I dont know what it does, but it uses all the bandwidth on my ADSL connection to do it. I have posted before on /. saying WTF can I do to get rid of the beast, but up til now the only workable answer is "run Linux" - I normally do. I even run netBSD on my laptop. This is a machine I only use when I *HAVE* to run Windows. It is running Win2000 professional edition, with all its patches up to date.
      Try this, and after that, this
    13. Re:Good luck calling around by Anonymous Coward · · Score: 0

      Maybe not morally responsible, but it probably makes economic sense for them to do it, unless bandwidth is cheaper than monitoring.

      Why am I responsible to lock my doors just becaus some jerk thinks he deserves the stuff in my house more than I do?

    14. Re:Good luck calling around by Anonymous Coward · · Score: 0

      When I had DSL part of my service agreement was that I would run NO servers of any kind over the DSL connection.

    15. Re:Good luck calling around by pqdave · · Score: 1

      Because they allow MS operating systems on their network?

    16. Re:Good luck calling around by Anonymous Coward · · Score: 0

      Telewest/Blueyonder are SHIT at doing anything about it. Completely fucking useless.

    17. Re:Good luck calling around by inquisitor · · Score: 1

      Don't use just AdAware; Spybot and MS Anti-Spyware (which runs on 2K) have assisted me much in clearing out istbar from the systems of people who're infested by it. If you know Windows enough, HijackThis can help you with manual spyware clearing.

      And switch away from IE - IE on Win2K is still unsafe as hell (not all of the XPSP2 updates have been backported). You're almost certainly regularly going to a website with ISTbar exploit installer, hence the reinstallation. Firefox or Opera.

    18. Re:Good luck calling around by sumdumass · · Score: 1
      Why are the ISPs responsible for cleaning up the poop left by infections in MS Operating Systems???


      Cleaning infections on MS operating systems and monitoring thier networks bandwidth usage are two different things. Think of it like a car with bad breaks. The laws say they need to be in good working order so you would get a ticket if they weren't. The state won't fix them for you though. Just fine you or make "you" fix them if they found out.

      Monitoring thier network just gives them a heads up on the amount of bandwidth they are using/paying for, the amount of harware they actualy need to provide the service on the bandwidth, and possibley notice on any preventable service interuptions. If all the sudden somethign wierd pops up, they can either expand to meet the needs or block ports to cancel negetive effects of malware on joe ignorants machine. Thye can then notify Joe ignorant about thier fix it or loose it policy. Not a very dificult task seeing how the benefits outway the negetives and most all the monitoring can be autometed until somethign happens.
  4. Spam prevention good for me. by Adult+film+producer · · Score: 2, Insightful

    Not the address I use here on slashdot but my regular email addy (which has been active for about 4 years) is virtually spam-free.. at least I don't see much of it. My domain is registered through EasyDNS, with the "plus" package you can setup email aliases for your domain.. everything is filtered through their spamhaus/sbl/dsbl/etc blacklists.. then I use thunderbird with junk mail filtering.

    On average I see one spam make it through my junk mail filter in thunderbird. I've set it up for my mom/dad/brother & sisters as well. Now they laugh at the amount of spam their friends get compared to their own, which is comparable to mine.

    I'm a techno-goof with hardly any understanding of networks and stuff.. If i can do it this easily, anybody can.

    I think maybe spam is overrated.. with the right technology in place, it can be defeated. Although indiscriminite blacklisting by Orbs or whoever doesn't really help the situation :(

    1. Re:Spam prevention good for me. by ciscoguy01 · · Score: 4, Informative

      I think maybe spam is overrated.. with the right technology in place, it can be defeated. Although indiscriminite blacklisting by Orbs or whoever doesn't really help the situation :(

      Overreated? You have lots of people working on solving the spam problem for you. LOTS of effort goes into maintaining those blacklists your provider uses to provide an acceptable spam level for you, and you find it meets your needs.

      The only reason you think it might be overrrated is that you are not realizing what an effort is being put forth for you.

      --
      .
    2. Re:Spam prevention good for me. by trelanexiph · · Score: 1

      apologies my HTML really is blowing hard tonight.

    3. Re:Spam prevention good for me. by pyrrhonist · · Score: 3, Funny
      my HTML really is blowing hard tonight.

      Just sit back and enjoy it, you fool!

      --
      Show me on the doll where his noodly appendage touched you.
    4. Re:Spam prevention good for me. by Anonymous Coward · · Score: 2, Insightful

      And, no doubt, not realizing how much of the fee he pays to his ISP probably goes to: a) bandwidth taken up by spam, b) hardware and software to filter spam, and c) personel to maintain the anti-spam systems.

      One way or the other, you are paying for the spammer's delivery, even if you have managed to filter it out to the point its personal impact is minimal. We all pay for the spammer's stupid get-rich-quick schemes. Spam is still an evil scourge, even if we don't see it thanks to the efforts of many.

    5. Re:Spam prevention good for me. by ad1 · · Score: 1

      But in the business world....you will have to give out your email and SPAM just love to see them. I had to change email from time to time and have like 3 emails at each time to avoid spam and some to keep in touch with friends. Kill the SPAM! Kill the SPAM!

    6. Re:Spam prevention good for me. by Anonymous Coward · · Score: 0

      Damn. If I had points right now, you'd get one. Great post.

    7. Re:Spam prevention good for me. by conteXXt · · Score: 2, Informative

      actually what he has done is a better deal.

      easydns (not his isp) is doing the mail filtering and relaying for him.

      so he pays for bandwidth, and pays for dns hosting + mail goodies.

      Bandwidth is only usd for what gets by the filter.

      If you are hosting a domain for yourself this is a good way to keep the bandwidth costs down.

      --
      The truth about Led Zep should never be told on /. (Karma suicide ensues)
    8. Re:Spam prevention good for me. by Anonymous Coward · · Score: 0

      Although indiscriminite blacklisting by Orbs or whoever doesn't really help the situation :(

      You boast about how little you are affected by spam due SOLELY to someone else indiscriminately taking advantage of Orbs,sbl,dsbl, whatever (everything is filtered through their spamhaus/sbl/dsbl/etc blacklists) and THEN YOU SAY IT DOESN'T REALLY HELP THE SITUATION???

      What exactly are you saying? That blacklisting doesn't work? So why are you and your family laughing at those who DON'T use it?

    9. Re:Spam prevention good for me. by lost_n_confused · · Score: 1

      I think you misunderstand what the parent was trying to say. He was saying it was very easy for an end user to block the spam from his account that other end users can do this too. I don't think he was saying he did it on his own rather then standing on the backs of giants. This is /. so I could be wrong.

      --
      -- To mess up an OS X box, you need to work at it; to mess up your Windows box, you just need to work on it.--
  5. So... whats out of the ordinary for this? by Tezkah · · Score: 3, Insightful

    BBC.co.uk reports that UK cable firm Telewest has had almost one million email address blacklisted by an anti-spam firm.

    So... ISP allows spam zombies to run free on its network, anti-spam firm overreacts by putting entire network on blacklist.

    Is this really out of the ordinary? Weren't they doing this to US ISPs like Comcast until they started disconnecting zombie PCs?

    Is there anything really out of the ordinary here?

    1. Re:So... whats out of the ordinary for this? by rsmith-mac · · Score: 1
      Weren't they doing this to US ISPs like Comcast until they started disconnecting zombie PCs?

      If I recall correctly, Comcast's primary method of blacklist prevention is that they don't allow outbound port 25 access from end-user machines, everyone has to go through their SMTP server; Comcast doesn't get blacklisted because machines on their network can't spam. It's a very effective method to prevent traditional spam, one Telewest may want to adopt. As for disconnecting zombie PC's, Comcast does this very rarely as of late; it's usually reserved for only the worst DoS, worm, and spam machines.

    2. Re:So... whats out of the ordinary for this? by spinfire · · Score: 1

      This simply isn't true anymore. I carefully report all of the spam I get from ISP customers using a script, and I can assure you Comcast users (zombies) send me more spam than any other ISP. Overall spam from ISPs probably accounts for around 50% of the spam I receive.

      Also, I have Comcast at my apartment, and I know they don't block port 25 there. So, they might in some areas, but not many.

    3. Re:So... whats out of the ordinary for this? by Tsu+Dho+Nimh · · Score: 3, Interesting
      "they don't allow outbound port 25 access from end-user machines, everyone has to go through their SMTP server; Comcast doesn't get blacklisted because machines on their network can't spam. "

      The current way of spamming is not to use Port 25 ... the spam-bots run the spam out through the ISP's mail server, JUST LIKE THE CUSTOMERS! A spam-bot sending 100-500 emails an hour, 24x7, doesn't sound like much until you figure out how many spam-bots Comcast has. I get spam from comcast ... enough spam that I whitelisted a couple of people and /dev/null the rest.

    4. Re:So... whats out of the ordinary for this? by eaolson · · Score: 1
      If I recall correctly, Comcast's primary method of blacklist prevention is that they don't allow outbound port 25 access from end-user machines, everyone has to go through their SMTP server; Comcast doesn't get blacklisted because machines on their network can't spam.
      Spamhaus has Comcast listed as the #6 source of of spam in the world. http://www.spamhaus.org/statistics.lasso It's not like Comcast has a lily-white reputation.
    5. Re:So... whats out of the ordinary for this? by Anonymous Coward · · Score: 0

      I swear, timothy is becoming the new michael, only dumb instead of dickhead.

  6. Hmph by oPless · · Score: 4, Insightful

    They're just listing IP ranges. A complete non-newsworthy item. Consumer machines on broadband/dialup should be going through their ISPs smarthosts anyway ... which seems to be standard practice these days, to the point many isps block smtp or redirect port 25 to their own smarthosts.

    Nothing to see here, move along.

    1. Re:Hmph by aug24 · · Score: 4, Informative
      many isps block smtp or redirect port 25 to their own smarthosts

      This is true... my UK ISP, Nildram, simply blocks port 25 outbound for all machines unless certain conditions are met. Very few home users will have any need for this as they will use Nildram's mail server outbound, so only compromised machines which already run smtp services (and have previously passed the open proxy test) can become an issue - a tiny proportion.

      With simple solutions like these, this should be a non-newsworthy item. However, with useless bastards like TeleWest not bothering to do this and permitting unfettered port 25 outbound, it is newsworthy, if only for name-and-shame reasons. Assuming you live in the UK and give a shit, of course ;-)

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    2. Re:Hmph by Anonymous Coward · · Score: 0

      I decent ISP will have a set of 'account tools' where the user can turn things such as spam/virus protection and port access on or off.

      My ISP, by default, turns on spam/virus protection for me and blocks most ports (including 25). But all I have to do is log onto their website to turn the prts back on. If you know enough to need port 25 then you know enough about how to enable access to it.

      This seems a reasonable solution to me, and as far as I'm concerned works well.

    3. Re:Hmph by zerbot · · Score: 2, Interesting

      Then make sure the freemail provider is set up to use the standard port for client submission of email, port 773, or better port 465 in order to use SSL.

    4. Re:Hmph by lost_n_confused · · Score: 1

      So why kill a flea with a hammer and block port 25? Chances are all you have done is stopped one of many problems. If the machine is compromised chances are it is doing more then just spewing email. IMHO it is far better to block all compromised machines , help the customer clean them up, and teach them about safe computing i.e. don't use IE.

      --
      -- To mess up an OS X box, you need to work at it; to mess up your Windows box, you just need to work on it.--
    5. Re:Hmph by Anonymous Coward · · Score: 0

      Yup, Love Nildram for this policy. If you pat £3/month extra, you get a static IP and you can have outgoing port 25 if a continual open relay scan shows you relay free. Brilliant! Telewest couldnt run a free whore house in France!

    6. Re:Hmph by Anonymous Coward · · Score: 0
      Telewest couldnt run a free whore house in France!

      In fairness to Telewest, it's hard to break into a saturated market.

    7. Re:Hmph by mcsmurf · · Score: 1

      Ah didn't know that port yet. But what if virii/worm programers also start using these ports? These ports just seem a workaround for me.

    8. Re:Hmph by zerbot · · Score: 1

      It's meant to be a port only for client submission, which means you authenticate them as a legitimate client of yours before accepting any submissions. If you don't, then you're just acting as a relay. And that would be bad. No biscuit.

    9. Re:Hmph by aug24 · · Score: 1

      You can detect the malicious activity and advise the customer with or without stopping the spam, but you might as well. What earthly good would leaving p25 outbound do?

      J.

      --
      You're only jealous cos the little penguins are talking to me.
  7. Responsibility by NoGuffCheck · · Score: 3, Interesting

    Seems Telewest are actually attempting to rectify this situation, although you have to wonder how it is their responsisbilty.

    FTFA: One hijacked PC on the Telewest network was sending out more than 100,000 e-mail messages per day, he said.

    In cases like these if the offending computer is cleaned with (insert time frame here) then perhaps some negative reinforcement should be considered. fines etc???

    --
    serenity now!
    1. Re:Responsibility by dspacemonkey · · Score: 1

      I'm not sure monetary fines would be a good idea, but I do like your notion in general.

      Perhaps the ISP should block the user (note user, not IP - these will all use dynamic DNS). Simultaneously, all http requests could be replied with a simple page saying what has been done and why, along with a copy of one of the free antivirus apps (AVG, Avast etc) and an anti ad-ware program (e.g. ad-aware). Two downloads later and you are unblocked.

      I wouldn't have thought it would be technically hard to do. I would also have said users would be grateful to know their PC had been hijacked and told how to deal with it rather than pissed off with the interupt in service. Also (here's the biggie for the ISP) it would save bandwidth (= profit! [for the ISP, anyway]).

      Have I missed anything out?

    2. Re:Responsibility by digitalchinky · · Score: 1

      The problem with your logical and ideal solution is that ISP's can't be bothered unless it is 'hurting' the bottom line so badly that the alternatives are far worse.

      Port blocking is vastly easier than the solution you suggest - this is unfortunate since, as you say, the end user might just learn a thing or two.

      Isn't the latest trend to hijack and then spam through the ISP's smtp relay anyway?

  8. Almost a million addresses? by jim_v2000 · · Score: 2, Interesting

    "Telewest have stated that they knew about the problem and have been working with customers to regain control of their machines."

    Somehow I have a bit of trouble believing this. How hard would it be for a large company like Telewest to send it's subsribers a CD with anti-virus/adware removal tools on it? Or an email with such software in it? Or even call users and tell them they have an issue?

    I don't think they've done jack crap myself. And anything they have done is some token gesture to salvage their image.

    --
    Don't take life so seriously. No one makes it out alive.
    1. Re:Almost a million addresses? by Anonymous Coward · · Score: 0

      Somehow I have a bit of trouble believing this. How hard would it be for a large company like Telewest to send it's subsribers a CD with anti-virus/adware removal tools on it? Or an email with such software in it? Or even call users and tell them they have an issue?

      You must be new here, what they should be doing is sending out Linux CDs. =)

    2. Re:Almost a million addresses? by Seraphim1982 · · Score: 2, Interesting

      Somehow I have a bit of trouble believing this. How hard would it be for a large company like Telewest to send it's subsribers a CD with anti-virus/adware removal tools on it? Or an email with such software in it? Or even call users and tell them they have an issue?

      You're first two suggestions would likely expose Telewest to possible litigation. I can imagine users blaming Telewest if the software they were sent managed to screw up their computer in a way that resulted in data lost.
      You're third suggestion is likely to take some time given that it is an issue with thousands people.

    3. Re:Almost a million addresses? by sumdumass · · Score: 1

      Nahh, they just need a big disclaimer stating that there not responcable and you should either purchase somethign or use one of thier freebees they offer. AOL and time warner have been offering free antivirus and in some cases spyware monitoring aplications for quite a while now doing this exact same thing.

      I think the protecting factor here is that they tell you to buy from someone else or use what they packaged for you. If it was a requirment to use thier stuff then i could see the litigation. If it is just a requirment to have somethign and keep it updated then i think a disclaimer would be enough.

    4. Re:Almost a million addresses? by quarkoid · · Score: 2, Insightful
      Somehow I have a bit of trouble believing this. How hard would it be for a large company like Telewest to send it's subsribers a CD with anti-virus/adware removal tools on it?

      Erm... Not as easy as you would have us believe. Firstly, the software has to be sourced, secondly, the licences have to be checked (they could get into trouble, for example, if they gave a CD containing 'free for home use' software to a business), the CD has to be produced and then it has to be distributed to the customers. If the total cost of this broke down to less than GBP1.50 per CD for 16,000 copies, I'd be very surprised.
      Of course, the other issue with this is how do you make sure the end user doesn't throw the CD straight in the bin, but follows the instructions?

      Or an email with such software in it?

      Nooooooooo. People are just starting to get the hang of not running attachments which arrive out of the blue and look genuine. Want to undo all that good work?

      Or even call users and tell them they have an issue?

      Given that this situation has occurred in the first place, it is clear that Telewest don't have a monitoring policy. a) This would have to be put in place, including expenditure on hardware and labour, and b) a team would have to be set up to make the calls. Given that the end user is likely to ask "What should I do", the person making the call has to have at least an idea of what a computer is, and man-hours aren't cheap.

      All three of your proposed solutions would also require Telewest to provide some sort of helpdesk to provide support to their customers, either by providing help with installing/running the software sent, or on cleaning their machine.

      In the UK, the margin on broadband products for volume providers such as Telewest is very low - it's a numbers game. Any action (such as sending CDs, making calls etc.) has an impact directly on their bottom line. They will have done some sort of cost:benefit analysis on tackling this problem and, although I don't know the results, riddle me this: What benefit to the bottom line is there in their reducing the number of infected machines?

      Here's what'll happen: Telewest will scream loudly and make sure that their smarthost is removed from the blocklist. Like other ISPs, they won't care if the IPs allocated to their customers are blocked - in fact, it saves them having to do all the work outlined above! After a week or so, everything will settle down and the whole situation will be forgotton. The bean counters will sit back and pat themselves on the back for not unnecessarily spending money on prevention.

      So, in summary, nice ideas, but not realistic - this is business and all business cares about is the bottom line.
    5. Re:Almost a million addresses? by jdowland · · Score: 1

      Given that this situation has occurred in the first place, it is clear that Telewest don't have a monitoring policy.

      They've had scanners looking at port 25 and performing open relay tests for months if not years.

    6. Re:Almost a million addresses? by BobTheLawyer · · Score: 1

      When I joined, Telewest sent me an e-mail with a link to Zone Alarm, AVG anti-virus and various anti-spyware utilities.

    7. Re:Almost a million addresses? by nogginthenog · · Score: 1

      Yep, my firewall logs can confirm this.

    8. Re:Almost a million addresses? by advocate_one · · Score: 1
      "How hard would it be for a large company like Telewest to send it's subsribers a CD with anti-virus/adware removal tools on it?"

      Telewest (AKA Blueyonder) sent one out to all subscribers about a year ago... it was a little tin box with a first aid symbol on the top with a CDROM inside... absolutely useless and unnecessary to me as I run Linux ;)

      I suppose I could open it up tonight and report back with what's actually on the disk... unless any other Telewest (AKA Blueyonder) user is able to check during working hours...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    9. Re:Almost a million addresses? by geminidomino · · Score: 1

      Apparently what they didn't have was someone to RTFL(ogs), since it doesn't seem to have done fsckall to stem the tide.

    10. Re:Almost a million addresses? by CaptainZapp · · Score: 1
      this is business and all business cares about is the bottom line.

      Isn't that what Mr. Gotti and Mr. Capone thought too?

      So, Telewest shouldn't be held accountable for such a situation going completely haywire? If they just want to smoke their own servers that's fine with me, but when their users spew millions of messages per hour to the global mail infrastructure it's their damn responsibility to clean up their act.

      Assume a chemical plant, which is a security hazard, but which the owners won't clean up, because it cut's into the profits. Well, that's about what Telewest has done and it seems obvious that they needed a good whopping and some public humiliation before cleaning up their act.

      --
      ich bin der musikant

      mit taschenrechner in der hand

      kraftwerk

    11. Re:Almost a million addresses? by Skuld-Chan · · Score: 1

      As someone who works in a call center they probably have a group of people calling these customers up and letting them know where to get help.

      Most of the software to clean this up can be had for free or little money.

  9. easy fix for this crap by timmarhy · · Score: 3, Insightful

    isp's - block port 25 by default, and in account management allow users to unblock it. 99% of people will neveruse it, and those that do will account for such a small number you won't get many support calls for it. shit loads less work then fixing 16000 machines.

    --
    If you mod me down, I will become more powerful than you can imagine....
    1. Re:easy fix for this crap by Anonymous Coward · · Score: 1, Insightful

      Where does this "Close port 25" shit come from? Do you know what you're talking about? Block the port in which direction? Blocking it inbound does nothing; the zombies don't run on port 25 anyway. Blocking it outbound and forcing your customers to use your SMTP server is a bad idea too; it would stop me, a Telewest Blueyonder customer, from using the mail server I use. I havn't use Telewests outbound servers for years; it all goes through my own domain on a server in the US.

    2. Re:easy fix for this crap by Entouchable · · Score: 1

      Not all ISPs by any means, it's still a newer protection standard that's growing. SBC just recently blocked me out 3 months ago. It's completely annoying for techs who know how to manage their comps but it's the best way to protect their networks by far for the time being.

    3. Re:easy fix for this crap by Anonymous Coward · · Score: 0, Informative

      Blocking port 25 would be cracking a nut with a hammer and also be totally ineffective...

      Do you know that spam trojans would never use port 25? why? cause some ISPs block port 25 already. Also it would never stop outgoing mail as no connections to mail servers originate from port 25!

      I'd suggest you get some background reading on SMTP and how it works

    4. Re:easy fix for this crap by jimicus · · Score: 0

      the zombies don't run on port 25 anyway.

      Would you mind explaining to me how a zombie sends email to a mail server other than the ISP's own if port 25 outbound is blocked?

    5. Re:easy fix for this crap by PacMan · · Score: 1
      Do you know that spam trojans would never use port 25? why? cause some ISPs block port 25 already. Also it would never stop outgoing mail as no connections to mail servers originate from port 25!

      I'd suggest you get some background reading on SMTP and how it works

      The block would be on any packet sent from the PC destined for port 25 on a remote system. An exception would be made for the ISP's own mail servers. This covers any source port on the users PC.

      And yes, I do know how SMTP works.

    6. Re:easy fix for this crap by sumdumass · · Score: 1

      SBC tried to lock me out too. Several different sites i have. They were able to add an exception though. It is a anoyance proccess mostly and will take several minutes to hours getting transfered from one department to another but they eventualy open it back up for you.

      SBC also gave me five public ip adresses then thier lower level techs decided i couldn't have a domain pointed to them in the dns. A few demands to talk thier supervisors cleared that one up too. The dns guys told me to call them direct or imeadiatly ask for level 2 support and then tell them to transfer you. SBC makes things as hard as possible for somethign as easy as possible but i guess with a little persistance you can get them on your side.

    7. Re:easy fix for this crap by sumdumass · · Score: 1

      Blocking port 25 inbond would block any open relays. Blocking out bound would also catch this. Every ISP that i have dealt with who block ports will open them for you if you have a reason. All you need to do is call them and ask.. well maybe bitch a little but it gets open.

      Also if you are manageing you domain server you can actualy change the ports you use. You can also find port redirecters that with allot you to send to port 89900 and then they relay it to port 25. I belive these are free too. Or they were the last time i checked into one. no-ip, dynamic dns.com or somethign like that both had one a couple of years ago.

    8. Re:easy fix for this crap by zerbot · · Score: 2, Interesting

      It is also necessary to block inbound packets with source port 25. Spammers often use split piping. Packets from the spammer to the victim are sent from a high bandwidth connection, but with the originating IP set to the hijacked PC, so that the victim sends the acks and small amount of SMTP conversation from the victim server to the hijacked PC (these packets have a source port of 25) thus disguising the spammer's fat pipe, and allowing them to keep from having their more expensive and difficult to set up bandwidth from getting disconnected all the time. If a hijacked PC gets fixed they just move on to another.

    9. Re:easy fix for this crap by ender81b · · Score: 1

      And what about trojans that grab the smtp server settings from OE? And username/password for that matter. Granted it makes it somewhat easier to identify (and slow down the spread of spam) but if it does that you still have to track down the customer and fix them. This would be a band-aid solution to the problem, spam would die for a bit then rocket back up. Not to mention that - although a small problem - you still run into the occassional "network admin" that runs an open relay or has a rooted windows/*nix box and refuse to believe you because they think they are some sort of computer god. Favorite story on that is a coworker called these people because we were getting spam complaints from their IP. So calls the guy, guy yells at him tells him it's a production mail server and no way in hell its infected, blah blah hangs up on him. Said coworker nmaps the machine, finds VNC running on it with no passwords VNCs in and opens up notepad saying "call us ASAP." ;)

      At my ISP we already have to deal with too goddam many spam/virus complaints and weren't not massive like these other ISPs. I don't think we've ever done any sort of time analysis to see how much time it takes to get these people cleaned off on a regular basis but i'd say I spend about an hour a week doing it. i'd hate to see the effort that would go into taking care of 1,000,000 consumer computers.

    10. Re:easy fix for this crap by digitalchinky · · Score: 1

      Finding someone to hop email (for free) is not so easy - the only place I've found that does this and actually works well is http://acc.rollernet.us/ Consider donating some cash to the guys - it's a good service. (I'm not affiliated by the way, just some random nobody)

    11. Re:easy fix for this crap by PacMan · · Score: 1
      Yes, but asymetric routing is difficult to setup on a trojaned PC. Most home PCs with broadband don't have the necessary second network connection.

      On the other hand, it can't hurt.

    12. Re:easy fix for this crap by zerbot · · Score: 2, Interesting

      You don't need a second network connection. You just have the trojaned PC accept everything. If the connection gets dropped due to a retransmit not happening, big deal. They're paying for that fat pipe to have a good connection, and almost all the mail servers the spammer is trying to get to will also have good pipes, so most of the time there are no lost packets to deal with.

      You can use this as an antispam measure, just send a zero window or hold an ack for test and if the sender continues to blow data at you, instant spam sign. If you don't want to or can't muck with your tcp stack, you can pause in the SMTP conversation, but unfortunately some "legitimate" emailers are pipelining their SMTP conversations and not waiting for go aheads but I don't have much sympathy if they get labeled spammers for not following RFC's.

    13. Re:easy fix for this crap by cortana · · Score: 1

      1. You should be submitting mail over the submit port (587).
      2. The poster specified that users should be able to unblock port 25 if they want to. Blueyonder could make this a part of their portal along with the existing account settings.

    14. Re:easy fix for this crap by Anonymous Coward · · Score: 0

      1. The server doesn't accept connections on 587 (I checked). I don't hold any hope at all at convincing a service provider to pop another inbound hole through their firewalls to let in mail on a port other than 25. 2. You don't use Blueyonder I see. Give customers a choice? Ahaha.

    15. Re:easy fix for this crap by Anonymous Coward · · Score: 0

      At work, I block and log outgoing connections to port 25. If a user's computer does get infected, it alerts me that they are infected and it keeps the virus from spreading via email (most dont use oe's settings).

      Why do this? Because there's several hours worth of lag between when viruses are introduced and signatures are available.

    16. Re:easy fix for this crap by Anonymous Coward · · Score: 0

      Im sorry but youre talking a huge pile of shit. Pull your finger out of your ass and think again. So youre tell me if you block the method of spam delivery for 16000 machines, that it wont make any different to the amount of spam delivered? Its people that you, with thoughts like that, they cause problems. Unless you know what youre talking about, i suggest that you shut the fuck up

    17. Re:easy fix for this crap by Anonymous Coward · · Score: 0

      Yes, you do know but the moron that you replied to obviously has no fucking idea

    18. Re:easy fix for this crap by Anonymous Coward · · Score: 0

      and this could be fixed by enabling basic facilities that ship with almost all router/core layer 2 switches - disable source spoofing. Cisco has it in almost all router code, set off by default.

    19. Re:easy fix for this crap by Tripster · · Score: 1

      As a hosting provider I offer both ports 25 and port 26 to clients who have blocking from their ISPs.

      All CPanel based hosts can easily enable this in the system control panel, I only have one CPanel box and this works well.

      On the regular systems you can either do it via a second process listening on port 26 or alternatively you can use IPTABLES to redirect port 26 to port 25 easy enough.

      I had little choice in offering this option since clients on various ISPs have port 25 blocked, in some cases (Telus) they won't even tell the customer the port is blocked and instead blame the hosting provider, pretty pathetic actually.

      Since I also consult a few ISPs I have recommended to them to close that port outbound except via their own SMTP server and to open it for those who request it be open with the caveat of if they ever get infected it gets closed and remains closed.

    20. Re:easy fix for this crap by cyways · · Score: 1

      Recently SBC bought out Southern New England Telephone, the Connecticut telco. A few weeks ago one of my clients suddenly could not forward his outbound mail to my relay server because they had blocked port 25. Did they tell him about this? No. I have no problem with ISPs blocking outbound port 25 if they announce it with lots of fanfare and provide an obvious means whereby legitimate customers can unblock it. Remember this happened on a business DSL connection, not a residential. Your experience shows the level of incompetence at many ISPs. The telcos seem especially clueless.

      For instance, for a while I couldn't send out my clients' mail to addresses in verizon.net. Turns out my SMTP sending server was blacklisted by Verizon, part of their "blacklist the world" approach to spam defense http://yro.slashdot.org/article.pl?sid=05/01/17/12 26237&tid=153&tid=17. (The server's IP address is not listed in any respected DNSBL.) I solved that problem by moving to another IP, but they also block messages that contain my domain in the SMTP "MAIL FROM:" field. Why? Well, I'd bet it has to do with the fact that my domain is joe-jobbed on a daily basis, and these guys apparently think that the From: address in an email actually means something. Can I do anything about this? Apparently not. There's no information on Verizon's website about how to report an inaccurate blacklisting. Apparently a Verizon customer could call them and ask to unblock an IP or domain, but how many of them would even know where to begin? Verizon's initial response to criticisms of their broad-brush blacklisting policy was to suggest using the telephone instead of email.

      That leads me to another gripe. Why can't ISPs use the reverse DNS to inform us whether a given IP address is business or residential? My inbound SMTP block list contains reverse entries for hundreds of DSL and cable IPs worldwide. Given that the telcos, in particular, make a residential vs. business distinction in their telephone services, why can't they use names like adsl-111-222-333-444.res.telco.net and adsl-111-222-333-444.biz.telco.net? I'd rewrite my SMTP rules to accept the latter and reject the former. Of course, many of those business machines are also infected, but since they are so few of them compared to residential users, I could fall back on SpamAssassin to handle the messages they send

  10. I miss the old days by birge · · Score: 4, Insightful

    I think this is a good example of how the democratization of the net has really screwed things up in some ways. The net was never intended to be so centralized (undecentralized?), with huge ISPs serving millions of customers. Of course there's going to be zombie networks. The net wasn't designed to have millions of individual users directly connected from essentially unsupervised subnetworks. Notice that you never hear about a company or university having a significant percentage of their machines taken over, especially not for a long time. Originally, the network was just large organizations connecting their managed networks to the backbones, usually from behind firewalls. But an ISP doesn't watch it's clients computers the way a sysadmin would (nor should they) and thus we have the present, sorry, situation of millions of Microsoft moms unwittingly playing host to a global crime wave.

    It's a good thing we have such secure consumer operating systems, or this could turn into a real problem!

    1. Re:I miss the old days by rob_squared · · Score: 0

      University compuers don't usually get owned because they have an IT staff to manage and protect them.

      --
      I don't get it.
    2. Re:I miss the old days by ahodgson · · Score: 1

      Notice that you never hear about a company or university having a significant percentage of their machines taken over, especially not for a long time

      Universites have the same end-luser problem that ISP's do. Many have started blocking port 25 outbound for the same reasons.

    3. Re:I miss the old days by birge · · Score: 1

      Point taken. In theory, though, they shouldn't have the same problem. A university should be able to have more control over the machines on their subnets than an ISP. An ISP connects disparate "subnets" offsite, whereas a university serves as ISP for a community of users on site, all within the confines of its property. A university has no excuse for not clamping down.

    4. Re:I miss the old days by birge · · Score: 1
      University compuers don't usually get owned because they have an IT staff to manage and protect them.


      That's my point. :-) The original internet was a bunch of large peer institutions who had a least a modicum of reason to trust one another and connect their networks. The model was one of fat local networks connected somewhat thinly together. A few servers would do most of the communicating between subnets. (Remember when mail actually took more than one or two hops and USENET servers only connected to nearby servers?) The current "internet" is really more of a free-for-all star topology with everybody only a few hops from the backbone and data centralized to a handful of servers. I'm sure there are tons of people who know this stuff better than me here, and I hope some of them jump in here, but my feeling is that this explains the reason DDOS attacks are so easy and yet effective.

  11. Re:ATTENTION DROP-OUTS by Anonymous Coward · · Score: 1, Funny

    You appear to have mis-spelled "dollars an hour" as "figures".

  12. Re:SPAM prevention for me ... by Tezkah · · Score: 1

    Exactly, and if you're forced to sign up for something, either use Bugmenot for anonymous login information, or Mailinator, for throwaway email addys.

  13. Telewest faced usenet death penalty 3yrs ago by throwaway18 · · Score: 4, Interesting

    About three years ago a usenet death penalty was issued against Telewest. Before it came into force they stopped all messages spreading out from their main newsserver and began scanning their customers for open newsservers and open proxys.

  14. Re:ATTENTION DROP-OUTS by Anonymous Coward · · Score: 1, Funny

    haha, you wasted years of you're life, while I'm earning seven figures sys-adminning.

    Pesos don't count.

  15. Re:ATTENTION DROP-OUTS by Anonymous Coward · · Score: 0, Funny

    the average slashdotter is to smart to attend

    Are you an average slashdotter?

  16. Amazing by Anonymous Coward · · Score: 0

    SPEWS blocked another million addresses? How the hell did anyone notice? That's like taking a glance at the night sky and saying "hey, there's a new star!"

    1. Re:Amazing by melonman · · Score: 1

      I'm waiting for SPEWS to start escalating to blocking all machines on the same 32-bit range as a known spammer, just to make really sure they get him. It would make about as much sense as their current policy.

      The Telewest customers I know have no other broadband provider to swap to, so pressure on Telewest through this block is zero. All this kind of thing does is penalise innocent users and make a few self-righteous slashdotters feel more self-righteous - unless it's their mail that is being bounced of course.

      I was on the receiving end of SPEWS "let's kick a million people for the hell of it" blocks a while back. It was seriously annoying in principle, but, in practice, I think we had 3 mails bounced among the tens of thousands our servers handle, which says something about how many people in the real world use SPEWS. I guess most of them have realised that a random number generator is about as selective.

      --
      Virtually serving coffee
    2. Re:Amazing by Anonymous Coward · · Score: 1, Interesting

      I can second that. SPEWS is garbage run by zealots. Its basicly basically vigilantism. "We will block a million sites to put pressure on one spammer" (who's machine was probably hijacked). "Then we will leave it active for years since we never bother to update our database." And because they are completely unknown they are also completely unaccountable. This group is a joke and this article lends them far more credibility than they deserve.

      Bottom line is, SPEWS does not block SPAM, it blocks whole huge ranges of IPs in a blackmailing attempt. If you goal is to block spam, SPEWS is useless. If you want to block legitimate mail, SPEWS is great.

      I have yet to encounter any respectable ISP that uses SPEWS as a method for blocking SPAM.

      SPAM is a scourge. SPEWS is a worse scourge.

      The internet does not need more anonymous vigilante groups. I'm sure since so few people use SPEWS to block they will no doubt resort to DDOSing next.

    3. Re:Amazing by Anonymous Coward · · Score: 0

      If nobody's using it, why are your panties in such a wad? It can't possibly be affecting you - it's just like someone writing your IP range on a Post-It on their refrigerator. Why do you care, unless it's being used by someone?

  17. Self help solution by wallior · · Score: 4, Interesting

    When my cable company had any issues with spam from any of their customers, they simply cut off their internet until the customer had their computer fixed. Seems easier than what this cable company is going through. User can either pay to have their computer cleaned and secured, or do it themselves. They then advise the Cable company to put them back on. Lot better for every other customer who is responsible enough to maintain their PCs.

    1. Re:Self help solution by Anonymous Coward · · Score: 0

      "When my cable company had any issues with spam from any of their customers, they simply cut off their internet until the customer had their computer fixed."

      or until they got sued for breach of contract - either the connection is cut off and they're breaching the contract or whilst the connection is cut off they're losing income - they certainly can't charge for a service whilst at the same time refusing to supply it.
      Then start to think of the suits if they cut off people who run businesses from home who get their business damage by being off the net for a week - the ToS may say "we are not liable" but that doesn't actually remove the liability if they deliberately cut someone off, IANAL, etc.

    2. Re:Self help solution by Anonymous Coward · · Score: 0

      But, if the TOS require the subscriber to secure their own machine, then the subscriber may be the liable party when the machine is zombied.

    3. Re:Self help solution by rob_squared · · Score: 0

      In a business model the one thing you try like hell to never do is cut off service to your subscribers. That's why you'll never hear things like: We're cutting off your cable, because you watch too much porn. We're cutting off your magazine subscription, you don't recycle. We're cutting off your phone, because you call people at 2AM.

      --
      I don't get it.
    4. Re:Self help solution by Anonymous Coward · · Score: 0

      People who abuse a service are cut of regularly. Nothing you describe is an abuse. Try abusing your phone line and see how long it lasts.

    5. Re:Self help solution by rob_squared · · Score: 1

      Will I get electrocuted for "abusing" my phone line? :)

      --
      I don't get it.
  18. Re:BBC news crawling, posting cache of site. by dspacemonkey · · Score: 0

    cockband connections?

    Didn't see that in the original.

  19. SPEWS isn't a firm by kaarlov · · Score: 5, Insightful

    SPEWS is not a "anti-spam firm". Check their website at http://spews.org/ for more explanation. And anyone too conserned about false positives should do their due dilligence when picking the DNSBLs they use and notice that SPEWS blocks fairly large netblocks. And there probably will be a lot of legitimate mail sent from bad neighborhoods. SPEWS is a very good tool for blocking spam and educating ignorant ISPs, but it's not suited for everyone.

  20. Email Addresses? by Underholdning · · Score: 5, Informative

    Spews doesn't block email addresses. As a matter of fact, they don't block anything. Spews is a database of IP addresses.

    1. Re:Email Addresses? by dotgain · · Score: 2
      As the headline said, it had blacklisted them, not blocked them. When you list entire networks of IPs, you effectively blacklist many addy's at many domains.

      So I think you've been a bit pedantic.

    2. Re:Email Addresses? by leuk_he · · Score: 1

      One would agree with you... until you get on the list and discover it is very hard to get off this list. Then you discover you are not dealing with policy's setup up according to their anti-spam department.

    3. Re:Email Addresses? by geminidomino · · Score: 1

      How hard is it to get off? You boot your spammers, post to NANAE, and badda bing.

      And yes, I'm speaking from experience. *sends malicious wishes towards spamming ex-client*

    4. Re:Email Addresses? by frankie · · Score: 2, Informative
      No, getting off SPEWS is very easy.
      1. If you are the directly-listed ISP, you kick every single indicated spam source off your network, make the relevant DNS/Whois changes, and post these facts to NANA*. Assuming you are not a repeat offender, you should be removed within days or even hours.
      2. If you are a customer of the offending ISP, you either convince them to do #1 above, or leave them.
      3. There is no step 3. TINLC. TINS3.
      p.s. I am SPEWS
    5. Re:Email Addresses? by iangoldby · · Score: 1

      If you are a customer of the offending ISP, you either convince them to do #1 above, or leave them.

      and therein lies the problem... The people who are hurt most have no real power.

    6. Re:Email Addresses? by thogard · · Score: 1

      Is that a lie or total BS?
      If sell me a net connection that isn't usable because you also sell to spamers then I can dump the contract and bail because you didn't provide your end of the deal. Thats all there is to it. Anyone clueless enough to sit and take it doesn't count.

    7. Re:Email Addresses? by Dimensio · · Score: 1

      and therein lies the problem... The people who are hurt most have no real power.

      Waah. They're giving money to a company that openly supports and abets criminal activity. Cry me a river because their email isn't being delivered to ISPs who have stated that they do not want it.

    8. Re:Email Addresses? by Anonymous Coward · · Score: 0

      You have plenty of power. You have the power to stop giving your money to people who allow spam.

    9. Re:Email Addresses? by dotgain · · Score: 1
      Good point, but consider this. The ISP is providing their end of the deal. They're accepting your outbound mail, queueing it, and sending it on to it's destination.

      It's completely beyond their control that the destination refuses it because they subscribe to SPEWS. A destination not subscribing to SPEWS would recieve your mail, one that does doesn't.

      So the ISP's lawyer would maintain that the connection is usable and provided in good faith. That they have spammers for customers and are listed with SPEWS is another matter entirely.

    10. Re:Email Addresses? by Desert+Raven · · Score: 1

      I see no problem.

      #1 My ISP got careless, and got listed.
      #2 The listing expanded to cover my address range. (level 2)
      #3 I raised a huge ruckus with my sales rep and the tech staff.
      #4 They kicked the spammer, modified their AUP and generally cleaned up.
      #5 They posted to NANAB, explaining the actions they took, and their plans on staying clean.
      #6 The listing was cleared.

      If your ISP is not willing to do what it takes to get rid of their spammers, then they are part of the spam problem. If you are still willing to give them money, then you are part of the spam problem.

      No sympathy here.

    11. Re:Email Addresses? by iangoldby · · Score: 1

      Of course you can bail out.

      But the problem is that I can't take my email address with me. That means that if I want all non-spam emails to reach me I'm no better off switching ISP than staying with one that blocks emails originating from SPEWS-listed servers.

      It's all part of the same problem. In my view, spam is evil and collateral damage is more evil still.

    12. Re:Email Addresses? by iangoldby · · Score: 1

      Don't worry - I'm not after your sympathy. What I am after is a reliable email service. One that doesn't treat collateral damage as an acceptable cost of spam, and that doesn't force me to change my email address due to someone else's incompetence (either sending or failing to stop spam).

    13. Re:Email Addresses? by AnotherBlackHat · · Score: 1

      Spews doesn't block email addresses. As a matter of fact, they don't block anything. Spews is a database of IP addresses.


      Well, technically spews.org blocks every IP address, since they don't operate a mail server.

      And while they don't force anyone to use their "service" they also don't publish any statistics about how bad their false positive and false negative rates are.

    14. Re:Email Addresses? by Desert+Raven · · Score: 1

      What I am after is a reliable email service. One that doesn't treat collateral damage as an acceptable cost of spam, and that doesn't force me to change my email address due to someone else's incompetence (either sending or failing to stop spam).

      Then find an ISP that does not tolerate spammers.

      As far as I'm concerned, there's no collateral damage when an ISP gets listed. It's not OK to sit on the fence anymore. You are either anti-spam or pro-spam, and an anti-spam person would *never* consider it OK to do business with a company that tolerates spam. Since you *are* willing to do so, by association, you are pro-spam.

    15. Re:Email Addresses? by iangoldby · · Score: 1

      Then you are simply wrong. I am both against spam and against collateral damage. You cannot argue with this - I know my own mind. I am sorry if I do not fit into your black-and-white world.

  21. Re:SPAM prevention for me ... by Horizon_99 · · Score: 1

    Sneakemail is you friend.

  22. Re:BBC news crawling, posting cache of site. by Sircus · · Score: 3, Informative

    Next time, if BBC News is "crawling", please look at your own link. BBC News is about as good as Google at staying up the whole time. A couple of extra visitors from SlashDot will get lost in the underflow.

    --
    PenguiNet: the (shareware) Windows SSH client
  23. Re:SPAM prevention for me ... by Mike+Markley · · Score: 1

    Until a spammer notices your domain name and tries a directory harvest/dictionary attack...

  24. Re:SPAM prevention for me ... by the_womble · · Score: 1
    Only give out your regular email address to PEOPLE you communicate with.

    Until one of them forwards an email, CCing to all their friends, suddenly an awful lot of people have your address and it gets picked up from somewhere.

    I have had to educate several people about (the existence of) BCC

  25. heh.. S.P.E.W.S by Ka+D'Argo · · Score: 1

    anyone else find that kinda amusing? [p] [b]S[/b]pam [b]P[/b]revention [b]E[/b]arly [b]W[/b]arning [b]S[/b]ystem

    --
    Aw Frell this
    1. Re:heh.. S.P.E.W.S by OneSmartFellow · · Score: 0

      Spam Prevention Early Warning System

    2. Re:heh.. S.P.E.W.S by Ka+D'Argo · · Score: 0

      yea i fucked up and forgot html formating for that reply :(

      --
      Aw Frell this
  26. You can't run, you can't hide... by xstonedogx · · Score: 4, Insightful

    ...but you can stand and fight.

    Wait until one of those PEOPLE gets a virus or trojan on their PC and your address is harvested. Or they forward you - and 600 other people - a joke. Or god forbid they post it on their website as part of their friends list, or what have you.

    Try having an email address like bob@some.tld. Try hosting a domain and forwarding root@, webmaster@, postermaster@, abuse@, et cetera to your account. Spammers have lists of simple and obvious usernames that they send to every domain they can think of hoping for hits.

    I want the public at large to be able to contact me in some instances, so I publish my email addresses unobfuscated. I have 'bob@some.tld'-style email addresses. I forward root@ (and et cetera) to my other accounts for my domains. I couldn't hide even if I wanted to hide.

    If you run your own email servers, take a look at this advice. Since the time I took the advice (a couple months ago) I have received *one* spam and that was appropriately tagged as spam and filtered into my spam folder. As far as I can tell there haven't been any false positives.

    (I realize the irony in my use of a gmail address for my slashdot account, but that's not about spam. That's about a whole different issue: anonymity.)

  27. Is blocking port 25 really useful? by tx_kanuck · · Score: 2, Interesting

    I only ask since I don't know. Isn't it possible to run an SMTP server on a different port then 25? It only has to send out from a zombie machine, not recieve mail, so why not run it on say....port 2000? Or is it the fact that it has to send *to* port 25 that's getting blocked?

    --
    Now, if that makes sense to anyone, could you please explain it to me? I think I've confused myself.
    1. Re:Is blocking port 25 really useful? by dotgain · · Score: 1
      It's possible, but it's an incredibly stupid idea.

      Nobody else would guess that you're running an SMTP server on port, say 34225, and DNS has no way of telling them that.

      So you'd get no spam at all, but you'd get nothing else either.

    2. Re:Is blocking port 25 really useful? by Stephen+Williams · · Score: 4, Informative

      is it the fact that it has to send *to* port 25 that's getting blocked?

      Yeah, that's right. The source port is irrelevant.

      -Stephen

    3. Re:Is blocking port 25 really useful? by AndroidCat · · Score: 1
      Not always stupid. You could do that for a private email network and not have to deal with attempted traffic from the great unwashed spammers and worms. Setup mail servers between company branches, only accept connections from a trusted list, and give that email an express route through the spam blockers and filters for zero false-positives.

      I get hits on my port 25 several times a day (Godzilla sfx) and I'm on an ADSL DHCP IP address. If they ever found a server, I'm sure the attempts would go to the next level.

      --
      One line blog. I hear that they're called Twitters now.
    4. Re:Is blocking port 25 really useful? by Secrity · · Score: 1

      There are several circumstances where the use of an alternate SMTP port is desirable, and RFC 2476 recommends port is 587 as an alternate SMTP port. Unless you have prior arragements with the recipient mail server to accept mail on an alternate port, it is extremely unlikely that they will receive your email using any port other than port 25. SMTP servers that use alternate ports are doing so for a reason, and they are very likely to use an authentication system.

    5. Re:Is blocking port 25 really useful? by dotgain · · Score: 1
      Yeah, you're right. My postfix install listens on a couple of high-numbered ports for local processes to inject mail straight into the Q without spam/virus checking.

      But I have to listen on Port 25 somewhere, or my company can't recieve mail without informing everyone of the other port number to use.

      I'm guessing the original poster meant running a production, email server on a different port, maybe he didn't.

      Back on topic, none of the Zombies on the infected machines could be expected to connect to ports other than 25. So blocking 25 outbound should go a long way to stopping them from working. The only case it would be useless is if the zombies in turn used another open relay running on a different port.

  28. port 25 by andrewweb · · Score: 1

    "Or is it the fact that it has to send *to* port 25 that's getting blocked"

    Yes.

    Some more responsible ISPs block port25 as a matter of course, except to their own mail servers which hopefully you won't be able to spam through madly without being noticed. If at all.

    Got a legitimate need to run your own mail server? Ask your ISP for it.

    Way to go.

    1. Re:port 25 by Anonymous Coward · · Score: 0

      Some more responsible ISPs block port25 as a matter of course, except to their own mail servers which hopefully you won't be able to spam through madly without being noticed. If at all.

      Bullshit. This is done to prevent spam filtering. The only reliable way of doing spam filtering is by checkint the IP address the connection came from. Anything in the headers can be faked[1]. ISPs are filtering port 25 to force both spam and legitimate e-mail to come from the same IP address, so that we can't block the IP address the spam comes from without also blocking all legitimate e-mail. And this is not only for their own customers, if someone receives an e-mail from me, and a spam mail from a zombie at the same ISP, they will come from the same IP. Block the zombie and you also block legitimate e-mail.

      So, once this is in place, we are back to filtering on fake headers, contents of subject and
      body, which the spammers seem to have more luck getting through than legitimate e-mail. This is the method used by SpamAssassin, and while it generally does improve things, I have seen spam with a score of -2.2 ("unlikely to be spam"), where as mail from work comes in and 1.4 ("might be spam") even after turning off all the HTML crap that Outlook usually puts in.

      [1] Before you say "except the last received: line", remember that it is added by the server itself, from the IP address the connection came from. Checking the IP or checking the line that was just added with the IP are different ways of doing the same thing.

    2. Re:port 25 by nogginthenog · · Score: 2, Informative

      Telewest already block incoming (maybe outgoing) connections to Windows NetBIOS ports. It shouldn't be too hard for them to add port 25 too.

      I am a Telewest customer, but I do not use their mail services (MS Exchange!!!) so this would affect me. However, my email provider allows me to connect to an alternative port (IIRC 2525). I believe this is quite common. GMail uses some non-standard port too.

      BTW, Telewest is probably one of the best ISPs in the UK. Reasonably priced and they have no bandwidth caps, which unfortunately seems to becomming the trend these days with UK ISPs.

    3. Re:port 25 by Anonymous Coward · · Score: 0

      > Got a legitimate need to run your own mail server? Ask your ISP for it.

      Yes, I pay for the service (and I do a better job than them - personalised etc).

    4. Re:port 25 by Anonymous Coward · · Score: 0

      Yup, exactly right and all ISPs should, by law, have to have this implemented because, as we know, all spammers operate "within the law" *cough*

  29. Who actually uses SPEWS!? by 91degrees · · Score: 1, Flamebait

    It's a useless service that is in no way forthcoming about its purpose, and has no accountability.

    The admins who run it are jumped up petty control freaks who think the internet should be run according to their whims, and they seem totally unable to decide whether it's there to stop spam, or punish spam hosters.

    When challenged, they make all sorts of excuses and justifications without any ability to back their aguments up. They have made no impact on spam at all, and their service reduces the functionality of the internet more than SPAM does.

    The SPEWS list is worthless as anything other than an indicator of potential spam. Any admin who takes blocks all of SPEWS doesn't deserve his job.

    1. Re:Who actually uses SPEWS!? by zerbot · · Score: 1

      I use SPEWS and some of my customers do too. Neither SPEWS nor "the admins who run it" "make all sorts of excuses and justifications" when challenged. SPEWS is anonymous and communicates with no one. Their accountability comes from the fact that they follow their posted criteria for listing an IP. If you like their criteria, you're free to use it. If you don't then don't use it. If they were to start making numerous errors or listing outside their policies people would stop using them. There are a large number of lax providers that cleaned up solely to get out of SPEWS. So I would say that they have had an impact on spam.

    2. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Neither SPEWS nor "the admins who run it" "make all sorts of excuses and justifications" when challenged.

      How do you know? Do you happen to know who runs it? I find it hard to believe the guys on news.admin.net-abuse.email are not totally responsible for it. This is purely specualtive though.

      Their accountability comes from the fact that they follow their posted criteria for listing an IP. If you like their criteria, you're free to use it. If you don't then don't use it.

      Their "posted criteria" are hard to find. Their justifications for these criteria are even harder to find. Whoever designed their website reeally needs to learn to use whitespace.

      There are a large number of lax providers that cleaned up solely to get out of SPEWS. So I would say that they have had an impact on spam.

      Yet this has not reduced spam. They mildly inconvenience spammers, and even then only affect the small scale ones.

      If it was remotely effective, spam would be falling. Not rising.

    3. Re:Who actually uses SPEWS!? by Anonymous Coward · · Score: 0

      PHBs who are really upset about incoming spam love the idea of RBLs. Although I am philosophically opposed to RBLs for some of reasons you mention, I use them because I specifically instructed to do so.

      And, yes, they do work, though, my own tracking has been nearly as effective as the RBLs.

      You can also do quite a bit with spamassassin, and a very low threshold (mine's set at 3.0).

    4. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      SPEWS just covers way too much. Everything but SPEWS would probably make a good whitelist, but you need better heuristics than that if you're just trying to block. With a few other lists and some sort of intelligent scoring mechanism it works quite nicely.

      I just find that many people who use SPEWS delight in the collatoral damage. If use it to punish spammers, or spam hosters, then they need to realise they are doing this with very little support from the community they're trying to protect.

    5. Re:Who actually uses SPEWS!? by zerbot · · Score: 2, Informative

      I have been around long enough to have some educated suspicions as to some people who might be running SPEWS. Only one of those people posts occasionally to nanae, and never about SPEWS. Few real admins have the time to post much, and I suspect that SPEWS is run as an adjunct to their normal duties as admins of mail servers. They probably started out trading information with each other, and eventually decided to make it public for others to use as long as it didn't land them in SLAPP suit land. The FAQ is quite clear. IP addresses are listed when 1) they emit spam that is received by those who run SPEWS, 2) they are advertised in spam received by those who run SPEWS, 3) they are likely to emit spam because they are under the control as the same entity that is permitting #1 or #2, and the spamming is continuing, or 4) they are likely to emit spam because they are under the control of someone associated with previous spam. SPEWS has most certainly reduced spam to me and to my customers who use it. Since the machines belong to me and my customers, we have the right to refuse email from anybody for any reason whatsoever.

    6. Re:Who actually uses SPEWS!? by zerbot · · Score: 1

      If they had very little support, then why would anybody like Telewest care if they got in SPEWS?

    7. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Whitespace! It's your friend.

      I've always had the impression that people get listed if they host IP addresses that have emitted SPAM as well. Am I mistaken?

    8. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Who says they care about SPEWS? If I worked fro an ISP, I'd simply care that many of my users are infected with trojans.

    9. Re:Who actually uses SPEWS!? by zerbot · · Score: 2, Informative

      Experience shows that if a provider has one spamming customer that they won't do anything about, then it won't take long before their spamming customers start to proliferate, as spammers clue in that they are a spam friendly provider and start to set up shop. Sometimes providers have moved legitimate customers out of their IPs and put spammers there because the spammers are willing to pay more money than the legitimate customers. They put legitimate customers on IPs that were spamming in order to cause deliberate collateral damage and direct the customer's ire at those who are trying to block spam. They lie about having cut spammers off, they lie about IPs being inhabited only by legitimate customers. There's no reason for a provider to keep even a single spamming customer, and if they balk at removing that customer, the lies and flimflam are almost certain to follow. SPEWS is an early warning system, and as such lists IP's that have an elevated risk of spamming, even if they haven't spammed yet. If you're not interested in an early warning system, don't use SPEWS. Me, I like it. Sorry about the whitespace, I'm just passing through (damn getting paged in the middle of the night and then twiddling thumbs while someone farts around trying to decide what they wanted you for).

    10. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      So, is that a yes? The FAQ isn't all that clear about it.

    11. Re:Who actually uses SPEWS!? by Anonymous Coward · · Score: 0

      You're quite correct. SPEWS routinely blocks /24s and higher to "punish" providers. "Innocent" users affected by such blocks aren't actually "innocent" at all to them since they are keeping the "spam-supporting" provider in business; nevermind the possibilities that:

      a) The IP space wasn't in SPEWS at time of contract signing (and let's face it, had the customer asked the provider if they hosted spammers, the answer would have been "no" no matter what the truth)
      b) Those contracts tend to be long-term, and I'm pretty sure SPEWS isn't offering to help anyone pay to break such a contract (and this isn't as trivial as switching cell phone carries before your year is up -- such providers typically aim at business customers and the contracts are structured thusly)
      c) As much as they'd sometimes like to claim otherwise (mostly when proclaiming that the blocked victims are "getting what they deserve"), the SPEWS guys aren't big on second chances and one mistake is likely to incur their wrath

      Posted anonymously in case someone tries to spew (pun intended) garbage about these complaints just being sour grapes. Yes, I am listed in SPEWS because someone on a /24 near me sent some spam. Like, two years ago. Sour grapes? Maybe. But I thought their service was garbage before then, too.

    12. Re:Who actually uses SPEWS!? by zerbot · · Score: 1

      If you mean what I think you mean, then yes. If you own an IP and a customer that is renting it from you spams and you don't disconnect them, you can expect to have your listing escalated until all of your IP space is listed as a preventative against the inevitable arrival of more spammers.

    13. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Okay. Where does it say this in the FAQ?

    14. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Yet this wasn't listed in the criteria that were "quite clear".

    15. Re:Who actually uses SPEWS!? by zerbot · · Score: 1

      Entry 5 in the FAQ deals with network address ranges that haven't actually sent out spam (yet). 21 and 22 deal with the difference between level 1 and level 2 and talks a bit about listing whole netblocks. I use level 1 on addresses that might be expected to receive mail from the general public, and level 2 with whitelisting of customers on addresses that are for customer support.

    16. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1
      Entry 5 in the FAQ deals with network address ranges that haven't actually sent out spam (yet).
      They are listed because they have been set up by known spammers and spam support operations, most with a demonstrable repeated history of spamming or spamming services. They are also listed if they host websites advertised in spam, as this too falls under spamming services - these listings normally occur if the owners of that network address range do not remove the offenders.
      It's not clear though. "Spam support operations" is not defiend, but does not mean to me an ISP that host a few spammers as well as others. Perhaps somethign like, "We also list IP addresses advertisied in spam, and netblocks of ISPs that host spammers. Sicne we list entire netblocks, this will also include IP addresses on non spammers that subscribe to the same service as a spammer".

      21 and 22 deal with the difference between level 1 and level 2 and talks a bit about listing whole netblocks.

      Still vague. "Spam support organsiastion" is not defined anywhere. How about "Level 2 contains IP ranges of all ISPS that host spam sources including their non-spamming customers"?

      They need to spell it out for idiots like me that don't understand the jargon.
    17. Re:Who actually uses SPEWS!? by zerbot · · Score: 1

      I suppose so.

      If you provide a service to a spammer (even if the spammer doesn't use it to spam with, such as a website), or a good (such as spamware) whose primary use is to facilitate spamming, then you are a "spam support operation". This includes providing DNS, email services, web hosting, bandwidth, spamware, or any of these used to harvest or provide addresses, etc. If you're making it possible or easier for the spammer to spam, you're a spam support operation.

      The problem with spelling it out is that spammers continue to come up with creative new ways to spam that might be outside an exhaustive list.

      I don't understand why a legitimate ISP would not terminate "a few spamming customers" or insist that Joe Home get his zombified PC fixed. But time and time again, ISPs demonstrate that they won't do it without getting whacked.

    18. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      "Innocent" users affected by such blocks aren't actually "innocent" at all to them since they are keeping the "spam-supporting" provider in business;

      Curious though. Telewest aren't making money from the spammers. The article explicitely states that the PCs are infected with trojans. The spammers aren't giving a penny to Telewest. Yet SPEWS still lists them.

    19. Re:Who actually uses SPEWS!? by AndroidCat · · Score: 1
      Amazing. Who did you talk to who claimed to be speaking for SPEWS?

      I've never met them and don't know if they're control freaks, and have never heard them making excuses (or anything at all). And yet all the black-hats claim that they have. Is there a special phone number to SPEWS that you only get when you sign a contract in blood with Al Ralsky? (Or are you like the Something Awful zombies who confused the nanae newsgroup with SPEWS?)

      --
      One line blog. I hear that they're called Twitters now.
    20. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Considering the NANAE group responds to criticisms about SPEWS, and the spews site suggests using that group to communicate, and given the hysterical loyalty to the SPEWS, I suspect some of the regulars there are responsible. It's not that much of a logical leap.

      Since they insist that you deal with spam in their way, and don't consider there might be any extenuating circumstances, I consider them control freaks.

    21. Re:Who actually uses SPEWS!? by AndroidCat · · Score: 1
      It's not that much of a logical leap.

      Not much of a logical leap, no.

      --
      One line blog. I hear that they're called Twitters now.
    22. Re:Who actually uses SPEWS!? by Dark_Gravity · · Score: 1

      91degrees meet clue by four.

      Just because SPEWS doesn't work for you, doesn't mean that it doesn't fit the needs of others. I have no problem with your dislike of SPEWS and I endorse your decision not to use it. I draw issue with your choice to attempt to berate those that find SPEWS meets their needs. You also cross the line when you begin putting your words in SPEWS mouth.

      You make some fantastic claims about the responses of SPEWS administrators to challenges. You lie. SPEWS does not participate in Q & A. If you bothered to read the content on their website you would know this. You would also know that the list data is good for both stopping spam and punishing spam hosters.

      SPEWS doesn't need accountability. No one is forced to use SPEWS data. The server admins that choose to use SPEWS data are accountable for their own networks. That is the extent of accountability needed to make things operate properly. Try to remember that email is not the only medium left for communication. If your email is refused, use a telephone, or send a letter in the mail.

      If protecting your private property against abuse by criminals makes you a jumped up petty control freak, then sign me up.

      SPEWS has a marked effect on the spam on my networks, and hasn't caused any problems worse than spam, but there are few problems worse than spam right now.

      Seeing as how I pay for my connectivity and all of my network hardware out of my own pockets, I don't see it as your place to determine that I don't deserve my job as administrator of my own networks simply because SPEWS meets my blocking needs and not yours.

      I refuse all SMTP from China and Korea, and it works for my needs. That policy would not work as well for my friends with family in Korea! There is no one-size-fits-all solution to spam short removing from the Internet all the spammers and anyone that buys from spammers.

    23. Re:Who actually uses SPEWS!? by Slashcrap · · Score: 1

      They need to spell it out for idiots like me that don't understand the jargon.

      No they fucking don't! It's quite simple - if you don't like their policies or justifications don't use their fucking list. That's all it is - a list.

      How retarded do you have to be to not grasp such a simple point?

      So fucking what if they block people that haven't spammed? If you're not using their list it doesn't affect you.

      If you're on their list and want to communicate with someone who is using their list then you're screwed. You can ask the recipient to stop using SPEWS or to whitelist you. You can just use your ISP's mail server like you're supposed to. And if your ISP's mail server is on the list, you need to find an ISP that isn't run by disgusting spam supporting fucktards.

      Any fucking questions?

    24. Re:Who actually uses SPEWS!? by Anonymous Coward · · Score: 0

      They're making money by not having to actually secure their network. If they were required to manage it properly, they couldn't have added so many clueless paying customers so quickly.

      Maybe they're not getting checks from spammers, but they *are* making money from the existence of the environment that spammers need (hordes of unsupervised M$ boxes)

    25. Re:Who actually uses SPEWS!? by Anonymous Coward · · Score: 0

      "Considering the NANAE group responds to criticisms about SPEWS"

      Too bad their only response to complaints is "get another ISP that doesn't spam LOL".

    26. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      No they fucking don't! It's quite simple - if you don't like their policies or justifications don't use their fucking list. That's all it is - a list.

      I don't fucking know what their fucking policy is. Their FAQ is not clear. If it was it would make it exceedingly clear that it lists IP ranges that are in the same block as those of spammers. and would make it totally clear that a "spam friendly ISP" is any ISP that hosts spammers and doesn't deal with them in the SPEWS accepted manner. Did you actually read what I said?

      This is the real problem. SPEWS apologists like you don't care what opther people have to say, don't even read what other people have to say and come up with a stock response that is so full of holes I don't know where to start.

      But it does affect me, it's more than a list, and oly idiots use it.

    27. Re:Who actually uses SPEWS!? by Filik · · Score: 1

      I got a new ISP and a new static IP, then noticed that it was listed in SPEWS as a dynamic IP which seemed enough to get my mail blocked. I sendt them an email about this error and after a short while it was removed from their database. -Filik

    28. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Just because SPEWS doesn't work for you, doesn't mean that it doesn't fit the needs of others. I have no problem with your dislike of SPEWS and I endorse your decision not to use it. I draw issue with your choice to attempt to berate those that find SPEWS meets their needs.

      Well, that's your right. I stil think that these people are fucking morons.

      You also cross the line when you begin putting your words in SPEWS mouth.

      If SPEWS has an opinion on this matter I invite them to respond to this post. I think it's quite clear that some of the regulars in NANAE are responsible for the list. Any statement of the purpose of functionality of SPEWS that is frequently made in that group, and is not contradicted, I will consider to be something that SPEWS administrators agree with.

      But I should clarify... If you want to use SPEWS on your own network, then that's fine. I think it's a poor product, but I'm pleased it works for you. If you run servers as a service for other people or on behalf of a company and use SPEWS then you show a complete lack of understanding of the requirements of your users.

    29. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      No they're not. Spammers are costing them money. They're trying to keep the costs down, but this is a long shot from actually making money from them.

    30. Re:Who actually uses SPEWS!? by frankie · · Score: 1

      If I worked fro an ISP, I'd simply care that many of my users are infected with trojans.

      91degrees, please pay attention.

      RTFA: TELEWEST DID *NOT* CARE UNTIL *AFTER* THEY GOT 56 /18 BLOCKS LISTED IN SPEWS.

      That's the bottom line. They are cleaning up their act because their customers are complaining. Their customers are complaining because they are listed in SPEWS. They are listed in SPEWS because Telewest has been completely ignoring their spam zombie problem for a LONG time.

      SPEWS WORKS. You may not like their methods, but they get results when other gentler attempts have failed.

      As a long-time NANAer (heck, I supported its initial RFD/CFV) I can tell you that SPEWS has very simple rules, they follow those rules, and anyone who has argued with you about SPEWS is in fact NOT SPEWS.

    31. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      RTFA: TELEWEST DID *NOT* CARE UNTIL *AFTER* THEY GOT 56 /18 BLOCKS LISTED IN SPEWS.

      Where does it say that?

      That's the bottom line. They are cleaning up their act because their customers are complaining.

      It doesn't say that either.

      Telewest were trying to deal with the spam. They still are. Well done to SPEWS for making them do what they were already doing.

      SPEWS WORKS. You may not like their methods, but they get results when other gentler attempts have failed.

      Does it work? I still seem to be getting spam. Seems to me a bad idea to clobber the effectiveness of the internet for a trivial reduction in spam.

      As a long-time NANAer (heck, I supported its initial RFD/CFV) I can tell you that SPEWS has very simple rules, they follow those rules, and anyone who has argued with you about SPEWS is in fact NOT SPEWS.

      Ah! great. So you happen to know who runs SPEWS then. Perhaps you should point out that telewest is not a spam support organisation since they're not hosting spammers.

    32. Re:Who actually uses SPEWS!? by Skapare · · Score: 1
      It's a useless service that is in no way forthcoming about its purpose, and has no accountability.

      Actually, it doesn't matter. Some people do find it to be useful. I find it to be useful. They don't need to state what their service does, as this can be determined through their very consistent actions. Words don't matter; actions do. And SPEWS has carried out some very effective actions.

      As for accountability, that belongs with whoever uses it. If it isn't doing what YOU want, then don't use it.

      The admins who run it are jumped up petty control freaks who think the internet should be run according to their whims, and they seem totally unable to decide whether it's there to stop spam, or punish spam hosters.

      Why do you think it has to be just one of those? I'm quite happy with it being both at the same time, which is what their actions show to be taking place.

      When challenged, they make all sorts of excuses and justifications without any ability to back their aguments up.

      They who? I bet YOU have NEVER spoken with the people that run SPEWS. If you have, say who they are to back up your statement.

      They have made no impact on spam at all, and their service reduces the functionality of the internet more than SPAM does.

      This is entirely false. I have seen numerous ISPs stop hosting spammers and turn around and clean up their act as a result. In fact I have actually helped 3 of them do that.

      The spam problem would be worse than it is now without SPEWS. I do have my own private blacklists that catch a substantial amount of spam. If I were to turn off my private lists, SPEWS would end up blocking about 80% of the incoming spam. I call that effective. And considering my spam volume is on the order of 700 pieces a day, it makes a huge difference in functionality as well.

      Maybe about 10 pieces of email per year that I actually wanted get lost as a result. It's easier to deal with than to deal with the onslaught of spam. Maybe your email box just doesn't get enough for you to realize the scope of the problem.

      The SPEWS list is worthless as anything other than an indicator of potential spam. Any admin who takes blocks all of SPEWS doesn't deserve his job.

      Different administrators have to deal with different dynamics of their user/customer base. The decision to use, or not use, SPEWS varies based on these factors. I have advised many of my clients to NOT use SPEWS, and have advised many others to go ahead and use it. Some in the middle I have suggested to try it and see.

      But my guess is you are most likely pissed off about SPEWS because SPEWS has listed your home email server. Because you want to use cheap services, and not make any effort to make your own email server stand out above the crowd the the ghetto in an obvious way, you want to find someone else to blame.

      --
      now we need to go OSS in diesel cars
    33. Re:Who actually uses SPEWS!? by Anonymous Coward · · Score: 0

      Spammers may indeed be costing them money, but the *net* effect of it all is that they are saving money by allowing an environment to exist which helps spammers. Do you *really* think that there would be so many compromised boxes allowed to function as spam hydrants for so long if that were not true?

      Go to a university (a clueful one) where they *don't* make more money every time some dingus decides to connect to that there Interweb. See how long your machine is allowed to be a zombie.

    34. Re:Who actually uses SPEWS!? by ClemensW · · Score: 1

      Whoa! Spanked spammer whining?

      I love that sound!

    35. Re:Who actually uses SPEWS!? by frankie · · Score: 1

      telewest is not a spam support organisation

      People receive spam that comes from Telewest IP space. Res Ipsa Loquitur.

    36. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Huh?

      Telewest are the victims here. You might as well blame the people who are receiving the spam.

    37. Re:Who actually uses SPEWS!? by frankie · · Score: 1

      If an ISP does not block outbound 25 by default, and some of their customers are spam zombies, and they are notified about the offending PCs, and they don't stop the zombies, then that ISP is most definitely NOT the victim. Telewest is grossly negligent, therefore spam-supporting.

      Preventing spam from your network is not just an afterthought or a courtesy, it is a RESPONSIBILITY. If you shirk it repeatedly, you should be held accountable.

    38. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Actually, it doesn't matter. Some people do find it to be useful. I find it to be useful. They don't need to state what their service does, as this can be determined through their very consistent actions. Words don't matter; actions do. And SPEWS has carried out some very effective actions.

      It seems a lot of people who use it don't consider what it does and just assume that by using it they'll block all spam. Which they probably will, but they'll do that by turning off their server as well. If ISPs are responsible for the actions of their customers, then I believe SPEWS should also be responsible for at least some of the actions of the list users.

      They who? I bet YOU have NEVER spoken with the people that run SPEWS. If you have, say who they are to back up your statement.

      Specifically, I can't say. If I were to give you a list of names of people I suspect, it would pretty much be a list of the top 20 posters on NANAE. It's an ediucated guess. But perhaps I'm wrong. Does it matter? I consider people who run it and the people who encourage its use all to be at fault.

      This is entirely false. I have seen numerous ISPs stop hosting spammers and turn around and clean up their act as a result. In fact I have actually helped 3 of them do that.

      I said it has made no impact on spam at all. I didn't say it made no impact on ISPs that were unfortunate enough to host spammers. The spammers just find another host. Has any spammer ever gone out of business because he couldn't afford hosting fees?

      Maybe about 10 pieces of email per year that I actually wanted get lost as a result. It's easier to deal with than to deal with the onslaught of spam. Maybe your email box just doesn't get enough for you to realize the scope of the problem.

      Well, if you use it for your own email then that's up to you. I still think you're using a crappy product, but what do I care?

      There are other solutions to the problem. There are better solutions. Disconnecting your computer from the internet would solve the problem, but not in a satisfactory way. The fact that you have an inadequate partial solution to the problem does not mean that is the only solution.

      But my guess is you are most likely pissed off about SPEWS because SPEWS has listed your home email server. Because you want to use cheap services, and not make any effort to make your own email server stand out above the crowd the the ghetto in an obvious way, you want to find someone else to blame.

      Never happened to me. I just have a lot of sympathy for the little guy. It's not about the spammer. It's not about the ISP, who I quite agree should take a tough line against spammers. The problem is the ISP's other customers. I do not see it as their responsibility to deal with spam. That's your problem. Not theirs. I don't see them at fault for not knowing about the ISP's other customers. I see them as being deliberately targetted by a lot of admins for something that is beyond their control.

    39. Re:Who actually uses SPEWS!? by 91degrees · · Score: 1

      Perhaps some of their customers might actually want to use port 25. I hear it's quite useful for email.

    40. Re:Who actually uses SPEWS!? by Dark_Gravity · · Score: 1

      But I should clarify... If you want to use SPEWS on your own network, then that's fine. I think it's a poor product, but I'm pleased it works for you. If you run servers as a service for other people or on behalf of a company and use SPEWS then you show a complete lack of understanding of the requirements of your users.

      Unless you are providing email services for a bunch of neckbeards...

      ;-)

    41. Re:Who actually uses SPEWS!? by frankie · · Score: 1

      And those users should be allowed to re-enable it. But it still should be blocked by default. And it definitely doesn't excuse Telewest for failing to cut off zombie hosts after receiving spam reports.

    42. Re:Who actually uses SPEWS!? by AndroidCat · · Score: 1
      Usually the poster has said which unreponsive void is their ISP by then.

      What do you want the peanut gallery to say? "Right-o, we'll fire up the SPEWS signal and you'll have your personal little hole punched in the block within the hour!"

      --
      One line blog. I hear that they're called Twitters now.
    43. Re:Who actually uses SPEWS!? by Skapare · · Score: 1

      When an ISP does turn around and stop hosting spammers, whether the result of SPEWS or not, that does reduce the spam somewhat. There are 2 mechanisms at play with this. A few small time spammers may give up, or at least be inactive for a while as they search for a new ISP. That's less spam. And the other mechanism is that the spammers that remain active are bunched tighter into less address space, increasing the spam to legitimate email ratio enough that a few more networks may be able to block the ISPs hosting those spammers. That helps, too.

      Neither of us really knows just how much spam we would have today had SPEWS never come into existance, or had shut down sometime in the recent past. But I speculate that in the short term there is some advantage to having SPEWS as described above, and in the long term, as the number of spammers concentrated into specific address spaces reaches a "critical mass", those addresses can be blocked at border routers. At some point the spammers will find other addresses, but as this cycle repeats, more and more ISPs learn not to become the hosts of these exploding spammers.

      The quality of a list like SPEWS depends on its history. SPEWS has a history of blocking ISPs, but it also has a history of doing so when there is a genuine problem at those ISPs.

      SPEWS works for me. But I also do whitelisting. I could go to the extreme and block the entire internet and allow email in only as whitelisted. Using SPEWS in place of blocking the entire internet is certainly better. Whitelisting in addition to using SPEWS does work for me.

      So what would you suggest as a means to at least work equally well as SPEWS, without using SPEWS? I also use some other blacklists. But I do not filter based on content for two reasons. One, it has resulted in far more false positives than SPEWS ever has. And two, it is just philosophically wrong. The definition of spam has absolutely nothing to do with content; it's all about the behaviour of the sender in selecting (or more specifically not applying any selection process at all) the addresses to send to. One person's spam could be another person's great opportunity. I get marketing messages from several companies that I have asked for and want.

      As to an ISP's other customers, the problem I see is that as long as they keep paying the ISP, the ISP won't have any incentive to remove spammers aside from the bandwidth wasted on their end. Were it not for blacklisting, zombie spam (at least at the level we have today) would not be something that ISPs hosting infected customers would care about. The bandwidth on their networks from it is not that big. But if they weren't faced with these blacklistings, fewer of them would be trying clean up the problem. The customers of an ISP are in a lot better position to influence the ISP policy than the peers on the internet. They do have more control (as little as there might be).

      --
      now we need to go OSS in diesel cars
  30. Irresponsible to let infected machines stay online by D4C5CE · · Score: 4, Interesting
    "have been working with customers to regain control of their machines."
    Not knowing the particular details of what went on at that provider, but hardly anyone can claim to "have been working with customers" without even (probing and) shutting down their Internet connections in the first place as soon as they knew that
    • these customers' PCs were infected
    • they were (at least about to be) hijacked
    • the users were unaware or incapable of fixing the problem, i.e. it was demonstrably out of control for the systems' owners.
    With 3+ GHz CPUs, 512-1024 MB RAM, 300+ gigs of HDD and on a 3+ Mbit/s broadband connection, every ISP knows that off-the-shelf PCs can still appear to work under an amazing (crap)load today, and they have more potential to wreak havoc than entire major companies or universites a decade ago ... I have seen (completely unsuspecting) home users' machines infected with no less than 200 different (!) "manifestations" of malware on them at once, several times this year already - from the kind of guys who don't even grasp the concept of a rescue disk, to whom a computer can only be "broken", and who just go and buy a new machine, every year or so, when their previous one comes down to a crawl. Even worse, the "old" machine (full wormload included) is usually passed on (and networked again) to primary-school kids or elderly relatives who are even more clueless.

    None of them had ever received that call from their providers (which could even be automated to some extent):

    "This is Incredible Internet Services Inc. - We regret to notify you that your Internet connection had to be temporarily shut down for violation of our Acceptable Use Policy: (specified ...) You may have overlooked an infection of your PC or an access to your home network accidently left open. To get you back online as soon as possible, a complimentary 30-day trial copy of Soandso Security Software is already in the mail to you. Once you have finished disinfecting and securing your systems, or if you need any additional help, please call customer support at ..."
  31. Should point out.... by Tehrasha · · Score: 5, Informative
    ..that no email addresses have been blacklisted.

    Telewest has had almost one million email address blacklisted by an anti-spam firm.

    SPEWS does not block email addresses, it lists IP addresses. Its up to admins who use SPEWS to decide whether or not to use the listing to block email coming from those IPs.

    If the users in those affected IPs use a legitimate email server, they can still send email to their hearts content. Only people running their own mail servers and direct-to-mx traffic would be affected.

    1. Re:Should point out.... by Flamerule · · Score: 0
      [...] no email addresses have been blacklisted.

      SPEWS does not block email addresses, it lists IP addresses. [...]
      Informative? Hardly. Look in the dictionary under blacklist: "A list of persons or organizations that have incurred disapproval or suspicion or are to be boycotted or otherwise penalized." The SPEWS blacklist fits that exactly.

      And just to make it crystal clear, they even have a tech definition: "A list of e-mail addresses of known spammers."

    2. Re:Should point out.... by Tehrasha · · Score: 1

      There isnt one single email address 'user@someisp.com' listed by the SPEWS blocklist. SPEWS only lists IP addresses and ranges. And if nobody uses the listings, nobody gets blocked. SPEWS blocks nothing.

    3. Re:Should point out.... by geminidomino · · Score: 1

      You might try looking at SPEWS instead of a dictionary. It's a DNSbl. It works on IP addresses. There's not a single email address in it.

      GP is right, Parent is way off.

  32. Pay and you are removed from the list by tmk · · Score: 1, 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.

    1. Re:Pay and you are removed from the list by zerbot · · Score: 2, Insightful

      Why would you pay $50 to be removed from a spam list that is probably used by only a few people? The only power a spam list has is in how many people use it to filter mail with.

    2. Re:Pay and you are removed from the list by tmk · · Score: 1

      You are right. I don't know how many admins use UCEprotect, but local authorities as the municipality of Munich seem to use this list.

    3. Re:Pay and you are removed from the list by Anonymous Coward · · Score: 0
      They say this was approved by local authorities, but this is bullshit. Local authorities can not brake federal law.
      It's not even covered by local law. They invoke an article (Art. 34 Para. 5 BayMeldeG) which covers publication of data by the authorities, and is useless anyway to avoid 6 TDG which states that every commercial service has to disclose name and address of a contact person.
  33. IP addresses are not email addresses by Anonymous Coward · · Score: 0

    The summary is misleading. No email addresses are being blacklisted. IP addresses, or in this case blocks of IP addresses, are being listed in a DNS based database of suspect hosts. SPEWS is an organization that attempts to pressure Internet service providers (ISP) in to resolving the issue of spam originating from their networks by the rather controversial technique of listing increasingly broad swaths of the ISP's IP address space in the SPEWS DNS database. Mail servers can query the SPEWS database to see if any connection is coming from a listed address, and use the response to help decide if they should accept mail from that host.

    IP addresses are not email addresses. Broadly put, IP addresses are numbers that identify hosts on the internet.

    Blocking individual email addresses doesn't work because the email address is given entirely as an article of faith. Even if a spammer used the email address of the person whose computer he/she was spamming from the email address would still be useless as a filter criterion because the spammer could just as easily put an email address of an innocent person on the message. This could then be used as a denial of service attack on the email server that blocked messages based on the email address. For example, if an email server blocked email this way, to prevent, say, mike@aol.com being able to send email to that server, all I'd have to do is send a spam that was addressed from "mike@aol.com" (which is, by the way, utterly trivial to do -- most people could figure out how to do it from their own email program in mere minutes with no additional knowledge about how email really works "under the hood").

    IP addresses can useful as a basis for filtering spam because in practice IP addresses are unique identifiers. Also, since the IP address can't be readily faked in the conversation that needs to take place between two computers in order to deliver email, filtering messages that come from hosts known to be sending spam is much less likely to ensnare innocent users. This isn't completely true, but most legitimate email comes from sources that are uniquely and consistently identified by particular IP addresses.

    Of course, this is where the controversy over SPEWS arises: rather than merely listing individual computers that are sending spam, SPEWS often lists entire ranges of IP addresses in order to put pressure on ISPs to cut off the flow of spam from those machines. If mail is blocked based on a listing in SPEWS, then it's once again possible that mail from innocent hosts may be rejected. (Although there is dramatically less danger of denial of service attacks, unlike the hypothetical blocking based on email address discussed earlier.)

    The author of the BBC article seemed to have a tentative understanding that there is difference between email addresses and IP addresses, but the person who submitted the story to Slashdot appears not so well informed. (Of course, most people scarcely need to know that IP addresses exist, so this is entirely reasonable, but it seemed worth correcting so as to avoid any undue confusion -- although normally I'd anticipate Slashdot readers would be familiar with both email and IP addresses ;-)

  34. Re:Irresponsible to let infected machines stay onl by mpe · · Score: 1

    I have seen (completely unsuspecting) home users' machines infected with no less than 200 different (!) "manifestations" of malware on them at once, several times this year already

    200 is not unusual, in some case you can multiply it by 10.

  35. My experiences with Telewest by Lurks · · Score: 2, Interesting
    I can't win. For ages I've run my own mail server for myself and two other flats in London that run off my 4MB Telewest cable modem. Unfortunately there's a number of these blacklist operators that have mapped out the IP space of the cable modems themselves and I find the odd email gets bounced.

    So awhile ago I switched to using their own mail servers and now I'm getting even more blocked. Argh!

    Broadband providers will actually have to start taking responsibility for this sort of thing and disconnect zombie infected clients. Not just for the good of the Internet as a whole but so their OWN customers don't jump ship to a small DSL provider to avoid this irritating blacklist nonsense.

    Interestingly a couple of years ago, or so, they cut me off because they eroneously claimed that my mail server was relaying. It wasn't, it never was. They refused to take my calls and sort it out and I had no option to cancel the service and write a letter of complaint to their management. I spent another six months on a DSL provider before running back, tail between legs. Maybe they've taken the view that enforcing these tests (which are necessary, I will admit, although they did seem inept at it) costs them customers like me - users of their highest and most expensive tier of service? But surely the biggest problem is zombies on family PCs via the basic service?

    Note: Other than that, Telewest/Blueyonder is by far and away the best broadband service I have used. Never any evidence of contention and it's many times more reliable than any DSL service (and I've tried six) with pretty much bugger all down time.

    1. Re:My experiences with Telewest by PigleT · · Score: 1

      > Broadband providers will actually have to start taking responsibility for this sort of thing and disconnect zombie infected clients.

      Interestingly, blueyonder *do* have a suitable clause in their Ts&Cs, or at least did when I signed-up (~3.5yrs ago), that security was the user's problem and that they may well disconnect idiots. I really wish they'd acted on it more.

      > they eroneously claimed that my mail server was relaying. It wasn't, it never was.

      I blocked their scanner with an icmp-admin-prohibition in the firewall. Easiest option yet ;)

      What's even more ironic is that these were the idiots who used M$loth sExchange to handle incoming mail, routing it *based on the bloody To: header* (when the reason it was hitting their MXen was the envelope - a Bcc-to-self job) and then complained they had a spam problem! And never *ever* solved the support case I opened concerning it! Small wonder I also ran my own MTA to bypass the problem. Bah.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    2. Re:My experiences with Telewest by BillGodfrey · · Score: 1
      ... but so their OWN customers don't jump ship to a small DSL provider to avoid this irritating blacklist nonsense.

      Thats possibly exactly what SPEWS want to happen.

      "Hey, our custimers are leaving us."
      "Darn, we'll have to cut the zombies off."

    3. Re:My experiences with Telewest by aug24 · · Score: 1

      Next time you want to jump ship, try Nildram if they're in your area. I've never had /any/ downtime on the service, and even their sales monkeys understand questions like 'Can you give me a static IP? Do you block port 25 by default?'. Compare with NTL's chaps who on being asked 'Do you hire cable modems' said 'yes, what channels do you want'...

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    4. Re:My experiences with Telewest by Lurks · · Score: 1
      Yes, I've tried Nildram too. Good stuff. The problem is they're DSL and basically it's just not as good as cable. Not as fast, not as low latency, not as reliable.

      After six different providers on both business and domestic tarrifs, I don't make this statement lightly.

    5. Re:My experiences with Telewest by Lurks · · Score: 1
      ... Thats possibly exactly what SPEWS want to happen.

      Undoubtedly but I contrasted that with the fact that their last effort on cracking down on this sort of thing (in the case of mail relay), they got wrong and it lost them a customer. So Telewest may be wary of pissing anyone off too.

    6. Re:My experiences with Telewest by aug24 · · Score: 1

      I think it helps if you're in the heart of the city, about twenty feet from an exchange ;-)

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    7. Re:My experiences with Telewest by Anonymous Coward · · Score: 0

      Frankly, you shouldn't be running a mail server off the end of a "consumer grade" retail cable or dsl line. Your cable or dsl is to connect your desktop host to the internet.

      With professional managed hosting as cheap as it is these days, there's no reason NOT to pay the $5/month to get managed hosting.

      Yup. telewest have a big problem. They either clean up their network, and that includes customer boxes, or stay listed. If that means disconnecting users until they certify clean boxes, that's what's needed. Cost recovery? You betcha! About $100/box would be a good deterrent to opening that email attachment or clicking the strange link, ... or for running Windows.

    8. Re:My experiences with Telewest by Anonymous Coward · · Score: 0

      Get a new provider, make Telewest clean up the mess that theyve made for themselves, by telling them with your wallet. Either that or put up with the collateral damage of using a company that doesnt give a shit about spam.

    9. Re:My experiences with Telewest by Anonymous Coward · · Score: 0

      Yeah but you wont find yourself on a block list and having to deal with a sub-10 IQ monkey on their "helpdesk" when you do find yourself blocked

  36. Re:Irresponsible to let infected machines stay onl by Jarnis · · Score: 3, Insightful

    No can do. High percentage of hijacked machines are in a state that no security software can rescue them from.

    Reinstall windows is the only thing that helps. After that the security software is a good thing.
    However, having seen dozens and dozens of computers where the user was clueful enough to buy a security software, only to find out the system was already in a state where no security software will even install, I'm quite confident that most of these 0wned setups are already way beyond what F-Secure, Norton or the likes can do while installing.

    And sadly reinstall windows can usually just get them owned again (recovery disks having no service packs, so the thing will get first Sasser-derivate into the system 30 seconds after the recovery install is done)

    What computer manufacturers would really need to do is to ship everyone a free replacement recovery disc to get the system up with all patches. Funded by MS because it's their holey software. However, this would actually cost money, so instead people are left on their own.

  37. Old news by Neophytus · · Score: 1

    Telewest have been blocklisted by SPEWS for quite literally YEARS! I remember discussing this with their support team in 2002/3 and them merely saying that they wouldn't pay their "charity" fee because that amounts to blackmail. Quite reasonable, IMO. I imagine it's quite a moneyspinner, extracting cash from corps who technically could afford it.

    1. Re:Old news by zerbot · · Score: 1

      SPEWS doesn't have a "charity fee" and never has. I suspect you mean SORBS.

    2. Re:Old news by Neophytus · · Score: 0

      Geh, my bad. So many acronyms of so many blacklists.

    3. Re:Old news by gorbachev · · Score: 1

      SPEWS does not ask fees for delisting. The only thing they care is that the spam stops.

      You (or Telewest) have them confused with some other DNSBL.

      --
      In Soviet Russia, I ruled you
    4. Re:Old news by Slashcrap · · Score: 0, Troll

      Geh, my bad. So many acronyms of so many blacklists.

      And so few brain cells, apparently.

    5. Re:Old news by Anonymous Coward · · Score: 0

      Still not as few as those that use SPEWS on ISP systems to block.

  38. No serious admin should use spews bl by weeeeed · · Score: 1, Flamebait

    They are randomly blocking whole netblocks without having any clue about what is really going on. That way they blacklisted whole countries like China, Hong Kong, etc.. While it is arguable if a random geek in the US needs to receive mails from China, any bigger corporation with any contacts to foreign companies does.

    In short, spews is USELESS for any serious business, and any admin that is using that blacklist for tagging should other BL lists (e.g. Spamcop.net)... any admin in a bigger company using that BL for killing mails should go to look for a new job, because he is obviously highly incompetent.

    We had many cases where we were unable to deliver our mails because some moron admin in a big international company with worldwide suppliers and customers was using spews for rejecting mails.

    btw. I am currently export manager for a manufacturer in china, and have to deal with such shit everyday. We host the servers by our self, because the ISPs here are incompetent. There are no other alternatives though, so we have to live with that. Pressuring the has NO effect. We still have after six months, three different isps, pressuring and detailed step-by-step instructions no r-DNS.
    Companies like SPEWS blocking whole countries upset me because of their pure ignorance.

    If you need a good BL, use Spamcop.net, kills nearly almost all spam here, the rest is done by spamassassin.

    1. Re:No serious admin should use spews bl by zerbot · · Score: 1

      Rent a smarthost somewhere that doesn't have a massive spam problem and route all your mail out through it. I get too many false positives with Spamcop, and hardly any with SPEWS, but then I don't do any business with China.

    2. Re:No serious admin should use spews bl by weeeeed · · Score: 1

      That's what we are going to do, we have a secondary mx in Germany, I am setting it up currently for routing all of our mail though it.

      That with the spamcop was a mixup, we use spamhouse.org for killing, which is quite reliable for us after extensive testing.

    3. Re:No serious admin should use spews bl by PigleT · · Score: 1

      Yes, I think one has to be quite brain-dead to rely on an RBL for instant rejection. Assess how accurate they are and use a weighted score - oh wait, that's what SpamAssassin does already! Goodie, then. :)

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    4. Re:No serious admin should use spews bl by gorbachev · · Score: 3, Informative

      They are not randomly blocking. They have an escalation policy that expands the netblocks listed from jus the spammers' IP addresses and netblocks to the whole ISP's netblocks, if the problems do not get resolved within a reasonable time period.

      I do agree one should be careful of choosing a blocklist to use. SPEWS is one of the most aggressive. It does not fit everyone's needs.

      SPEWS does not block whole of China. Only the network providers that do not act on spam complaints. Exactly like the SBL does.

      Next time before you insert your foot in your mouth, do some fact checking first.

      --
      In Soviet Russia, I ruled you
    5. Re:No serious admin should use spews bl by weeeeed · · Score: 1

      SPEWS does not block whole of China. Only the network providers that do not act on spam complaints. Exactly like the SBL does.

      By blocking nearly all netblocks of chinese providers (there are not many of them), you are effectively blocking whole China. There is no chinese IP I could take that is not blacklisted, except probably some government owned. I know that, we tried all of the providers here, several times.

      No person in this country is able to do any pressure around the actions of those ISPs. When we and several other companies I know of have contacted them several times about the SPEWS entry, they said they do not care about that and it's our business to get the ip removed from there.

      Nobody at those ISPs gives shit about the block, the only people who suffer are those who cannot do anything about it. You even cannot white list your own IP with SPEWS, no chance.

    6. Re:No serious admin should use spews bl by gorbachev · · Score: 2, Insightful

      So how is that a problem with SPEWS? Looks like the Chinese ISPs don't really care about the spam problem.

      --
      In Soviet Russia, I ruled you
    7. Re:No serious admin should use spews bl by jcr · · Score: 2, Insightful

      We had many cases where we were unable to deliver our mails because some moron admin in a big international company with worldwide suppliers and customers was using spews for rejecting mails.

      As it happens, quite a bit of the spam I've seen lately has been from Chinese manufacturers trolling for customers. If your netblock was listed by Spews, I'm inclined to believe you had it coming.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    8. Re:No serious admin should use spews bl by weeeeed · · Score: 1

      The whole subnet of 218.106.34.0/24 has no reported spam, our current ip is somewhere in there. We are being blocked by the 218.106.0.0 - 218.106.63.255 clause, which... also has no reported spam (as far as I can see it in the spews "evidence file"):
      http://www.spews.org/html/S2171.html

      I agree the spam is annoying, we get it too ;)

    9. Re:No serious admin should use spews bl by corblix · · Score: 1
      They are randomly blocking whole netblocks without having any clue about what is really going on.

      No, of course they are not random. SPEWS lists IP addresses whose owners, in the opinion of the SPEWS folks, do not take proper responsibility for preventing spammers from using their systems.

      You said, "the ISPs here are incompetent". Exactly. SPEWS is not random. SPEWS lists addresses managed by irresponsible ISPs. If you do not want your traffic blocked by others using SPEWS, then you must use a responsible ISP. Evidently you have become your own, a very reasonable response. If enough companies do that, then responsible ISPs will be able to make more money than irresponsible ones, and the bad ones will either change their ways or go out of business.

      In the mean time, it's tough going for many of us, but I think we must admit that SPEWS has a good goal, and an effective (if sometimes draconian) means of helping to achieve it.

    10. Re:No serious admin should use spews bl by some1somewhere · · Score: 1

      Indeed, i dont know of any large companies using Spews.

      I think SPEWS is okay used in a scoring system like Spamassassin as ONE of the rules, but certainly not for blocking spam outright.

      I recommend SPAMHAUS XBL and SBL lists for more accurate anti-spamming.

      --
      **FREE** Track and view your phone's via CellID and/or WIFI and/or GPS :- http://tinyurl.com/la6fhd
  39. Helpful Explanation for non-admin types ;-) by aug24 · · Score: 1

    When you see people refer to 'outbount' port 25, they mean an attempt to connect to p25 on some other machine. In fact, these zombies are not smtp *servers*, they are smtp *clients*, acting similarly to Outlook Express or Thunderbird, but with the user bits automated. They are a programe to 'type in' millions of spam emails and then send them direct to the target user's smtp server.

    In fact, as smtp works on a 'store-and-forware' principle, most real people send their emails to their ISPs smtp server (eg smtp.nildram.co.uk for me) which then sends it on to the target machine for them. This is part of the design of smtp to make it resilient, but which also allows us to do the following:

    Specialist 'smarthosts' at the ISPs network firewall can spot any attempt to make an outbound port 25 call and block it or forward it to the ISPs own smtp machine. This gets rid of the problem as the spam becomes traceable and deniable. Any company failing to do this is lazy and shite and should be named and shamed on slashdot ;-)

    Hope that helps.
    Justin.

    --
    You're only jealous cos the little penguins are talking to me.
  40. spamhouse not spamcop by weeeeed · · Score: 1

    Whoops. I think spamhouse.org write spamcop.

    We use sbl-xbl.spamhaus.org for killing and spamcop.net for tagging in spamassassin at a low level, sorry :p

  41. I could have told you this AGES ago. by burnttoy · · Score: 1

    I'm not a terribly happy telewest customer. I now _only_ use them as a pipe to the outside world and host mail etc elsewhere. Even now I get blocked from IRC left, right and center. Spamhuas have eaten them alive.

    There net service is actually pretty reliable but (as with all ISPs) is full of crap. I don't really want all the additions they give me (I'd like to save my cash and their resources) but that won't happen.

    One last thing... the image quality of their TV broadcasts has plumetted in recent years. Especially after the change over to digital! We were promised better pictures with digital but the amount of compression is obscene! Seriously... blocky artifacts everywhere... I wonder if they're ready for hidef TV??? My TV sure is.

    Oh... and their cable box is CRUD! It took 2 years to get the volume control working and the "interactive" features are more slideshow (try playing frogger at .5fps!)

    Sadly in London you don't have much choice in providers as the city is geographically divided up between just a couple of players. There are options (like ADSL) but they're pointless..

    My plan is SIMPLE and EFFECTIVE... but a Wifi router in every lamppost... should give pretty good city wide bandwidth.

    --
    Time flies like an arrow. Fruit flies like a banana.
    1. Re:I could have told you this AGES ago. by mikael · · Score: 1

      One last thing... the image quality of their TV broadcasts has plumetted in recent years. Especially after the change over to digital! We were promised better pictures with digital but the amount of compression is obscene! Seriously... blocky artifacts everywhere... I wonder if they're ready for hidef TV??? My TV sure is.


      I'll certainly agree with that. Anything was fast motion, flames, water drops, waves all look worse than Ceefax pages. Don't blame Telewest, they use Scientific Atlanta equipment.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  42. Pesos? by Anonymous Coward · · Score: 0

    I thought it was Rubles?

  43. As a Telewest customer... by Drasil · · Score: 1

    I have to say they are the best ISP I have used to date. My only other option for broadband in my area is British Telecom or AOL and the like which use the British Telecom network. Their service is reliable, fast, and although they don't officialy support open source operating systems they have never put artificial barriers in my way to cause problems. I use a BSD based NAT router/firewall and my home LAN is all Debian. It all works fine.

    Their tech support line is a free call, and on the rare occasions I have had to call them I have always talked to someone who knows what they are talking about! Being a true computer fanatic I run my own mail server (I guess that makes me one of the 16,000 email servers mentioned in the story) and from my logs I can see that they have an automated check running to ensure it's not an open relay.

    I think the story highlights the dangers of running a well-known incompatible and insecure operating system. Personally I blame the companies that produce such operating systems, not my ISP which has offered nothing but exemplary service for the last 4 and a half years.

    1. Re:As a Telewest customer... by Slashcrap · · Score: 1

      Their tech support line is a free call, and on the rare occasions I have had to call them I have always talked to someone who knows what they are talking about!

      Maybe they need to reassign their phone techs to actually running their network then? Because blocking outbound port 25 except to their mailservers and cutting off the avalanche of spam spewing from their network would be utterly trivial.

      If they are as competent as you claim, the only explanation is that they just don't give a shit how much damage their fuckwad customers are doing isn't it?

      Obviously the above is a rhetorical question. They've known about the issue for years and they've been listed by SPEWS for years.

    2. Re:As a Telewest customer... by Drasil · · Score: 1

      Perhaps the problems just don't effect me. I've not used windows for 5 years and I rarely want to email anyone who's ISP blocks my mail. If I do then I just route it via Telewest's mail servers. If they blocked outbound port 25 I would not be happy. One of the reasons I like Telewest is the absence of such arbitrary restrictions. I would have no problem with them disconnecting zombies.

      You said...

      If they are as competent as you claim, the only explanation is that they just don't give a shit how much damage their fuckwad customers are doing isn't it?

      I said...

      I think the story highlights the dangers of running a well-known incompatible and insecure operating system. Personally I blame the companies that produce such operating systems, not my ISP which has offered nothing but exemplary service for the last 4 and a half years.

      If a particular make of car regularly spews oil all over the road who is responsible? The car manufacturer or the authority charged with maintaining the road network?

      Oh, and I will generously ignore the fact you called me a fuckwad :P

  44. I'm on Telewest I can confirm... by StephanTual · · Score: 1

    You cannot, I repeat cannot install Win XP from scratch with the ethernet plugged in if you are on Telewest Broadband (aka 'blueyonder'). The machine gets owned in 20 seconds or less after the first boot. Try it if you don't believe me, it's quite an experience.

    Here's how it works: first boot. A few seconds after you log in you start to get the first spam netsends. You go on windows update to get SP2 and while it updates you get the 'rpc server error, machine will reboot in 60 seconds'.

    Once you reboot your machines is infected with several hundreds trojans. It's incredible, I've been in IT for 12+ years and I've never seen something like this.

    The only way around it is to use a good router, or buy the sp2 CD and a firewall and install those BEFORE connecting to the net.

    My router registered 98,000 intrusions attempts in just the past two weeks... I can't imagine a non-techie managing a windows install on this network, or even maintaining one. Their network is toasted.

  45. SPEWS doesn't make announcements either by AndroidCat · · Score: 1
    In late April, Spews announced that it had started blocking more than 900,000 net addresses used by Telewest's Blueyonder broadband service. Many were suspected of being used by spammers.

    They don't make annoucements other than publishing their block list itself. Nor do they block addresses themselves--that's up to the admins who find their list to be a useful tool. (Many use it to tag email for filtering.) Also suspect is the assumption that those addresses were listed for directly spamming. It's also likely that they were listed because Telewest has had spammers that they have ignored for a while and the SPEWS listing expanded because Telewest is seen as spam-supporting.

    Anyone making exact statements about SPEWS' reasons or motives is speculating. IANS.

    --
    One line blog. I hear that they're called Twitters now.
  46. Re:Irresponsible to let infected machines stay onl by dlZ · · Score: 5, Interesting

    I get quite a few machines from Road Runner customers that have received a notice and had their service turned off until the machine was fixed. One customer told them she fixed it (she didn't, was using all Macs) and had her service turned back on, just to be almost immediatly turned off until she had proof from some sort of tech support it was fixed (it wasn't her machines... It was her open wireless router and her clueless neighbor who just connected to whatever popped up first.) I had to fax over a letter on my companies letterhead to have her service turned back on once her router was configured properly.

    Have never seen one from a Verizon customer locally, though (RR and Verizon are pretty much the only two providers you see used around here.)

    --
    rm -rf ./evidence @ punkcomp
  47. For the record, a list of spamming ISPs by spinfire · · Score: 1

    Hate to reply to my own post, but here is a list of ISP Zombie spam I received this morning:

    modemcable204.203-131-66.mc.videotron.ca
    68-184 -141-14.cpe.ga.charter.com
    pool-68-160-42-154.bos .east.verizon.net
    adsl-67-65-232-106.dsl.lgvwtx.s wbell.net
    wbar22.lax1-4.31.136.154.lax1.elnk.dsl. genuity.net
    c-67-182-92-72.hsd1.ca.comcast.net
    c-67-167-19- 28.hsd1.in.comcast.net
    adsl-67-36-114-254.dsl.cle voh.ameritech.net
    pool-68-160-242-240.ny325.east. verizon.net
    adsl-068-153-180-046.sip.mia.bellsout h.net
    82-38-102-51.cable.ubr02.donc.blueyonder.co .uk
    c-24-12-53-105.hsd1.il.comcast.net

    I included only the major US ISPs. This is from spam sent during the last 8 hours, sent directly from the above address to my SMTP server. There is a major problem with these zombies, and ISPs need to be more active about fixing it.

  48. Email addresses? by gorbachev · · Score: 1

    I've heard all kinds of confusing things when people try and explain an IP address to the general public, but that a slashdot subscriber confuses an IP address with an email address takes the cake.

    SPEWS blocks IP address ranges, i.e. netblocks, as the article very clearly states.

    --
    In Soviet Russia, I ruled you
  49. The article is *all* wrong by Eggplant62 · · Score: 1

    This article mischaracterizes how SPEWS works completely. SPEWS does not communicate actively. The only form of feedback one can gain is through their listings and from their website. Otherwise, SPEWS has said nothing since it's inception, has been represented by no one (no one except the denizens of news.admin.net-abuse.email, and then only from a third-party viewpoint), and will probably continue to say nothing.

    What's really happened is that TeleWest, like many other cable and dsl providers, has had their users overrun with zombie trojans and depite being informed of the problem appear to be doing nothing to solve the problem. Meanwhile millions of spam emails are being spewed from the zombies occupying their network. In the absence of any apparent effort by TeleWest/BlueYonder to do anything about the zombie problem, SPEWS has simply blocked their IP Addresses, not email addresses.

    When TeleWest/BlueYonder start taking steps to get the infected zombies off their network, notifying the machine owners that they will not be allowed back on the 'Net until they clean up their fscking machines, then I'd think the SPEWS listing could be lifted. Similar situations are happening at several providers: Comcast, WideOpenWest, SBC, Verizon, and others.

    This really is nothing new. All a network has to do to keep off the SPEWS list is to stop the flow of spam from their IP addresses, no matter the source--be it zombied windows boxen, spammers operating directly from their netspace, or other circumstances.

  50. When you connect they ask you if you have a Virus by SD+NFN+STM · · Score: 1

    I recently re-connected to Telewest, and they now ask you "Is your PC free of Viruses, Spyware, Trojans". This is the first time an ISP has ever asked me this, so in my opinion they are getting a bad wrap.

    Maybe their actions are just a reaction to their blocking, or possibly they are being PRO-active... you be the judge.

  51. Solution? by AviLazar · · Score: 1

    Telewest have stated that they knew about the problem and have been working with customers to regain control of their machines

    Start
    Shut-Down
    Restart in MS-DOS
    c:\format c:

    --

    I mod down so you can mod up. Your welcome.
  52. Lazy maintainers by dtfinch · · Score: 1

    So rather than ban 16000 individual IP's, they figured, "hey, a 60 to 1 false positive rate isn't so bad, lets just block a million IP's worth of subnets."

    1. Re:Lazy maintainers by Rasta+Prefect · · Score: 1
      So rather than ban 16000 individual IP's, they figured, "hey, a 60 to 1 false positive rate isn't so bad, lets just block a million IP's worth of subnets."

      It's not about the machines on the end, it's about the ISP they're connected to. Any one of those other IP's owned by Telewest could start spewing spam tomorrow and Telewest has conclusively demonstrated they won't do squat about it. So it's listed in spews. SPEWS stands for Spam Prevention EARLY WARNING system. I wouldn't block on spews but I certainly don't mind adding it to a scoring system.

      --
      Why?
    2. Re:Lazy maintainers by dtfinch · · Score: 1

      It's all about the machines on the end. A couple hundred thousand people will now have a portion of their outgoing email silently dropped with no error message. If my IP was added to SPEWS, I'd blame SPEWS, and its users. I've known companies that were royally screwed over by emotionally unstable blacklist maintainers with big egos who thought it was a good idea to teach an ISP a lesson by punishing the users who are locked into their internet service.

      I sincerely believe that EVERY ISP who's users are purposely and unfairly blacklisted would be doing the right thing to sue the blacklist into the ground.

    3. Re:Lazy maintainers by Anonymous Coward · · Score: 0

      It's up to the people running the mail server to determine if you get a bounce or if your mail gets "silently dropped". It all boils down to this: Whoever you're trying to communicate with, or their agents (i.e., mail admin) has decided that the benefit of being open to mail from your area is outweighed by the spammers/zombies who are also in your area.

      It makes no more sense to try to sue them than it would for a restaurant to try to sue a food critic after serving him a shitty meal.

      If the smoke alarm is going off, try putting out the fire rather than taking out the battery.

    4. Re:Lazy maintainers by Anonymous Coward · · Score: 0

      "A couple hundred thousand people will now have a portion of their outgoing email silently dropped"

      If third parties are dropping email without an error, then that's not the fault of SPEWS or anyone except the third party dropping the email. A sensible system would return an error.

      Also, it's not anything like "a couple hundred thousand people" - pretty much all of them will be using an email client set up to send to Telewest's servers and will be unaffected by this.

    5. Re:Lazy maintainers by Rasta+Prefect · · Score: 1
      It's all about the machines on the end. A couple hundred thousand people will now have a portion of their outgoing email silently dropped with no error message.

      Some places bounce spam, some don't. If you have a problem with silent drops, you need to talk to the administrator doing the silent dropping, not SPEWS. It's a choice made my the mail admin one way or another. Although I do tend to favor a bounce, you can seriously screw someone over if they're joe-jobbed.

      If my IP was added to SPEWS, I'd blame SPEWS, and its users.

      Your ISP doesn't deal with abuse complaints. Ergo, your ISP is a more likely source of SPAM and other abuse. So I score mail from your ISP higher. I do it manually for some ISP's (telefonica.br comes to mind). Spews just automates the process. Seems to be your ISP's fault for being a cesspool, unless you feel that being a customer of an ISP should be a legally protected class like being a minority or disabled.

      I've known companies that were royally screwed over by emotionally unstable blacklist maintainers with big egos who thought it was a good idea to teach an ISP a lesson by punishing the users who are locked into their internet service.

      I'm not saying this has never happened, but I will say that what I've seen happen a lot more often is that some company representative finds out that his company has been blacklisted for one thing or another and demands to be delisted RIGHT NOW. And you better take his word for it and not do any investigation into whether the block is legit. When they don't delist him RIGHT NOW he starts making cart00ney legal threats about how he's going to "sue them into the ground". Things usually degenerate from there. If this exchange is taking place in nanae, there are usually a lot of offensive comments from the penut gallery on behalf of SPEWS and people don't realize, because they couldn't be bothered to actually read and understand the FAQ at SPEWS.org, that the people they're talking to are mostly bored teenagers and not, in fact, SPEWS.

      I sincerely believe that EVERY ISP who's users are purposely and unfairly blacklisted would be doing the right thing to sue the blacklist into the ground.

      Whats with the entitlement attitude? Who decided you had some kind of god-given right to deliver mail to my server? SPEWS publishes a list based on publicly available criteria on their web site. So long as they're not lying they're not committing any sort of crime, and I can't see that they're really doing anything unfair.

      Meanwhile the SPEWS users are doing their best to block SPAM. If they decided SPEWS listings are a useful metric for judging spaminess they have every right to block or score based on that. It's their server. If you don't like it you can try and convince them they're mistaken, or you can move to an ISP that does something about their abuse problems.

      Incidentally, those running SPEWS choose to remain anonymous because of people with your attitude - plantiffs never win these suits because the blacklists _aren't doing anything illegal_, but the costs of defending them will often force them to shut down.

      --
      Why?
    6. Re:Lazy maintainers by Anonymous Coward · · Score: 0
      I sincerely believe that EVERY ISP who's users are purposely and unfairly blacklisted would be doing the right thing to sue the blacklist into the ground.


      Please tell us oh great Clarence Darrow, Jr., what important legal precedent are basing your grounds to sue on here? What part of the Magna Carta or there in the US, the constitution, are puts forth that stating an opinion, which is what these blacklists do, is some sort of crime or illegal act?


      I'm really offended by all people named "Finch", can I sue you for this offence?


      AC


      * Okay, I'm not really offended by all people named "Finch", just the jerkwad ones who try play lawyer in /.

  53. They almost know what they're talking about by eaolson · · Score: 1

    Ugh. The article gets almost everything mostly wrong.

    SPEWS doesn't list "email addresses." It lists IP addresses for spam-friendly ISPs. (Although the article says "net addresses," not "email addresses," as in the Slashdot summary.

    Telewest admits that a huge virus infection meant they were a large source of spam. The SPEWS listing is allowing the rest of the world to quarantine them until they can clean up their act.

    Telewest was a big source of spam. They were blacklisted. That's what blacklists do. That's why we use them. Don't like it? Don't use SPEWS.

  54. Re:Irresponsible to let infected machines stay onl by nonumnos · · Score: 1

    Yeah... when the malware injects itself into the running explorer.exe, you usually are pretty screwed! Oh wait! Gee, you COULD boot into safe mode where the majority of this crap (even the "shell-injector") do not auotload. You'll have to scan, reboot, scan, reboot, etc about 20 times, but eventually you will have a mostly clean system. This leaves us with two problems still: (1) that the majority of the malware being used for spam and DDoS are not detected by most AV products, and (2) the user must then sufficiently patch their OS to keep from being owned within the first two minutes of being back online. $ISP should negotiate deeply discounted rates with "Worst Buy" and their Geek Patrol so that people can make an honest effort at cleaning their machines.

  55. at least no public outcry by v1 · · Score: 1

    I'm surprised the isp isn't doing the usual maneuver and crying us rivers for being abused. Kudos to them for sucking it up, taking their lumps, and attempting to do something about the problem they fostered instead of whining to us about it not being their problem.

    If I were on their service I'd be a little peeved for having my email blacklisted, but I would know the correcct organization to direct my ill-content to: not the blacklister, but to the isp. Hopefully they can get a good percentage of their customers' owned machines back under control and get delisted soon.

    Any isp that does not have detection systems to identify and either cap or disconnect machines that are clearly spam engines is doing the internet a dis-service, and as a result their customers are getting the shaft by blacklist. Best way to look at it is the ISP should be providing the "service" of not getting their customers blacklisted periodically by catching and dealing with clueless customers with owned machines. Customers going on the cheap with their ISPs risk not receiving this oft-overlooked "service" and finding their email roundfiled.

    --
    I work for the Department of Redundancy Department.
  56. maybe they should not have ignored their problem by harlows_monkeys · · Score: 1
    SPEWS starts out listing just the IP address that is spamming. They send complaints. They expand the listed range only if the complaints are not dealt with.

    To get thousands or millions of addresses listed requires an ISP to ignore their spammers for a long time.

    To get unlisted requires cleaning up the spammers.

  57. What are you talking about? by frankie · · Score: 1

    Since those guys are not SPEWS, what the hell does your inflammatory tidbit have to do with anything?

  58. Blacklist Blues by shaved_weasel · · Score: 1

    I've had problems with blacklists in the past and though some may think it's a great idea, when you've made the list it makes you think twice. I went in circles between our ISP and the Blacklist website trying to work things out. We had our mail server hijacked and in the end the draconian rules of the blacklister forced us to purchase a entirely new email system. In my opinion, Hijackers 1 Good Netizens 0. There has got to be a better way.

    Anyone else got any sob stories? Maybe we could start a coalition of the pissed off.

    1. Re:Blacklist Blues by Todd+Knarr · · Score: 1

      There is a better way. Get reliable SMTP server software (there are several), keep up-to-date on security patches, follow best practices for securing your systems and restrict access to only what's needed. In fact, segregate your mail servers so seperate machines handle incoming mail from the world, that way you can monitor the machines the crackers can reach more thoroughly. Internally, use e-mail clients and browsers that have the best records for not being susceptible to attack. If anyone gripes, point to the cost of dealing with infestations and tell them that dollars decide, deal.

      Also, monitor both your outgoing mail and your own network for suspicious activity or evidence of infestation. If you spot a problem, shut the offending machine down stat and keep it off the network until it's been cleaned up. If the same person keeps getting infected repeatedly, revoke their network privileges. If they can't learn after several lessons, they'll just have to accept the consequences.

      When a blacklist does contact you about a problem, don't stall and don't deny. If you knew about the problem already, simply tell them what the problem was and what steps you took to deal with it. If you didn't know about the problem, acknowledge the report and give them a time you expect to have it investigated. Then investigate it and send a followup within the timeframe you gave telling them what you found and what you did about it. For the big blacklists, this is all you'll need to do to stay off them. And the people who run them do have memories. If you've a history of good behavior and cleaning up the mess ASAP, they'll be more inclined to cut you slack if a truly major problem occurs because they know it'll be dealt with. By the same token, if you've a history of not acknowledging problems and letting them persist, they'll cut you no slack at all.

      If there's a person on your network actually causing problems repeatedly, present the situation to management in dollars: kicking that person will cost $X, keeping them will cost $Y, Y is far greater than X. Management should be receptive to hard numbers that affect the bottom line, and once the problem person's gone that's one less headache and one less reason for you to wind up on a blacklist.

    2. Re:Blacklist Blues by LorenzoV · · Score: 1

      No doubt, you were the asshat running an MSExchange server connected directly to the internet.

      In spite of what you might think, the listing was most likely fully warranted. Your lack of due dilligence in selecting an MTA is not a reason to whine when the rest of the internet refuses your traffic.

      Get over it.

    3. Re:Blacklist Blues by shaved_weasel · · Score: 1

      Thank you for taking the time to reply with so lengthy a post. Taking me to task as if I were a child to be lectured to was great fun for me.

      I'm not going to defend myself however because the situations was complex and so frustrating that I'm turning red in the face right now just thinking about it. All of the things you mentioned were done. The problem wasn't getting on the list, braniac, IT WAS GETTING OFF!!

      You can't possibly be working in a real world job, because one does not revoke the network priveleges of a managing partner in a major law firm.

    4. Re:Blacklist Blues by shaved_weasel · · Score: 1

      Your insulting tone and assumptions tell me scores about your abilities and intelligence. The server was a linux server and was provided by the ISP with assurances that they would secure it. They didn't, we suffered for it and both the ISP and the Blacklist did little to nothing to help us out.

      In the ISPs defense at least they had a rep I could speak and reason with. The blacklist mine as well have been a faceless machine. Wait correction it was a faceless machine. If you are going to run process with so profound an effect on an organization you should at least have enough staff on hand to email a poor soul.

      Questioning a process, entity or event does not make me an asshat nor an idiot. If we all just sat around waiting to "Get over it" I think we'd still be in the dark ages.

  59. Re:Pamela Jones EXPOSED by shaved_weasel · · Score: 1

    Ummm was this moderated??

  60. Re:Irresponsible to let infected machines stay onl by Jarnis · · Score: 1

    Wrong. Today's antivirus/antispyware programs are mostly crap. They remove a lot of stuff, but hardly everything. For example, crappy F-Secure commonly FINDS lots of viruses, then says 'can't delete, renaming file', and then silently fails even that, so next scan the pest is still there. Also lots of current malware will even interfere with safe mode (you should see some of the trickery these software go into to keep running and/or prevent deletion of the files/registry keys).

    Then again, if you don't work in PC repairs/support, you wouldn't know. Go try it someday. You'll be amazed how hosed systems people carry into paid 'remove the viruses please'-service. People simply won't move their butts until the system is at a state where nothing meaningful can be done.

    Only way I have manually cleaned badly hosed systems is via deleting files of the malware using a WinPE live bootdisk, or by putting the drive as additional drive to another computer and manually getting rid of the actual files of the pests. Antivirus programs are fine in preventing infections of known junk, but once the system is Gone, its Gone. None of the big commercial antivirus software is today able to remove all of the viruses they detect.

    I've seen stuff that just goes to immense lenghts to prevent deletion. From your average 'I'm sorry dave, I can't let you delete that one (permission denied)' via premissions (yeah, Take 0wnz0rship works, to a degree), to just plain locked files that cannot be touched - even in safe mode, and need removal using WinPE or some other method of booting from somwhere else than the messed up OS disk. Most funny situations is where the malware actually messes up with the permissions of the OS to a degree where an Administrator account suddenly doesn't have access to a lot of stuff. You could manually start restoring permissions, but really - it's just not feasible. It takes so immense amount of time, that it's not cost-effective compared to 'wipe disk, reinstall OS'.

    (and I know of SFC /SCANNOW - except that in such cases it usually fails to start at all due to some service or file being hosed)

    You guys don't seem to understand the amount of mischief these money-incentived malware writers can do on a 'rooted' windows box (since everyone runs at Administrator). If someone roots your linux box completely, it's POINTLESS to try clean it up. It's compromised, and no amount of antivirus snake oil at that point can restore your trust to the status of the system. Only full reinstall and recovery from a known good backup is any good. Yes, you can rescue data files (after suitable checks that they cannot be infected), but beyond that the only real cure is reinstall.

  61. Re:Irresponsible to let infected machines stay onl by Skapare · · Score: 2, Interesting

    It was still her resposibility. If she said she fixed it, and in fact she had not fixed the wireless router (her ignorance is probably why she didn't think it was the point of the problem), then she told an untruth (maybe not intentionally so). But Road Runner was in the right to immediately cut her back off and require more definitive proof. I'm glad you knew to check the router.

    Maybe Verizon is blocking outbound port 25 that goes to other than their own smarthost MTAs. That would stop a lot of zombie spam until the spammers shift their paradigm to having the zombies do smarthost relaying. They are already using the zombies to do mass and distributed signups of new users at Hotmail, Yahoo, etc, so they have ready accounts to do spamming from over there, too. That's hard for the free mail providers to detect as a spammer activity.

    --
    now we need to go OSS in diesel cars
  62. Dear SPEWS ... by Skapare · · Score: 1

    ... I owe you a beer. I owe you many beers. Great job!

    --
    now we need to go OSS in diesel cars
  63. Re:Irresponsible to let infected machines stay onl by dlZ · · Score: 1

    Oh, not saying it wasn't her fault for not having her equipment properly configured. And I charged her for having to drive to her place just to take 5 minutes to configure it.

    I don't believe Verizon is blocking port 25, but they may be. The service they provide locally is horrid compared to RR, though, so I wouldn't be surprised if they're just ignoring the problems. The speed difference alone is amazing. The commercials for RR always talk about being a bit faster, but when actually comparing the two directly, it's very noticable.

    --
    rm -rf ./evidence @ punkcomp
  64. Re:Pamela Jones EXPOSED by Anonymous Coward · · Score: 0

    Who Is Pamela Jones?
    By Maureen O'Gara

    Friday May 6 2005 - A few weeks ago I went looking for the elusive harridan who supposedly writes the Groklaw blog about the SCO v IBM suit.

    The now-famous opinion-shaping open source leader Pamela Jones, aka PJ, doesn't give conventional face-to-face interviews. Never has, near as anyone knows. All communication is virtual. Only one person in the world has ever claimed to have met her - in the pressroom at LinuxWorld in Boston complete with a Pamela Jones badge - and described her as a fortyish reddish-blonde who giggled a lot.

    Oh yeah? Wonder what cold crème she uses.

    Pamela Jones is a 61-year-old Jehovah's Witness who lives in a shabby genteel garden apartment in desperate need of an interior decorator on a heavily trafficked commercial road at 304 North Central Avenue in Hartsdale, New York. Hartsdale is in Westchester and Westchester is IBM territory.

    See, even though Groklaw treats cell phones like they were Kleenex and changes its unpublished numbers regularly, one number it left with a journalist led to this flat and - wouldn't you know it but - some calls from there had been placed to the courts in Utah and to the Canopy Group so obviously this just isn't any Pamela Jones.

    Pamela has lived in apartment 1A for 10 years at least, according to the super, who says he's watched people move in, have children, and the children marry and move away.

    Now, this isn't your usual anonymous New York apartment. It's practically a self-contained village where the super goes for the old ladies' groceries when there's snow on the ground and people know each other's business.

    But the super didn't know much about Pamela except that she had a computer, worked at home (maybe sometimes) for a lawyer, was "paranoid" - his word - and "sensitive to smells."

    He remembered how he was cleaning paintbrushes one day and she came running down the stairs screaming "Fire."

    She was also missing and had been for weeks.

    Nobody there knew where she was.

    She had up and disappeared one day, and the super was worried about her. He said her son had dropped by and he didn't know where she was, and that some strange man that "nobody knew," as the super described him, had tried to get into her apartment while she was gone - the Medeco lock she had had installed on her door - something nobody else in the complex seemed to feel a need for - was more expensive than the door. But, as it happened, the super said, she had just sent in her rent in an envelope postmarked Connecticut.

    Like an episode out of "Where in the World is Carmen San Diego," the trail led to 10 Bittersweet Trail in Norwalk, Connecticut, 24 miles away. Sure enough, parked in the driveway was Pamela's car, just as the super had described it, a dark gray '90s Japanese number with a bunch of Jehovah Witness pamphlets tossed on the backseat.

    The woman at the house, Barbara Sharnik, told a disjointed story. She didn't know Pamela, Pamela hated her, Pamela wasn't there, Pamela left her car there because it got bumped, Pamela left her car there because she left town, and so on.

    Afterwards Barbara called the cops, and then the cops called the number we left with her and the cops said that she was Pamela's mother and that Pamela was on the run and had shacked up with her mother because she had gotten "threatening mail" weeks before and that she had just gotten spooked again because "people were getting hurt around [my] stories" and had lighted out for Canada.

    Odd, the subject of my stories - or any stories - never came up during our brief interview. I was just looking for Pamela.

    That left Pamela's son, Nicolas Richards, who, as it happens, had been in the software business in Manhattan until - why, my goodness - things seem to have come a cropper right around the time Groklaw came into existence.

    Nick and his ma were apparently involved together in Medabiliti Inc, an ISV, because one Pamela Jones with a Westche

  65. So which spammer are you? by Dimensio · · Score: 1

    You're posting common spammer anti-SPEWS lies. You can tell us. What ISP kicked you off because your constant criminal spamming activities caused their blocks to get listed in SPEWS?

    1. Re:So which spammer are you? by 91degrees · · Score: 1

      Wow. Name calling. Let me guess.. you're 12 years old.

      Here's the deal. I get irritated by a self appointed elite telling people how they should and shouldn't behave, using the excuse "We're just trying to stop spam".

      What makes you think I'm a spammer?

    2. Re:So which spammer are you? by Dimensio · · Score: 1

      Here's the deal. I get irritated by a self appointed elite telling people how they should and shouldn't behave, using the excuse "We're just trying to stop spam".

      No one is telling you how to behave. They're simply offering a list of IP addresses belonging to known spam-supporters freely to anyone who wishes to see it for whatever purpose they might have.

    3. Re:So which spammer are you? by 91degrees · · Score: 1

      No one is telling you how to behave. They're simply offering a list of IP addresses belonging to known spam-supporters freely to anyone who wishes to see it for whatever purpose they might have.

      Bullshit! They're offering it as a email blocking list. You're still sounding like a 12 year old. I mean talk about evading responsibility. It's only useful purpose is to block emails. It is advertised as a list in association with technology to block emails.

      But if you prefer to be a total immature wit about it then that is your right.

      But I wasn't talking about them. I'm talking abou the people who use the list on order to pressure ISPs to pressure their providers.

      You didn't answer my other question. What makes you think I'm a spammer?

    4. Re:So which spammer are you? by Anonymous Coward · · Score: 0
      Wow. Name calling. Let me guess.. you're 12 years old.

      The admins who run it are jumped up petty control freaks who think the internet should be run according to their whims..

      ..self appointed elite..

      Well, that's your right. I stil think that these people are fucking morons.


      How odd, you too are 12 years old?

      Why not try here, it's much more skewed towards your demographic than Slashdot, K?

      Okay, this insult we can all agree on:


      They need to spell it out for idiots like me that don't understand the jargon.

    5. Re:So which spammer are you? by 91degrees · · Score: 1

      The admins who run it are jumped up petty control freaks who think the internet should be run according to their whims..

      The admins that run it refuse to modify their own behaviour and demand everyone else does so. They are inflexible. They overrate their own impotance. They expect everyone else to do things their way. Hey, take it as an insult if you like.

      ..self appointed elite..

      They are self appointed in that they make the rules. They are an elite in that the barrier to entry is high enough to stop other people from having any say in the matter.

      Well, that's your right. I still think that these people are fucking morons.

      My personal opinion. I didn't accuse them of anything.

  66. Businesses cant change email addresses by maxwells_deamon · · Score: 1

    I worked for a while for a very small company which had about 7 full time employees. Because we did business in part via email we could not change addresses without a signifigant impact. The employees did not worry about giving their addresses out to anyone. We were getting 20 to 30 thousand emails a day. That is over a million per employee.

    I spent at least 1/3 of my time updating spamassassin filters.

  67. Re:maybe they should not have ignored their proble by Tripster · · Score: 2, Informative

    I've had run ins with SPEWS, they don't just list IP addresses that are spamming but will also list IPs only slightly associated with a spammer.

    Example, I had a long term hosting reselling client, he had sites relevant to the local area he lived in at the time, mostly some sites based around Oregon, etc and they were all perfectly legitimate sites. He had never relayed any spam via my servers.

    After a couple of years this fellow had taken to working with some of the big spammers, he was doing this elsewhere and I had absolutely zero knowledge of it as the account he had with us was still perfectly normal.

    One day I get a call from our NOC that one of our servers had been disconnected due to a SPEWS listing and they were going to terminate my server entirely. I was shocked, I had no idea why and they finally pointed me to the SPEWS listing on the newsgroups.

    What had happened was this person had used an email address on the domain he hosted with me as a contact for another domain he was using elsewhere, all of sudden this made me "spam friendly" apparently.

    This person caused trouble on several of my servers also because of secondary DNS, SPEWS actually started listing my secondary DNS boxes because of this.

    I was quite pissed off because of all of this because my company had zero knowledge of what this client was doing elsewhere and we had nothing at all to do with any spam deliveries and yet we were branded guilty with little choice in booting the client and then begging SPEWS to delist us.

    Our TOS states we don't allow spam to generate from our clients nor do we allow it to generate elsewhere pointing towards their domain names hosted with us. It doesn't state we can dictate what they do elsewhere however and frankly we have no business knowing what our clients do elsewhere.

    It took two seperate tries to fix this problem, we were delisted only to be relisted again later for the exact same thing and this was after we had completely removed the client from our servers. Our NOC had access to our server and I told them to look for themselves to see we had long since removed the client but had no control over what DNS servers they listed in their zone records, that was the issue the second time, our DNS servers still appearing in the zone records was enough apparently, even if we'd long since removed the domains and zones from our DNS.

    In short SPEWS caused hours of downtime for our clients due to a false accusation, we were never informed by anyone at SPEWS this client had ties elsewhere and we had never had any spam sent via our server.

    Quite honestly, had SPEWS been a local office I would have probably shown up with a baseball bat and beat some common sense into them for a while.

    SPEWS it one of the RBL's that will NOT be used on any mail server we have control over. They proved to us that they are very prone to over reaction. What really makes me mad is would they have listed AOL if the guy had used his AOL email address instead? How about Hotmail? Gmail? Doubtful.

    As I asked them, are they listing the guys cable company? His utility providers? The restaurants he eats at?

  68. Re:Irresponsible to let infected machines stay onl by Lost+Race · · Score: 1

    It's strange that none of the anti-virus makers include a bootable CD to do the first-pass scan and disinfect of potentially compromised systems. How can a compromised system be trusted to diagnose itself correctly? I managed to hack something together with a Slackware live-CD and the Linux version of F-PROT and removable HDDs, but it's a PITA to use and doesn't support NTFS very well.... Just sticking in a pre-made antivirus CD and rebooting would be so much more convenient. Symantec already has a mini-Windows environment on CD for some of their other utilities, so they easily could make a bootable AV CD.

  69. Re:Irresponsible to let infected machines stay onl by Jarnis · · Score: 1

    F-Secure's Internet Security 2005 does that.

    However, 3-6 months old AV signature files do exactly Jack and Squat against new threats. Yeah, again you can remove some bits, but not everything.

  70. No corporations use SPEWS by some1somewhere · · Score: 1

    SPEWS is, indeed, not widely used as compared to SPAMHAUS and it's SBL or XBL lists or Spamcop. I dont know any large corporate network or mail service that uses SPEWS to block outright, simply because SPEWS regularly bans/blocks/lists entire ISPs, huge netblocks, etc. and the collateral damage is too high when you cannot afford to miss important emails.

    They then want you to go to USENET groups to post about things, yet when you get there, all you'll find are a bunch of people all saying "i'm not SPEWS". So... go figure what company, corporation, or network of any size would use such a list. I suppose individual users could use it on a scoring-based system like Spamassassin without too much problem.

    --
    **FREE** Track and view your phone's via CellID and/or WIFI and/or GPS :- http://tinyurl.com/la6fhd
  71. Re:maybe they should not have ignored their proble by don.g · · Score: 1

    Isn't it the the fault of the NOC for making the leap of SPEWS listing -> must be evil spammers? Maybe you (or they) should have read whatever contract you had with them more carefully.

    --
    Pretend that something especially witty is here. Thanks.
  72. Telewest are Virus ridden Noob fools by Anonymous Coward · · Score: 0

    My dad is an Edinburgh Telewest Customer
    I connected a SP4 WIN2k machine to telewest and it was a burnt out virus ridden wreck within 2 minutes, it is a horrendous network, slow, very slow at weekends, even with Zonealarm and AVG they get in.
    Finally I got a router and that helped.
    Now telewest Surfmodems have a router built in but Telewest won't switch it on unless you give them loads of extra money for a "small office connection" - Telewest really really suck and I am glad someone is forcing them to clean up their act.
    The UK Goverenment rolled out Broadband Small Business Grants, they should have required routers to be part of the equation, even an unpatched windows machine can survive behind a router, a router is way better in my experience than a software firewall.
    Now the East Euro Haxor Mafia ownz all UK small business info and it didn't have to be that way.
    I tell people NOT to connect their business machines to the Internet, do you havbe any private information on that computer? Yes. Well you won't once you plug that modem in.
    P.S. Telewest is cable so viruses have more ability to roam than adsl.

  73. SPEWS critical = flamebait by Anonymous Coward · · Score: 0

    Nice to see that all SPEWS critical posts get moderated as flamebait. It just confirms how badly the moderation system is abused. If it's not popular opinion, mod him down.

    1. Re:SPEWS critical = flamebait by 91degrees · · Score: 1

      Yeah. The moderation system has always been broken. It's just as easy to whore for +5 mods. Unfortunately the solution to a brken mod system always involves adding more arbitrary rules, and sticking with them whether they work or not.

  74. Re:Irresponsible to let infected machines stay onl by StikyPad · · Score: 1

    As of 4/26/05 I enter the world of a non-smoker. Wish me luck and a lot of support.

    I quit back in February, using nicotene replacement. I still pop those Committ pills from time to time, but it's a lot better than smoking, and cigarettes honestly taste like shit to me now. Gained 10lbs when I quit, but I've almost lost it again. Just remember, having 1 smoke doesn't mean you failed, and the more times you try to quit, the more likely you are to succeed.

  75. Re:maybe they should not have ignored their proble by Tripster · · Score: 1

    Don't worry, I informed the NOC of the displeasure of them taking SPEWS so seriously when this was obviously something I had no knowledge of and could not have known about.

    They lost business from us over it and other things, btw, the NOC was the same one that bought that SCO license which was the final straw.

  76. Re:port 25-I need new ISP now who WONT block ports by iamcf13 · · Score: 1

    Got a legitimate need to run your own mail server? Ask your ISP for it.

    I asked my ISP to unblock port 25 so I could continue to develop email related software I've written but my request went unfufilled.

    I am not a n00b and I need affordable dialup access before June 1st with an ISP with nationwide access dialup numbers who will not block any ports coming or going! Anybody here have any recommendations?

    1) ISP must be affordable (<= $10/month for 'unlimited access').
    2) ISP must offer nationwide access numbers in the USA.
    3) ISP MUST NOT BLOCK PORTS COMING OR GOING!

    Please do not suggest I search The List -- that will take too much time and is only as a means of last resort.

    Thank you for your consideration.

  77. Re:Irresponsible to let infected machines stay onl by dlZ · · Score: 1

    I'm using nicotine replacement, too. Using Nicoderm right now, actually, and it is making it a lot easier. I don't mind a bit of weight gain, either, I work out pretty regularly and always have a lot of trouble putting on weight in the first place. Tend to be very skinny, no matter how much I eat. One of those things were everyone told me I would grow out of it, and I haven't. Thanks for the support, though! All the support of those around me makes it a lot easier, much more than any patch does.

    --
    rm -rf ./evidence @ punkcomp
  78. Re:maybe they should not have ignored their proble by harlows_monkeys · · Score: 1
    I've had run ins with SPEWS, they don't just list IP addresses that are spamming but will also list IPs only slightly associated with a spammer

    You have misunderstood what SPEWS lists. They do not list spamming IP addresses. The "EW" in SPEWS is "Early Warning". They list IP addresses that are owned by people that support spammers.

    Listing spamming IP addresses is pointless, because providers that support spam just shuffle them around. SPEWS lists the IP addresses owned by the bad providers.

    The usual analogy is crack dealers. You may not be a crack dealer, but if you live in an apartment building full of crack dealers, where there are random shootings, and pizza delivery people get mugged whenever they try to deliver to that building, they are going to stop delivering to you. It doesn't matter that YOU are not a crack dealer. You are in a bad neighborhood.

    That's what SPEWS lists: bad internet neighborhoods.

  79. Re:maybe they should not have ignored their proble by Tripster · · Score: 1

    And again I state I doubt very much that they would have listed Gmail, AOL or any other large ISP had this user used an email address under those domains.

    I'm all for getting rid of spammers, I run mail servers that filter as much of the crap as possible, however I am NOT a spam supporter and was mistakenly painted as one by SPEWS.

    If what they did to me was correct then they should be listing the guys utility companies and anyone else who does business with him, right down to the corner shop where he buys milk.

    Now had they warned me first, had they informed me about it, etc. I would have taken the steps necessary, but really the guy was doing zero spamming from my servers so technically he was within the TOS so it becomes quite tough to deal with.

    It came down to "kick your client because he's a spammer, we're not providing you with proof we're just telling you he's a spammer".