Slashdot Mirror


Catching Spam by Looking at Traffic, Not Content

AngryDad writes "HexView has proposed a method to deal with spam without scanning actual message bodies. The method is based solely on traffic analysis. They call it STP (Source Trust Prediction). A server, like a Real-time Spam Black list, collects SMTP session source and destination addresses from participating Mail Transfer Agents (MTAs) and applies statistics to identify spam-like traffic patterns. A credibility score is returned to the MTA, so it can throttle down or drop possibly unwanted traffic. While I find it questionable, the method might be useful when combined with traditional keyword analysis." What do you think? Is this snake oil, or is there something to this?

265 comments

  1. sounds good to me by seanadams.com · · Score: 5, Insightful

    I realize most of us here would ordinarily prefer for our ISPs to just move bits around, but it seems like they are in a pretty good position to curb spam if they were to start look at traffic patterns like this. If some DSL customer suddenly starts opening hundreds of outgoing SMTP connections, that would be a pretty reliable sign that his machine is pwned. Just block or throttle port 25, and send the customer an email telling him to fix his computer, and keep it blocked until he does - or he contacts abuse@ with a legitimate explanation. Not filtering based on the contents of the data should let them maintain plausible deniability and common carrier status.

    We can't do this on our personal or company internet connections because we only see individual messages coming from many different IPs, but on the other end of the connection, or even at the backbone level, this strikes me as a pretty solid solution. They could even just tag the packets with the evil bit and let us decide if we want to filter them or not.

    1. Re:sounds good to me by Anonymous Coward · · Score: 2, Informative

      That may be just another tool to circumvent Spam. My primary email spam filtering is Spamd @ openbsd.org/spamd. The service-based spamd is known as Spam Assassin. This is a daemonized version that was ported for Openbsd by the gods. It can be troublesome to configure if you are a first timer. But remain vigilant with google groups and documentation provided by openbsd.org and the man pages within spamd.

    2. Re:sounds good to me by GreggBz · · Score: 4, Interesting

      The new bread of zombies have wised up to port 25 blocking / throttling and like to funnel everything through the MTA for the domain to which they are connected.

      A combination of policyd, postfix, spamassain and ids/bandwidth accounting software has turned it into something manageable, at least where I work. Customers are allowed say, 100 e-mails in a 30 minute time span. If they complain and have a real reason, we can adjust. This also makes finding users with pwned machines a lot easier.

      Some of them now (the spam zombies) seem to be moderating their outgoing connections so that it's not so obvious but their volume is still substantial. It just never ends...

    3. Re:sounds good to me by webdragon · · Score: 2, Insightful

      I'm sure they could do that fairly easily but with how everyone is sue happy their going to have to change the terms of use contracts first to reflect that they can and will do it so they can cover their rear from being sued.

    4. Re:sounds good to me by ronanbear · · Score: 1

      Or examining patterns might be a less resource hungry way to look for spam. Anything that does get flagged can be assessed in more detail. The more mail you send the more it gets checked to see if it's spam. Most people send valid bulk email (where they send it) to similar lists of people. That's easy to block using blacklists if a spammer tries the same method. But if you're sending 100s of messages to different people and it's a different 100 people and a large number of them are invalid addresses then it's something that's much more indicative of suspected spamming. btw I think there are several problems with the idea of blocking someones email ports and then sending them an email telling them that they have a problem with their email. For one thing people shouldn't mightn't read unsolicited emails telling them to do something that they don't understand. Spammers do the same thing.

      --
      the more they over-think the plumbing the easier it is to stop up the pipe
    5. Re:sounds good to me by kripkenstein · · Score: 4, Insightful
      Sounds good? Don't major email providers already do something like this? What else are Google doing when lots of people click on "This is Spam" for a particular email - surely they notice such things? The same should be true of email traffic patterns. Yet, perhaps some minor detail in TFA is the new bit. Obviously any improvement in this area is welcome.

      While this will not stop spam, it will be reduced dramatically. The STP value of a spam source will grow proportionally to the number of junk messages sent. The first several thousands emails will get to unlucky recipients when spamming starts, but the rest hundreds of thousands will not.
      Actually, webmail can do one better: if a message is marked as spam at some point in time, the system can retroactively remove it from the Inboxes of the 'first few thousand unlucky recipients' (or mark it 'this may be spam', gray it out, etc., at the least). I don't know of anyone doing this, but I wish they would.
    6. Re:sounds good to me by djtack · · Score: 1
      Not filtering based on the contents of the data should let them maintain plausible deniability and common carrier status.
      This is a popular myth, ISP's are not common carriers, nor do they want to be.
    7. Re:sounds good to me by nine-times · · Score: 1

      If some DSL customer suddenly starts opening hundreds of outgoing SMTP connections, that would be a pretty reliable sign that his machine is pwned.

      But what if the machine isn't "pwned"? Maybe the DSL customer just started a mailing list on his home server about... whatever.

      This is part of what makes spam such a problem, that the Internet really needs to be a bit of a free-for-all, or else people will be prevented from doing reasonable things that they technically should be able to do. We could end spam tomorrow if we chose only to receive e-mail from trusted sources. However, that would prevent Joe Schmo from setting up his own e-mail server.

    8. Re:sounds good to me by Mr.+Underbridge · · Score: 1

      I implemented a somewhat similar system (based on statistics such as TLD, time the email was received, whether it had attachments, how many recipients on the recipient list, etc) and it was decent. It's not as good as a good system that does consider text, but it wasn't as bad as many of the systems on the market.

    9. Re:sounds good to me by MBGMorden · · Score: 1

      That's one of the few GOOD things about Lotus Domino - the standard Notes client uses a proprietary protocol to submit messages back to the server (at least by default - it can be configured to use SMTP if you want to). So here we don't accept SMTP connections to our mail server from anything but the mail filter, which in turn blocks SMTP from all internal IP's except for the main mail server.

      All of our internet access also must go through an autheticated proxy, making the zombies that go out via HTTP kinda difficult to work too.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    10. Re:sounds good to me by Anpheus · · Score: 2, Interesting

      Qwest does this in a decidedly stupid fashion. Recently they detected a lot of SMTP traffic being spoofed as my email address (we don't even use their mailserver!) going through one of their servers and decided to drop our DSL. My father runs a few commercial websites for people and provides services through the DSL. We don't need much upload speed, so it works. Long story short, Qwest disconnected us after hours, and then refused repeatedly to connect us to anyone who could actually change our connection status. No port 25 blocking or throttling, just a full disconnect become somebody spoofed my email address and must have sent a good portion of spam with it. The mailserver that I use records a whopping twelve emails sent from me in the last five days. Connection was finally restored today, over thirteen hours later. Unacceptable.

    11. Re:sounds good to me by Anonymous Coward · · Score: 0

      There will probably always be Spam. However, I used to work for a company who had lots of problems with SPAM. After they used this service from Messagelabs. The spam dropped dramatically close to 0 messages. (see link for more info http://www.messagelabs.com/publishedcontent/publis h/services_dotcom_en/email_services/email_protect/ DA_157231.chp.html )

      I can't find any major flaws(besides price etc.)This system seems to have everything withstand Spam.I was wondering if there is a opensource alternative which has the same capabilities ans quality of scanning.

    12. Re:sounds good to me by DrSkwid · · Score: 1

      I'm a DSL customer.

      I've been known to send 1,000,000 legitimate emails a month.

      ISP's should protect their own mail servers. And that's it.

      They send me an invoice. I send them a cheque. End of story.

      However, in other news, I also rent a SPAM filtered POP box from them. They add the evil bit to stuff they consider SPAM. I download it and see if I concur. It works pretty well.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    13. Re:sounds good to me by jgc7 · · Score: 2, Insightful

      I agree, but you would have to be careful, because every newsletter/promotion might get marked as spam by a couple of people. The algorithm would need to be pretty sophisticated.

      --
      70% of statistics are made up.
    14. Re:sounds good to me by Anonymous Coward · · Score: 0

      I floated this before: why not start charging for email posting? Have each account type get a certain level of free messages and after that charge say 10 cents per message, or upgrade your internet service level for more message privilege? Would ISPs refuse a money making deal?

      Some spam will still get through, look at all the snail mail junk.

      Second a question, how come if I mis-spell an email address the message gets lost, but I recieve spam whose only similarity to my email address maybe the first letter??

    15. Re:sounds good to me by nuzak · · Score: 2, Insightful

      > Maybe the DSL customer just started a mailing list on his home server about... whatever.

      Then he asks to get port 25 unblocked. Or he's serious enough about his hobby mailing list to drop 8 quid a month for a dreamhost account (which isn't itself spam-free, but you know at least DH's nets aren't full of zombies). Or he switches to a web feed. There are solutions, but giving random strangers the benefit of the doubt isn't one of them.

      If SPF and Domainkeys ever got any traction, then Challenge-Response would be somewhat workable ... but I still refuse to jump through C-R hoops.

      --
      Done with slashdot, done with nerds, getting a life.
    16. Re:sounds good to me by vakuona · · Score: 1

      This would actually be a good idea. Most people I know use their web mail for personal use. Its available everywhere. If you send more than 1000 emails from home, then you (usually) have way too much time on your hands. At the very least, they could limit all people until they ask for more. That would take care of the zombies. If you normally send about 200 emails, and you find you can't send anymore, because someone has used up your allocation, they you are quite likely to take action. I know it is punishing the user, but it is unavoidable. If users can't take care of their PCs, they should expect inconvenience here and there. And besides, they always have webmail.

    17. Re:sounds good to me by seanadams.com · · Score: 1

      The new bread of zombies have wised up to port 25 blocking / throttling and like to funnel everything through the MTA for the domain to which they are connected.

      But that doesn't make this any less effective. We're not looking at the _receiving_ side, we are catching the _senders_.

      A sender is still going to open connections and send data just as quickly, whether he's consolidating recipients by MTA or not. The number of attempted recipients may be higher, but the detection would be exactly as effective.

    18. Re:sounds good to me by goofyspouse · · Score: 2, Funny

      Zombie Bread, a whole brain in every loaf!

    19. Re:sounds good to me by GreggBz · · Score: 4, Funny

      It's blue! It's moldy! It's the The night of the living Bread.

    20. Re:sounds good to me by beckerist · · Score: 1

      Is there any sort of consumer interest in this? This sounds convenient for a corporate system where you have complete control over the server, but in a residential environment where my email is controlled at every level until it hits my inbox, this isn't a very plausible solution.

      Ultimately, we should get rid of "email" altogether, or at least the 30 year old technology behind it, and use more secure messaging methods. Sure this would take a lot of work, but I have many clients (ie: Outlook Express) that can not only check SMTP mail, but also HTTP (and I'm sure many more with the right plugins). Granted, this would require much more than a simple change in protocol, but I don't see how it would be so hard to force validation of each message sent (in the form of worldwide black/white lists?)

      What we need is the Email 2.0 revolution.

    21. Re:sounds good to me by floydvoid · · Score: 1

      yahoo is already doing something like this , there is one particular newletter/ad (optin ,definately legit ,not spam) that I subscribe to that about half the time ends up in my "bulk" mailbox. on the whole though less than 1% makes it to my real inbox, so I just do a quick scan of my bulkbox before I hit empty.I woulnt want them automaticly deleting it though or I would lose (a small amount)legitimate mail.

    22. Re:sounds good to me by PitaBred · · Score: 1

      If you're using a business DSL line, you should complain loudly. If it's a home user line, well... you get what you pay for. Running a serious business on the Internet requires redundant connections.

    23. Re:sounds good to me by Joosy · · Score: 1

      I've been known to send 1,000,000 legitimate emails a month.

      Unhh ... well if this is really true then you could always explain your legitimate reasons to the ISP and they'd let you send it.

      ISP's should protect their own mail servers. And that's it.

      One way to protect their own mail servers is by not sending 1,000,000 emails a month from zombied computers.

      --
      I'm sick and tired of these hip, "ironic" sigs. This is an actual, honest-to-goodness no-nonsense sig!
    24. Re:sounds good to me by DrSkwid · · Score: 1

      >> I've been known to send 1,000,000 legitimate emails a month.
      > Unhh ... well if this is really true then you could always explain your legitimate reasons to the ISP and they'd let you send it.

      It is really true and I should have to explain as much to my bandwidth supplier about how I use bandwidth as I do to my electricity supplier concerning my joules per coulomb.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    25. Re:sounds good to me by macdaddy · · Score: 1

      Exactly. I can't stop a machine from being pwned. I can however stop the flood of SMTP from my customers. I posted some numbers in another message. It's the only effective method we as ISPs can undertake. A single outgoing message can get an IP in one of our customer dynamic pools on a dozen lists. A dozen messages from a dozen random users will poor local security (not too hard to find I imagine) can get the entire dynamic pool blocked. A hundred pieces of spam and a poorly run DNSBL will expand the block to our whole ISP. That's not good for business. Throttling obviously can't work. Flat out rejecting outgoing SMTP connections is the only way.

    26. Re:sounds good to me by macdaddy · · Score: 1

      Agreed. If they used a residential connection then they got exactly what they paid for. If they were on a business connection then they should become very vocal.

    27. Re:sounds good to me by Joosy · · Score: 1

      I've been known to send 1,000,000 legitimate emails a month.
      Unhh ... well if this is really true then you could always explain your legitimate reasons to the ISP and they'd let you send it.
      It is really true and I should have to explain as much to my bandwidth supplier about how I use bandwidth as I do to my electricity supplier concerning my joules per coulomb.
      Try telling your electricity provider you expect to get 1,000,000 amp service for the same price you're getting 150 amp service.
      --
      I'm sick and tired of these hip, "ironic" sigs. This is an actual, honest-to-goodness no-nonsense sig!
  2. This is painfully obvious and hopelessly naive but by Recovering+Hater · · Score: 3, Interesting

    I am going to say it anyway. Why can't people stop responding to spam in the first place? Is it too much to ask? If spammers made absolutely zero dollars for their efforts would they stop? Will underdog be able to escape from the burning rubble in time? Tune in next week to find out in our next exciting adventure!

    --
    My humor is probably your flamebait
  3. Re:This is painfully obvious and hopelessly naive by jimicus · · Score: 5, Funny

    As soon as you've found a way to get that message through effectively to 100% of the population, do let us know.

  4. I'll never stop by diskofish · · Score: 5, Funny

    Where else would I get my Viagra from?

    1. Re:I'll never stop by El_Muerte_TDS · · Score: 4, Funny

      You shouldn't. Impotence is nature's signal that you are not fit for reproduction. Your reproduction will only result in more people responding to spam, which is ofcourse a bad thing.

      So do the world a favor... please...

    2. Re:I'll never stop by lufo · · Score: 1

      Viagra isn't a cure for reproductive problems. Surely it makes reproduction easier, but you can take Viagra without heading for reproduction.
      On the other hand, you can have perfectly normal erection AND total reproductive impairment.

    3. Re:I'll never stop by Anonymous Coward · · Score: 0
      Where else would I get my Viagra from?
      It looks like you mispelled that, here let me help you.
      Where else would I get my ..;:- V 1 A G R A -:;.. from?
      There, much better
  5. unlikely indicators by Speare · · Score: 4, Insightful

    I think the question raises an interesting point: spams *behave* differently on the network than most legitimate emails. It may not be a perfect discriminator, but it sure might be a corroborative scoring aid. This reminded me of the controversy when Slashdot started using text compressibility as a metric for "lameness." I was a disbeliever, and still have my reservations about it, but as a part of the overall toolbox for filtering lameness, the technique seems to have value.

    --
    [ .sig file not found ]
  6. Dangerous by Anonymous Coward · · Score: 0

    Spammers could reduce the trust in this system by reporting false traffic from legitimate servers, especially as long as the participation is still low. Instead of having to trust the source, you now have to trust intermediates. In order for this to work, intermediates would have to be selected carefully.

  7. greylisting works by grub · · Score: 2, Insightful


    OpenBSD's greylisting in spamd works wonders.

    --
    Trolling is a art,
    1. Re:greylisting works by ivan256 · · Score: 1

      Greylisting is great and all, but I'm left wondering what OpenBSD has to do with it... Can you name a single operating system that can run an MTA that can't do greylisting?

      I didn't think so.

    2. Re:greylisting works by grub · · Score: 1


      Greylisting is great and all, but I'm left wondering what OpenBSD has to do with it... Can you name a single operating system that can run an MTA that can't do greylisting?

      Durr... This isn't on the MTA, this runs on the firewall or gateway before the spam touches your MTA. It saves your MTA from having to deal with this crap before it ever touches it.

      --
      Trolling is a art,
    3. Re:greylisting works by ivan256 · · Score: 1

      I read the docs, and I still don't see how it's any different than the greylisting deamons (written in a variety of languages, and some probably sharing code with this one) that run on Linux or Windows.

    4. Re:greylisting works by TheRaven64 · · Score: 1

      OpenBSD's spamd does tar-pitting as well as grey-listing, and can run in front of any MTA. It uses pf to redirect connections on port 25 from suspect IPs to its own port. It is very low resource usage; a modest machine can easily keep a few thousand connections to spamd open for 10-15 minutes to send the 'denied' response, while still processing mail in whatever MTA you happen to be using. It has been part of the OpenBSD base system since OpenBSD 3.3 (2003), and is very easy to configure. Since the cost of running it is so low, pretty much all OpenBSD machines running an MTA turn it on.

      --
      I am TheRaven on Soylent News
    5. Re:greylisting works by h4ck7h3p14n37 · · Score: 1

      Bob Beck gave a talk on spamd at NYCBSDCon this past October. I've published some recordings of the conference proceedings, but only on DVD and CD media so they're not available on the Net. A guy named Nikolai from the NYC group also made recordings, which he's posted here:
      http://www.fetissov.org/public/nycbsdcon06/


      Here's a direct link to the spamd presentation. Slides are also available.


      You're welcome :)

  8. The problem with this by wiredog · · Score: 5, Insightful

    Mailing lists. How does it not tag a server that sends out mail to a list as a spammer?

    1. Re:The problem with this by crossmr · · Score: 1

      I'm betting the average bit of spam set out doesn't have anything on 99.9999999999% of mailing lists out there. Anyone with a mailing list which would approach the levels of spam one would expect from a compromised computer can speak with their ISP and give them the details to get an exemption.

    2. Re:The problem with this by gmuslera · · Score: 1

      Mailing list are a problem, but is something that could have a sustained ratio of sent mails, and maybe more important, a sustained ratio of received mails, if you count mails coming from and going to that host can lower the score as the mix of both traffics can hint a mailing list server there.

      But what about announcement lists? You know, you sign up in a site, company, etc, and want to receive a mail when something big changes, a new product, whatever. That are usually unidirectional, targets a lot of people, and happens once in a while, very much like spam, if you look only at the traffic there.

    3. Re:The problem with this by kevin_conaway · · Score: 1

      Indeed.

      To expand on your idea, think about the small business owner who sends a monthly newsletter to a few hundred of his customers from his home pc.

    4. Re:The problem with this by Tom · · Score: 1

      Solveable problem. The traffic pattern of a mailing list is different from the traffic pattern of spam. Just for starters: Very few mailing lists have 50 million different subscribers.

      The devil in this doesn't lie in the concept, the concept is sound. Implementation will be tricky.

      --
      Assorted stuff I do sometimes: Lemuria.org
    5. Re:The problem with this by Duhavid · · Score: 1

      I expect you are correct, but what do you want to bet that
      the ISP's will institute some small fee for so listing.

      And some spammers will declare themselves as mailing lists
      ( they claim to obey opt in now, right, but we know they dont )
      and continue.

      Here is an idea: find a way to combine this with user moderation,
      if enough of your list thinks you are spam, and the traffic
      pattern analysis thinks it might be, then it is. How to
      moderate is the question. Embed a link in the email?
      "Click here to vote this email as spam."
      Or, for the purists, one could send a voting email to the
      user ( with the above link, and some explaination ), delay,
      then send the actual email. Or make the original email
      an embedded attachment to "our" email, send as a unit.
      Assuming that the traffic pattern analysis determined the item
      was questionable. Link would point back to a site set up
      by the maintainer of the MTA.

      --
      emt 377 emt 4
    6. Re:The problem with this by jdunlevy · · Score: 1
      This is addressed -- somewhat less that satisfactorily, I think, but, then, this is a first proposal -- in the linked article under the "One-To-Many" junk mail scenario heading:
      Unless you are a large ISP or an official mass-mailing source (for example, an organization sending periodical newsletters to customers), there is no need for you to send thousands of messages within minutes. Official bulk mail sources can be exempted (whitelisted) if necessary. Large SMTP sources (ISPs or webmail providers) with more or less constant traffic volumes can also be statistically identified. But if a source suddenly appears and starts sending hundreds of messages in all directions, it is likely a junk mail transmitter.

      The problem is whitelisting involves additional work.

      For Source Trust Prediction (STP) filtering to work, you not only have to get an STP score, but you also have to check whether that score should be discounted because the sending IP is a known legitimate mass mailer. What about a legitimate mass mailer (including not just mailing lists, banks, online stores, political organizations, and social networking sites, but also services that handle mailings for these entities) that's ramping up -- either adding additional IPs to its network or changing IPs -- for sending mail or adding new clients? What's the process for getting whitelisted, and what's to keep spammers from using and abusing that process (either getting themselves somehow listed or DOSing the whitelist request process -- assuming shared/centralized whitelists, shared/centralized being less work than if every mail admin maintains his/her own whitelists.)

      For that matter, imagine a scenario it which a news site or blog posts something of particularly bursty interest and that site lets users e-mail the article to a friend? Suddenly a site that historically hasn't looked anything like a spammer may look statistically similar to a spammer. No need for that site to have been whitelisted before, but suddenly the need is there.

      Interesting idea, though, and I could certainly see STP being useful in combination with other tests (bayesian, pattern matching, dnsbl, etc.), but I'm much more skeptical about usefulness (avoiding false positives) in terms of actually blocking mail. And: a test that's used for filtering but not blocking spam means even more work for the filtering mail server (or client) to do.

  9. Greylisting by Daemonstar · · Score: 1, Informative
    This is similar to greylisting that has been around for a bit.

    Greylisting is a simple method of defending electronic mail users against e-mail spam. In short, a mail transfer agent which uses greylisting will "temporarily reject" any email from a sender it does not recognize. If the mail is legitimate, the originating server will try again to send it later, at which time the destination will accept it. If the mail is from a spammer, it will probably not be retried, however, even spam sources which re-transmit later will be more likely to be listed in DNSBLs and distributed signature systems such as Vipul's Razor. Greylisting requires little configuration and modest resources. It is designed as a complement to existing defenses against spam, and not as a replacement.
    --
    I don't reply to Anonymous posts; if you have something to say to me, identify yourself or I won't reply.
    1. Re:Greylisting by Anonymous Coward · · Score: 1, Interesting

      No it's not similar. Greylisting works by exploiting that most spam-MTAs aren't RFC-compliant and don't retry after temporary errors. Greylisting will certainly be worked around. Legitimate MTAs can get around it. The fact that many spam-MTAs currently can't is a fixable bug.

      The proposed method looks at traffic patterns to find and block spammy MTAs. It does not rely on bugs in the MTAs.

    2. Re:Greylisting by Gary+W.+Longsine · · Score: 1

      No, greylisting can be applied to RFC-compliant MTAs as well.

      --
      If you mod me down, I shall become more powerful than you could possibly imagine.
    3. Re:Greylisting by Daemonstar · · Score: 1
      *sigh* I'll bend my rule of not responding to AC's this time, because you obviously do not understand the reasoning behind greylisting; it has nothing to do with "buggy MTA's", but with intentional misconfiguration (taken from the TAMU website):

      According to the internet specification, when a mail server receives a "400-level" error, it must queue the e-mail message and try later to deliver it. For legitimate e-mail, this process is standard and mandatory. Properly configured mail servers will redeliver their messages appropriately and greylisting should not represent a delivery challenge to them. Because SPAMmers send hundreds of thousands of e-mails per day to addresses they do not know to be working, they generate a large number of bounced messages. Acknowledging server responses for these messages, storing the messages on a server for some period of time, and redelivering them again represents for SPAMmers a resource-intensive process that might very well not return sales of their products or services. As a result, they intentionally misconfigure their mail servers. By requiring that every incoming e-mail message to the University originate from a properly configured mail server, most SPAM is filtered.
      Of course greylisting can be worked around, but doing so puts a resource hit on the sending mail server; the bigger the hit, the slower it can send out SPAM. As for the receiving mail server, the greylisting service doesn't run on the MTA, but on the MX farm for the domain. Legitimate mail is then forwarded to the domain's MTA.

      In the realm of similarity, slowlists are also an option.
      --
      I don't reply to Anonymous posts; if you have something to say to me, identify yourself or I won't reply.
    4. Re:Greylisting by Anonymous Coward · · Score: 0

      As a result, they intentionally misconfigure their mail servers. ...and thus make them non-compliant with the applicable RFCs. If greylisting becomes a problem for spammers, it will be worked around. The spammers handle gigabyte-sized lists of email addresses with ease. What makes you think they can't remember what messages to retry if they have to?

  10. Re:This is painfully obvious and hopelessly naive by stavrosg · · Score: 2, Insightful
    I am going to say it anyway. Why can't people stop responding to spam in the first place? Is it too much to ask?

    People will stop buying from spam when they stop forwarding every hoax or urban legend they recieve through their company e-mail to everybody else on their address book.

    When someone finds a way to do it, please ping me.

  11. request by illuminatedwax · · Score: 3, Funny

    please put obligatory Standard Spam Form joke below here please

    we've got to keep this place organized

    --
    Did you ever notice that *nix doesn't even cover Linux?
    1. Re:request by Anonymous Coward · · Score: 0

      It's not a joke. Ok, maybe the idea of responding to technical proposals with a form letter can be considered humorous, but the actual points in the form letter are valid and it is usually filled out pretty much correctly. Spam is a difficult problem, there is an ongoing flow of half-baked proposals, and most proposals fail in a number of common ways. If the proponents can't be bothered considering the common failure modes, why should the respondent take more trouble than filling out a standard form?

    2. Re:request by Anonymous Coward · · Score: 0

      yeah, but this way we can keep all those forms together instead of spreading them out all over the top level!! didn't your mother teach you anything

    3. Re:request by NaDrew · · Score: 1

      Spam is a difficult problem, there is an ongoing flow of half-baked proposals, and most proposals fail in a number of common ways. If the proponents can't be bothered considering the common failure modes, why should the respondent take more trouble than filling out a standard form?
      Because by implication--since some asshat posts this form message to every single discussion about spam--there is nothing that can be done, so why bother? And that's not the way to think if you want to win a battle.
      --
      Vista:XPSP2::ME:98SE
  12. Re:This is painfully obvious and hopelessly naive by the+dark+hero · · Score: 4, Insightful

    That's the problem. this world is full of stupid people. They might not make money off of most people the spam gets to, but if you cast a big enough net you're bound to catch something(including some dolphins). Millions of pennies still add up to thousands of dollars.

    --
    You constantly struggle for self improvement - and it shows.

    Hooray for bad Engrish on fortune cookies

  13. Re:This is painfully obvious and hopelessly naive by Grey+Ninja · · Score: 5, Funny

    We could try mass mailing them. I've had some success with that in the past. =)

  14. An interesting approach by APOLAUF · · Score: 0

    I believe that this is a very viable approach. I am currently doing research on intelligent intrusion detection systems (not based on traffic analysis), and while SPAM and IDS don't seem awfully related, both traditional traffic-based IDSs and STP utilize data traffic analysis methods to identify potential problems. That being said, I think that the traffic analysis should be used only in combination with existing spam control and heuristics; it's a complex and multi-faceted problem and thus requires several fronts to combat it.

  15. Yes and no - but a suggestion... by Penguinisto · · Score: 2, Insightful
    I like the idea of gathering and using statistics on traffic patterns, but what they're looking for in many cases can be too easily defeated (e.g. "Junk messages are small"... now we get to watch MTA's spend more time trying to sort spam messages packed to the gills w/ random ASCII, necessitating a look through the message body all over again).

    OTOH, As part of a larger array of spam-fighting tools, okay - there's bits in there I actually like and which can be used as part of other solutions, if not used in the way suggested. As someone who runs a couple of MTA's on top of everything else I do around here, I always like to find new and interesting ways of stopping spam.

    N.B., all that I ask is this: Please make it useful w/o sucking down resources or requisitioning another server. I detest external RBL's - please don't suggest anything that may have an overly-subjective and/or an overly-dependant basis like that. If it isn't RFC-compliant (yes, Verizon, I'm talking to YOU when I say that!), I won't go near it.

    Satisfy those, and yes, I'm interested, as would lots of other SMTP-monkeys out here.

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
  16. Obligatory by teslar · · Score: 4, Funny

    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
    (x) Mailing lists and other legitimate email uses would be affected
    ( ) No one will be able to find the guy or collect the money
    (x) It is defenseless against brute force attacks
    (x) 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
    ( ) 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
    ( ) Armies of worm riddled broadband-connected Windows boxes
    (x) Eternal arms race involved in all filtering approaches
    ( ) Extreme profitability of spam
    ( ) Joe jobs and/or identity theft
    ( ) Technically illiterate politicians
    ( ) Extreme stupidity on the part of people who do business with spammers
    ( ) Dishonesty on the part of spammers themselves
    ( ) Bandwidth costs that are unaffected by client filtering
    ( ) Outlook

    and the following philosophical objections may also apply:

    ( ) 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
    (x) 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!

    1. Re:Obligatory by Anonymous Coward · · Score: 1, Insightful

      Frighteningly, this was the first thing I looked for in the comments. It's almost becoming the de facto "executive summary" for every article on a new spam fighting technique.

    2. Re:Obligatory by hlh_nospam · · Score: 1
      "( ) Sending email should be free"


      Interesting canned response letter; although I've seen similar posted on the usenet email abuse lists.

      However, the assertion that sending email should be free is questionable. First of all, email is NOT free anyway -- it ALWAYS arrives postage-due, i.e., the recipient pays the majority of all cost either directly or indirectly for all email. That is the ONLY reason that spam exists in the first place. The marginal cost of sending spam is very nearly zero, so even a four-sigma sucker rate is profitable. And recent headlines indicate that 419 "advance fee" scams are still lucrative. As are "pump-and-dump" scams.

      As unpopular as the idea of email postage is, it is the only effective way to stop spam. (Hunting down and killing spammers is not considered Politically Correct in most countries.) Another thing that might help some is an email system that does not allow forged addresses (which I would definitely like to see, especially since one of my business email addresses was joe-jobbed into uselessness).

    3. Re:Obligatory by Tom · · Score: 1

      (x) You didn't understand before you hit "reply".

      In theory, this would work and mailing lists would not be a problem. If the implementation sucks, though...

      Same for "why trust your servers"? - you don't have to. If the method works, there will be multiple services offering similar products, and you can choose which one to trust.

      --
      Assorted stuff I do sometimes: Lemuria.org
    4. Re:Obligatory by Peter+La+Casse · · Score: 2, Interesting

      This form is for ideas that have been thought of before and have been discredited, but I'm not convinced yet that this idea wouldn't work. Here are the biggest objections you raised:

      (x) Mailing lists and other legitimate email uses would be affected

      How? The method specifically mentions whitelisting, and only mailing lists or other "legitimate uses" (can't think of any myself) that involve thousands of recipients would be noticed by the proposed algorithm.

      (x) It is defenseless against brute force attacks

      All the usual anti-DOS strategies would work perfectly well here. The same statistics used to identify patterns can identify junk data sent by spammers to confuse the system. The closest thing to a "brute force attack" that would work would be for a spammer to use a bigger botnet and have each node send messages at a rate low enough to not be noticed. That's a significant victory for the rest of us.

      (x) It will stop spam for two weeks and then we'll be stuck with it

      What other methods counter this approach, and what stops people from dropping it if/when it stops working? (Note that the article discusses four attacks, two of which count as a win for the good guys and two of which have viable counterattacks.)

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

      You don't have to trust them any more than you trust any other anti-spam service that provides data to your filtering algorithm.

      I don't claim that this method is good, but that the objections raised so far have not been very convincing.

    5. Re:Obligatory by Anonymous Coward · · Score: 0

      It is funny, and I think the point of if there was a simple solution to spam, we'd be using it.

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

      I just don't like the defeatist attitude. So what if spam is an arms race? That's no reason to proclaim that something won't work without even thinking about it, let alone trying it.

    7. Re:Obligatory by kenb215 · · Score: 1

      Wow. For a standardized form, parent and a post above vary a lot. Fourteen options are either checked here and not there, or vice versa.

    8. Re:Obligatory by SanityInAnarchy · · Score: 1
      How? The method specifically mentions whitelisting

      Oh, so should we have checked "whitelists suck"?

      You don't have to trust them any more than you trust any other anti-spam service that provides data to your filtering algorithm.

      Which is still too much. Blacklists can block things I'd rather have come through.

      --
      Don't thank God, thank a doctor!
    9. Re:Obligatory by Peter+La+Casse · · Score: 1

      How? The method specifically mentions whitelisting

      Oh, so should we have checked "whitelists suck"?

      Yes, why wasn't that box checked? That's a legitimate criticism not mentioned by the article's authors. At least it's only high-volume mailing lists that would need to be whitelisted.

      You don't have to trust them any more than you trust any other anti-spam service that provides data to your filtering algorithm.

      Which is still too much. Blacklists can block things I'd rather have come through.

      It was a trick statement: the amount that you have to trust other anti-spam services is zero. So, you don't have to trust the servers of the implementors of this new method at all; simply don't use it. More realistically, if you don't trust it, assign it a lower than usual percentage of your spam-detection algorithm and then see how well it correlates with actual spam.

    10. Re:Obligatory by totally+bogus+dude · · Score: 1
      i.e., the recipient pays the majority of all cost either directly or indirectly for all email.

      Is there anything to support this claim? It doesn't sound right to me. Both the sender and the recipient need an internet connection, and both parties have to pay for that. Cheap home internet connections are quite capable of receiving very large numbers of emails (especially with services like Gmail available). Large-volume senders tend to need to either pay another company, or manage their own mail servers.

      That is the ONLY reason that spam exists in the first place.

      Most spam seems to be sent by botnets, so it's the user of compromised machines that pays for most of the volume; and this cost is spread amongst a very large population. This is what makes it cheap. If the spammers actually had to pay for all the bandwidth they're using, it would almost certainly cease to be profitable.

  17. And yet likely... by paladinwannabe2 · · Score: 1

    Bayesian filters sometimes find weird words to do filtering on. Obviously there is 'Viagra' and 'Manhood' but there are also words like 'Republic' that have very high correlations with phishing spam- because any email that from the 'Democratic People's Republic of $Country' is likely to be as bogus as the countries name. If a country needs to add 'Democratic' or 'Republic' to its name, you know something's wrong.

    In a similar way, any easily compressed text (like boing
    boing
    boing
    boing
    boing
    boing
    ) is most likely someone hitting cut and past over and over again. AND I THINK WE CAN AGREE THAT TALKING IN ALL CAPS /-\|\||) |_33+ |5 |_/-\|V|3.

    --
    You are reading a copy of my copyrighted post.
    1. Re:And yet likely... by Zocalo · · Score: 3, Insightful

      because any email that from the 'Democratic People's Republic of $Country' is likely to be as bogus as the countries name. If a country needs to add 'Democratic' or 'Republic' to its name, you know something's wrong

      • Central African Republic
      • Czech Republic
      • Democratic Republic of the Congo
      • Dominican Republic
      • Former Yugoslav Republic of Macedonia
      And that's just the common names and not the official ones like "Republic of Ireland". Given that this is precisely the kind of verbose terminology that you would find in a genuine official email from a government body in such a country, I don't think that's going be suitable for anything other than a minor nudge towards spamminess.
      --
      UNIX? They're not even circumcised! Savages!
    2. Re:And yet likely... by bscanl · · Score: 1

      Totally OT: "Republic of Ireland" is not a country. Éire, or Ireland, is the name of the country you are thinking of. "Republic of Ireland" is a description of Éire, or Ireland, as per the Republic of Ireland Act 1949.

  18. OPPOTUNITY. == DISCRETION REQUIRED == by Anonymous Coward · · Score: 5, Funny

    SIR,

    OUR TECHNOLOGY DEPARTMENT HAS COME UP WITH A GREAT OPPUTUNITY TO STOP ALL YOUR SPAM. THIS TECHNOLOGY IS CALLED source Trust Prediction (STP). IT WORKS BASED ON identifying patterns and trends in real time AND IN THIS WAY PREVENT SPAM. HOWEVER TO MAKE PROFIT FROM THIS NEW TECHNOLOGYY WE NEED TO DO A PATENT APPLICATION. YOUR NAME CAME FORWARD AS AN EXCELLENT INVESTOR FOR THIS. WITH THE CURRENT RISE OF SPAM THIS TECH WILL BE REQUIRED QUICKLY BY A LOT OF PEOPLE.

    I am only contacting you as a foreigner, I will use my influence to
    effect legal approvals and onward transfer into your account At the
    conclusion of this business, you will be given 50% of the total
    PROFITS, 50% will be for me and my family AFTER DEDUCTION OF THE PATENT COSTS
    . I await to hear from you.

    Yours truly,

    Mr.Barry Leoard.

    FNB OF SOUTH AFRICA
    THIS
    IS MY PRIVATE EMAIL ADDRESS, YOU CAN SEND YOUR REPLY HERE:-
    barryleonard@walla.com

    1. Re:OPPOTUNITY. == DISCRETION REQUIRED == by Archangel+Michael · · Score: 3, Funny

      Source Trust Detection (STD)

      There, fixed your spelling ...

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  19. Dead on the money. by WindBourne · · Score: 1

    3 years ago, I was working developing some software for sale to the feds and commercial world. For the commercial world, I proposed the same idea. The only way to stop spam is have cooperating servers. More importantly, they need to have a lot of servers where fake addresses can be sent to. Load these into outlook and let the spammers harvest them. Now, you have a decent service that can be offered for free or sold.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Dead on the money. by Dark_Gravity · · Score: 1

      More importantly, they need to have a lot of servers where fake addresses can be sent to. Load these into outlook and let the spammers harvest them.

      That makes no sense whatsoever! While I have no doubt that address books have been captured by virii over the years, your plan is lacking in both clarity and details to the point where it is on the verge of absurdity. There are certainly easier ways to seed spammer lists with your spamtraps.

    2. Re:Dead on the money. by WindBourne · · Score: 1

      Even though it looks to me like you are just trolling and I am guessing that you have not worked in the security field, here goes. Something like about 1/3 to 1/2 of all captured addresses/spam come from Windows being infected. At that time, the virus spews spam based on what is in outlook. If you have a single address in there with a varied host abc@def.com, while I have u@suck.com, then the spammer can not figure out which address is real. Once the email is sent to the capture box, and it has several with similarities (point to a site; talk about a product; etc), then it can look at it and tell other front-end mail servers (or in what was suppose to be our case, even in front of that ), that an e-mail is spam. Basically, this is a way to prime the pump early on so that you can minimize the damage from poorly designed OS.

      --
      I prefer the "u" in honour as it seems to be missing these days.
  20. Re:This is painfully obvious and hopelessly naive by Pontus_Pih · · Score: 4, Interesting

    I was going to say... What would happen if we all started replying with the same auto generated mails? How would the spammers tell the difference from legit spam replies?

  21. Re:Obligatory spam solution post by Southpaw018 · · Score: 1

    Damn, got beat to it. Sorry for the redundant spammy post!

    --
    ACs are modded -6. I don't read you, I don't mod you, I don't see you. Don't like it? Don't be a coward.
  22. Re:This is painfully obvious and hopelessly naive by Anonymous Coward · · Score: 0

    As soon as you've found a way to get that message through effectively to 100% of the population, do let us know.

    Send out a spam saying you can enlarge the recipient's penis. When the link is clicked, it should go to a website that plays audio screaming at the person for being an idiot. A big flashing red message would be good too. Not everyone will get the message, but everyone that needs it will.

  23. The efficiency of throttling by kalpaha · · Score: 1

    I guess it makes sense to throttle the connection: it will do no harm to legitimate email (I mean, it's not like it would really matter if the delivery takes 10 seconds or 50 seconds), but would seriously hamper the sending of millions of messages. That way, it wouldn't really matter if it gets some false positives, unlike with methods where the message is removed if it's deemed spam.

    1. Re:The efficiency of throttling by markbt73 · · Score: 1

      Better yet, throttle the spammers themselves...

      --
      "Oh boy! Are we going to try something dangerous?"
  24. Problem by Billosaur · · Score: 1

    What about legitimate mass marketers. The company I work for contracts with advertisers to send out bulk mailings to our opted-in users. Now, we don't spit out emails by the millions, but we certainly do send out large chunks of emails from a common source. Is this kind of thing going to interfere with legitimate mailings to opted-in customers?

    --
    GetOuttaMySpace - The Anti-Social Network
    1. Re:Problem by radja · · Score: 1

      probably, but since the use of hexview's product is also opt-in, that's not a problem.

      --

      No one can understand the truth until he drinks of coffee's frothy goodness.
      --Sheikh Abd-Al-Kadir, 1587
    2. Re:Problem by cdrguru · · Score: 0, Troll

      You apparently don't get it. First rule of anti-spammers is "Spammers lie". The second rule is there is no such thing as a voluntary, opt-in managed mailing list that isn't just spam.

      So, you say your business is legitimate. Obviously, you are lying. Spammers lie.

      But your list is opt-in and only send legitimate email? Too bad, if someone gets it that forgot they signed up, it's spam. Therefore, you are a spammer.

      While this technique might hold some value, it isn't going to counter the way spam is being sent today - not from a single source but from many, many sources.

    3. Re:Problem by Billosaur · · Score: 1

      We have a new world's record in the Jump to Conclusions!

      Anybody got a "Troll" mod point to spare?

      --
      GetOuttaMySpace - The Anti-Social Network
    4. Re:Problem by 91degrees · · Score: 1

      You apparently don't get it. First rule of anti-spammers is "Spammers lie".

      Yes. Spammers say they don't spam. Non-spammers say they don't spam. You're at a fork in the road with a spammer and a non-spammer...

      The second rule is there is no such thing as a voluntary, opt-in managed mailing list that isn't just spam.

      Sure there is. I'm subscribed to 5 of them. 3 from yahoo groups, and a couple of DVD shops that occasionally have decent special offers.

      So, you say your business is legitimate. Obviously, you are lying. Spammers lie.

      Why is this "obvious"?

      But your list is opt-in and only send legitimate email? Too bad, if someone gets it that forgot they signed up, it's spam.

      If the subcribers genuinely opted in, this "spam" would appear to benefit the subscribers as well as the sender. Why should everyone else suffer because one of the subscribers is incompetent?

      Therefore, you are a spammer.

      How so? He's sending solicted email.

    5. Re:Problem by ynohoo · · Score: 1

      What about legitimate mass marketers.

      Dont be silly - they are all bastards.

      Just because your business model is (currently) legal, does not make it defensible outside of a court of law. Around here, you are still vermin.

    6. Re:Problem by Animats · · Score: 2, Interesting

      The company I work for contracts with advertisers to send out bulk mailings to our opted-in users.

      And did they opt in by specifically requesting your mail, or implicitly as part of some other transaction? If it's the latter, you're a spammer. Die.

      If people really want your content, offer an RSS feed. If nobody subscribes to your feed, they didn't want your content.

    7. Re:Problem by metamatic · · Score: 1

      Legitimate mass marketers can provide web feeds of their promo information. Like Nintendo do, for example. Or TigerDirect. Or Amazon.com.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    8. Re:Problem by British · · Score: 1

      Excellent point. There are way too many websites with 'sign up for our email newsletter' , and you know what? Most of it is pointless, and is probably an excuse to get peoples' email address for, of course, to resell it to spammers. The next step of that are websites that require registration for no real reason.

      An RSS feed would also prevent X from signing up to mailing lists with person Y's email address. There are guards in place for that(one-time-passwords), but an email still gets sent, and thus can be an annoyance.

      RSS all the way, I say. RSS is great for impersonal communication.

    9. Re:Problem by Ash-Fox · · Score: 1

      I used to run a free webhosting provider some time ago. Our servers used to get hammered badly on the hour, every hour because of RSS feeds that users used to have on their sites. RSS is not as bandwith friendly as sending out a single e-mail to each user when there is a update.

      --
      Change is certain; progress is not obligatory.
  25. Its not snake oil, but... by popo · · Score: 4, Interesting

    ... and its not disimilar from greylisting from what I can tell, but I don't think its going to be
    effective in the long term. Getting around this type of filter (or delay) seems relatively simple
    compared to the task of defeating the bayesian filters over the past couple years.

    The lynchpin of greylisting is that legitimate mail will "try again" after being returned by the
    server, while spam will not. The conclusion (which we hope is true) is that any mail that is
    not re-sent was in fact spam. Never mind the danger that the assumption could be false and
    legitimate mail gets lost -- how long will it be before spammers simply "re try" their spam --
    or worse -- just send everything twice?

    As with any attempt to modify behavior electronically -- behavior usually wins.

    --
    ------ The best brain training is now totally free : )
    1. Re:Its not snake oil, but... by stu42j · · Score: 1
      just send everything twice?


      Many already do but not enough to stop greylisting from being ineffective. Even if all you do is delay the message you still increase the chance that the message can be blocked by other means.
    2. Re:Its not snake oil, but... by raddan · · Score: 2, Insightful

      The nice thing about greylisting is that if spammers learn the "trick" of becoming RFC-compliant and thus retry their connections, the cost of their operation goes up. The cost may be small over several thousand messages per day, which is easily handled by a normal, behaving MTA, but for a spammer whose cost calculations depend on spewing out millions of emails per day, it may be a dealbreaker. Combine that with tarpitting and some way of feeding Bayes scores back to the tarpit/greylist (ala relaydb), and you have a really effective spam-prevention system. A spammer who lets himself get stuck in a tarpit is going to lose money. Spammers will have to work a little harder than simple RFC-compliance.

  26. Solution by VincenzoRomano · · Score: 1

    The SMTP protocol is showing all its age and weakness. It has not been designed to cope with today's use.
    First of all it lacks authentication and authorisation mechanisms. The various anti-spam, white/black/grey listing look more like workarounds than solution.
    Then you'd like to really know whether your message has been delivered or not and other nice details about the messages.
    My personal feeling is that it's time now for a new messaging protocol.
    SMTP is dead, long life to SMTP!

    --
    Maybe Computers will never be as intelligent as Humans.
    For sure they won't ever become so stupid. [VR-1988]
    1. Re:Solution by John+Bayko · · Score: 1
      I see two possible replacements for email.

      One is based on RSS (or similar, like Atom). Right now, RSS is used for what amounts to "mailing lists", by notifying the recipients there's something new, and they can pick up their copy - though it works by polling, no actual notification is sent.

      One extremely important advantage of this is that you know exactly where the material is from.

      I'm hoping that future versions will allow an RSS feed to be customised per user, which would basically amount to sender-hosted email, meaning a) the sender bears costs for the email, and b) the source cannot in any way be faked.

      There are disadvantages, including the question of how someone can send you email for the first time. One solution is that you can "piggyback" on someone else's RSS feed for the first message (a common friend, or a well-known site like slashdot, or a blog site). This acts like an implicit filter, since you wouldn't have an RSS feed from someone you didn't trust enough to have some discretion to not spam you.

      You'd no longer ask for someone's email address if you wanted to send them something, you'd give them your RSS feed.

      The second scenario I see happening is based on "community sites" like MySpace or Livejournal. Most of these sites have features to let you know if someone else has a new blog post, to list friends or block enemies, various privacy levels, and so on. And among the younger users who are the target for these sites, many of them already think of email as old-fashioned (and useless because of spam), so their primary communication is through blogs and IM.

      Right now, any email replacement would be limited to within a single "community", but I'd expect that at some point two or more (possibly smaller) sites would agree to exchange messages between them. If the protocol weren't open, some other site (or group) would come up with one that was. Once the exchange of messages (and friend information, etc.) became a feature attracting users, other sites would have to follow.

      It would not be too much different from the growth of "OpenID", which is now used by several blog sites to identify users from outside their "community".

      Once messaging is possible using a standard web protocol, it will gain the same functionality of email, but again with verified source and so no spam. It will be more centralised than an RSS type solution, but still work well enough to replace email.

      I think one or the other is inevitable. Unfortunately I'm working on other things and can't try any of this myself, but maybe someone will.

  27. Controlfreak Alarm!!! by Anonymous Coward · · Score: 0

    FTA: "root cause of the problem: Internet messaging allows anyone to send as many messages as s/he wants."

    Ahhh... another controlfreak who lost my interest after his first 1-2 sentences.

  28. What about SenderBase? by NtroP · · Score: 3, Insightful

    This isn't a new concept. Our mail gateways already participate in something like this with IronPort's SenderBase reputation filtering. 90%+ of our incoming mail traffic is dropped based on poor reputations scores without looking at anything more than the sender's address. So far, we've never had a false-positive that we know of, and only once, after many customers were made a part of a bot-net and started spamming, did SenderBase throttle traffic to one of the local ISP's. A quick call to their mail admins pointing out the problem and they were able to block those customers from sending mail until they were cleaned up and the reputation score climbed back up again.

    It has really taken the load off our mail servers by blocking millions of connections. The rest, we run through SpamAssassin and everything works great!
    --
    "terrorism" and "pedophilia" are the root passwords to the Constitution
    1. Re:What about SenderBase? by Anonymous Coward · · Score: 0

      I was hoping someone would mention this. We are still in the process of migrating to a bunch of X1000s. So far we are impressed.

    2. Re:What about SenderBase? by ACMENEWSLLC · · Score: 1

      This was the general basis for the http://antispam.or.id/ blocklist. It worked well for a while. I used it for a few years. But it's dead now. Long live spam.

  29. I am curious... by localman · · Score: 2, Interesting

    Are any of you people still living with spam? Do we really need another solution? I've found that a personally managed baysean filter is plenty good enough. I'm down from 700+ per day to 2-3 per day. I still dislike the fact that spam is out there, but I haven't actually had to deal with it in years. Has this not worked for other people? I mean, I do have to continue to feed the filter, but it's very little work. Nothing wrong with new ideas in the battle, but I thought that for anyone who cared it was already won.

    Cheers.

    1. Re:I am curious... by Intron · · Score: 1

      Why do you think it "works" when your server has to scan and reject 700+ emails/day?

      Personally, I think that email should have a button that you can press if you don't like the email that adds a 0.1V charge to the sending PC. If one person presses it, the charge won't be noticeable, but if 1,000,000 press it...

      --
      Intron: the portion of DNA which expresses nothing useful.
    2. Re:I am curious... by Torvaun · · Score: 1

      Well, there's the consideration that even filtered spam takes up bandwidth. Then there's the question of how much time you actually spend dealing with spam, what with continuous filter tuning and all. Then there's the simple fact that this suggestion, as printed, involves alerting the owners of spambots, some of whom will clean their computers, and possibly learn halfway decent security measures.

      I'm all for this.

      --
      I see your informative link, and raise you a pithy comment.
    3. Re:I am curious... by Anonymous Coward · · Score: 0
      Personally, I think that email should have a button that you can press if you don't like the email that adds a 0.1V charge to the sending PC. If one person presses it, the charge won't be noticeable, but if 1,000,000 press it...

      The spammer's UPS would kick in and the spam will continue to flow on battery power. Your idea already has a purchaseable workaround. ;)

    4. Re:I am curious... by localman · · Score: 1

      Why do you think it "works" when your server has to scan and reject 700+ emails/day?

      Because I don't have to :) My server has no trouble doing the work, and it doesn't cost me anything.

      But I guess you're saying that if spam is out there, then it's still a problem. To me, if everyone who wants to stop it from reaching them can do so with minimum effort... it's just not a big issue any more. Let them spam. Let the morons who buy the stuff buy it. As long as there's a decent means of avoiding it for anyone who wants to. And I believe there is.

      Cheers.

    5. Re:I am curious... by localman · · Score: 1

      All reasonable points. And if the suggestions in the article helps things, excellent.

      On the "time spent dealing" with it: I spent a couple hours back in 2003 figuring out how to install a baysean filter, then a few more hours (spread over several weeks) figuring out the best settings and the best way to "train" it. That was the initial investment, and it is higher than it should be for sure, though I bet there are more user friendly setups available. But now, I literally spend barely a minute a month on it... I just make sure to flag any spam that comes through (2-3 per day) and have everything else go to a "ham" folder when I delete them. A script runs and feeds those two sets to the filter automatically. No further tuning has been necessary.

      I mention it all just in case there are people out there still suffering with spam: you can solve it, for all practical purposes.

      Cheers.

    6. Re:I am curious... by nuzak · · Score: 1

      "The social dynamics of the net are a direct consequence of the fact that nobody has yet developed a Remote Strangulation Protocol." -- Larry Wall

      --
      Done with slashdot, done with nerds, getting a life.
    7. Re:I am curious... by Phroggy · · Score: 2, Informative

      Are any of you people still living with spam? Do we really need another solution? Anyone who's a mail server administrator is living with more spam than you could probably imagine. During a four-week period, across two of the (very small) servers I manage, 38,728 connections were refused because of RBLs. Of the messages that were accepted, 8,102 were assigned a SpamAssassin score above 15 and sent to a system-wide quarantine folder that users never see. Another 13,619 messages were assigned a score between 5 and 15, and sent to a user-accessible quarantine folder for review. I use Rules Du Jour to keep rules from the SpamAssassin Rules Emporium updated daily, and I spend quite a bit of time writing and tweaking my own custom rules to catch spam that everything else misses.

      After all of that, I STILL get about 5 per day. Bayesian filtering in my e-mail client usually catches these, but since it occasionally catches false positives, I have to check it anyway.

      Nothing wrong with new ideas in the battle, but I thought that for anyone who cared it was already won. No, the battle is already lost. We absolutely cannot keep up with the spammers if all we have are technical solutions. The only real solution is increased law enforcement. In the mean time, we need all the help we can get with technical solutions.
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    8. Re:I am curious... by localman · · Score: 1

      At the server level you're totally right: the battle is all but lost. But I did want to ask about your bayesian setup... I am using spamassassin as well with just the following config:

          required_hits 5
          rewrite_subject 0
          bayes_auto_learn 0
          score BAYES_00 -2.0
          score BAYES_01 -2.0
          score BAYES_10 -1.0
          score BAYES_20 -1.0
          score BAYES_30 -1.0
          score BAYES_40 -1.0
          score BAYES_44 -1.0
          score BAYES_50 5.0
          score BAYES_56 5.0
          score BAYES_60 5.0
          score BAYES_70 5.0
          score BAYES_80 6.0
          score BAYES_90 6.0
          score BAYES_95 7.0
          score BAYES_99 7.0
          score ALL_TRUSTED 0

      Each user feeds it ham/spam separately (I've admittedly only a handful of users). After the initial all-manual feeding (which was laborious) I simply feed it spam that gets through and all other mail as ham. I don't know, I'm just trying to help here. Maybe it only works for me, but it works pretty darn well. But yeah, like yours, my server has an amazing amount of spam coming in. If I had to see even 10% of it I'd pull my hair out.

      Cheers.

    9. Re:I am curious... by David+Jao · · Score: 1
      A well managed bayesian filter is a lot better than nothing, but I do not agree that it is good enough.

      I use spamassassin, like you, and I've been using it for years. I am also fairly open with my email address (for example, my email is displayed publicly on my slashdot posts, of all places). The problem with a bayesian filter is that it is not perfect. Given enough spam volume, such as the amounts we're seeing today, any filtering approach is bound to make errors, and beyond a certain point any attempts to improve the performance (for example by tuning parameters) end up destroying the usefulness of the filter.

      The reason I use the filters is because they are the least bad option out of a sea of sucky alternatives. For example, if I were to sort email by hand, my own rate of human error would already be higher than the error rate of the filter. But to say that filters are the least sucky option is a far cry from saying that filters solve the problem. At best, it might be true that at "low" spam volumes such as ~1000 spams per day, a filter can perform perfectly. However, at higher volumes even the filters start to break, and since the amount of spam is increasing at a phenomenal rate, this is not a battle that can be won.

      Simply put, filters do not solve the spam problem because they still inevitably make errors, and every such error represents a failure of the filter to eliminate the major harmful effect of spam, which is losing legitimate email (I'm ignoring secondary harmful effects such as bandwidth consumption, which others have already addressed).

      Filters do help to solve the spam problem, because with good filters in place it is no longer necessary to suppress all sources of spam. It is only necessary to suppress spam sources to such an extent that the resulting volume of spam lies within the range that can be effectively handled by filters. Unfortunately, at the present time the internet as a whole is failing to achieve even this modest goal.

      There is another problem with filters, one that does not affect you and me, but does affect the vast majority of internet users, and that is the issue of user expertise. It takes quite a bit of sophistication and computer savvy on the part of the end user in order to properly run and manage a bayesian filter. I'm not saying the task is very demanding on an absolute scale, but remember, we're talking about users who can't even keep their own computers free of spyware and trojans, which is administratively a far easier task than maintaining a bayesian spam filter. For this reason I think that, even if filters do end up solving the spam problem, it will take quite a bit of work to implement that solution in a manner that benefits the average internet user.

    10. Re:I am curious... by Phroggy · · Score: 1

      I'm not currently using Bayesian filtering in SpamAssassin at all. I don't want to deal with trying to train my users, and without a pretty crazy level of training, I don't see how Bayesian filtering can properly deal with the crap text that spammers are including in their messages (recently somebody has started using current news article headlines as their subject lines, which is brilliant). If it works for you, that's great, but the combination of other rules I have in place sound like they're about as effective as what you've got (based on how many spams you said get through the filters), so I've chosen not to bother with it for now.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    11. Re:I am curious... by localman · · Score: 1

      You are totally correct that if you can't get your users consistently following the right steps, it won't work. And that is a bigger and bigger challenge the more users you have. The creativity of the spammers has impressed me on occasion. News headlines is clever.

      Cheers.

    12. Re:I am curious... by localman · · Score: 1

      Thanks for the post... I can see what you're saying here. I am under the threshold of "low" spam volume you define, so I perhaps haven't seen the filters break meaningfully yet. I don't think I get any false positives, but a couple slip through and if spam volume increased 100 fold I'd be screwed. But for now, I guess my question was more aimed at whether many slashdot users were still suffering with tens or hundreds of spams per day actually making it to their inbox.

      I wonder what can be done to solves spam on a more basic level, though. Law enforcement raids as though it was a drug bust)? Or a secondary system with optional micropayments for "unwanted" mail? Or a trust network of mailservers of some kind? Or maybe we really are just screwed by our species' own greed and lack of consideration.

      Cheers.

    13. Re:I am curious... by David+Jao · · Score: 1
      Well, "low" spam volume is a relative term here. A few years ago, 1000 spams per day would have been considered high. Back then, everyone who used filters was seeing perfect performance, and a few optimistic folks thought that spammers could not raise their spam volumes to compensate. However, that theory isn't holding true anymore.

      Nowadays the main effect of filters is that they improve the spam situation from totally unmanageable to borderline tolerable. The result is that we have two tiers of email users: those who use filters can actually for the most part continue to use email as they have been using it all along, with relatively minor differences (but still with enough inconvenience that I don't consider the spam problem "solved", even for this class of user). OTOH, those who do not use filters have been forced to drastically curtail the types of things they do with email, sometimes to the point of periodically abandoning email addresses that have become overrun with spam.

      I don't think there is a way to solve the spam problem at this point. Conceptually, the set of solutions can be divided into two types: elimination approaches, where you try to reduce the amount of spam sent, and blocking approaches, where the spam has already been sent and you try to distinguish the spam from the non-spam. The experience of the past 20 years tells me that the elimination approach is impossible unless we change the underlying protocol, which is not going to happen. Since reducing or eliminating spam is impossible, a consequence is that any sort of blocking technique would have to be perfect in order to solve the problem, because for any nonzero amount of error rate that you have, the spammers will gladly raise their spam volumes high enough to compensate.

      This analysis may be flawed, in the sense that there may be some physical upper limit to the amount of possible spam in the universe, but from where I'm sitting I don't see it (okay, I'm joking here, but only slightly).

  30. Re:This is painfully obvious and hopelessly naive by KKlaus · · Score: 4, Insightful

    Complaining that people are frequently bad decision makers is usually not worthwhile. Much better to recognize the truth that they are, and then work to try and take the decisions out of their hands.

    Its similar to a pretty interesting conceptual innovation in medicine, when people realized that even excellent doctors will at some point make grossly negligent mistakes simply due to the shear amount of work they do (i.e. operating on people with paralytics but not analgesics). So the innovation is to make them make fewer decisions - machines that check settings before running, labels that a four year old could understand, arrows and other reminders liberally applied.

    So similarly here, yes it's annoying that people continue to "fund" spammers, but education is not the answer. Because, unfortunately, the spammer's target market of "everyone in the world" will always contain enough people to make their trade profitable if all we rely on is good decision making on the parts of spam recipients. So the solution has to be technical or legal. And in that regard, another small step for man here.

    --
    Relax I just want some peanuts.
  31. your specific idea sounds damned good to me by Penguinisto · · Score: 1
    "If some DSL customer suddenly starts opening hundreds of outgoing SMTP connections, that would be a pretty reliable sign that his machine is pwned. Just block or throttle port 25, and send the customer an email telling him to fix his computer, and keep it blocked until he does - or he contacts abuse@ with a legitimate explanation."

    ...locking down port 25 outbound from the client would cure most of the bots out there (though not all - some jackass could set up a couple of open relays to listen on port {something-else} to then send the spam along from places where port 25 is wide open outbound. Then again, it ups the bar a bit, which isn't a bad thing either)...

    Keep the port open for business commercial clients using T-1 or bigger (or who can at least demonstrate that they have an IT department), and (please!) allow it to be opened upon request by the customer w/o extra charge if he/she can demonstrably articulate on the phone that "yes, I'm setting up my own MTA here for (testing stuff / personal use / etc)".

    'course, an ISP requiring clients to use IMAP w/ SSL would really rock, but I'm just dreaming by now...

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
    1. Re:your specific idea sounds damned good to me by fifedrum · · Score: 2, Informative

      I work for an email hosting company and our standard with ISP customers is they use IMAP or SMTP auth, worst case, POP before SMTP. It's amazing how much spam is blocked going from an open relay for an ISP to authenticated-only.

      spambots are bad, but my biggest problem is with fraudsters, both 419ers and standard credit card fraud types.

      These sleazebags cause more trouble than the bots, and it's illegal to kill them. I'm not sure why they cause more trouble, they send out less email than the bots, perhaps the scammer's email is better targetted to real people, as opposed to directory harvesting type attacks.

      Anyway, definately agree with you there, smtp auth, imap or whatever, all piped through SSL or nothing at all.

  32. As you wish by Kadin2048 · · 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
    (X) 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
    (X) 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
    ( ) 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
    (X) Open relays in foreign countries
    ( ) Ease of searching tiny alphanumeric address space of all email addresses
    (X) Asshats
    ( ) Jurisdictional problems
    ( ) Unpopularity of weird new taxes
    ( ) Public reluctance to accept weird new forms of money
    ( ) Huge existing software investment in SMTP
    (X) Susceptibility of protocols other than SMTP to attack
    ( ) Willingness of users to install OS patches received by email
    ( ) Armies of worm riddled broadband-connected Windows boxes
    (X) Eternal arms race involved in all filtering approaches
    ( ) Extreme profitability of spam
    ( ) Joe jobs and/or identity theft
    (X) Technically illiterate politicians
    (X) 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:

    ( ) 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
    (X) Blacklists suck
    ( ) Whitelists suck
    (X) We should be able to talk about Viagra without being censored
    ( ) Countermeasures should not involve wire fraud or credit card fraud
    (X) Countermeasures should not involve sabotage of public networks
    ( ) Countermeasures must work if phased in gradually
    (X) Sending email should be free
    ( ) 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
    (X) 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!

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  33. this and other effective weapons by fifedrum · · Score: 5, Interesting

    yes, traffic shaping is effective in determining the nature of connections

    I work for a small email company we process millions of emails an hour inbound, but only a few million a day outbound.

    Our most effective filters are:

    connect/HELO restrictions: you can only get email into the environment if your IP address resolves to a FQDN.

    HELO restrictions: if you connect using X different HELO strings, you are blacklisted. Spambots often randomize the helos, this blocks those.

    Spamassassin at the client side, filtering email into various folders based on the score.

    antivirus server that filters the few viruses that make it in, and phishing is filtered too.

    The problem? All this doesn't catch enough of the spam. We still have loads of CPU dedicated to filtering spam, but something like this technique at the border will help, and I'll predict (based on experience watching the traffic and spam filtering graphs) that we could cut spam another 30% just by watching the curves and tightening the restrictions during those peaks.

    1. Re:this and other effective weapons by dodobh · · Score: 1

      Hmmm, sounds like my employer, except that we have a ton more outbound. Is your employer part of MAAWG yet?

      --
      I can throw myself at the ground, and miss.
    2. Re:this and other effective weapons by TheRaven64 · · Score: 2, Interesting

      connect/HELO restrictions: you can only get email into the environment if your IP address resolves to a FQDN. Does this actually do anything? I just checked and my (residential) cable modem IP resolves forwards and backwards. Since most spam is sent by zombies on similar connections, won't they all resolve?
      --
      I am TheRaven on Soylent News
    3. Re:this and other effective weapons by macdaddy · · Score: 2, Informative

      I'd suggest you look into Canit-Pro from Roaring Penguin. It's from the author of MIMEDefang. Actually it's MD's commercial big brother. They make an appliance but I still run the app locally on Fedora boxes. They give you the full source code. It's extremely extensible. It makes Barracuda Networks' products look like child's play. Basically it will take the knowledge you already have and give you a platform to extend and build upon it. Canit-Pro is slick. The auto-tempfail by recipient and IP is great. The regex and user controls are worth their weight in gold. By far the most essential feature that is lacking in most other canned spam filters is the ability to scan incoming messages during the SMTP transaction. That way you can reject the message as spam before you actually accept it. This eliminates the need for DSNs. Give the demo a try sometime. You'll like it.

    4. Re:this and other effective weapons by fifedrum · · Score: 1

      that's a good question, no idea

    5. Re:this and other effective weapons by fifedrum · · Score: 1

      no, believe it or not we find that a large amount of rejects from dhcp type addresses that don't resolve, especially overseas. but you are right, loads of road runner and dsl customers do have names in reverse tables

    6. Re:this and other effective weapons by fifedrum · · Score: 1

      thanks for the tip! I'll definately pick it up and check it out next week in our demo environment.

  34. For those keeping track at home by Anonymous Coward · · Score: 1, Insightful

    ISP traffic analysis blocking spam = good
    ISP traffic analysis blocking torrents = bad

    1. Re:For those keeping track at home by Miseph · · Score: 2, Insightful

      Makes sense, since:

      spam = bad
      torrents != bad

      Anyway, you're comparing apples to socket wrenches... Torrent is a file transfer protocol which can be used legitimately. Spam is a specific abuse of the various e-mail protocols, and by definition cannot have any legitimate use. For your comparison to make sense, it would either have to be between using torrent to distribute virii and spam, or between torrent and SMTP/etc. traffic.

      --
      Try not to take me more seriously than I take myself.
  35. No! by Penguinisto · · Score: 3, Funny
    We have enough problems with idiots who leave all their backscatter-inducing defaults on @ their mail servers - coupled with the common joe-jobs, it would quickly turn the Internet into a gelatinous mass choked with bounces.

    Thx in advance,

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
    1. Re:NO! by nine-times · · Score: 1

      And what if you have a home-office or run a hobby site, and you need more access/control than a virtual server will allow? Dedicated hosting and co-location are still relatively expensive. I have no objection to ISPs blocking port 25 by default, and only making it available on request. I don't even mind the idea of charging a small fee for a "business account" or whatever, which gives you access to port 25 and a static IP.

      However, I do object to the idea that people shouldn't be permitted to do things at their homes in in their home office, just because they aren't a "real business" with a full-on data center. The internet should be a neutral medium without inherent directionality.

    2. Re:NO! by pwainwright · · Score: 1

      Q: What's the difference between a "real business" which can
      rent a co-lo server, and a "residential customer".
      A: The "real business" has money.

      Unfortunately, SPAMMERS HAVE MONEY. Restricting bulk email
      to the rich will only help spammers. In fact, it will only
      enforce natural selection in favour of the REALLY EFFECTIVE
      spammers.

    3. Re:NO! by macdaddy · · Score: 1
      I stand by what I said earlier. If you want to run a server then you need to host it with other servers and not in a netblock with other residential customers. Now the ISP I run does make exceptions for people wanting to use alternative SMTP servers (such as their employer's). We simply do this with static IPs that are assigned out of a particular block. This isn't for them to run a server though. It's only for them to connect to other SMTP servers (hopefully with AUTH and TLS).

      I sympathize with SOHO businesses. Many of our customers fall into that category. Fact of the matter is many of them do not host any services whatsoever. Very few of our SOHO customer (and many even larger) have their email hosted somewhere, including with us. Almost all of them have their web presence hosted elsewhere and usually generated by someone else. The only thing they do with their Internet connection is access the Internet. The only SOHO business that I can think of that do not host everything elsewhere are tiny tech support startups or are run by the 5% user (the 1% of the 5% user being the proverbial group that consumes 95% of your available bandwidth, and the 1% user being the component that thinks they're technical but are really an average user that isn't afraid to click on anything). Nevertheless, virtual hosting is quite cheap. 1U hosting can be had for under $100/month now. ISPs almost always offer hosting options as well, as do registrars. There's a plethora of hosting options out there. People don't have to run services from their residential connection for any real reason.

      It's a very unpopular opinion on a site like Slashdot (as one might deduce from the replies to my other comments). Unfortunately it's the only viable one. We absolutely can not in any way shape or form not have this block. It would eat away at our bandwidth. It would get our entire ISP blacklisted for "hosting spammers" when in reality we're hosting average users that have no clue how to properly secure their machines or conduct themselves in a secure manner on the Internet. These past few years people having been stuffing DNSBL into into BGP feeds to create their own little RBL. They've also been using this data, on the presumption that these hosts likely are open proxies, to filter inbound web requests. Nevermind that the effect the DNSBLs have on email. ISPs simply can't exist without this kind of filtering. I've been at this for 12 years now. We couldn't have gotten to where we are today without filtering along the way.

      Here's another viewpoint on the matter. Imagine what the Internet would look like if no ISP did any filtering of any kind. The NSPs' backbones would have crumpled under the load. The costs of peering with NSPs would shot through the roof. ISPs would be forced to pass the increased costs on to the users. It wouldn't end here though. The industry has recognized this for some time. The result of this scenario would be that the Internet would become regulated. It's as simple as that. Customers would be forced to secure their PCs before putting them on the Internet. Of course the customers can't be responsible for this. They're users; they can barely power on their PCs. This requirement would be forced upon the ISPs. ISPs would have to start hand-holding users, coddling them and securing their PCs. This would of course dramatically increase costs. ISPs would start building MDU access layers that completely isolate users from each other. Users would be NATed and ISPs would have to build huge proxy clusters with near-infinite logging capabilities because Congress couldn't possibly pass a bill requiring something like this without also tacking on auditing and monitoring "features". Of course these "features" would then be referred to by POTUS in a signing statement that authorizes the federal LEOs to access this data any time they want in the name of National Security.

      I'm not kidding either. This has been discussed in insane detail. I'm only summarizing here; I'm

    4. Re:NO! by nine-times · · Score: 1

      Nevertheless, virtual hosting is quite cheap. 1U hosting can be had for under $100/month now. ISPs almost always offer hosting options as well, as do registrars. There's a plethora of hosting options out there. People don't have to run services from their residential connection for any real reason.

      Virtual hosting is cheap, but you also end up restricted to what your host will allow (no system level access, for example). There are smaller size/volume limits on all sorts of things. Sometimes the limits of a virtual host aren't acceptable for a person/business. 1U hosting is much cheaper than it used to be, but it still isn't quite cheap. That $100 a month can add up over a few years. A lot of these issues depend on you needs and your budget.

      I've already said this, but I agree that port 25 should probably be blocked by default. However, there should be a cheap/free method for disabling this block for those people who know enough to secure their own system (which will roughly work out to be the same people who know enough to ask you to stop blocking port 25).

      Personally, I hate the fact that my ISP blocks port 25 and 80, and I'm considering changing my ISP because of it. I didn't know before I signed up. Port 80 is an annoyance for certain things, but blocking port 25 is just a PITA. The ISP offers it's own SMTP without authentication as long as your on their service, but doesn't allow access to it if you're coming from the outside. The problem: I have a laptop. If I'm at home, I can only use 1 SMTP server, and I can't use that server if I'm not at home. So I have to keep switching servers all the time because my ISP is looking to collect another $15 just to allow ports 25 and 80 (still no static IP).

      And the problem is not that I can't secure my own machine. I work in IT, and though I'm not an uber-geek that knows how to do everything, I can sure as hell run a network and keep it virus-free. I can produce paperwork to that effect if that's what it took, but it's more like they know the broadband options in my neighborhood are limited, and they're just trying to squeeze out every last penny.

    5. Re:NO! by macdaddy · · Score: 1

      Problem is you're 1 person in a group of many thousand users that's capable of performing the task. The other 99.99999% can not. You're connection can not simply be singled out for an exception unless they use the static IP trick I mentioned earlier. It doesn't make good business sense to spend resources to satisfy the 0.00001% of their userbase that needs this functionality. It sucks but it's true. The only way we can justify doing it is because we're small when compared to big players like Cox and SBC.

    6. Re:NO! by nine-times · · Score: 1

      As I said, I think your static IP trick is acceptable. Charge me a little extra, open the ports, and give me a static IP. I'm just annoyed with ISPs that don't even offer that option.

  36. Done that for 2years now by Anonymous Coward · · Score: 0

    I have been doing this or something very similar, for 2 years now. It works. I use a special Linux Bridge, kernel ip traffic linked to a Postgresql DB for statistical analysis and scalability. As I have said many times, you have to control Spam by parameters the Spammer can not control. And not by parameters which are in his/her control, like text, pictures...

  37. Re:This is painfully obvious and hopelessly naive by AndroidCat · · Score: 1

    And don't worry, it's not spam because... (Pick one or many)

    --
    One line blog. I hear that they're called Twitters now.
  38. Acceptable loss. by Kadin2048 · · Score: 1

    I'm not sure I care. Those "legitimate" "opt-in" lists tend to get reported by users as spam eventually anyway. Meaning even if they did originally 'opt in,' it's basically nothing but a nuisance eventually. (Usually people opt in, allegedly or actually, and then can't figure out how to opt out, or don't want to spend the effort to do so.) The effect is the same as spam, even if the intent isn't.

    I would consider the elimination of commercial mass email a very small price to pay for the elimination of spam. In fact, I'd consider it a bonus.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  39. Even if no one ever responds, it won't stop by MarkusQ · · Score: 4, Insightful

    Even if no one ever responds, it won't stop as long as the people paying to have it sent think it works. It's like burning candles to St. Balderdash for scam marketing morons. As long as there is a steady supply of rubes who think that sending spam is their road to riches, and are willing to pay some brighter but no more honest spam lord to send their dreck to a bazillion hapless victims for them, spam will contine to flow.

    This is true even if no one ever responds to, falls for, or even opens a spam message ever again.

    --MarkusQ

    1. Re:Even if no one ever responds, it won't stop by thePowerOfGrayskull · · Score: 1

      Even if no one ever responds, it won't stop as long as the people paying to have it sent think it works. It's like burning candles to St. Balderdash for scam marketing morons. As long as there is a steady supply of rubes who think that sending spam is their road to riches, and are willing to pay some brighter but no more honest spam lord to send their dreck to a bazillion hapless victims for them, spam will contine to flow.

      This is true even if no one ever responds to, falls for, or even opens a spam message ever again.

      --MarkusQ

      I think this is pretty far from the mark. While there might be some who would continue to use the service, most wouldn't. Face it, if you're paying for any kind of advertising (and that's all spam is, really), you want results. If it doesn't make a significant difference in your sales -- easily measurable -- you won't continue to pay for it. Even stupid people know when they're losing money.

      You might get a steady stream of first-timers who fall for the lure of sending spam, but the volume would be a trickle compared to what we have today.

  40. Has been done for a long time. by MadTinfoilHatter · · Score: 5, Interesting

    My (previous) ISP did this several years ago. I found out when I was making a computer for a friend. At the time (this was a few years ago) I didn't yet know just how quickly an unprotected windows-box is owned by viruses. I thought I'd be okay for the time it takes to download a firewall. 20 seconds later I got a popup that I recognized as an infection, so I shut down the machine, and tried to get the firewall / AV-software with my other machine instead - only to be greeted by a screen where my ISP informs me that "By the look of your outgoing traffic, it would seem that your machine has been turned into a spam-bot by a virus, and your account will be automatically unblocked 1 hour after the suspicious traffic stops." This was followed by some generic instructions for virus removal.

    1. Re:Has been done for a long time. by kenb215 · · Score: 1

      What ISP did you use?

    2. Re:Has been done for a long time. by MadTinfoilHatter · · Score: 1

      What ISP did you use? At the time I used Elisa. http://www.elisa.fi/ It's one of the two big ISPs in Finland.
  41. Re:This is painfully obvious and hopelessly naive by Tim+C · · Score: 1

    What would happen if we all started replying with the same auto generated mails?

    The time it takes me to deal with the 2000+ spams I get each day would increase unmanageably?

  42. Botnets? by Jabrwock · · Score: 1

    This wouldn't really work against botnets, would it? Because of the fact that they are distributed, you wouldn't really have a source trust issue... Not one that would trip any warning flags, anyway.

    I can see it though, be a handy tool to aid against regular spammers, perhaps in analysing traffic to assist in maintaining SBLs...

    --
    Magic doesn't work in my presence. My power of disbelief is too strong.
    1. Re:Botnets? by gregmark · · Score: 2, Informative

      Sending spam the old fashioned way (sans botnet) is still very effective. My company uses two throttling appliances, IronPort and Symantec 8160. Both score senders based on their spamminess and throttle appropriately. When we first turned on our 8160s last year, some people in our company thought we had eliminted spam completely. We'll be moving to the IronPort solution soon as its scoring system appears to be a great deal more thorough and reliable; we expect our spam numbers to drop even further when the go live.

      Botnets make rate-limiting (which really, is all STP is, besides Stone Temple Pilots and motor oil) an imperfect solutions, but if you can eliminate the old school spammers, trust me, you will take a giant chunk out of your daily spam volume, giving your true anti-spam software more CPU cycles to do its thing, like catch that blasted image spam.

  43. Re:This is painfully obvious and hopelessly naive by cdrguru · · Score: 3, Interesting

    The money in spam isn't from people buying stuff - it is from the silly advertiser thinking they can send their ads to millions of people for $1000. They do this and get a report back that says only 0.8% of the people opened the email.

    The spam-sending organization then shows them that they need to revise their message with a better subject line so more people opened the email. Another $1000 and more spam is sent, this time 0.7% of the people open the email.

    Continue this until the advertiser runs out of money. If you have enough contracts for sending spam it matters not a whit if anyone buys the stuff at all. It is only important that people pay for it to be sent.

  44. Re:This is painfully obvious and hopelessly naive by hackstraw · · Score: 1

    I was going to say... What would happen if we all started replying with the same auto generated mails? How would the spammers tell the difference from legit spam replies?

    That too has been implemented. Its an invited DDOS attack on the spammer. I love it :)

    Regarding the article, this is no big deal. Blacklists, whitelists, and greylists already exist. There is no additional market value with those techniques to eliminate spam.

  45. Re:This is painfully obvious and hopelessly naive by jcr · · Score: 1

    Why can't people stop responding to spam in the first place?

    Get back to us when you convince enough newbs to do that. The reason spam persists is because there are enough idiots to make spamming pay off, even if nearly everyone ignores it.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  46. Spam is desensitizing people for other reasons by scottsk · · Score: 1

    No one cares if anyone responds to spam or not. Spammers are the lowest of the low on the food chain. What people who peddle immorality want is a steady stream of junk mail coming into your inbox hour after hour, day after day, and year after year. Eventually, it's going to weaken you - being exposed to all the viagra, penny stock, erase your credit without paying, etc etc etc - pretty soon you'll think this stuff is normal, and when you have to make a moral decision someplace else (someplace more profitable, I might add) this has to play some role in weakening you to think this stuff is normal. You'll be more likely to make a bad moral decision, and they'll profit from it. So the vast web of affiliate programs, spammers, botnets, etc is a low-cost investment for the real sleaze merchants and criminals. You can entice someone else to spam as an affiliate. They hire a botnet. Etc. The real people who profit from spam don't touch it, as is usual for this sort of thing.

  47. All they have to do is slow down. by edunbar93 · · Score: 1

    And this applies to botnets... how, exactly? If you can infect just a million computers with your spam bot, then you can send a million messages an hour by sending *one* message an hour per host! With a billion plus hosts on the net, you need to infect less than 0.1% of them to make that happen. The number of vulnerable computers at any given moment in time is easily more than 20%.

    But hey, for every complex problem...

    --
    "No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
  48. Re:This is painfully obvious and hopelessly naive by Ambidisastrous · · Score: 1

    I was going to say...What would happen if we all started replying with the same auto generated mails? How would the spammers tell the difference from legit spam replies?

    Sure, it'd be pretty tedious to do that by hand, but if we automated the process somehow...

    Oh, wait.

    I imagine that if you ran a script by yourself, your e-mail address would be targeted as belonging to a valid sucker, and passed around on lists, so you'd be spammed even more. The efforts of a scrappy community of geeks are no match for the millions of pwned PCs around the world.

  49. Re:This is painfully obvious and hopelessly naive by TheMeuge · · Score: 0, Offtopic

    Oh how I wish I hadn't spent my mod points yesterday. Please mod parent up for a very insightful comment.

  50. Re:This is painfully obvious and hopelessly naive by Daniel_Staal · · Score: 1

    Easy, first you start a nuclear war...

    ...Then once all the humans are dead, there will be no more spam problem. Except for the kind in cans. Those will last forever.

    --
    'Sensible' is a curse word.
  51. Re:This is painfully obvious and hopelessly naive by Archangel+Michael · · Score: 1

    I know of a way, but it is distasteful to too many people.

    Death

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  52. Whitelists by Doc+Ruby · · Score: 1

    Everyone should prioritize their incoming email by who in their address book sent it, or it's unsolicited, probably commercial, email, "UCE", aka SPAM.

    --

    --
    make install -not war

    1. Re:Whitelists by chromatic · · Score: 1

      How do I add everyone with whom I would like to have some sort of professional or personal relationship and who will first contact me in the future to my address book because we haven't met yet right now?

  53. Places you don't want to be by paladinwannabe2 · · Score: 2, Insightful

    Democratic Republic of the Congo- Welcome to the land of warlords, genocide, and more genocide.
    Central African Republic- Less than half the genocide of its neighbor in the congo.
    Dominican and Czech Republics, and Macedonia- actual democracies.

    So two of your five examples help prove my point- and when you start stacking adjectives together- like 'People's Democratic Republic of Korea' you know you've got one of the worst places to live on Earth.

    Also, why on earth would you get an 'official government email' from someone in these countries? That's less likely than you being a Viagra dealer and have Viagra mentioned correctly in your email. That's also why different people will have different spam filters for their mail- if I worked with the Republic of Ireland or was a professor of Greek history I would probably see the word 'Republic' in legitimate email.

    --
    You are reading a copy of my copyrighted post.
  54. Won't really work by jerseyjim · · Score: 2, Insightful

    I use a popular, public email service. My emails have been identified as spam at times. The reality is the everyone from the service uses the same IP email address. All it takes is one person from that service to send spam and all those using the service get flag...so volume along isn't a good indicator.

  55. Re:This is painfully obvious and hopelessly naive by bcrowell · · Score: 2, Insightful

    Why can't people stop responding to spam in the first place? [...] If spammers made absolutely zero dollars for their efforts would they stop?
    First off, if people stopped responding to spam, it wouldn't have any effect on phishing spam, since phishing is based on tricking the user into thinking it's legitimate mail rather than spam. Also, once you have control over an army of zombies, the incremental cost of sending one spam is zero. Even if the spammer thinks he's unlikely to make any money at all by sending out spam, he's already set up to do it, so why not? If even one person in ten million clicks on a spam accidentally because his cat walked across his desk, that makes it worth it to the spammer to have sent out the other 9,999,999 spams. Look at all the bayes-poisoning spams we get, with no link to click on; the spammers know they aren't going to profit from those, but they send them anyway, because it's free. And finally, there are a lot of other things you can do with a network of zombies. For instance, you can carry out extortion schemes by threatening DDOS attacks. The basic problems are (1) poor security of Windows, and (2) the fact that the e-mail protocols were designed before the internet existed, in an era when you knew everybody who was on your network.

  56. excuse to reduce investment in real solution by scumbaguk · · Score: 1

    Unfortunatly all this actualy does is reduce costs for anti spam companys as they do not have to keep up with the growing levels of spam while consumers keep paying more for their service each year. I have seen this method in action and what it means is people who pay for an anti spam solution are sometimes getting legitimate emails days later then they should. This is due to the mails not actualy being scanned for content just being put on the slow path because of the antispam providers unwillingness to invest in a system which can cope with actualy scanning the content. These test have their place but I have seen them missused at many antispam providers and IMO it's not acceptable.

  57. Would work if by crossmr · · Score: 1

    We made everyone who had a mailing list which contacts more than 100 people "register" with their ISP. They don't have to disclose the recipients or the nature of the list, simply a "I will be sending out a mailing list to x amount of users everyday in addition to my personal usage. Any customer who spits out more than some reasonable number of e-mails (who knows, maybe 200 per day is sufficient for most home users even on the upper ends of e-mail usage) will find their ability to use the outbound server restricted until they contact the ISP. Spammers send massive amounts of e-mails. It would be easy to find a cut off number that would help distinguish between the home user and the user who's computer has been compromised. This probably wouldn't even be that hard of a solution for an ISP to implement and could be mostly automatic except for the entering of exceptions into the database. Spam is really in the hands of the ISPs and their unwillingness to hold their customers accountable. Were I an ISP, I'd keep an eye for any evidence that any of my customers computers had been turned into a bot and require they fix the problem before they were allowed to use the services again. Sure they might go elsewhere, but if every ISP implemented the policy it would make the internet a vastly better place.

  58. Re:This is painfully obvious and hopelessly naive by jonadab · · Score: 1

    Or we could make doing business with a spammer a felony, with a minimum sentence of 15000 hours of community service working for spam-fighting organizations.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  59. Openbsd spamd by wondersparrow · · Score: 0

    Anyone ever looked at it? The concept is so simple its amazing. I am not the most technical person, but here is my impression of how it works/ A message comes in from a server that is not on any of the black/grey/white lists. The message gets bounced back saying try again later and the mail server gets grey listed. If the server retries again later (within the allotted time), it gets whitelisted. Spammers never try twice. I went from well over 200 spam per day to ~3 last year. Yup only 3. It is not cpu intensive, the mail is not analyzed or modified in any way, it just plain works. Try it, love it, tell others.

    1. Re:Openbsd spamd by wondersparrow · · Score: 0

      Oh, forgot to mention. It tarpits all grey and blacklisted connections. Woo for tying up spammers mta's states. :D

  60. WTF? The product promises to slow down your email? by kingpetey · · Score: 1

    The kind of analysis HexView suggests seems to promise a drastic bottleneck in email delivery as their servers check source IP addresses, etc. Awesome. I love the possibility of MY email grinding to a halt in an attempt to cause spammers delays in packets delivery. Sounds like greylisting under a euphamized name, like how time-shares are now called "fractional ownership."

  61. The only real solution to spam. by arthurpaliden · · Score: 2, Interesting

    Is to have the ISP charge for email usage in the same way as you get charged for your cell phone usage.

  62. Ditto. Big mass marketers will benefit. by giafly · · Score: 1
    This system relies on whitelisting to handle companies like yours. Hence you'll need to spend more on ISP relations. Big bulk-mailers can more easily afford this so they will gain at the expense of competitors.

    BTW this system won't work because the author's assumptions are wrong. Botnet senders can easily afford all the following suggested countermeasures. I expect they'll carry on as normal. Then, if blocklisted, switch over to DDOSing the the STP servers until the blocklisting is removed again.
    How spammers can fight the STP server
    1. By slowing down message rates for each source
    2. By limiting the number of messages sent by each source
    3. By feeding STP server with useless noise
    4. By DoS-ing the STP server(s)
    --
    Reduce, reuse, cycle
  63. Follow the money and stop the source by spectro · · Score: 2, Interesting

    1. Company offering product or service hires spammer 2. Spammer creates botnet by installing spyware in unsecured computers 3. Botnet sends spam Pretty much any solution so far involves stopping step 3, the delivery when the real problem relies in step 1, we need to find ways to stop step 1 from happening. Lets make hiring spammers a criminal offence, the same way "murder for hire" is. You can catch them by just having undercover officers order the product/service. I say let's make hiring spammer to advertise a product or service a Criminal Offense punishable by jail. It will stop U.S. companies from hiring spammers. Then we put pressure in foreign governments to pass similar laws.

    --
    HTML is obsolete. It's time for a new, simpler and richer markup language.
    1. Re:Follow the money and stop the source by jbf · · Score: 1

      Your post advocates a

      ( ) technical (x) 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
      (x) 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
      (x) Lack of centrally controlling authority for email
      ( ) Open relays in foreign countries
      ( ) Ease of searching tiny alphanumeric address space of all email addresses
      ( ) Asshats
      (x) 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
      ( ) Armies of worm riddled broadband-connected Windows boxes
      ( ) Eternal arms race involved in all filtering approaches
      (x) Extreme profitability of spam
      (x) Joe jobs and/or identity theft
      (x) Technically illiterate politicians
      (x) Extreme stupidity on the part of people who do business with spammers
      (x) Dishonesty on the part of spammers themselves
      ( ) 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
      ( ) Why should we have to trust you and your servers?
      ( ) Incompatiblity with open source or open source licenses
      (x) 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
      (x) 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!

    2. Re:Follow the money and stop the source by Anonymous Coward · · Score: 0

      1. Company offering product or service hires spammer

      No. They hire "company that will handle internet marketing". Either the company doesn't know it's a spammer, or they do and just want plausible deniability.

    3. Re:Follow the money and stop the source by spectro · · Score: 1

      (x) The police will not put up with it
      If we put enough pressure on congress to pass the law, we make sure to fund a department to take care of investigating this.

      (x) Anyone could anonymously destroy anyone else's career or business
      Nope, you need proof to prosecute somebody. In this case your investigators operate undercover and puts orders for v1agr or whatever the spammer is selling. Once the transaction is completed you have proof to prosecute the seller.

      (x) Lack of centrally controlling authority for email
      Does not apply, it has nothing to do with who controls email. Investigators receive spam, they order product, gotcha!

      (x) Jurisdictional problems
      Lobby congress for a federal law

      (x) Extreme profitability of spam
      This is exactly what we are fighting with this proposal, if hiring spammers to advertise is illegal, they won't get any money.

      (x) Joe jobs and/or identity theft
      what % of spam come from these?

      (x) Technically illiterate politicians
      That's what lobbies and letters to your congressman are for.

      (x) Extreme stupidity on the part of people who do business with spammers
      Stupid enough to go to jail?

      (x) Dishonesty on the part of spammers themselves
      Spammers don't matter, if they don't get hired they need to find another business.

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

      (x) Feel-good measures do nothing to solve the problem
      I don't see how this is a feel-good measure

      (x) Killing them that way is not slow and painful enough
      Ok, but it provides fresh meat to Big Bubba in cell 23A

      (x) Sorry dude, but I don't think it would work.
      Just sit on it for a while and you may see the light. It's not *THE* solution but I think, if properly implemented, may do some good.

      --
      HTML is obsolete. It's time for a new, simpler and richer markup language.
  64. It already exists by m0i · · Score: 1

    Commtouch does this already:
    http://www.commtouch.com/Site/Enterprise/e_technol ogy.asp
    few false positives, >97% catch rate, 0.3s per message scan (on my system from live data, not marketing specs).

    --
    have you been defaced today?
  65. Re:This is painfully obvious and hopelessly naive by cmeans · · Score: 1

    Except that, maybe, once the spammer constantly sees bogus (usless) email coming from your "legit" email account, it's in their best interest to stop sending you spam...just to reduce the noise at their end. I guess they could black-list your email address, but then they'd still be getting tones of junk mail to filter...serves them right!

  66. Great idea, just several years late ;) by Thorizdin · · Score: 4, Informative

    For everyone screaming that this isn't feasible, will kill mailing lists, and other wise render effective communication via SMTP impossible you might want to consider that about a quarter of global email volume is already flowing through a system very much like what the OP describes.

    Ironport (recently purchased by Cisco for $830 million US) has been doing this kind of service for large providers for several years.
    Their statistics site is publicly viewable, but using their stats requires a subscription fee.
    http://www.senderbase.org/
    Its interesting to look at how well or poorly the MTA's you use are scored. All of the stats are gathered by the systems they sell to ISP's and enterprise customers. These boxes perform the spam filtering for that organization's customers and provide statistical data back to senderbase.org, which allows all Ironport customers to "know" about problems for all other Ironport customers.

    The link to their PDF on their metric's is here:
    http://ironport.com/pdf/ironport_wp_reputation_bas ed_control.pdf

    We evaluated their system last year as a possible replacement for a third party spam/virus scanning provider and may end up purchasing their equipment once everything with the Cisco purchase shakes out. Their solution, while not perfect, behaves far better than some of the things that large service providers *coughAOLcough* have tried and are (or were when we tested) comparable to most of the content based scanning systems in terms of spam filtering with a lower rate of false positives.

    1. Re:Great idea, just several years late ;) by archaicTG · · Score: 1

      IronPort / Cisco are not the only ones doing this. TrustedSource (http://www.trustedsource.org/) has a similar database.

      Having used IronPort in a large scale environment for 2 years, I would never go back to plain blacklist + content scanning. Unlike blacklists, reputation filtering can be tuned for your business. If the score is poor, block inbound mail before it even reaches your MTA. Low scores can be throttled or greylisted and senders with a good score can be allowed in with few limits.

      In my environment, I block nearly 80% of inbound mail before it even reaches the cpu-intensive content scanners. My only real complaint about the above reputation systems is that while some of the information is publicly available, the scores themselves are reserved for customers only.

  67. Less talk, more broken limbs by drew_92123 · · Score: 1

    Really, if people start hunting for spammers and breaking limbs the spam would stop almost over night. Maybe countries should offer spammer as well as terrorist hunting permits... ;-)

  68. The best and worst places to be by paladinwannabe2 · · Score: 2, Insightful

    Looking at Wikipeida we find that out of the 14 freest places to live, 'Republic' is part of the title on 4 of them. Looking at the 8 worst places to live, 'Republic', 'Democratic', and 'People's' are part of the title of 6 of them, and they appear a total of 10 times in the name of 8 countries. So it seems that my point has some factual backing, and there's a strong correlation between having 'Republic', 'Democratic', and 'People's' in a countries name and it being none of the above.

    --
    You are reading a copy of my copyrighted post.
  69. Won't work. by Animats · · Score: 2, Interesting

    Won't work. It just means the owners of zombie PCs get big bills.

    1. Re:Won't work. by metamatic · · Score: 2, Interesting
      It just means the owners of zombie PCs get big bills.

      That's not a bug, it's a feature.

      Right now, the costs caused by Windows insecurity are passed on to me even though I don't run Windows. Passing those costs on to the people causing them would be much fairer.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    2. Re:Won't work. by arthurpaliden · · Score: 1

      So you get a massive cell phone bill, do you just pay it or do you try to find out who was making all those calls on your phone.

    3. Re:Won't work. by nasch · · Score: 1
      Won't work. It just means the owners of zombie PCs get big bills.
      Not if it's prepay. Email costs $.005 apiece, and you put $1 in your account. You send email to someone who accepts it, you get the money back. You don't have money in your account, your email doesn't get sent. If someone loads their account and the first email they send 5 minutes later bounces because their account is empty, presumably they'll figure out something is going on. This scheme would not work (currently) for various other reasons, but at least big bills for zombie PC owners isn't one of them.
  70. Already been done by pete.com · · Score: 1

    CipherTrust has had a setup like this for quite sometime.... its called TrustedSource.

  71. Why not require this at the protocol level? by Simetrical · · Score: 1

    Here's what I've never gotten. By definition, spam is unsolicited mass e-mail. So ditch SMTP, and replace it with a protocol that has the following characteristics:

    1. A list of approved gateways will be maintained by ICANN or some similar body. Any gateway found to not abide by the protocol will be removed from the list. To eliminate the possibility of spammers repeatedly getting approval, registration will require some kind of real-life physical registration with photo ID. Deliberate violation of the protocol by a gateway for some reason would be a criminal offense in all countries; if a country did not enforce this adequately, their citizens would be prohibited from setting up gateways (although they could still use other countries').
    2. All e-mail must pass through an approved gateway (major e-mail providers could get approval for themselves, your dinky little server can route through one of the biggies while keeping the address). Each domain name will probably get assigned to a single gateway, but gateways can have multiple domain names.
    3. Each gateway will track its clients for mass e-mailing. Whenever a mass e-mail is detected, as defined by the specification, every recipient's gateway will be queried for whether the recipient has whitelisted the sender. If the recipient has not, the message will not be sent to that user (and the sender will be informed). Mail clients would provide a standardized mechanism for whitelisting, such as the user clicking a particular kind of link (and confirming via popup), and would display a message at the top of whitelisted messages allowing the whitelisting to be removed.
    4. If unsolicited e-mail is received, a "report spam" function would exist at the protocol level, which would instruct the sending gateway to deal appropriately with the user.
    5. The regulatory body in question could require all gateways to perform some particular kind of analysis on all outgoing and/or incoming e-mails. This wouldn't be heuristic-based if at all possible, but would rather perform simple yes/no checks such as whether an attachment matches a known virus.

    Currently, any computer can send out as many SMTP messages as it wants and claim that they originate from wherever it wants. This protocol would mean transparency: gateways would have to be trusted and so you couldn't fake the recipient. There would be basically no change on the front end; only the hosts would have to adjust. And there would be no way to send unsolicited mass e-mails.

    Of course, this isn't a cure-all. It wouldn't prevent viruses from sending spam to all their host's contacts, or prevent someone from setting up many accounts via proxies to do nothing but spam at a very low rate. But it would leave a more solid information trail than we currently have, and e-mail viruses would be halted within days at worst. Best of all, due to the centralization, improvements to the protocol could easily be made. In short, as far as I can see, it would be a win-win for the Internet, even if it would require some minor sacrifices.

    --
    MediaWiki developer, Total War Center sysadmin
  72. Re:This is painfully obvious and hopelessly naive by jdunlevy · · Score: 1
    That's the problem. this world is full of stupid people.
    The problem isn't so much stupid people as it is naive people. One big reason there are suckers ready to be taken in by spam is that every day, there are still a great many people experiencing spam for the first time. (The internet was "growing at an annualized rate of 18%" as of December 2005 according to one source just found in a quick Google search.) There are still a lot of people out there who've never read e-mail; they haven't yet learned about spam. If they start using e-mail, those people will be particularly vulnerable. The reality seems to be that education efforts about spam need to be directed not just to current e-mail users, but to potential e-mail users.
  73. This technology has been around for years by j0yc3 · · Score: 2, Informative

    IP Reputation filters are not a new idea by any stretch of the imagination.
    CipherTrust TrustedSource

  74. Re:This is painfully obvious and hopelessly naive by CohibaVancouver · · Score: 3, Insightful
    >What would happen if we all started replying with the same auto generated mails?

    Generally there's nothing to 'reply to' - To order the viagra you've got to go to a web site, or fax in an order - and all the latest 'pump and dump' stock-selling emails don't sell anything at all. They buy some stock, spam out their messages, then dump the stock when the price goes up. Often the company in question knows nothing about it.

  75. My version by Valdrax · · 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
    (X) Mailing lists and other legitimate email uses would be affected
    ( ) No one will be able to find the guy or collect the money
    (X) 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
    ( ) 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
    ( ) Joe jobs and/or identity theft
    ( ) Technically illiterate politicians
    ( ) Extreme stupidity on the part of people who do business with spammers
    ( ) Dishonesty on the part of spammers themselves
    ( ) Bandwidth costs that are unaffected by client filtering
    ( ) Outlook

    and the following philosophical objections may also apply:

    ( ) 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!

    ----

    In addition, contacting a central STP source for every email would be expensive both computationally and in terms of bandwidth. The STP system would become a huge bottleneck.

    I just don't see how politicians, "asshats," blacklists, talking about viagra, sabotage of public networks, email not being free, or killing people has anything to do with the proposal. Did you just random check boxes on yours?

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    1. Re:My version by Kadin2048 · · Score: 1

      I just don't see how politicians, "asshats," blacklists, talking about viagra, sabotage of public networks, email not being free, or killing people has anything to do with the proposal. Did you just random check boxes on yours?

      Well, I figured that politicians figured into it, because inevitably, any system that creates a single or centralized point of control (or failure) can also be used to deny service for political ends. My test is, would the [Nazis, Chinese Communists, Soviet Politburo] think this is a good idea? Does it put more hands into the control of a central authority? If yes, it's probably subject to political manipulation in some way. Which is bad. Hence, politicians.

      As for Viagra, I didn't mean that quite literally; I took it as a stand-in for "legitimate users ought to be able to use the full capabilities of the network all the time, not subject to artificially-imposed restrictions aimed at abusers." E.g., discussing Viagra shouldn't get you marked as spam; similarly, sending out a high volume of email messages for some legitimate purpose shouldn't get your connection throttled. It's the 'guilty by suspicion' problem. Same for email not being 'free,' anything that imposes artificial restrictions on the amount or frequency of mail that you can send, seems like it impinges on the 'freeness' of email (which may in fact be a good thing, but I didn't write the list).

      Sabotage of public networks is probably a weak checkbox, but in general, anything that seems like it blocks, delays, or otherwise purposefully restricts the flow of traffic across the network could fall under this one, since they undermine the idea of the net being "public" and the traffic traveling across it all being equal, and not subject to restrictions on content. We could argue all day as to whether this is a legitimate objection, and whether having all traffic transiting with equal priority is a good thing or not, but I don't think that's really the purpose.

      As to killing people, since the proposal doesn't painfully execute spammers, it's clearly unsatisfactory.

      Your list probably contains more defensible objections, but I'll freely admit I didn't put that much thought into mine. The point of the list is that every possible solution you could possibly propose to solve spam will fail it, in one or (usually) more ways.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  76. Solution... by nairb774 · · Score: 1

    Why not add some of the results form the spam filtering software in the results...something that would have to be done anyways and is also helpful. This means not only would the traffic analysis be done but it can also be placed against spam scores making the blocking more comprehensive and at the same same time avoid the mailing list problem.

  77. Re:This is painfully obvious and hopelessly naive by soft_guy · · Score: 1

    I am going to say it anyway. Why can't people stop responding to spam in the first place? Is it too much to ask? If spammers made absolutely zero dollars for their efforts would they stop? Will underdog be able to escape from the burning rubble in time?Tune in next week to find out in our next exciting adventure! Spam would probably eventually stop if ALL people FOREVER quit responding in any way to it.

    Prior to the twentieth century there was not advertising in the modern sense. When radio was invented there were people (like investors) who asked "why would anyone want to send a message to no one in particular?" It was a major discovery that advertising actually worked. This discovery happened because early advertising was simply announcements (such as in a newspaper to announce that a new business came into existance) and merchants found that their sales increased when they increased the amount and frequency of their announcements.

    I think it would be interesting to know what the implications would be if human brains were wired in such a way that advertising didn't work.

    Perhaps if we genetically engineered our children to have their brains wired so that they were immune to advertising, spam would go away eventually when there were no longer people in existance for whom it would be effective. However, this is unlikely to happen because even if we could engineer people to be immune from advertising, it would be hard to stop everyone from procreating naturally and it would take a long time for everyone else to die off.

    We might also find that there were other effects of the human mind being altered in this manner.

    It would probably be easier to develop a drug that would prevent spam from bothering you. (Probably if spam bothers you a lot, then becoming a heroin addict might give you bigger problems and then you wouldn't care about spam anymore - you'd be too busy trying to acquire more heroin and throwing up and stuff.)

    Or we could quit using email.

    One idea that I had was to create a new email protocol that doesn't have compatibility with existing email systems. Basically redesign email from the ground up. Such a new system might require that all emails me digitally signed with valid certificates that could be authenticated, etc. I put a lot of thought into it. After thinking about it carefully for a long time, I have come to a realization that such a system could not work unless the problem of zombie PCs can be solved.

    As long as people are allowed to send email to anyone they want from their personal computers AND there are zombie PCs, then there will be spam. I don't think there is any way around that.
    --
    Avoid Missing Ball for High Score
  78. Re:This is painfully obvious and hopelessly naive by skiingyac · · Score: 1

    The most effective way to do it is to give the spammer a legitimate-looking but fake response. By response, I don't mean email.

    For example, if you get a phishing email for bank XYZ which directs you to a page asking for your name, SSN, account #, credit card #, phone #, etc. type in some junk and hit submit. Then you are GUARANTEED that the spammer will get your junk.

    It would be GREAT if there was an easy way to trap the spammer with this information, instead of telling the authorities about it (who are VERY slow in my experience and obviously not very effective). For example, call your credit card company & report a card as stolen, and enter that # on the phishing form (I'm not condoning this!). Or, enter bogus contact info and enter some government agency or the bank's REAL phone number, maybe they will call it, etc.

    Sort of like virtual card #'s that the big issues use now... you generate an identity ONLY to be used to trap these losers, and when they attempt to use it, they get caught. There are a lot of missing pieces to my cunning plan, but you get the idea.

  79. hahahaha! You crack me up, by Gary+W.+Longsine · · Score: 1

    It's nice that your baysean filters are working just fine. If you think that can't be changed in about an hour and a half, then give me your email address. I'll post it to a few web pages and you'll be back to hundreds of unfilterable emails a day. I guarantee results. What rock are you living under?

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  80. Catching Spam by Looking at Traffic.... by naChoZ · · Score: 1

    What do you think? Is this snake oil, or is there something to this?

    There is definitely something to this. At the ISP where I work, they have an excellent spam filtration system set up and it's very similar to what is being proposed. Our first line of defense here is a bit lower level though. As soon as a remote MTA makes a SYN connection to us, that ip is checked against the blacklist and if there's a match, the packet is simply dropped. This alone drops millions per hour.

    If the message passes to the next step, it's given a quick envelope check and also makes an ldap check for the recipient. If it passes that, it's handed on again where a body check is done. This portion is done largely by a third party vendor's servers located here on site and takes care of checking for virii, as well as content checks and bayesian filtering. (Though our relationship with this vendor is pretty tight, my boss has actually written some code for them.) If it passes all of this, it's finally handed off to our MTA which does one more ldap check before passing it on to the LDA.

    Overall, it does a great job of paring down the tens of millions of inbound delivery attempts to just a few hundred thousand actually delivered messages per day.

    The same servers handle our customer outbound mail traffic and they do keep track of usage in an sql database for trend analysis. Any customers that exceed our delivery thresholds are automatically added to the blacklist and blocked during the syn packet check. It literally takes just a few minutes for an infected customer to be noticed and automatically blocked.

    It works very well for us and mail servers that used to be under crushing load trying to handle all the spam traffic now perform very well and barely even break a sweat.

    --
    "I can be self-referential if I want to," said Tom, swiftly.
  81. Want to get rid of Spam? by jstmehr4u3 · · Score: 3, Insightful

    Get rid of HTML emails.. Spam isn't as cool when it doesn't have a bunch of fake links, pretty pictures, etc. You think the internet would cease to exist if we went back to text only?

    Send a URL in your text-only email if you want to check the email out in HTML...

    Just a thought

  82. Re:This is painfully obvious and hopelessly naive by rel4x · · Score: 2, Informative

    You sir, have no idea what you're talking about. They get paid by the sale for products, by the lead for mortgages, or a percantage for stocks. Go to bulkerforum.biz and look around.

    --

    Before you mod me funny, think, perhaps I was insightfully funny?
  83. We did it first by Anonymous Coward · · Score: 0

    Secure Computing invented this Technicque!!TrustedSource gathers data on the behavior of senders across the Internet. In addition to the traditional techniques such as global email traffic patterns and volume, network characteristics and public blacklists and whitelists, TrustedSource is unique in that it includes timely, precise data from Secure Computings's extensive customer network.

  84. Re:This is painfully obvious and hopelessly naive by nuzak · · Score: 1

    > For example, call your credit card company & report a card as stolen, and enter that # on the phishing form (I'm not condoning this!)

    I should hope not, since it's extremely illegal, to say nothing of the hassle you'd put yourself through.

    It would be nice to be able to generate virtual card numbers for the express purpose of catching a phish. Thing is, someone's going to do it to a legitimate merchant, the merchant doesn't get paid, the merchant gets pissed, and those are the real customers of the CC companies.

    --
    Done with slashdot, done with nerds, getting a life.
  85. Unfeasible Solution by mandelbr0t · · Score: 1

    See the form above. Your "solution" falls into the "everyone needs to adopt it all at once" category. Not to mention that it solves absolutely nothing.

    First of all, SMTP does not lack authentication or authorization methods. SMTP+SASL allows for authentication via login. You can also authenticate via SSL certificates. Once identity has been established by one of these methods, authorization is trivial. You can restrict relaying access based on IP. Most spam gets sent through open relays and pwned boxen, so the protocol isn't the issue: the open relays and pwned boxen are.

    I think you misunderstand the concept of "delivery" here. Just like the mailman doesn't drop by your house to make sure you read your mail, delivery simply means that the recipient mail server dropped a copy of the e-mail in the location that corresponds to the address you sent it to. Whether the server is correctly configured to then make the e-mail available to the actual person who's supposed to read it, or any other reason that could cause the person to not read your mail is beyond the scope of a mail server. Most mail clients allow you to request a read certificate anyway. I'm not sure what other "nice details" you'd like to see, but "250 - Message accepted for delivery" and "550 - User not found" are useful details from my point of view.

    I'm not trying to discourage you from implementing this new messaging protocol. When you're ready for primetime, write an RFC describing how it works and convince some other people to implement your idea. Also, make sure you lobby for legislation requiring everyone to use the new protocol, since that's the only hope in hell you have for widespread adoption. Good luck!

    --
    "Please describe the scientific nature of the 'whammy'" - Agent Scully
    1. Re:Unfeasible Solution by John+Bayko · · Score: 1
      See the form above. Your "solution" falls into the "everyone needs to adopt it all at once" category.
      Actually, no, it doesn't - they are parallel systems already in use. One or the other can replace email gradually, much like web forums have replaced Usenet groups (which also had terrible spam problems driving people away) - in that case, there was no sudden cutover, yet the change happened (mostly - Usenet groups still exist, but are far less important now and not as widely used).

      And as I pointed out, "online community" messaging is already starting to replace many uses of email for some groups of people. That's not a "plan" or prediction, it's an observation. New things start slow, then adoption speeds up if it's worthwhile. And it's speeding up.

      First of all, SMTP does not lack authentication or authorization methods.
      It has them, they just don't work. For example:
      Most spam gets sent through open relays and pwned boxen, so the protocol isn't the issue: the open relays and pwned boxen are.
      The protocol is the problem in that it's vulnerable to things like these.

      As for the rest of your post, I think you're misunderstanding what I wrote (or I mixed up some words - I'll have to go back and check). It has nothing to do with whether the sender knows the receiver received or read the mail. It's all about the receiver knowing with certainty where the mail came from. Uncertainty about that is what allows email to be abuse by spammers.

    2. Re:Unfeasible Solution by mandelbr0t · · Score: 1

      The protocol is the problem in that it's vulnerable to things like these. No, inept sysadmins are the reason it's vulnerable to things like these. Any additional information in the protocol would just point back to the open relay or pwned box, which is a dead end. The only way to stop an pwned box from sending spam would be to prevent the same box from sending e-mail, period. Or are you seriously suggesting that it's possible to have a protocol that determines the sanity of the sender's machine?

      Open relays are the protocol's fault? What idiot configured the mail server to accept mail from unindentified users, or from another network? I'm gonna guess you, since you clearly need changes to a well-established protocol to prevent your server from being used to send spam. Maybe you should learn how to administer a mail server before talking out your ass.
      --
      "Please describe the scientific nature of the 'whammy'" - Agent Scully
    3. Re:Unfeasible Solution by John+Bayko · · Score: 1

      You seem to be intentionally not following me - you're not arguing against anything I've said. And aside from that, exactly how is one competent administrator such as yourself going to stop the world's spam by properly configuring all other mail servers in the Internet? I just don't see that happening, so whether SMTP can theoretically be configured correctly doesn't help.

      To recap, RSS exists, is used, is a standard, and it could be extended to provide per-user messages reliably, without the problems of SMTP which allow spam. I expect that it, or "online community" web services, will eventually replace existing email because of these advantages.

    4. Re:Unfeasible Solution by mandelbr0t · · Score: 1

      How does a series of RSS subscriptions duplicate the simplicity of having a single final destination for per-user messages? It seems that under your scheme I would have to subscribe to every user community that involves a person I wish to communicate with. Or do you have an idea about how per-user messages would be passed from community to community? That's called relaying, and is still prone to the same abuses as SMTP relaying. How does an online community know that a machine hasn't been compromised? If I trojan your machine, I can tell it to do anything it's capable of, including spamming dozens of RSS channels using the identity of the machine I compromised. Good luck tracking that down, or preventing it.

      Your proposition does one of two things, though I'm not sure which you're advocating. It either makes e-mail more complicated for the end-user, requiring them to subscribe to a dozen different user communities, or it fails to solve the relaying issue. SMTP "allows" spam the same way you "allow" somebody to break into your home, steal your credit card or otherwise impersonate you. No matter what, you've got one hell of a hill to climb to replace the overall simplicity and ubiquity of e-mail.

      --
      "Please describe the scientific nature of the 'whammy'" - Agent Scully
    5. Re:Unfeasible Solution by John+Bayko · · Score: 1
      How does a series of RSS subscriptions duplicate the simplicity of having a single final destination for per-user messages?
      They both have a single destination. In one, the sender copies it onto your email server. In the other, the sender copies it onto their server. When you check for email, you poll one server, or several servers in the second case. They're about the same level of complexity.
      It seems that under your scheme I would have to subscribe to every user community that involves a person I wish to communicate with.
      For web based messaging, you don't even have to do that now, because they got together and created OpenID. For selecting individuals to receive email from, that would be handled much like email address books work now.
      Or do you have an idea about how per-user messages would be passed from community to community? That's called relaying, and is still prone to the same abuses as SMTP relaying.
      No it isn't, because SNMP is a "push" model and RSS is a "pull" model. You can "push" spam, but at best you can only meekly beg users to "pull" it because they need to know who you are to poll your server.
      If I trojan your machine, I can tell it to do anything it's capable of, including spamming dozens of RSS channels using the identity of the machine I compromised.
      You only have access to your own RSS source. At worst, you'll spam your friends, and they'll tell you about it so you can fix it (or they won't accept any more email from you if you don't fix it).
    6. Re:Unfeasible Solution by laffer1 · · Score: 1

      As far as getting you to pull spam with your model, it will just mean new methods of infection for clients. The way to force a pull is malware. Another approach would be to attack the host serving the RSS feeds.

      The problem is that everything thinks they have this great answer to spam. Its a social problem which is not possible to fix. We can slow it down, but never stop it. Creating a new protocol will not work. I get spam on IRC, MSN, AIM, ICQ, message boards, e-mail, etc. The only real advantage to using RSS is the ease of using SSL certificates and other authentication methods which are available on mail servers anyway. It would make more sense to argue for forced SSL certificates from a trusted (read expensive) authority. That would piss me off since I run my own mail server and do not have the money for such a cert. I'd almost live with it if it would help. As pointed out somewhere above, spammers are now relaying through the ISP mailservers now.

      A good start would be to push mail servers that have integrated authentication, authorization, ssl and some antispam filters with defaults that limit relaying. Its a hassle for someone to configure a mail server, especially using sendmail or postfix. One has to add a bunch of third party software.

    7. Re:Unfeasible Solution by John+Bayko · · Score: 1

      As far as getting you to pull spam with your model, it will just mean new methods of infection for clients. The way to force a pull is malware. Another approach would be to attack the host serving the RSS feeds.

      That's true, but it makes it much harder for the spammer, which is important. In the case of malware, at least you could take responsibility for the security of your own system, whereas now you're at the mercy of others - if only one system in the world (out of millions) is owned or has an insecure open relay, spammers can use it against you.

      As far as attacking the RSS host, at least the attack would be far more visible, and easily identified, and the damage would be very limited even if it weren't caught. If it's not fixed, you can stop reading from it until it is (still send mail to them to let them know). Again, it becomes far more work for the spammers for far less payoff - hopefully enough to make it no longer worthwhile for most of them.

      I'm sure there will be a bunch of new problems with something like that, but I'm certain that overall it will be far better than email as it is now.

  86. SpamAssassin already does that by flyingfsck · · Score: 1

    by looking at the mail headers.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  87. Re:This is painfully obvious and hopelessly naive by skiingyac · · Score: 1

    Right, its not possible/legal today which is the main problem...

    The fake card # would be flagged somehow, since the point is that the phisher WANTS to use the card at a legitimate merchant (otherwise its worthless). Attempting to process the card would alert the merchant to not fulfill the transaction (no money lost) but they could tell the phisher the order was successful or that item is out of stock or make up some other excuse, and by the time the phisher knows what hit him, the cops show up at his door.

    If they can be stopped before they've spent a few grand of some old lady's money on motorcycles (using phished legitimate card #s), then both CC companies AND merchants will be very happy about this.

  88. Re:This is painfully obvious and hopelessly naive by flyingfsck · · Score: 1

    Exactly - you are only the second person I have encountered that knows how the spam industry really works!

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  89. Re:This is painfully obvious and hopelessly naive by TheRaven64 · · Score: 1

    Many banks allow you to generate one-use credit card numbers with a spending limit. You could, potentially, create one of these with a 1 limit. Then, as soon as it was used, the bank would be able to contact the merchant, inform them that a customer had attempted to use a stolen card, and request that they supply all relevant data to local law enforcement.

    --
    I am TheRaven on Soylent News
  90. Re:This is painfully obvious and hopelessly naive by TheRaven64 · · Score: 1

    Do they get paid at all? All of the spam I have received recently has been criminal in nature; some stock scams, some phishing, some selling pirated software (why would anyone buy pirated software? If you are going to pirate, surely you would get it for free...)

    --
    I am TheRaven on Soylent News
  91. Re:hahahaha! You crack me up, by localman · · Score: 1

    My email address is already available online right now in several locations. You can find it in less than a minute, if you want. It has been available online since 1998. In fact I have multiple addresses listed on multiple public sites right now, all forwarding to my inbox. I've never put any effort into protecting it, I give to all sites that I sign up to. If you want to put extra special effort into attacking my inbox, well, I don't know if it would survive... go ahead if you want, but that's not really the point. The point is that my email has been and continues to be publicly available, so I'm not hiding from spam, yet my inbox is under control. So spam is not a problem for me.

    Actually, I just checked and in the past 2 days I've received over 4300 spam messages and only 1 got through. The 700+ figure was based on the last time I bothered to check.

    Baysean works different for different people. Maybe if it didn't work for you it's because the emails you want are not as different from spam as mine are? More likely is that you didn't train it properly or have the thresholds set right. Beyond that, I don't know what to tell you.

    Cheers.

  92. Re:This is painfully obvious and hopelessly naive by Cedric+Tsui · · Score: 1

    I have a question along similar lines.
    What motivation do spammers have for designing spam that gets around the filters? If I implemented a filter to get rid of viagra ads, what is the likelihood that I will buy it? Sure. Maybe the 'enter your bank password here' scams need to get around the filters. But if I haven't responded to the first thousand viagra ads, you really aren't gaining anything by sending me more.

    Heck. Spam MIGHT be tolerable if like snail mail ads, they're done tastefully, done well and in moderation.

    Take home message.
    I really wish they wouldn't compromise my filters... Thunderbird lets in half of the spam these days because they're all images over top a page from a novel. My sysadmin doesn't have time to implement server side filtering. I'm just swimming in spam.
    Help!

  93. Re:hahahaha! You crack me up, by localman · · Score: 1

    Whoops -- I confused my work email with my personal email there for a sec and mixed up the info. The correct stats are:

        4300 spam at work in about 45 days, 2 spam got through.

        900 spam at home in about 2 days, 1 spam got through.

    It varies, of course, so sorry if my previous numbers were a) wrong or b) outdated. Still, I think my original point stands.

    Cheers.

  94. Re:This is painfully obvious and hopelessly naive by Phroggy · · Score: 1

    Rule #1: Spammers lie.

    The person actually sending you spam very often doesn't care whether you buy the product being advertised or not. They've sold their spamming services to a paying client, after convincing the client that their "opt-in e-mail marketing campaign" will be effective. If nobody buys anything, the client doesn't make a dime, but the spammer has already been paid, and moves on to the next victim. If people do fall for it, the client may be interested in repeat business, but that's not necessary.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  95. Re:This is painfully obvious and hopelessly naive by Phroggy · · Score: 1

    You can't just hit the "reply" button; spammers spoof the return address on their spam to make it look like it came from some random address on their list. As others have mentioned, it's called a "joe-job". If you reply to the spam you get, you'll be sending your replies to just another one of the spammer's innocent victims.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  96. Re:hahahaha! You crack me up, by Gary+W.+Longsine · · Score: 1

    No, your original point does not stand, it was only ever wobbly at best. The minor differences in your stats really don't bear on the point at hand, which is that although you have managed to massage your filters to an impressive degree, the experience of others indicates that baysean filters are no longer as effective as they need to be. The approach is (a) too labor intensive, (b) error prone (valid emails get eaten) and (c) failing for many people. It's really nice that it hasn't bitten you yet, but really, I didn't think there was anybody left on the planet who didn't realize that spam is a growing problem because the spammers have learned some clever ways to get around clever filtering. You should be studied by science. There is probably some area of your brain that will light up when you think about this problem that will someday be called the Missouri Lobe.

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  97. This concept is already implemented by Anonymous Coward · · Score: 0

    http://www.networkworld.com/reviews/2005/041105sym antectest.html

    www.networkworld.com - Symantec's new Mail Security 8100 Series appliance offers a twist on spam management. It limits the amount of network bandwidth spam can consume. In our exclusive Clear Choice test of the Mail Security 8160, we found that when the bits start flying it manages the load on corporate mail servers quite well, providing a good first line of defense in reducing the amount of spam that enters the network

  98. There are no legitimate mass marketers by quixote9 · · Score: 1

    I hate spam. I still get mountains of it, because I haven't sent a separate snail mail to a separate address to every jerk on earth who wants to spam me. You wouldn't have to worry about any traffic-based filters if the messages only went out to real opt-in users.

  99. I could not resist... by Vario · · Score: 1

    Your post advocates a

    (x) technical (x) 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
    (x) 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
    (x) 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
    (x) Lack of centrally controlling authority for email
    (x) 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
    (x) Huge existing software investment in SMTP
    ( ) Susceptibility of protocols other than SMTP to attack
    ( ) Willingness of users to install OS patches received by email
    ( ) 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
    ( ) Technically illiterate politicians
    ( ) Extreme stupidity on the part of people who do business with spammers
    ( ) Dishonesty on the part of spammers themselves
    ( ) 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
    (x) 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
    (x) 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!

    1. Re:I could not resist... by Simetrical · · Score: 1

      While I realize this was partly a joke . . .

      (x) It will stop spam for two weeks and then we'll be stuck with it

      Perhaps, but I suspect it will put a fairly large crimp in the business. Sender-side validation is going to be more useful than recipient-side, because the sender has more information about the sending client. Even aside from that, it has the benefit of putting framework for easy upgrade in place.

      (x) Requires immediate total cooperation from everybody at once

      The same could be said for pretty much any protocol change, and it's not true. The infrastructure will be phased in, and then once it's in place and running, SMTP service will end. The only ones who will be screwed over by that are the guys who were sending e-mail from their own servers, but we can campaign to inform them (to begin with, sending alert messages that "you're still using SMTP, stop!!" in response to any SMTP e-mail sent to a prepared server).

      Of course, we aren't going to block packets for being SMTP . . . just the major players will (be required to) stop accepting it. If you want to send SMTP to your own server somewhere, go ahead.

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

      Wha? How?

      (x) Lack of centrally controlling authority for email

      Um, I'm suggesting we create one.

      (x) Open relays in foreign countries

      No difference between them and any other client, really. The entire point is that the gateways do the analysis, and open relays have to go through gateways like anyone else.

      (x) Huge existing software investment in SMTP

      There's a huge existing software investment in HTML, too. Let's ditch this XHTML foolishness. I mean, standards are supposed to stay static forever and ever and no new ones ever created, right?

      (x) Joe jobs and/or identity theft

      Not relevant, unless you're referring to the photo-ID requirement. If you are, well, the cameras would kind of pick you up, y'know, so even if you give false ID you'd suddenly be an internationally wanted criminal.

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

      Well, yeah, I noticed. But saying "you have to prove it's practical" is kind of a conversation-killer. I was asking why it wasn't practical.

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

      Why should you have to trust those damn DNS servers? And the Internet routers? They're controlled by telecoms, for crying out loud!

      (x) I don't want the government reading my email

      Never mentioned the government reading anyone's e-mail. Actually, you could probably use SSL or something in any new protocol people come up with, so the likelihood of the government reading your e-mail is probably decreased.

      --
      MediaWiki developer, Total War Center sysadmin
  100. Keyword Analysis is Dead -- Image Spam by fupeg · · Score: 1

    Keyword analysis and Bayesian methods that depend on it, are useless. Most spammers are switching to image spam where they embed pictures of text instead of actual text.

  101. You are correct, in principle by MarkusQ · · Score: 1

    If it doesn't make a significant difference in your sales -- easily measurable -- you won't continue to pay for it. Even stupid people know when they're losing money.

    You might get a steady stream of first-timers who fall for the lure of sending spam, but the volume would be a trickle compared to what we have today.

    You are correct, in principle. As soon as the supply of stupid people dries up, it would slow to a trickle. But how long will that take?

    If you want to get an idea of how much spam would get sent even in that trickle, grab a copy of every daily paper on the planet and count up all the prayers to St. Jude and so forth in the classifieds. Multiply that number by the number of addresses in a typical spam list and that should give you a rough estimate of the amount of spam that would still be getting sent each day even if it didn't work.

    My back of the envelope estimate puts it at around 1,000,000,000,000 individual pieces of spam a day, put I'll admit I only looked at a few papers and extrapolated. Another way of looking at it: if only one person in a million is dumb enough to send a piece of spam each day even knowing it would not work, and they send it to a million people, there would be 6,500,000,000 pieces sent every day.

    And 0.00001% of the population may be a low-ball estimate of how many dumb people there are. I suspect the actual number is somewhat higher.

    --MarkusQ

  102. Re:[OT] abuse of moderation by Anonymous Coward · · Score: 0

    Other than a possible cultural misunderstanding of the phrase "the peanut gallery", I have no idea what prompted such an abuse of moderation. I fully expected to find this at +3 or higher when I woke up this morning, with some combination of funny and insightful.

    When I came back to see -1 troll, I closed Slashdot for a while but then I got angry and decided to post. This type of moderation abuse is why people stop coming to Slashdot. If you don't think it's that funny, just leave it alone. There is no troll in the above message. Read it again if you still think so. If that fails, read it again.

  103. Can I do this? by NotPeteMcCabe · · Score: 1
    I was just thinking about this recently. I hope some /.ers can tell me how feasible it is.

    Background: I have 2 accounts: my own domain (primary) and my isp account.

    I'd like to set up the followng for my own domain: I maintain a whitelist, any email from someone on the list goes right through. Everything else is bounced with a message explaining about the whitelist and asking them to email me on my isp account -- or contact me some other way -- to have me add them to my whitelist.

    Unless I'm missing something, this will eliminate 100% of spam from my primary account. It shouldn't affect spam to my isp account, because that address is already on the web. All in all, this seems like a very simple and extremely effective solution.

    The downside is that it will make it a little harder for people who aren't already on my whitelist to contact me. I'm trying to think how many times I received a message I care at all about from someone who isn't already in my address book, and I'm not sure it has happened in at least a year. Most such people -- for example, someone who reads a post of mine on a forum -- already contact me through my isp address.

    If there's a downside I'm not seeing (aside from "Whitelists suck" :-), I'd like to hear about it.

    Mostly I'd like to know if there's a domain host who can make this happen. My current provider (domain direct) already has a whitelist option, but not a user-configurable autoreply to non-whitelist messages, which is important to my comfort with this plan. If anyone knows a domain host who can do this, I'd appreciate posting it, or email me at pjmccabe@adelphia.net.

    Alternately, is this something I can set up reasonably easily on my Mac running OS X 10.4? I know mail has filtering and autoreply features, and I was a programmer about 20 years ago, so a roll-your-own solution is not out of the question. But I'd rather my ISP do it.

  104. Where's the beef? by ttul · · Score: 1

    > STP server correlates this information with the data received from other MTAs
    > and replies with a number that reflects how likely the sender is a junk mail source.

    How exactly is this done? What differentiates spammers from legitimate senders?
    And how is this idea any better than reputation databases which assess the long term
    sending history of particular mail servers (and domains, where domain authentication
    is provided)?

    These days the vast majority of spam is sent from botnets. Botnets by definition
    fly under the radar -- the only thing you know about them is that you know nothing about
    them until it's too late.

    Correlating traffic patterns is an interesting idea, but the author doesn't flesh it out.
    What specific correlations would you make? Give us the details!

  105. Short term solution by Kazoo+the+Clown · · Score: 1

    It seems to me that there's no reason that a spam mailer couldn't operate with a traffic pattern virtually indistinguishable from a non-spam mailing list. To the extent they don't *already* do that it's probably just because they haven't had to. If such analysis becomes routine at ISPs, that will simply motivate the spammers to tune their engines behavior a bit, and the "fix" will be rendered useless in no time...

  106. I have a better idea: by Anonymous Coward · · Score: 0

    100% of the trouble on the Internet is caused by Windows computers. PERIOD! Boot the stupid bastards off our (Unix&Mac:OUR!!!) Internet and don't let them back on until they can run something that doesn't get ass-raped in five minutes! But ooohhhh no, we couldn't solve the REAL problem, could we? No, we'll just keep farting around doing nothing about it.

    Anybody refute this? Show me ONE spam incident where the server access log doesn't show a drolling moron running Windows with no service packs/security updates.

    1. Re:I have a better idea: by sheepdog43 · · Score: 1, Informative

      Funny, my BSD dedicated server was recently hacked and was spamming. It was hacked through a php/mysql exploit through a poorly written script a customer was using.

      Many DDOS attacks are often carried out by Linux boxes as well, the .com I worked at had it happen to their server. Stop blaming Windows for the problems of the world. Besides if Windows did not exist, you would just have to blame something else. The most likely candidate would be Linux.

      I would almost bet that your Linux or Mac box has no anti-virus protection on it, so how does that make you any better?

  107. The problem is that it is still filtering by cyberscan · · Score: 2, Interesting

    One can come up with all kinds of trick to filter spam, however, the problem still remains. Spam will continue as long as it is profitable. There are too many "Puppies in a barrel" for a spammer to choose. After many, many years of prodding, many people have finally gotten antivirus program, yet they neglect to download or purchase virus database updates. Many people spend time and effort to ensure that their computers are malware
    free, yet their router retains the default username and admin password. Spammers have programs that allow people to try to log in to these routers and use their embedded telnet commands to send spam without the knowledge of the computer owner or any program residing on their computer. The point is that the Internet can be compared more to "swiss cheese" rather than the "series of tubes" that the politicians use. There are many, many points of attack for spammers to use.

    Filtering spam is much akin to a person who holds hands in front of his or her face while a bully is pummeling him or her. The person is likely to fend off blows from the bully, but some of the blows will get through. Once a spam is sent, even if properly filtered, the damage has already been done. Until very recently, all I had in my area was dialup. My program successfully filtered about 99% of the spam received, however I still had to wait about 30 minutes before I was able to view my legitimate mail. I lost 30 minutes of time that I could have been working on a client's problem, while the spammer lost nothing. I also lost a client because a program that I previous used labeled his email he sent me as spam. Again the spammer who spammed me lost nothing. Spammers are like bullies, they will not stop until people HIT BACK!

    It is only when spammers have to deal with the large amount of bandwith used, the processing power to handle complaints, and the loss of sales that result from efforts to filter complaints will spam be much less profitable. The idea is to punch back and deter the bully. Sending complaints to the spammers' websites get them at their weak point - the place where they make contact with potential buyers. Several program have attempted to hit back, and 2 of them were very successful in doing so. However, like spammers, these programs had a weak point, and that point was the fact that they needed a central server in order to instruct each individual program. Now things are different. There are several projects currently underway to trade complaint instruction files via peer to peer networks. What this means is that there is no central server which spammers can attack in order to silence complaints to their websites. One such project is called SpammerSkewer, and it is an open source GPL program that is in alpha. The program can be found at http://spammerskewer.sourceforge.net/ .

    It is also important to note that these new programs are not distributed denial of service programs. As for SpammerSkewer, it only receives instructions on how to complain. It does not initiate complaints. Only a user can initiate a complaint by either bringing up the complaint interface or by dragging an email into SpammerSkewer's spam directory. It is the Spammer who determines how many complaints are submitted to their websites. SpammerSkewer's author even provides a way for spammers to "opt out" from receiving complaints if they insert a header clearly labeling their email as spam. Another way they can opt out is by not sending spam in the first place. In a distributed denial of service attack, a person other than the one who controls a victim's website is the one that controls how many visits a site receives. With SpammerSkewer, it is the Spammer who sends out the spam that determines how many visits a site advertised via spam gets. The only sites that are put in SPammerSkewer's instruction files are those well known to be advertised via spam. Instruction files are also cryptographically signed in order to prevent tampering. I

  108. Re:This is painfully obvious and hopelessly naive by zoltamatron · · Score: 1

    I want to make a program that you can give a spam link (or many links) to and it will access that website over and over and over again when my computer is idle. How 'bout fighting back? Get enough people to use this program and you have a legitimate force.

    Send a spam e-mail.....get slashdotted. How about that?

    --
    Tolerance does not tolerate intolerance, or hypocrisy.
  109. How is this different from... by Palefrei · · Score: 0

    ... www.senderbase.org?

    "SenderBase is the technology that allows IronPort Reputation Filters to block 75% of incoming spam at the connection level, with less than 1 in 1M false positives. SenderBase also enables IronPort Virus Outbreak Filters to stop virus outbreaks as much as 42 hours ahead of industry standard signature availability. Only IronPort has access to the global traffic data of SenderBase."

  110. Re:This is painfully obvious and hopelessly naive by Baricom · · Score: 1

    You just invented Blue Frog. They essentially shut down after the DDOS attacks got to be too expensive.

  111. Re:This is painfully obvious and hopelessly naive by zoltamatron · · Score: 1

    My software is nothing like blue frog. Blue frog would give you tools to easily get your e-mail removed from the spammers lists. They folded because spammers targeted DDOS attacks on their servers and made the software unusable. My software would basically launch a DDOS attack on anyone that sent out a spam e-mail to people that had my software. The more people you send out spam to, the larger the DDOS attack. The recipient of the e-mail has the final word on what is spam and is not. I think this would at least make spammers think about who they send e-mail to. At least if they actually targeted people that might be interested, not just any valid e-mail, the spam volume would reduce immensely.

    --
    Tolerance does not tolerate intolerance, or hypocrisy.
  112. Re:hahahaha! You crack me up, by Emrys · · Score: 1

    Yeah, this is pretty well understood by the content filtering community. The spam problem was solved several years ago, but most administraters still refuse to do any of their own work to implement a working solution and expect someone else to give them a button to push to solve it. Hence the arms race.

    It works for you because you spent hours doing research and training. It works for everyone else who does the same thing. Despite the "common knowledge" that "bayesian filters can be beaten", no one has yet published any evidence demonstrating that a properly-configured filter can be beaten in any significant degree without making ridiculous, easily-defeatable assumptions.

    Complaints that setting these filters up correctly are "too hard" are ridiculous when you compare the time most people spend day after day trying to stay ahead of the arms race vs. the up front time needed to configure a decent content filter and then leave it alone. Even the ongoing training can be (mostly) automated. And false positives are just more indication the filter isn't configured correctly.

    This bit from TFA:

    "Statistical (bayesian) scanning is easily defeated by randomization; numerous techniques exist to avoid keyword-based detection and new methods surface regularly. Content scanning is also known to suffer from false positives."

    is particulary absurd, since anyone who knows anything about Bayesian Classifiers knows that _random_ words are never going to show any statistical significance at all unless your normal, legit mail flow is also comprised of the same "random" words. NBCs look for statistically significant anamolies, they aren't fooled by mere randomness.

    Do spammers try to poison Bayesian filters with random words? Yes, certainly. Has anyone demonstrated real, verifiable evidence that this has any effect at all against properly configured filters? No. But people are so used to losing, they assume they've lost once they see the attempt.

  113. Re:This is painfully obvious and hopelessly naive by totally+bogus+dude · · Score: 2, Insightful

    Chances are the people that actually send the spam messages (those who control the botnets) are not the people making money from stock scams, phishing, or sales of pirated software.

    In the same way legitimate businesses will pay marketing companies to run advertising campaigns, design, send and manage email distribution lists, etc, less legitimate 'businesses' pay spammers to send out their message to as many people as possible.

    So yes, they do get paid - just not by the victims of the spam.

  114. Re:hahahaha! You crack me up, by localman · · Score: 1

    Thanks for the reply. That's more or less what I thought. I didn't mean to offend anyone by implying spam isn't bad... it is bad. But it just seems like the industrious user can all but eliminate it these days. I think it is critical with bayesian classifiers that it is per-user. We have a site-wide implementation at work which sucks and I asked them to turn off (false positives and still too much spam slipping through) so I could manage it myself. Actually, I'm not even sure how a site-wide one could possibly work as intended. Some default configs also take shortcuts like having the filter self-teach, which is stupid, because that means it just learns to repeat mistakes.

    Anyways, as usual, the devil is in the details.

    Cheers.

  115. It doesn't matter why people respond to spam by billstewart · · Score: 1
    Please moderate the parent article as a troll. Or at least moderate it "overrated".


    Spamming makes money for some people, because "there's a sucker born every minute, and two to take him", and spammers are happy to sell to the sucker, the two that want to take him, or both. It doesn't matter that some spammers are wanabees who lose money; if they fall off the map, there are more replacements on the way. If spamming didn't work, there wouldn't be so much of it, and it wouldn't be increasing in volume so fast.


    We don't care why spammers think they can find suckers - we only care how, because that offers some hints for how to detect them and either kill them or distract them into areas where they spam each other and leave us alone, optionally while we sell them bandwidth or imaginary hosting space in Nigeria or whatever. If we can make it technically infeasible or economically non-profitable to spam *us*, they'll stop spamming us, but otherwise they'll keep it up.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  116. Re:hahahaha! You crack me up, by localman · · Score: 1

    the experience of others indicates that baysean filters are no longer as effective as they need to be

    That's interesting... I thought the proof would work the other way: if I can make it work then doesn't that prove they are effective? I don't know if you feel you are happy with your own spam filtering, but if you can install spamassassin I'd be happy to share my setup with you.

    Cheers.

  117. Hmmm - interesting idea by Anonymous Coward · · Score: 0

    Anything that requires cooperation with the ISP's are probably going to fail. Spam mail will usually be coming from a huge variety of IP addresses. In the past, I've kept statistical record of IP addresses, and the pattern usually comes from a lot of Cable and DSL users who were no doubt unaware their PC's were part of a large botnet.

    In 2004, from July (After HOPE), I deployed a proof of performance system which involved
    aggressively reporting ALL spam, going far far beyond what SpamCop is doing. It shut down over 500,000 infected machines... infiltrating the Russian language spammers chat channels, we leard how effective it was. Brightmail reported a 20% drop in spam while I was running these tests. I realize now it needs a lot of streamlining, and now the Whois servers won't allow automatic polling anymore, I abandoned the project by November.

    if I can have a "nice" way to poll whois servers on about 20 - 30 IP addresses automatically, I can realize such a system might be useful to others.

    I wasn't interested in making it available to others, because I thought it could be abused, because if just one non-spam message gets reported, that poor unluckey person won't have internet service until they call and explain. Most of the time I spent care and feeding this puppy was to have a very clean "spam pot" of 100% spam. I was reporting about 25,000 spams a day (something you can't do from home DSL or cable), from my Co-Location's T3.

    The ISP's really liked the reports. They contain any and all information the ISP is going to need to identify the infected machine, and it even aggregates reports into a CSV file defined by the ISP's needs.

    The net result is this, according to my statistical reports... the average lifetime of
    an infected host is 6 - 10 days before it's discovered and shut down, and some NEVER get shut down because the ISP's dont give a crap or they are offshore. For Chinese ISP's I wasn't sending them spam reports, instead I was sending them spam reports to the American Gateways providing China's Connectivity to the States, Scolding them for not taking a more
    active approach and pressure the Chinese to be more aggressive. Seems to have worked to some extent...

    When we ran our "Proof" code, the average lifetime of a zombie was hours instead of days. ISP's late in dealing with our reports were scolded and sent more reports to their upstream providers. Eventually, some in my list of ISP's I'm reporting to, will usually deal with them within hours... some will immediately cut off a subscribers access as soon as more then 3 spam messages tied to their IP block are noticed. User would then wind up calling the ISP, who then would notify them that they need to clean their PC's before being allowed on.

    About 15% of the IP addresses had incorrect Whois information. Where were intered into a dated database, and are automatically mailed out to ARIN, APNIC or others to inform them their records are outdated. In this process, we nailed down several instances where some large upstream cisco routers had been hacked, and some unused IP addresses were snatched up for spamming purposes.

    if I can solve the problem of obtaining accurate Whois on IP blocks and acquire accurate CIDR blocks of spam originating machines, I might reserrect it again.

    If anyone wants to contact me on this, then please leave a message here in /. with contact info, and I'll contact you. If the Russian Mafia knows who I am, I'm sure they can "touch" me - so I wish to remain anonymous.

  118. Re:This is painfully obvious and hopelessly naive by Anonymous Coward · · Score: 0

    Because replying to these messages just winds up going to some forged address, and in the past, some people get flooded if their Email address is used as a Reply-To address.

    Anyone who replies to spam messages should know that in most cases, it goes nowhere but to some innocent person who happens to have that reply-to address.

    The only way to identify the TRUE location of where the message comes from is the First
    recieved line's IP address in backets [202.12.12.1] like this. It only identifies the IP block of some machine in some botnet, and the owner is usually unaware it's their machine that send that particular spam message. A whois will give you details of the owner of that IP block, but due to privacy laws, it's impossible for us mere mortals to know who's machine it is. A court supena when submitted to the ISP might result in some action. ISP's will only give this info to Law Enforcement agencies.

    If you have a lot of money to burn, and want to hire an attorney, a PI, and other professionals to go after them, FAR OUT - Knock your self out - all of us will get behind you.

  119. Really stopping spam... by Anonymous Coward · · Score: 0

    If people really want to stop spam, they have to stop using the same linear thinking that caused the arms race "Don't want that email, must block source" and attack the ROOT CAUSE of the problem. The majority of spam has one underlying purpose, to direct Internet traffic to a destination for the purpose of making profit for the spammer. I propose a simple solution.

    A consortium of ISPs agrees to block all access TO a site advertised in spam emails sent to recipients of that service. i.e. Someone spams tens of thousands of AOL customers telling them to go to www.bigblacktitties.net. Instead of blocking the email, AOL blocks any of the people on their ISP from surfing TO that URL. An automated message is also sent out to other consortium members with the URL, and that address is then blocked on all of them as well.

    This solution hits spammers where it hurts. By spamming a broad audience to promote a site, they end up making their site invisible to millions of potential prospects. They want to drive traffic to their site, not prevent people from being able to get there!

    Blocking the sender will never work because of spoofing. Blocking the DESTINATION is far more effective. :)

    NOTES:
    * No the system isn't automated, an admin adds sites to the block list to prevent malicious attempts to block legitimate sites.

    * Users attempting to connect to the blacklisted destination get an automated message that the site was blacklisted due to being associated with spam, fraud, phishing, or some other TOS violation. It also gives them instructions on how to reactivate that address just for themselves. This allows legitimate customers of bigblacktitties.com to regain access, but puts the onus on them to initiate this and can tip off ignorant suckers to potential scams (i.e. like when they get the fake paypal phishing page and it wont even load the images because its been blocked)

  120. Re:hahahaha! You crack me up, by Emrys · · Score: 1

    Site-wide can work. It just takes some extra tuning considerations. See e.g. http://www.usenix.org/events/lisa04/tech/blosser.h tml

    The predictions were that it wasn't feasible but the evidence from multiple quarters hasn't supported that so far. I'm not sure anyone has published anything on *why* that might be yet, but it is probable that there are population size break points between which legit mail is relatively homogenous enough to still be distinguishable from spam. In our environment the filter can tell the difference between wanted and unwanted mails coming from the same opt-in vendor newsletter to multiple business recipients.

    If you guys had a DFW office I might be convinced to come show you. ;-)

    And self-updating classifiers are Russian roulette.

  121. Spamd's an MTA proxying for your MTA by billstewart · · Score: 1
    Spamd's basically a lightweight MTA that you use as a proxy front-end for your real MTA.


    It's still running SMTP, but instead of running a full-scale turing-machine-complete bells-and-whistles mail forwarding and delivery extravaganza like Sendmail, or the somewhat lighter postfix / qmail / etc., all of which have to manage complex delivery rules, spam filters, and mail relay capabilities, spamd is basically configured to do some simple spam-repeller rules, relay mail that's potentially not spam to your real MTA, and optionally harass anyone that looks spammy. This makes 50-90% of the email go away, letting your memory-hogging CPU intensive spam filters and mail delivery engine handle the more clever spam and the occasional real message.


    It doesn't take that much resource to do basic SMTP and greylisting. After all, Sendmail originally ran on a PDP-11, as did UUCP, and it's mostly a simple state machine that does a couple of handshake plus keeping a simple database lookup - and the database doesn't need to be an SQL engine, just a simple hash table or Berkeley DB or equivalent, keeping track of an IP address and a timestamp, plus another list or two of valid email usernames, known evil sites, etc.


    Spamd has another big advantage, which is that cleverness of spam content and cleverness of spam delivery method aren't closely correlated. The spam that puts lots of work into embedding images in the message body or being the most uniquely plaintive Nigerian widow may be harder for your CPU-burning Bayesian filters to crunch, but it may be delivered from known zombies or high-performance delivery engines that don't slow down to respond to return codes, so you can save a lot of transferred bits and CPU just by greylisting or by running slowly for the first few seconds. And some of the really clever spam/phishing writers are using stolen address space, which is a really clever delivery system that doesn't survive greylisting either.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Spamd's an MTA proxying for your MTA by ivan256 · · Score: 1

      I'm completely on board with all of that stuff. I use a greylisting proxy in front of sendmail on my linux mailservers (actualy I run exim4 on one of them...). It's not complicated software either. It's just a script written in python with no other requirements. I was just giving the guy a hard time for gratuitous and off-topic pimping of OpenBSD, and for being misleading.

  122. Re:hahahaha! You crack me up, by Gary+W.+Longsine · · Score: 1

    Please post it to a web page where everyone can benefit. Undoubtedly your configuration is more effective than those used by many people, probably including me. If I may humbly submit, however, it is not my own inbox that I have in mind when I suggest that spam is a real problem. One of my clients rejects so many messages at their gateway that they generate about 1 GB of logging messages about that activity each day. Despite several very competently designed antispam layers, including spamassassin, at least 1 GB of spam still gets through each day. They are responsible for many thousands of inboxen. Even if only 1 in 900 spam leak through, it's still a huge, huge problem. Spam accounts for the majority of email traffic on the internet. Spammers can and do generate messages which defeat baysean filters. It is a real, large, and growing problem.

    If you could solve the spam problem with your SpamAssassin rules, you would be an internet hero and perhaps could become very wealthy as a result. Why are you hiding out in a slashdot forum when you can help save the world from spam?

    now don't talk to me about the polar bear
    don't talk to me about the ozone layer
    ain't much of anything these days, even the air
    they're running out of rhinos - what do I care?
    let's hear it for the dolphin - let's hear it for the trees
    ain't running out of nothing in my deep freeze
    it's casual entertaining - we aim to please
    at my party
    -- Dire Straits

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  123. sounds like crap by hcoder · · Score: 1
    I'm always interested in a solution saying 'all the other vendors and their methods are crap, but our solution is the ultimate solution to spam'.

    The article says: "Statistical (bayesian) scanning is easily defeated by randomization".

    This is simply not true and I guess folks at hexview haven't met any real bayesian anti-spam application. I develope (and use!) a statistical (though not Bayesian but inverse chi square) content filter and I can tell you that it's far from "being defeated". I get lots of spam every day and it marks them correctly and catches at least 99.5% of the spam easily.

    Nowdays most of the spam is sent by botnets as illustrated in the "Many-To-One" scenario. They accept that it's a difficult to handle situation and heuristic filtering is required unless the bots send a high email traffic. What about new botnets, unknown to the STP system? Bayesian filters can handle this. A typical shortcoming of this STP thing is that they cannot handle situations when you get spam from a low traffic host or if your colleauge bothers you with some stuff. Statistical filter can help you with this, too. It's unacceptable for me if a 3rd party judges my emails whether they are spam or not. That's why I keep avoiding solutions like STP, RBL, ...

  124. Re:hahahaha! You crack me up, by localman · · Score: 1

    You are right! I shall retire off the proceeds from referring people to the spamassassion man page!

    More seriously, I'm not saying that I can solve the world's spam problem, just that a motivated person can make spam a non-issue for themselves.

    Actually I already posted my config in reply to another comment, but more importantly you have to feed it properly.

    I think there may be a misunderstanding of what bayesian filters do when it is said that spammers can "generate messages which defeat baysean filters". Which bayesian filters? Certainly not all, because they're all different. That's the point. Unless you're using them site-wide, which kind of misses the point.

    Anyways, I'm pretty sure I'm not convincing you of anything, but I thought I'd wind down with that.

    Cheers.

  125. The main difference: yours is illegal by JavaRob · · Score: 1

    My software is nothing like blue frog. The main difference is that BlueFrog took the same approach, but with adjustments to:
    * keep it legal (a straight DDoS is not legal, and your users would expose themselves to legal repercussions)
    * involve human-written scripts to access the spamvertized company's site, so that the response (a complaint) would be successfully delivered in the most effective way possible.

    The legal question is essential. You need more than a few hundred (or a few thousand) people using the software, or the impact is negligible and avoidable. And of course if the spammers just manage to get one of your users or YOU heavily fined or jailed for DDoS attacks, that pretty much finishes it.

    So BlueFrog was designed on the idea that one spam = one complaint on the spamvertized company's server, often submitted into an order form or something like that to get their attention. Unfortunately for their model, they managed this by having users send all spam to a central server, where they processed it and sent reporting scripts back out to the clients, who would submit the actual complaints. Obviously this presented an attackable weak link. The complaints would include text that told the spammer how to download software to clean *all* bluefrog users from their lists... unfortunately (this was the other, smaller flaw) the spammers could figure out the blue frog users on their lists by doing a simple compare of lists pre & post cleaning. Then harass them directly... though the number of users was high enough that this didn't amount to much in the end.

    Personally, I STILL think this is the closest anyone has come to a successful campaign against spam. There's a project set up to create a similar, but distributed, system at http://okopipi.org/ if you are interested in pitching in and solving the remaining issues.

    Just please don't create yet another DDoS against spammers tool (there are others out there already, of course) that is blatantly illegal to use and thus cannot be anything more than a mild irritation to spammers.
  126. If only Grandma studied, she could be Ninja, too! by Gary+W.+Longsine · · Score: 1

    You are right! I shall retire off the proceeds from referring people to the spamassassion man page!
    If you can solve SPAM so easily with your customized SpamAssassin rules and your skills in proper care and feeding of the filters, then you could easily train a few disciples and charge $25,000 a week to fix the problem for each of the Fortune 500. Yes, you could get rich from your SpamAssassin rules and skills. You would do it for the first customer for free, and then there would be a line outside your door.

    SPAM is a real problem which has threatened to make email unusable. If we professionals don't acknowledge that this is a real problem and figure out how to fix it, email will become such an annoyance for people that they will stop using it. I submit that in fact this is already happening. Ordinary people who don't make their living in Information Technology are already abandoning email. Why? SPAM makes email a pain in their backside.

    More seriously, I'm not saying that I can solve the world's spam problem, just that a motivated person can make spam a non-issue for themselves.
    Yes, that's what you are saying. Unfortunately, this isn't a relevant point. Just because you, a Ninja, can walk safely through the streets of a crime-ridden neighborhood doesn't mean that this neighborhood would be safe for your grandmother, too. Your answer is the naive (or perhaps merely innocent) equivalent of "Grandma can be safe if only she too became a ninja!"

    Actually I already posted my config in reply to another comment, but more importantly you have to feed it properly.
    So, can your grandmother "properly feed" her baysean filter? (Thanks for posting your configuration. I'll take a peek at it, and I'm sure others will benefit. I'm not calling you a liar, I'm simply pointing out that your solution isn't scalable. It's not like there are not lots of smart people using the same tools to fix this problem. It's still a problem. Something is obviously not working.)

    There have been quite a few articles about this problem in the past couple of months. Here's one: Spam on the rise with new breeds Researchers say spam has risen significantly in recent months -- by as much as 80 percent
    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  127. Re:This is painfully obvious and hopelessly naive by Firefly1 · · Score: 1

    Its similar to a pretty interesting conceptual innovation in medicine...
    See also in this vein: professional, particularly military, aviators and their many checklists (sometimes referred to as 'plastic brains'). According to this article, several hospitals have seen this as something to learn from.
    --
    - White Knight of the Order of Mihoshi Enthusiasts
  128. Block tcp/25 by macdaddy · · Score: 1
    Frankly I see absolutely nothing wrong with a SP blocking outbound tcp/25 to all dynamically assigned customers. I run an ISP and I do this myself. We only permit outgoing tcp/25 to customers paying for a business circuit and to customers who have requested a static IP for another $5/month. All outgoing tcp/25 is blocked at the access edges. The only exceptions are for our static ranges and for SMTP to our ISP SMTP servers. The $5/month is enough to deter the person who always blindly requests a static IP even though they have absolutely no use for it whatsoever. It's not so expensive as to be cost prohibitive to someone with more technical knowledge and abilities. The ACLs on the edge all but eliminate spam from our netspace.

    Hell let me just give you some numbers. I'm terminating 760 ATM PVCs (DSL customers) on this router. It's rejected 359,093 outgoing tcp/25 flows since I last updated that ACL 1.5 months ago. Over here I have about 800 cable customers. It has rejected 4,217,900 outgoing tcp/25 flows in the same time frame. Over here I have a pair of routers for a dual-home CMTS with 411 customers on it. Between the 2 routers in 2 months time they've rejected 8,918,045 outgoing tcp/25 flows.

    Mind you these ACL counters only increment on flows, not individual packets. That's 13.5 million (say it with me again, 13.5 million) tcp/25 flows from less than 2000 customers that have been blocked by this simple, yet obviously effective, ACL. That's a lot of spam we've blocked and this is only a snapshot of a small window into our network. That's spam that would have ended up in your inbox. Ya'll can thank me later by buying me a beer at NANOG.

    Naysayers who bitch and moan about their ISP blocking tcp/25 which keeps them from running a poorly configured and ill-maintained SMTP server on a residential broadband connection need to get a grip on reality. Their ISP is acting responsibly. Their ISP is doing what it can to stem the tide of spam flowing from its networks. I'm not responsible for a given user's personal PC. I am responsible for making sure that their neighbor, another paying customer of mine that isn't spamming the world, gets the service they're paying for. If my unsecured spamming customer #1 causes us to get our entire ARIN allotment listed on an overly aggressive and irresponsible DNSBL (I'm not saying all; I'm only saying that a few are run by 12 year olds that hurt the rest of the anti-spamming community of which I'm a card-carrying member) which in turn is stuffed into a BGP feed and dropped by an idiot netadm somewhere else in the world then customer #2 is not getting their money's worth. I'll gladly kick out customer #1 to meet my SLAs with customers #2-#n. Unfortunately by that point it's too damn late. Customer #1 has caused me weeks of grief and had caused customers #2-#n to become unhappy with my services. The fix is to keep Customer #1 from inadvertently becoming a pain in the ass.

    If you want to run a SMTP server then rent a damn co-lo server or a virtual slice of one. Myself and other mail and netadms go out of our way to block tcp/25 traffic from any dynamically-assigned netblocks of our peer SPs. We willfully share this information with other SPs and we rarely have trouble getting it in return. If you want your mail to be received by a large percentage of the world then you'd better not be relying on a SMTP daemon you set up on your mother's PC. SMTP is only as reliable as the effort you put into making it so.

  129. NO! by macdaddy · · Score: 1

    This isn't a reasonable thing. Repeat after me people, the willy nilly free love days of the Internet ARE OVER. Running a SMTP server on your home PC is not a reasonable thing to do. All responsible ISPs will block outgoing tcp/25 to dynamically assigned residential customers. I do this. If you want to run a server then get yourself a 1U co-lo or a virtual slice of a server for $10/month. Stop being part of the problem. Stop running SMTP daemons on your mother's PC.

  130. Let me introduce Slashdot to a problem user by macdaddy · · Score: 1
    Ladies and gentlemen, allow me to introduce you to a person who's part of the problem. DrSkwid, please stand up and wave to the audience.

    Users like yourself are not desired by any ISP. You're a member of the elite and self-righteous groups of users we fondly call pain-in-the-ass users.

    We're not just blocking outbound tcp/25 to protect you. We're doing this to protect 99.999% of our userbase that doesn't abuse our services and stretch our networks to the extreme. Frankly we ISPs don't care about users like yourself. You increase our support costs. You bitch and moan about everything. You put up websites to flame your ISP because they happen to have an maintenance window when you wanted to play WoW through the wee hours of the morning. You bitch and moan because network congestion caused by other users like yourself adversely affect your Skype traffic, even though you won't pony up for a DSL with QoS.

    If you want to run a server then buy a damn server and rack in up in a co-lo where servers belong. Or buy a business connection because that's what your traffic level meet. If you want residential broadband then buy residential broadband. The two are mutually exclusive.

  131. I don't need no steenkin' introduction by DrSkwid · · Score: 2, Funny

    Thanks for you misguided rant, quite amusing.

    My ISP (and I mean mine, I'm a shareholder) doesn't give a flying fuck what I do with the bandwidth I paid for (and yes, I do pay). The fixed IP of my 2Mb ADSL suits my needs, and many of the needs of other business users we have as customers, extra QoS not required

    Get off your high horse and suck it's cock.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter