Slashdot Mirror


Lousy E-mail Filters Complicating Outlook Worms

Mar writes "FRISK Software founder Fridrik Skulason has issued an open letter in which he blames other anti-virus companies for much of the Sobig.F network load problems: 'If mail filters send out one message for every copy of Sobig.F received, they are in effect doubling the amount of traffic. This makes them a part of the problem, not a part of the solution.'"

461 comments

  1. But still less... by mindriot · · Score: 4, Interesting

    ...traffic than you'd have if the worm got to its target and continued spreading.

    1. Re:But still less... by nacturation · · Score: 5, Insightful

      ...traffic than you'd have if the worm got to its target and continued spreading.

      That's a lousy argument for obvious poor behavior on the part of anti-virus software. It's like saying every time the police catch a violent criminal, they should kick the ass of some random citizen. Hey, it may be annoying, but it's still less violence than you'd have if the criminal got to their target and acted violently.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    2. Re:But still less... by Hayzeus · · Score: 2, Insightful

      That's beside the point. The problem isn't that the mail blocking is objectionable. It's the idiotic reply messages that worsen traffic problems. The email can be blocked with the stupid "warning" being returned to a forged address.

    3. Re:But still less... by American+AC+in+Paris · · Score: 5, Insightful
      ...traffic than you'd have if the worm got to its target and continued spreading.

      I'm still getting about 200-300 "You sent a message with SoBig.F! Patch your computer immediately!" every day.

      Trouble is, I'm on a Mac. I couldn't be infected with SoBig.F if I wanted to.*

      Further trouble is, SoBig.F spoofs the FROM: field, so these messages invariably go to everybody except the schmuck with the infected box.

      So no, these messages hurt far more than they help.

      [* Pedant filter: I suppose I could buy Virtual PC or somesuch and install a vulnerable version of Windows. That'd probably do the trick.]

      --

      Obliteracy: Words with explosions

    4. Re:But still less... by aallan · · Score: 1

      Trouble is, I'm on a Mac. I couldn't be infected with SoBig.F if I wanted to...

      I'm on Linux, and I've had far more bounce messages telling me I've just sent an infected email than copies of SoBig-F, and my spam filter has caught well over 400 copies of SoBig-F now...

      Al.
      --
      The Daily ACK - Eclectic posts by yet another hacker
    5. Re:But still less... by Anonymous Coward · · Score: 2, Informative

      The downside is that the lusers are protected but those who keep their system in shape and don't click on every attachment become victims and can't even do anything about it. After 30000 SoBig.F related messages you learn that it is nearly impossible to filter bounces. They come in all languages, with or without headers. Some mention the worm, others don't because they're just "user unknown" bounces. My system is clean. The 900+ wormmails per day were easily filtered, but I had to sort through more than 100 bounces a day. To me, the bounces where the real problem.

    6. Re:But still less... by gi-tux · · Score: 2, Insightful

      And on top of that, some of them return the virus with the message. Therefore, it you don't have virus protection (which is stupid) and your address is forged on one, you might get a copy and also get infected.

      There are people out there that don't understand that email addresses are easy to forge. I had two people last night a church services comment about me sending them a virus. I never check email with anything except Linux at home and even at that I have virus scanning on and working to make sure. I also received a few messages bounced by corporate systems that included the virus within the message they sent me, to "notify me that I was infected". Glad I wasn't on Windows.

      --
      I have no sig, does anyone have one to spare?
    7. Re:But still less... by mindriot · · Score: 4, Insightful

      Of course you're right. The bounces are becoming a problem because most new worm variants fake the From: header anyway. The question would be, what percentage of total SoBig.F-related traffic comes from bounces? It might, of course, be as high as 50% if every message sent is bounced; but Frisk didn't really point out how much the Bounce problem contributed to the general worm traffic.

      I'd be happy if bounces in SoBig-like cases were reduced, but I find it a weak argument to blame the worm problem on anti-virus software without giving numbers of how much bounces actually added to the problem. (Well, it's another anti-virus software producer writing this statement, so this open letter could be considered a PR statement to some extent.)

      Somehow this also reminds me of those stupid Windows firewall products that by default alert you of every single stupid network packet...

    8. Re:But still less... by arivanov · · Score: 4, Insightful

      It is well known that the Sobig.F and many other viruses forge the sender address. These viruses are identified by the relevant filter product.

      Then, why on earth do you send a notification to an address that is known to be forged?

      The answer is simple - free advertising payed with your and my money. It is not stupidity. It is malice. An outright form of advertising a product by SPAM. I think that any Washington (or other state with antispam laws) resident should sue them for this.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    9. Re:But still less... by gl4ss · · Score: 2, Insightful

      it's just utterly stupid from the companies making the software, for crying out loud, most of the programs can tell about sobig.f that it forges it's address(have a flag for it in their virus db, so it wouldn't be much of a chore to add it to NOT send warning email to that forged address)!

      but i guess it's just a nice feature some phb's think that is cool.

      --
      world was created 5 seconds before this post as it is.
    10. Re:But still less... by mph · · Score: 4, Insightful
      Further trouble is, SoBig.F spoofs the FROM: field, so these messages invariably go to everybody except the schmuck with the infected box.
      Yeah, I got tons of those Virus Warnings. I haven't run Windows, or any MS software, since 1995.

      The worst part of it is that the antivirus software sending these messages knows that it's SoBig.F. Thus, it should also know that the virus forges the From: header, and that it's pointless to send out the warning message to that address.

      So thanks, antivirus programmers. Thanks for wasting my time instead of doing your job correctly. How long would have taken to add an extra if(){} to your code, and another boolean field to your virus database?

    11. Re:But still less... by The+Old+Burke · · Score: 0
      The reason they implemented the "warning feature" is because 1. It works and 2. At that time very few in any viruses at all used spoofing of eamail address.

      Therefor they should add dymanic warnings instead based on what type off virus that is detected. Wheter a virus spoofs the eamil adrres and adds afake address should be information "embedded" inside the virus detection files.

      As this:

      if Detected.Virus=Sobig.F(spoofing email adrress) then DO NOT SENT WARNING.

      else if Detected.Virus=Chernobyl(old-school virus without eamil spoofing) send warning.

      (Sucky coding, but you get the picture)
      Symantec should send me dime when they implements this in their next version.

      --
      Proud patriot and republican voter.
    12. Re:But still less... by John+Miles · · Score: 4, Insightful

      And on top of that, some of them return the virus with the message. Therefore, it you don't have virus protection (which is stupid) and your address is forged on one, you might get a copy and also get infected.

      <rant>

      That's what utterly astonished me during the recent SoBig.F infestation. When an undelivered mail message with an attachment bounces, the mail servers return not just the subject line, or the message text, but the attachment to the putative sender.

      Were the architects of the common Internet mail utilities just plain stupid? What other conclusion can possibly be drawn? Who taught these epsilon-minus lackwits to use a computer, and why? What else am I supposed to think when a mail gateway or server is designed to bounce hundreds of kilobytes worth of attached junk to someone who, by definition, already has the data (since, after all, it's not as if he or she is the one who fucking sent it the first place)? And when it's designed to do so via an untrustworthy return address courtesy of the nullwits who designed the SMTP protocol, no less?

      It is WAY past time to scrap the Internet's existing email infrastructure in favor of something designed by actual engineers. What we have now is a giant, virtual Petri dish better suited for the cultivation of worms, viruses and spam than for communication between legitimate users.

      </rant>

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    13. Re:But still less... by Hayzeus · · Score: 1

      I think this is true in some cases. After reading this on /., though, I've noticed that around 1/2 of the bounces (at least the ones I'm seeing), are either very generic, or have very little information about the scanner itself -- perhaps just a name (and not even a company name). I still think that most of this is just lameness, both on the part of the AV vendors AND and the part of the admins responsible for configurting them.

    14. Re:But still less... by Lars+T. · · Score: 3, Funny

      Since many even return the offending atachment - they are knowingly spreading the virus. Which makes them terrorists.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    15. Re:But still less... by LiquidCoooled · · Score: 2, Interesting

      Shouldn't it be handled one step further upstream - ie when the mail is being transmitted initially.
      In the same way that the server indicates error messages regarding destination addresses or transmission errors etc, couldnt the virus checker scan the data at that point, and only allow the data in if its clean?

      --
      liqbase :: faster than paper
    16. Re:But still less... by afidel · · Score: 0

      Ain't that the truth, for my home account in the last 3.5 months I have recieved 192 legit emails. By contrast I have recieve 421 spam's, viruses and other unwanted email, in the last 11 DAYS.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    17. Re:But still less... by Anonymous Coward · · Score: 0

      How did the virus get your email address? Some random person on the internet with your address in his or her cache? Possible. However, it is more probable that it is someone you know. If you are getting a huge volume of these messages then doesn't it seem likely that someone you know is infected and that maybe, just maybe, you being the ubergeek that you must be to post on slashdot should do something about it?

    18. Re:But still less... by pboulang · · Score: 2, Insightful
      Who are terrorists? The AV companies or the people that don't know how to configure the software?

      Terrorism has INTENT. The behavior you are referring to I think may be better classified as sociopathic.

      I am only offended by that comment by today's date. I'm sure I will get over it tomorrow.

      --

      This comment is guaranteed*

      *not guaranteed

    19. Re:But still less... by dspfreak · · Score: 2, Insightful
      About as long as it took you to write that comment. Hmmm, too bad that stuff isn't open source, or it would be fixed by now.

      --
      "Tolerance is the virtue of the man without convictions." -- G. K. Chesterton
    20. Re:But still less... by WWWWolf · · Score: 1
      It's like saying every time the police catch a violent criminal, they should kick the ass of some random citizen. Hey, it may be annoying, but it's still less violence than you'd have if the criminal got to their target and acted violently.

      Except that in case of Sobig, sender name is spoofed so e-mail is always sent to a wrong address.

      So, the annoying police analogy would be that the police would be kicking random bystanders constantly - somewhat annoying, but at least they catch real criminals too if they're not busy kicking the bystanders.

    21. Re:But still less... by isomeme · · Score: 4, Insightful

      It can actually exceed 50% in some scenarios. For example:

      1. Trojan fakes from address of 'joe@foo.com', sends email to 'sue@bar.com' with infected attachment.

      2. Filter at 'bar.com' detects infected attachment, sends rejection email from 'sue@bar.com' to 'joe@foo.com'.

      3. It turns out that 'joe@foo.com' is no longer a valid address. 'foo.com' mail agent sends a delivery failure email to 'sue@bar.com'.

      Thus we get two pointless administrative emails generated by a single infected email.

      I am seeing this happening quite commonly, by the way.

      --
      When all you have is a hammer, everything looks like a skull.
    22. Re:But still less... by DrPepper · · Score: 1
      Unfortunately, no real solution is suggested:

      1. Have the mail filter properly distinguish between worms that falsify the "From:" address and ones that do not and only send a warning message when the "From:" address is likely to be genuine.


      I've seen a lot of discussion on various mailing lists concerning that, but it seems to generally be agreed that this isn't really feasible - especially with emails from some of the large providers. It simply isn't possible to say whether a message legitimately came from the email address stated at the moment. And no, the sending mail server and/or domain gives no real clue.

      2. Do not send the alerts at all.


      Unfortunately this means that the message gets dropped and you end up with lots of aggrieved people who have believe their messages are getting delivered, when they aren't.

      I don't believe the numbers of bounces are really that huge a problem compared with the amount of other spam floating around (*ducks*). Perhaps the language should just be modifed to state that a message purporting to come from the senders address was undeliverable. Otherwise, I can't really see a decent solution.
    23. Re:But still less... by dosius · · Score: 1

      Obvious viruses and messages with obviously faked senders should be rejected outright by the SMTP server or by a passthrough further upstream.

      Rejection
      Message: YOU FAIL IT!
      Reason: Mail header is forged

      and just pipe the mail to /dev/null.

      -uao.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    24. Re:But still less... by Anonymous Coward · · Score: 1, Informative

      The rationale behind including the attachment with the bounce is that the server which rejects the mail is doing so because of the mail content, not due to a protocol error. The sender has no reason to believe that the email has not been sent correctly. In the early days of the internet, an email got through or it came back to the sender. It "never" got lost. So it is very possible that the sender deletes the file after sending it, for example if it is not in the form he usually keeps on his computer (example: a reduced version of a high res image for a recipient with a slow connection, or other "dynamic" data). Returning the attachment was a sensible concept at the time, but nowadays it's just wasteful. People don't expect the same level of reliability from email anymore - with reason.

    25. Re:But still less... by AKnightCowboy · · Score: 4, Funny
      Were the architects of the common Internet mail utilities just plain stupid? What other conclusion can possibly be drawn? Who taught these epsilon-minus lackwits to use a computer, and why?

      Why don't you go ask him:

      SIMPLE MAIL TRANSFER PROTOCOL
      Jonathan B. Postel
      August 1982
      Information Sciences Institute
      University of Southern California
      4676 Admiralty Way
      Marina del Rey, California 90291
      (213) 822-1511

      I'm sure many of us would love it if you met up with him and had a spirited debate about the issue very soon.

      Did you ever stop to think that many of the Internet's protocols were designed when there were no fuckwits running operating systems that are a virtual "petri dish" for viruses and worms?

    26. Re:But still less... by dosius · · Score: 1

      A friend of mine in my chatroom said his mother didn't believe him when he had an e-mail saying he sent someone a copy of SoBig.F.

      I explained how e-mails could be spoofed, and also mentioned how the FreeDOS list got flooded with SoBig viruses. (I also said that I have gotten spams claiming to come from my own e-mail address!)

      The e-mail addies I use most are 3 webmail addresses. One of them gets spammed the hell out of...that's the one you see.

      -uso.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    27. Re:But still less... by perlchild · · Score: 1

      mailscanner one of the nice open source free scanning engines has a feature like that, called silent delete, for spoofing viruses I believe.

    28. Re:But still less... by Anonymous Coward · · Score: 0

      It's going to be tough to have that debate with Jon, as he passed away a number of years ago. Damn shame too, because Jon would have mopped the floor with him in a debate...

    29. Re:But still less... by angst_ridden_hipster · · Score: 1

      Um, you'll have trouble discussing protocols with Jon unless you've got the services of a good Medium (hey, and maybe a good protocol!)

      Jon passed away in 1998.

      --
      Eloi, Eloi, lema sabachtani?
      www.fogbound.net
    30. Re:But still less... by flymolo · · Score: 1

      The worst I've seen is:
      2 accounts with auto-replies looping infinitely because one received a virus warning because of a forged from header.

      Also annoying is when the forged from address is a mailing list and the whole list gets the virus warning.

      --
      "Sometimes it's hard to tell the dancer from the dance." --Corwin Of Amber in CoC
    31. Re:But still less... by isomeme · · Score: 1

      Yeah, I've seen both of those, too. Autorepliers and mailing lists open up vast new landscapes of misconfiguration-generated pain. :P

      --
      When all you have is a hammer, everything looks like a skull.
    32. Re:But still less... by LiquidCoooled · · Score: 3, Interesting

      I would not want to ban based upon email address, there would be no way to identify the fake from the real.
      No, the AV companies need to start working on an effecient mailserver (or simply hook into the existing ones), and prevent sucessful transmission of viral contents.

      Because it would be on an upstream server away from the users, Virus definition files will be updated quicker, and protection will be automatic.

      The problem then becomes one of localised ISP traffic only, and this can be cured by the ISP themselves. Another benfit of this, the ISP can send a single "You are infected" mail to the Account holder of the source IP.
      For Unknown IP addresses - simply block relay access :)

      --
      liqbase :: faster than paper
    33. Re:But still less... by jovlinger · · Score: 1

      ... but with partial headers, so there is no way for me to figure out which of my friends has been compromised.

      that's what gets me. Either don't bounce, or bounce with enough information to fix the problem.

    34. Re:But still less... by Ruie · · Score: 1
      Actually there is a good reason to send these notification e-mails: it could be that a legitimate attachment was misidentified as a virus.

      In this case I want the sender to receive automated reply so they know that something is amiss.

      And, of course, people who send .doc files as attachments are more likely to assume that all e-mail they send out is eventually read and that none of it could be filtered out.


      Thus, the notification e-mails serve a purpose, they are pretty easy to filter out and, if done properly, they are a lot shorter than the virus e-mail and add negligible load.

    35. Re:But still less... by linkjunkie · · Score: 1

      We recieved an automated bouce that included a copy of virus.
      (It sent the original email as an attachment.)
      Makes me wonder how much of an echo effect there is.

    36. Re:But still less... by John+Miles · · Score: 2, Interesting

      Did you ever stop to think that many of the Internet's protocols were designed when there were no fuckwits running operating systems that are a virtual "petri dish" for viruses and worms?

      (Shrug) Bad engineering is bad engineering. Postel's accomplishments were legion, but in the email department, he and his colleagues dropped the ball big-time. There's just no room to defend the decisions that were made.

      The minute the Internet showed signs of growing out of the obscure DARPA-funded labs where it was born, the engineers should have started paying attention to security and authentication issues. It would not exactly have been hard to fix SMTP by disallowing open relays and including a trivial sender-authentication mechanism to prevent forged headers, but now it's probably too late. A couple dozen lines of C code written between coffee breaks at USC would have made all the difference.

      That being said, the bouncing-attachment idiocy most likely has more to do with the default configurations of popular server-side virus filter packages than with anything Postel was involved with. The common denominator is that people with a great deal of responsibility in the Internet engineering field seemed to have taken leave of their senses at a few critical junctures with no one around to say "Hey, wait, maybe that's not a smart thing to do."

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    37. Re:But still less... by Anonymous Coward · · Score: 1, Informative

      It's an efficiency problem: In order to stop the mails at the SMTP level, the scanner has to work while the connection is kept open. For a high-profile email server that's an unacceptable delay because it increases the number of open sockets at a time. Scanning "after the fact" doesn't keep the TCP connections open, so it's preferred. On the other hand, if the virus scanner is going to send out notifications, that may as well not be the tradeoff to make.

    38. Re:But still less... by Czmyt · · Score: 1

      I agree with the other person who replied: the software is just lame. It was designed during a time when viruses piggy backed on legitimate files and there might have been some small amount of merit to informing the sender that they sent a virus. With the latest round of viruses, there is absolutely no point to sending a bounce message back to the sender, because 1) the from address is forged, and 2) the messages are pure auto-generated virus with absolutely no legitimate content.

    39. Re:But still less... by John+Miles · · Score: 1

      Did you ever stop to think that many of the Internet's protocols were designed when there were no fuckwits running operating systems that are a virtual "petri dish" for viruses and worms?

      Oh, and by the way, while we're waiting for Jon Postel to come to the phone, let's track down a kid named Robert Morris and get his thoughts on that particular point. I don't believe Morris was a big Windows user, but I understand he knew his way around sendmail.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    40. Re:But still less... by Anonymous Coward · · Score: 0

      the other big reason virus bounces are a problem is because they are virtually impossible to block because of the variety

      as an exaple i am on the mainling list code-com@undernet.org

      thier blocking policys prevented a single virus mail comeing through the list

      but virus bounces that was a totally different matter

    41. Re:But still less... by John+Miles · · Score: 1

      Returning the attachment was a sensible concept at the time, but nowadays it's just wasteful

      I still wouldn't buy that. Think in terms of the value of the resources used to send (and bounce) a particular amount of Internet traffic versus the value of the same amount of storage space on the originating machine. If anything, back in the days when v.32bis modems hadn't even been invented, it made less sense to rely on the 'Net to return your bounced attachment safely to you than it does today.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    42. Re:But still less... by Havokmon · · Score: 1
      Were the architects of the common Internet mail utilities just plain stupid?

      I run Qmail-Scanner. Not only does it's "You sent a virus here" message only include the first 50 lines or so of the original message, but I can turn off those notifications for any criteria I wish.

      I now respond to 'You sent me a virus' emails with a not-so-kind reply to the postmaster encouraging them to turn off notifications for KNOWN spoofed FROM addresses.

      It's been weeks guys, take a free product, and front-end your commercial POS.

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    43. Re:But still less... by jabuzz · · Score: 1

      I've seen a lot of discussion on various mailing lists concerning that, but it seems to generally be agreed that this isn't really feasible - especially with emails from some of the large providers. It simply isn't possible to say whether a message legitimately came from the email address stated at the moment. And no, the sending mail server and/or domain gives no real clue.

      This shows breath taking level of cluelessness. The point its that when the virus scanner identifies the virus, a flag in the virus database says Sobig.F this uses forged email headers don't send out a warning. It is actually less work for the email server. There is no need to determine if the sender is valid, you work on the basis that the virus is known to use forged headers.

      If you don't believe the bounces are a problem you are have not suffered from them. There are unfortunate soles like myself that are getting hundreds of bogus bounces a day. What is worse it is several orders of magnitude harder to filter these than the actual virus, which is easy. When your email becomes almost unusable you will take a different attitude to these things.

    44. Re:But still less... by mobiGeek · · Score: 1
      Terrorism has INTENT.

      Someone(s) set the default behaviours. Those are your terrorists.

      --

      ...Beware the IDEs of Microsoft...

    45. Re:But still less... by Satan+Dumpling · · Score: 1

      To me it seems pretty simple. Virus software knows what virus it caught. Therefore it should know whether the virus forges the "from" or not. So bounce and warn the sender if it's a non-forging virus. Do NOT bounce if it's a forging virus.

    46. Re:But still less... by Anonymous Coward · · Score: 0
      It would not exactly have been hard to fix SMTP by disallowing open relays ...

      In the days before DNS, sometimes the only way to get mail from one machine to another was through an open relay. Your hosts file could not contain every address out there, and could quickly become out of date. Not to mention mail that had to cross network boundaries, such as from the internet to bitnet or vice versa.


    47. Re:But still less... by Anonymous Coward · · Score: 0

      Attachments were rare and smaller (and people got flamed for not using FTP). Fewer messages bounced. The system was designed to avoid data-loss. Local storage may be cheaper, but it is much less convenient: The sender has to receive confirmation before he can delete the file, and since the confirmation he gets from the email-server isn't valid for attachments anymore, he has to get manual confirmation.

    48. Re:But still less... by SSpade · · Score: 2, Interesting

      So thanks, antivirus programmers. Thanks for wasting my time instead of doing your job correctly. How long would have taken to add an extra if(){} to your code, and another boolean field to your virus database?

      They are doing their job correctly. They're using spam (email? check. bulk? check. unsolicited? check. heck, commercial? check) to advertise their virus filtering products.

      They're violating various state anti-spam laws, so there's one obvious way to encourage them to stop spamming.

    49. Re:But still less... by Anonymous Coward · · Score: 0

      In the days before DNS, sometimes the only way to get mail from one machine to another was through an open relay. Your hosts file could not contain every address out there, and could quickly become out of date. Not to mention mail that had to cross network boundaries, such as from the internet to bitnet or vice versa.

      Very true. So why are we still using all that old shit, now that DNS is old enough to get into R-rated movies without an accompanying parent or adult guardian?

    50. Re:But still less... by LiquidCoooled · · Score: 1

      My realtime virus scanner manages to scan files in realtime. Back in days of old, I wouldnt run a scanner because of the sluggishness, now they are an accepted, invisible filter to the filesystem.

      I realise this is a server and its going flatout at busy periods, but surely this is where multiprocessors help.

      --
      liqbase :: faster than paper
    51. Re:But still less... by LiquidCoooled · · Score: 1

      Excellent, thank you - I'm gonna get my head round this tomorrow and see about uploading it to our testserver :)

      --
      liqbase :: faster than paper
    52. Re:But still less... by Brendan+Byrd · · Score: 1

      Somebody needs to take the One Question Test.

    53. Re:But still less... by AKnightCowboy · · Score: 1
      Jon passed away in 1998.

      Yes he did. Now reread my message with that in mind.

    54. Re:But still less... by Brendan+Byrd · · Score: 1

      It's not just known that Sobig.* uses forged headers; it ALWAYS uses forged headers. I send my own bounce message to idiot sysadmins, telling them that their system creates a problem just as big as the virus.

    55. Re:But still less... by Anonymous Coward · · Score: 0

      It's an efficiency problem: In order to stop the mails at the SMTP level, the scanner has to work while the connection is kept open

      Well, SMTP itself shouldn't be in the virus-scanning business. The "S" stands for Simple, after all, and that certainly doesn't include content validation.

      However, SMTP most certainly should be in the sender-authentication business. While the connection is still open, SMTP should send a packet back to the transmitting host saying, "Are you talking to me?" If the originating host doesn't answer, then the header is assumed to be forged and the message is dumped unceremoniously into the bit bucket.

      But I guess that would have broken the whole Internet-over-carrier-pigeon RFC, huh.

    56. Re:But still less... by statusbar · · Score: 1

      Not only that, but I've had one email smtp server email me to say that any further email from me will be blocked to that domain! I run linux and never sent the spam - the headers in the returned email show it originated in brazil - but their anti-spam software actually trusts the From: header! insane!

      --jeff++

      --
      ipv6 is my vpn
    57. Re:But still less... by DrPepper · · Score: 1

      10 out of 10 for the theory, but nil-points for putting this into practice...

      1. Sobig/F spread as a .pif attachment. Nowadays if you want to stay ahead of viruses, you configure your mail server to reject these before virus scanning. The anti-virus companies themselves have admitted that they can't keep their definitions up-to-date fast enough to cope with the speed with which this sort of thing spreads. It's only going to get worse.

      2. It's not unusual for the reject to be done at SMTP time (with appropriate message). The bounce will hence be generated by the last mail relay with that message, not knowing what it's really doing. Whilst there isn't always a previous relay, it's not always the case and most don't do virus scanning anyway.

      I'd really like to see a workable solution - unfortunately this does seem to be tending towards just dropping emails on the floor, or stripping out the payload and letting the email continue on.

    58. Re:But still less... by m_frankie_h · · Score: 1

      The first server that sees a Sobig message is the MX it is being delivered to.

      Upstream blocking is completely irrelevant.

    59. Re:But still less... by isomeme · · Score: 2, Informative

      Good post, overall, but I have to object to your phrase "the nullwits who designed the SMTP protocol". SMTP was designed at a time when the nascent internet was more or less a research preserve, all users of which were cooperative and well-intentioned. SMTP uses what I call "Moria security", for reasons which will be obvious to Tolkien fans.

      SMTP lacks meaningful authentication features for the same reasons that TCP/IP lacks such features; they weren't needed at the time, and better to get something working out there and doing good than to sit on it while you build in design features that might possibly someday become useful.

      A dirt path is a perfectly useful way for a few hikers to climb a hill. When a stream of passenger cars start using that path and a few of them lose their oil pans, don't blame the people who created the path.

      --
      When all you have is a hammer, everything looks like a skull.
    60. Re:But still less... by joebubba · · Score: 1
      Postini got smart real quick and added virus notification options after the first wave of Sobig. You can change it to be notified once per day, or not at all when it traps a virus (instead of every single time).

      God Bless Postini.

    61. Re:But still less... by isomeme · · Score: 1
      Trouble is, I'm on a Mac. I couldn't be infected with SoBig.F if I wanted to.
      Will you Mac users ever stop whining about porting delays?
      --
      When all you have is a hammer, everything looks like a skull.
    62. Re:But still less... by Lars+T. · · Score: 1
      There is no good reason to send sombody something you think is harmful. If you write software that does it - even if a third party has to activate that "feature" - you sure as hell have the intent to do that.

      As for calling it terrorism, tell it to Ashcroft. Interesting that Ashcroft mentioned computer viruses in conection with "power grids, power generation".

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    63. Re:But still less... by John+Miles · · Score: 1

      You're right; there's only so much blame we can lay at the feet of the Original Implementers of things like SMTP. And (as I mentioned in another post) I'm not blaming SMTP in particular for the lameness of SoBig.F bounces.

      But at some point, the Garden-of-Eden argument loses its steam. Someone had to stand idly by and let that stream of passenger cars onto that dirt path without thinking ahead far enough to warn them about the bridge up ahead with its 500-pound load limit and resident troll encampment. Or to stretch the analogy even further past its breaking point: like the doped-up monkeys in "28 Days Later," SMTP and Sendmail should never have been released from their cages in the IT equivalent of a Level 3-biohazard research lab.

      We're going to have to deal with this stuff sooner or later. I'm sure Jon Postel was a great guy and all, but so is Woz, and we've managed to get past the Apple I.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    64. Re:But still less... by richard_willey · · Score: 1

      that was the beauty of the initial post
      Droll way to tell someone to drop dead
      "Spirited" discussion, indeed

    65. Re:But still less... by S.Lemmon · · Score: 1

      Nice statement - if it weren't completely false.

      Most of the hundreds of bounces I get a day *specifically* say they detected Sobig-F. Now, how could they know that if what you say is true? If they know enough to put the virus' name in the email, they should know enough not to send such a pointless message in the first place. Sobig-F never uses a valid from address.

    66. Re:But still less... by S.Lemmon · · Score: 1

      They are actually very hard to filter - they can come in all kinds of different formats, with all kinds of different text. There's no commonality to filter on.

      The worst to detect are the bounces from auto/vacation replies and the like since they can contain anything. The crud sent out by AV products, at least usually includes the word "Sobig-f" somewhere in the mail (all the more reason they have no excuse for sending it to begin with)

    67. Re:But still less... by S.Lemmon · · Score: 1

      It's worst of course if you have a public email address - stuff like software support, mailing lists and public contact addresses.

    68. Re:But still less... by pboulang · · Score: 1

      No, I think it is perfectly normal for a clueless person to make a configuration without thinking ten steps down the road (or even two) what the ramifications are. Terrorism is too strong a word for that.

      --

      This comment is guaranteed*

      *not guaranteed

    69. Re:But still less... by pboulang · · Score: 1
      And the people that sell bullets to cops have the intent of them being fired at people. The issue is that the original model of notifying the sender worked and that AV vendors haven't bothered to update their models. Their code is being exploited, not enabling. Somebody said hey, I can use this behavior to my advantage.

      *sigh* I really hate Ashcroft and the whole Bush administration. I just heard on the radio that 7/10 Americans think that Iraq was involved in the 9/11 hijackings. Ashcroft hinting that hackers caused the power grid is reprehensible.

      --

      This comment is guaranteed*

      *not guaranteed

    70. Re:But still less... by SharpFang · · Score: 1

      it's dumb. Why on earth would I buy an antivirus program that LIES that I had sent a virus!? I know this virus wasn't from me, I know the "warning" is all wrong, I'll buy any antivirus but that one!

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    71. Re:But still less... by Anonymous Coward · · Score: 0

      Or even better (and when I say better I mean worse, of course), worm fakes From address as big_mailing_list@foobar.com and everyone gets their very own copy of the bounce/delivery failure. I get this sort of thing addressed to my research group at university - only about 20 people but this sort of thing has the capacity to cause carnage

    72. Re:But still less... by Anonymous Coward · · Score: 0

      I hate to say it, but this is at least as much a stupid administrator problem as a stupid AV software problem.

      Most AV packages have a switch as to whether to notify the sender. The default for ours is OFF.

    73. Re:But still less... by jabuzz · · Score: 1

      Except when the ISP has it's routers set to force
      all outgoing port 25 traffic through it's mail servers. At least one large ISP in the U.K. does this. I saw hundreds of delivery failure reports of Sobig.F because of this.

    74. Re:But still less... by Lars+T. · · Score: 1
      Their code is not "being exploited", it still does exactly what they intended. It sends "back" an attachment they think contains a virus. I don't know what bad reason(s) they have, but like I said, there is no good one.

      The fact that they simply couldn't imagine that the From: header could be forged (yeah, right, where have they been the last years, this was hardly the first virus to do so, let alone single assholes doing it by hand) doesn't excuse that. Let's assume for a moment that the header isn't false.

      The virus scanner finds something suspicious - OK. Blocking or reporting it to the user - OK. Reporting it to the original sender - OK. Sending him back the attachment - what for? Isn't the name of the attachment together with the email headers enough to identify the infected file?

      So why send the file back? Punitive mailbombing? Childish, and when only sending it once also inefective. To test wether the sender has working virus detection? To make sure he gets infected again? To generate traffic because you have shares in ISPs or backbone providers?

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

  2. Stupid Bounce by crayiii · · Score: 3, Redundant

    After so many viri's that fake return to headers it's stupid to continue responding to them. No I didn't read the article...

    1. Re:Stupid Bounce by Anonymous Coward · · Score: 0

      worse. s/viri's/viruses . Two grammatical errors in one word.

      The Latin plural of virus is virus. Apparatus is the same way. It's all a matter of whether it's a short or long u.

      Otherwise, yes, the grandparent is dead on.

    2. Re:Stupid Bounce by Anonymous Coward · · Score: 0

      After so many viri's that fake return to headers it's stupid to continue responding to them.

      Thank you, Captain Obvious, for regurgitating the article summary.

    3. Re:Stupid Bounce by Anonymous Coward · · Score: 0

      The -us ending of virus suggests it may fall into the second declension. Nominative plural ending of 2nd D. nouns and adjectives in Latin is -i. If virus is 2nd d masculine as its ending suggests, its nominative plural form would be viri. Although a look at this page on the word virus suggests that it may be of fourth declension, in which case the parent post would be correct: virus (with a long u). It goes on to argue that perhaps the word virus was never used in plural because the noun itself already refers to a group of things.

  3. Yes, virus bounces suck by Anonymous Coward · · Score: 3, Insightful

    The email bounce is nearly dead now. Between spam and viruses faking the from and reply-to headers, it's become almost a menace. I got nearly as many bounces as I did sobig messages.

    1. Re:Yes, virus bounces suck by i.r.id10t · · Score: 2, Insightful

      I actually got more bounce messages than sobigs... 10 messages saying sobig spoofed my addy as the sender, and no sobigs (we got good email admins here).

      --
      Don't blame me, I voted for Kodos
    2. Re:Yes, virus bounces suck by realdpk · · Score: 4, Insightful

      The bounces from the anti-virus software programs is pretty damned close to spam. Close enough that it gets their name out there, but not close enough that they'd actually be pinned about it except by the most self-righteous of the anti-spammers.

    3. Re:Yes, virus bounces suck by Xzzy · · Score: 4, Funny

      I must have really smart friends, because I didn't get a single bounce! /preen

      Or maybe I just have no friends. /sigh

    4. Re:Yes, virus bounces suck by i.r.id10t · · Score: 2, Funny

      Same boat... do I get happy because no one is sending the virus to me, or do I get depressed because I'm not in anyones contact list?

      --
      Don't blame me, I voted for Kodos
    5. Re:Yes, virus bounces suck by Jucius+Maximus · · Score: 2, Insightful
      "The email bounce is nearly dead now. Between spam and viruses faking the from and reply-to headers, it's become almost a menace. I got nearly as many bounces as I did sobig messages."

      On my main account, I got exactly 0 sobig bounces and 0 actual sobig messages. This applies for all versions of sobig. (Only the competent get access to my real address.)

      On my main 'spam address' however, it got about a 10:1 ratio of bounces to sobig messages. I guess a lot of spammers got infected and since they have a lot of e-mail addresses for spam purposes on their systems, a number of sobig messages went out with my address on them.

    6. Re:Yes, virus bounces suck by Anonymous Coward · · Score: 0

      From my understanding, the virus scanned browser caches to get email addresses, too. This is how some of my spamtrap email addresses ended up getting hit with the virus.

    7. Re:Yes, virus bounces suck by MegaFur · · Score: 1

      My opinion? Be happy. Lotsa people kinda suck once you get to know 'em. Anti-social is the way ta be! :-)

      --
      Furry cows moo and decompress.
    8. Re:Yes, virus bounces suck by AnotherBlackHat · · Score: 3, Insightful

      The bounces from the anti-virus software programs is pretty damned close to spam.


      Not just close - they meet most of the definitions of "spam" that I've heard;

      They're excessive unwanted emails.

      They're unsolicited bulk.

      They're mass mailings from a stranger.

      They're sent without consent.

      They're commerical (they're an ad for the anti-virus software that sends them.)

      -- this is not a .sig

  4. How come we even get them? by TerryAtWork · · Score: 4, Interesting

    This is completely stoppable at the ISP level. I received over 1,000 SoBig.F messages, not one of which had to go through!

    --
    It's Christmas everyday with BitTorrent.
    1. Re:How come we even get them? by stratjakt · · Score: 0

      I'd rather they let them through than to know my ISP is sniffing all my incoming/outgoing mail.

      But that's just me.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:How come we even get them? by Anonymous Coward · · Score: 0

      They don't need to "sniff" anything. You can reject sobig based on SMTP behavior since it has it's own internal server.

    3. Re:How come we even get them? by Anonymous Coward · · Score: 0

      This is completely stoppable at the ISP level.

      Really?

      If the ISP allows port 25 incomming, how does the ISP stop the mail-based worms run on individuals hosting their own mail?

      Given the $10+ cost per mail box for anti-virus, who will pay that extra cost? Will *YOU* pay $10+ per mailbox per year extra?

    4. Re:How come we even get them? by TerryAtWork · · Score: 1

      I don't think it's violating our privacy to scan our email for virii.

      Unless your email is encrypted your privacy is an illusion anyway.

      --
      It's Christmas everyday with BitTorrent.
    5. Re:How come we even get them? by Anonymous Coward · · Score: 0

      Yes, the ISP can stop viruses, and I think they should.

      Microsoft is giving a very good example here by scanning all of Hotmail's e-mails for viruses. It saves people from a lot of problems, and no, Microsoft doesn't have to charge for it. And the other ISPs won't have to charge for this either, considering that their e-mail server load will be much lighter if viruses can't use e-mail to spread!

      Why can't all the other ISPs do the same?

    6. Re:How come we even get them? by Tenareth · · Score: 1

      I would never want my ISP making decisions for me... That's not what I pay them for.

      If you want someone making all your decisions, use AOL or MSN.

      ISP is just that, Internet Service Provider. Not a nanny.

      --
      This sig is the express property of someone.
    7. Re:How come we even get them? by Anonymous Coward · · Score: 1, Informative

      SoBig.F had an SMTP "signature" which was different from normal MTAs, so it was recognizable and could have been rejected without affecting other direct-to-MX applications. This deviation obviously isn't necessary, so the next worm may not be stoppable as early in the processing chain as SoBig.F was.

    8. Re:How come we even get them? by ConceptJunkie · · Score: 2, Interesting

      My ISP offers Postini, which is a pretty decent spam filter, for free. Therefore the 20,000 or so SoBig virus and related crap got stopped before it reached the mail server.

      Of course, the folks at Postini have failed to take Microsoft's abysmal software into account: You can view/delete quarantied spam up to 200 at a time, but viruses must be deleted 10 at a time. Thpthpthpthpthpptt!

      Microsoft: Creating the most effective virus development tools for over 10 years!

      --
      You are in a maze of twisty little passages, all alike.
    9. Re:How come we even get them? by Anonymous Coward · · Score: 0

      I think they should implement this feature, because it will benefit the unknowing people who execute the viruses, and if those people are not infected, the virus can't spread and annoy others either.

      In all these years, I've never received a non-malicious executable through email. It cloggs up bandwidth, as you're forced to download it. It's much better to provide a link to the file, which is what people with good intentions do.

      And if you seriously want to receive viruses, because it's part of your masochistic nature or because you are t33kid and you want to modify it... then maybe the possibility to "opt-out" should be considered. But turn it on by default!!!

    10. Re:How come we even get them? by ajs · · Score: 2, Insightful

      1. The world isn't quite that authroitarian.
      2. Your desire to have people behave politely doesn't override the general need to have the Internet remain an open exchange of packets between peers.
      3. What's an ISP? What's a customer? Should UUNet filter mail coming from their peers? Should a University filter mail coming from its own dekstops? What about labs that have their own Internet presence, but are part of the University? What about multi-homed businesses?

      I get a slew of these messages, and I have to admit to not having the time to solve the problem, but it's easily solved, if a monumental social engineering problem.

      What you need to do is this: first, get everyone to agree that they need to use SMTP/TLS. Second, get everyone to agree to get a key that's signed by a CA. Notice I didn't say "ISPs" above... that's because not everyone relates to their upstream in the same way, and some people (big Universities for example) tend to peer with multiple providers.

      Once everyone has a CA-signed key for their TLS-only mail then we can kill this sort of thing, dead. You send spam, you get axed. You send spam from multiple certs owned by the same entity, that entity gets axed. You send spam from multiple certs owned by multiple entities with the same CA, that CA gets axed.

      Apply SpamAssassin-like weighting to this process (weighting each key and entity and CA based on frequency of good or bad mail) and you quickly evolve a system of personal and community reputation that lets us get back to business without hurting those who don't deserve to be hurt (e.g. you might use a bad CA and work for a bad company, but if your key is never used for spam, you will evolved a good reputation over time).

      The same is true of viruses, it's just slightly more important to track individual sender keys (which will reprsent homes, corporate divisions and whatever other units make sense for you to create a unique mail server) when it comes to viruses. Databases of keys will have to be huge, but they can be distributed on various useful boundaries in the same way as DNS (e.g. by CA and then by organization).

      We'll get there, it's just that the pain threshold has to increase to the point that we all nod our heads and say, "I'm shutting off non-TLS now".

      I already run TLS on my server, how about you?

    11. Re:How come we even get them? by Anonymous Coward · · Score: 0

      So, if the plural or "virus" is "virii", then I guess the plural of "radius" is "radiii".

      The plural of 'virus' is 'viruses' (or if you're using latin, you could say 'viri' although that would be confusing, since 'viri' is also the plural form of 'man' (please no feminist jokes here)). The plural of 'radius' is 'radiuses' or 'radii'.

    12. Re:How come we even get them? by Anonymous Coward · · Score: 0

      I've started using the term "wormii" too. :D

      So now we have:
      - virii
      - radii
      - penii
      - wormii

    13. Re:How come we even get them? by lseltzer · · Score: 5, Interesting

      My latest column deals with this too. I got a lot of e-mail in response from ISPs talking about how it would be difficult/expensive to implement and that it would violate customer privacy. One said it would be a HIPAA violation. My own ISP (Speakeasy.net) virus-scans all e-mail that goes through their servers; is that a HIPAA violation? A lot of them are also scared of losing customers after offending them by blocking their outbound port 25 access, but does an ISP really want business from someone infected with Sobig?

      It is true that since Sobig uses its own SMTP server the ISP would have to do the monitoring via a port 25 monitor. I'm not completely sure how difficult/expensive this would be to implement on a large scale, but there's an opportunity for someone who comes up with a cheap solution. I suppose it could be part of a general IDS, but it needs to be something price-accessible to an ISP.

      Larry Seltzer
      Security Editor, eWEEK.com
      http://security.eweek.com/

    14. Re:How come we even get them? by AnotherBlackHat · · Score: 1

      I already run TLS on my server, how about you?


      I can't.

      TLS doesn't support multiple domains being hosted on the same IP.

      So you either need to add a "fix TLS" step,
      or use a completely different protocol,
      or wait for IPv6 (and fix SMTP and TLS to be IPv6 compatibile),
      or give up on the 5-10% of the smtp servers supporting multiple domains.

      Personally, I vote for "use a different protocol".

      -- this is not a .sig
    15. Re:How come we even get them? by Anonymous Coward · · Score: 0

      First, there's the obvious problem: CA based schemes are centralized schemes, which many consider a bad choice for a variety of political, economical and reliability reasons.

      Then there's the problem that your proposal relies on aggregate rating to combat manageability problems: How can an ISP be responsible for its customers' misbehaviour, especially with a system which almost naturally lends itself to end-to-end encryption? Once everybody has a key, it's dumb-network-intelligent-terminals again, reducing service-oriented solution providers to precisely the network operators they once were.

    16. Re:How come we even get them? by Juggler · · Score: 1
      What I generally recommend to ISPs, when given the chance, is that they offer two sorts of subscriptions - the default being a locked down subscription which allocates IP addresses behind ACLs blocking outgoing port 25 and incoming 135-137, along with a few others.

      If the technical-minded people can opt out of the firewall then they're generally quite happy. In some cases they're even willing to pay a little bit extra, which is after all justifiable because the risk is higher for the ISP and offering this sort of thing adds complexity.

      I realize this isn't technically feasable for all ISPs, but for many it provides an excellent solution.

      Disclaimer: I work for FRISK on e-mail stuff.

    17. Re:How come we even get them? by Czmyt · · Score: 1

      I personally think it's a good thing for ISPs to block port 25 outbound access for their customers. That block does not stop customers from checking their corporate e-mail with POP, IMAP, or HTTP; and those customers can send outgoing e-mail using the ISPs SMTP server. The ISPs can then virus scan the outgoing e-mail on their SMTP server and block any virus infected messages, especially virus messages like SoBig where the entire message was auto-generated illegitimate content.

    18. Re:How come we even get them? by Genom · · Score: 1

      Just so long as there's a reasonably affordable way for a "normal", non-corporate customer to get a non-blocked, static ip, I'm OK with most others blocking port 25.

    19. Re:How come we even get them? by Czmyt · · Score: 1
      I wish there was such a way for residential customers to get static IPs for a reasonable price if they want or need one, but I think that time has long passed.

      There's no real need to block incoming port 25 since most are using dynamic IPs. I would prefer to see the ISPs not block port 25 outgoing unless it was abused. I would consider abuse the sending of 20 or more messages per minute.

    20. Re:How come we even get them? by nacturation · · Score: 3, Interesting

      It is true that since Sobig uses its own SMTP server the ISP would have to do the monitoring via a port 25 monitor. I'm not completely sure how difficult/expensive this would be to implement on a large scale, but there's an opportunity for someone who comes up with a cheap solution. I suppose it could be part of a general IDS, but it needs to be something price-accessible to an ISP.

      This is trivial. Allow for normal port 25 access to the ISP's email server (with the usual restrictions on volume and content) and, for external port 25 access, there's a number of possibilities:

      1. Allow the client to setup a pre-determined list of specific hosts they want to connect to. This might be done using a web-based interface.
      2. Only allow the first 10 hosts (per dialup connection, per DHCP lease, per hour, etc.) to be accessible via port 25. This should satisfy even power users as few need to check mail on over 10 different servers. Adjust number as appropriate.
      3. Setup a proxy service which allows unlimited port 25 access. Any viruses which include their own SMTP delivery engines won't know about the proxy and will simply fail. There's no additional security risk to using your ISP's proxy than using the ISP's connection itself, as both can be logged with equal ease.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    21. Re:How come we even get them? by nacturation · · Score: 1

      Typo... instead of:

      This should satisfy even power users as few need to check mail on over 10 different servers.

      The correct version is:

      This should satisfy even power users as few need to send mail to over 10 different servers.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    22. Re:How come we even get them? by ajs · · Score: 1

      Uh... no, that's not quite true.

      Your server *does* have to have a single name that it admits to, but you can accept mail for (and send it from) andy name you like. You can use TLS today.

    23. Re:How come we even get them? by ajs · · Score: 1

      The idea of a CA is totally independant of any centralization.

      The implementation of existing CAs is centralized.

      Don't confuse those two. You could, for example, start a "TLS SpamKiller" CA and distribute your CA key with your software. Then anyone that you sign keys for can certify sites that send mail using your software.

      If your software is just a plugin for lots of existing mailers, then all people have to do is use your plugin. Done.

    24. Re:How come we even get them? by Tony-A · · Score: 2, Interesting

      Something I don't think I've seen addressed in coping with these things. Short-term versus long term. The tactics and priorities are quite different.
      Getting rid of all of them is a long-term process.
      In the short term, you want to stay operational with minimal colateral damage. While emergency training will certainly help, it's almost a certainty that what needs to be done is not covered in the book. Sophisticated tools could certainly help, but it seems to me that with TCPDUMP and a pair of eyes and almost no knowledge it would be obvious that something was going on plus a few clues as to what and from where. I suspect that the best bet for long-term survivability is to leave decisions at the point of crisis to the whim of whoever is manning the stuff at the time.
      One PC goes wild. Probably ignored since there's plenty of capacity to handle it.
      One PC goes wild and a large bunch of it neighbors do too. You do something to stop the flood. Probably catches a bit of legitimate stuff too. Then you look and see what's making the flood and refine your stuff a bit. After such as Slammer, I would rather see a mixed-up mess that gets the internet back operational in an hour than something carefully thought-out that gets it back in 24 hours.

    25. Re:How come we even get them? by AKnightCowboy · · Score: 1

      Then again, there are those of us that use Speakeasy that are not running clueless open Windows boxes on our connections so why punish everyone? I would be seriously pissed if Speakeasy, or any other ISP I was using, blocked any of my outbound ports without giving me the option of opting out. I WILL take responsibility for the security of my systems and if I violate your AUP then cut me off. Too many ISPs offer no choice though, Speakeasy does.

    26. Re:How come we even get them? by Anonymous Coward · · Score: 0

      Sorry, while CA doesn't stand for "central authority" it just as well might. There are different levels of centralization, obviously, but smaller circles also mean less pervasive trust. If you send mail using a certificate from CA-A and I use software which knows only about CA-B and CA-C, then it won't work (I can only know that you have a certificate, but not if it's correct or if you just made it up). So either I'd have to import more "root" certificates or the CAs would have to come together under a smaller number of parent CAs. One strategy is impractical and the other is centralized. Authority can be delegated in a hierarchical fashion, but it still relies on a small number of central CAs.

    27. Re:How come we even get them? by mikeswi · · Score: 1

      Absolutely agreed. Most people have no reason to talk to a foreign SMTP server, but some of us do. I have a web site and a mail server that I pay quite a bit of money for each month. My host has had to open alternate ports on the mail servers for customers with ISPs that block them without permission.

      I would be happy with port 25 blocked by default with an option to turn it off for specific customers. However, what's to stop a trojan from installing an SMTP server that uses something other than port 25? Not being argumentative, just curious.

    28. Re:How come we even get them? by Pharmboy · · Score: 1

      I would be happy with port 25 blocked by default with an option to turn it off for specific customers. However, what's to stop a trojan from installing an SMTP server that uses something other than port 25? Not being argumentative, just curious.

      Try setting your email client to use a port other than 25 and you will see. No response (or rejected, rather). Since the trojans rely on SPEAKING with the other mail servers to deliver the mail, they must communicate on the same port, 25. That is the whole idea. Its like trying to surf the web on port 55. Unless you FIND a web server that is Listen'ing to 55, you don't connect.

      Won't bother you with a more detailed description unless you ask.

      --
      Tequila: It's not just for breakfast anymore!
    29. Re:How come we even get them? by lseltzer · · Score: 1

      I think you don't understand. There's no need to block your ports unless you're spreading a worm or something similar.

    30. Re:How come we even get them? by mikeswi · · Score: 1

      Ahhhh..... OK, I understand that much at least.

      What I was theorizing was something that installs a fully functional SMTP server that sends mail directly from an infected machine. It doesn't use the ISP or any relaying SMTP server.

      Still, ISPs blocking the port would help quite a bit with the problems already present. I would hope that ISPs would have an option to reopen the port for certain customers if they needed it and agree to keep themselves secured.

    31. Re:How come we even get them? by arcade · · Score: 1

      All of which are idiot solutions. It's a hack, and it's a damn ugly hack. Blocking outbound port 25 breaks the option of having an external host with authentication which you can connect to and do your stuff. Which is irritating to say the least.

      A proxy server would have to be supported by all the pieces of software in use. Not fscking likely

      The "allow 10 hosts per dialup connection per DHCP lease, per hour" option _could_ be alright, hadn't it been for the _slight_ problem that it would be hell to implement in most cases.

      --
      "Rune Kristian Viken" - http://www.nwo.no - arca
    32. Re:How come we even get them? by nacturation · · Score: 1

      All of which are idiot solutions. It's a hack, and it's a damn ugly hack. Blocking outbound port 25 breaks the option of having an external host with authentication which you can connect to and do your stuff. Which is irritating to say the least.

      [Ignoring your trolling...] It's not a total block, as I pointed out. Merely a limitation. What residential internet user really needs to connect to thousands of SMTP servers per hour directly? Er, none. Unless someone is running their own email server... but then that's a business use not residential. There will always be ISPs to cater to the business/poweruser market.

      A proxy server would have to be supported by all the pieces of software in use. Not fscking likely

      Only by the mail clients. How many mail clients *don't* support sending mail via proxy these days? A very rare few. And we're only talking outbound email here. And for really old clients which don't support outbound mail via proxy, instead of sending your email out through mail.yourserver.com, you simply send it out through mail.yourisp.com. As I pointed out right at the top, your ISP's port 25 wouldn't be blocked, subject to the usual volume and content restrictions.

      The "allow 10 hosts per dialup connection per DHCP lease, per hour" option _could_ be alright, hadn't it been for the _slight_ problem that it would be hell to implement in most cases.

      It's up to the ISPs as to whether this hell would be worth it to implement. Customer protection + bandwidth savings + good netizen karma > implementation hell?

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    33. Re:How come we even get them? by Pharmboy · · Score: 1

      I can see for MOST people, the ISP blocking this port is no big deal (blocking except the ISP's own SMTP server) As a matter of fact, this would prevent spam as well, since you could only send through the ISP, and THEY would know if you sent 1.3 millions "Viagra" ads. This is ONLY if they use their own computer to send the spam, which is not always the case.

      This would have no effect on people who use Squirrelmail, Hotmail or other web based email clients since they use ports 80 and 443 generally. All the SMTP activity happens on the SERVER instead of the client. These are not good clients for sending mass mail of any kind anyway, way too slow. Ironically, A Good Thing(tm)

      This has better potential to prevent spam than to cut viruses/worms, although anyone can still rent a rack and use it for a smtp server for spam, or find an open relay (more rare now). Either way, there is higher accountability since the source is absolutely known and tied to a credit card at the ISP or RackShack.

      And like you say, if you want port 25 open, you have to agree to a certain code of conduct and security. If only 3% of their customers need port 25 open (likely less) then full logging is much easier, and more accountable.

      Only problem is getting all major ISP's to agree to such a policy, and making ISP's who won't, look bad in the public eye. (ie: shame them into it)

      --
      Tequila: It's not just for breakfast anymore!
    34. Re:How come we even get them? by ajs · · Score: 1

      You are correct. What you describe is a community of trust, and in the real world, communities of trust are disjoint and apply only to certain applications and certain ways of interacting.

      The same is true in software.

      That does not make the idea of a CA useless, it simply makes it no more useful than it is in the real world.

    35. Re:How come we even get them? by arcade · · Score: 1

      [Ignoring your trolling...]

      There is a difference between trolling and being outright frustrated by idiocy.

      It's not a total block, as I pointed out.

      I appologize for flaming you for that. I seem to have been a bit hasty reading your post. However, when I look at your first point again, I just have to ask .. how much work do you think that webinterface and the following filters would be to implement? I can't fathom the amount of ugly hacks needed. I can't see any good way to implement in any of the systems I've worked on.

      Luckily I've never worked with dialup ;)

      Unless someone is running their own email server... but then that's a business use not residential.

      Bullshit. It's quite practical to run ones own mailserver for ones own private domains. Of course, many people "don't see the use", and think that "one can just use the ISP's outgoing mailserver". Bollocks I say.

      There will always be ISPs to cater to the business/poweruser market

      Indeed, and usually more expensive. What I want is quite simply a link with some bandwidth - no tech support (but a competent NOC, when things fail on their side), no bullshit. They don't need to provide a webserver, mailserver, newsserver or anything - just give me the damn bandwidth and an IP address and shut up about it. Oh, and please - they could have a good abuse department to cut off actual abusers.

      How many mail clients *don't* support sending mail via proxy these days?

      I have to admit that I haven't checked whether pine, mutt, /bin/mail or any of the other clients I tend to use have that option -- never _Seen_ it though.

      And for really old clients which don't support outbound mail via proxy, instead of sending your email out through mail.yourserver.com, you simply send it out through mail.yourisp.com.

      No thanks - and I should't be required to give a better reason than that.

      It's up to the ISPs as to whether this hell would be worth it to implement. Customer protection + bandwidth savings + good netizen karma > implementation hell?

      Good netizen? To break end-to-end connectivity by random blocking? bullshit.

      --
      "Rune Kristian Viken" - http://www.nwo.no - arca
    36. Re:How come we even get them? by nacturation · · Score: 1
      There is a difference between trolling and being outright frustrated by idiocy.

      There is also a difference between calling an idea without merit (even stupid) and inferring the presenter of that idea is an idiot.
      • It's not a total block, as I pointed out.

      I appologize for flaming you for that. I seem to have been a bit hasty reading your post. However, when I look at your first point again, I just have to ask .. how much work do you think that webinterface and the following filters would be to implement? I can't fathom the amount of ugly hacks needed. I can't see any good way to implement in any of the systems I've worked on.

      I don't have your experience with various systems, but I can see how such things could be implemented. A software firewall could be modified to check whether certain ports are flagged for additional rules. If so, check the memory cache for the rules. If not present, those rules and the current person's IP is looked up in a database. The web interface could add to that database. Or the firewall could keep in memory a list of the last n port 25's accessed with a timeout value (eg: one hour). Correct me if I'm wrong, but I don't see how this presents such a tremendous challenge.

      • Unless someone is running their own email server... but then that's a business use not residential.

      Bullshit. It's quite practical to run ones own mailserver for ones own private domains. Of course, many people "don't see the use", and think that "one can just use the ISP's outgoing mailserver". Bollocks I say.

      Of course. However, many ISPs specifically state in their AUP that you are not allowed to run your own servers, so how would this be effectively any different? I understand the practical need for some to run their own mail servers. I do it myself. But "Joe Six-Pack" out there running an unpatched Windows 98 on an AOL account certainly has little need to do this.

      • There will always be ISPs to cater to the business/poweruser market

      Indeed, and usually more expensive. What I want is quite simply a link with some bandwidth - no tech support (but a competent NOC, when things fail on their side), no bullshit. They don't need to provide a webserver, mailserver, newsserver or anything - just give me the damn bandwidth and an IP address and shut up about it. Oh, and please - they could have a good abuse department to cut off actual abusers.

      And I'm sure there are ISPs which will provide this. The trick is allowing power users to have the freedom they need and keeping out the Clueless Cathys of the world from fucking it up for everyone else.

      I have to admit that I haven't checked whether pine, mutt, /bin/mail or any of the other clients I tend to use have that option [proxy] -- never _Seen_ it though.

      I'm talking about the regular users who use Windoze. If you use command-line mail software, you don't fall into that category. However, this is irrelevant to the technical merits (or lack thereof) of what I presented.

      • It's up to the ISPs as to whether this hell would be worth it to implement. Customer protection + bandwidth savings + good netizen karma > implementation hell?

      Good netizen? To break end-to-end connectivity by random blocking? bullshit.

      Many ISPs "break end-to-end connectivity" by blocking port 135 already, as just one example. Remember that all security is a trade-off. And nobody's forcing you to have port 25 restricted on *your* connection either. As I see it, it boils down to this: power users want high speed unrestricted connections at low cost. Clueless users with their viruses cause more technical support problems and use up more bandwidth, slowing the network down for others and incurring more costs for the ISP. This increased cost is shared by everyone, so the responsible power users are punished.

      If someone wants unrestricted

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    37. Re:How come we even get them? by schon · · Score: 1

      It is true that since Sobig uses its own SMTP server the ISP would have to do the monitoring via a port 25 monitor. I'm not completely sure how difficult/expensive this would be to implement on a large scale, but there's an opportunity for someone who comes up with a cheap solution.

      There is an easier way - you transparently proxy all outbound SMTP connections to your own mail server.

      We initially implemented this in 1998 to prevent our dial-up users from spamming, and it's worked wonderfully. The one time we had a spammer, he managed to send a total of 3 spams before my pager went off (which happens when the load on the mailserver reaches a set level) before we shut him down (there were over a thousand spams in the queue, which we simply deleted.)

    38. Re:How come we even get them? by theBOPfromH*LL · · Score: 1

      cuz I'm the BOTH and I get all bounced messages, silly.

  5. Mod story -1 (Duh...) by setzman · · Score: 1

    You would think that server admins would know that responding to each worm would double traffic and take action to prevent it, by either using a better filter or reconfiguring the filter to not reply.

    --
    C:\>
    1. Re:Mod story -1 (Duh...) by blunte · · Score: 2, Insightful

      Duh it may be, but that's the default behavior for Norton's Exchange AV software.

      You have to fool around with it in a most confusing way to get it to stop doing that. Like all good Windows management interfaces, it's confusing and inconsistent. But I digress...

      --
      .sigs are for post^Hers.
    2. Re:Mod story -1 (Duh...) by Anonymous Coward · · Score: 0

      You'd think that, but you'd be wrong. If you actually had a job in support right now as many of us do, you'd realize the doubled load is there, and is making all of our jobs harder. Frankly I think your post needs to be ranked -1 Duh.

    3. Re:Mod story -1 (Duh...) by dosius · · Score: 1

      I thought the only good Windows management interface was a Linux CD. ;)

      Seriously, we know that Windows (NT-class) is at fault. I think Windows 98 is passable, and Linux (modded Red Hat 8 distribution that I use) is quite good, but I really do not like XP... I think corporations should switch to a platform that just isn't as full of holes. As for the users...well...NT-class Windows was never meant for the home user.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    4. Re:Mod story -1 (Duh...) by Anonymous Coward · · Score: 0

      Where are you posting from? I thought all the IT people in the US got laid off.

  6. This is so true by blunte · · Score: 5, Funny

    Our Norton Exchange AV kicks out "we-saved-your-butt" emails to the admin, the original recip, and back at the "sender", who of course knows nothing about it since it was forged.

    I've just been creating more and more filters that send to trash with no notification to anyone.

    Of course, you have to pay attention when you first turn some of the capabilities on, as Norton kindly preset you to block AOL mail :) Serves AOL right...

    --
    .sigs are for post^Hers.
    1. Re:This is so true by trompete · · Score: 1

      Yeah, especially since AOL has been blocking tons of other people's mail servers. That was a Slashdot story a few weeks ago...

    2. Re:This is so true by rampant+poodle · · Score: 1

      The autoresponse can be turned off. With Sobig et al it really makes a big difference in server load and amount of crap hitting user's inboxes.

    3. Re:This is so true by hmallett · · Score: 1
      Our Norton Exchange AV kicks out "we-saved-your-butt" emails to the admin, the original recip, and back at the "sender"

      Not only is this something which you can configure, IIRC it's also not the default. I think the default is admin and recipient only. Perhaps this illustrates that those who select all the options are also part of the problem...
    4. Re:This is so true by blunte · · Score: 1

      Ok, in fairness to Symantec, I didn't install it, so I can't say what the defaults were. I assumed my "top notch" MCSE did what made most since with the setup, which means little or nothing ;)

      --
      .sigs are for post^Hers.
    5. Re:This is so true by Anonymous Coward · · Score: 0
      function a() { echo 'all work and no play makes jack a dull boy '; a(); }

      Error - stack overflow.

    6. Re:This is so true by toddestan · · Score: 4, Funny

      Maybe I should configure an autoresponder that responds to the message from Norton AV that tells the person how to turn off the autoresponse?

      *ducks*

    7. Re:This is so true by Zigg · · Score: 1

      I had a message written up along those lines, essentially informing postmaster@... that I'd be denying mail from their domain as they chose to use phenomenally stupid virus software. Manually sent, of course.

      Then Sobig stopped, so I never got around to using it.

    8. Re:This is so true by xanadu-xtroot.com · · Score: 3, Funny



      Must
      Consult
      Someone
      Else


      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    9. Re:This is so true by trompete · · Score: 1

      Unless php can handle tail-recursion

    10. Re:This is so true by ungerware · · Score: 1

      You laugh, but I never realized that my IT-installed NAV was sending out these rediculous bounces until some kindly gentlement replied to one and informed me of it (in a polite way, I might add). I immediately figured out how to configure NAV not to do that anymore, and notified IT, who proceeded to disable the bounces company-wide.

      --

      -----
      Kvetch is Yiddish for "throw an exception" --Dr. Ron Cytron
    11. Re:This is so true by Anonymous Coward · · Score: 0

      Must
      Consult
      Somebody
      Experienced

  7. Is that better than... by stovey · · Score: 0, Redundant

    letting the user get the email and start spewing out more viruses? I'd rather those reject emails go out than having more virus emails floating around..

    1. Re:Is that better than... by cybermace5 · · Score: 1

      Uh, the virus software already caught the message and the user won't be getting it. Sending a "you're infected" email back to the sender won't do a single bit of good, since the vast majority of SoBig viruses spoofed addresses using the infected computer's address book.

      --
      ...
    2. Re:Is that better than... by rgmoore · · Score: 1

      It's not an either/or question, you know. Blocking the message from getting to its intended recipient is completely unrelated to sending a message back to the alleged sender. It's perfectly possible to block the message without informing the (alleged) sender. It's even desirable in the case of email worms like SOBIG that are known to forge the From: header, since in that case you're pretty much guaranteed not to be sending the message to the right person. A well writting program would take this kind of thing into account.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    3. Re:Is that better than... by Anonymous Coward · · Score: 0

      since the vast majority of SoBig viruses spoofed addresses

      No, actually - that should be every SoBig virus. As in every single last one.

      There is no point in sending them at all.

      When I receive them, I immediately blackhole the admin's server (they're not fit to be on the internet anyway, so I'm not losing anything), and then forward the message (which usually includes the attachment in question) to the admin.

      Yes, I know that each mail server will try to bounce the message back to me, but since they're blacklisted, the bounce will end up in the admin's mailbox. With the attachment. Which will probably then be bounced. Hopefully with the attachment. :o)

  8. How about a real email client or real rules? by TWX · · Score: 4, Insightful

    Do most users exchange executable files? How about just blocking them if they're executable... How about getting an email client that isn't known for it's ability to spread received infected email without the user having to even open the email?

    /been using pine since 1996...

    --
    Do not look into laser with remaining eye.
    1. Re:How about a real email client or real rules? by Elwood+P+Dowd · · Score: 3, Insightful

      There have been semi-successful email viruses where the user had to download a .zip attachment, decompress, run the executable, and click "yes" to install.

      Sure, we can remove capabilities in order to increase safety, but with users like that... I'm really not sure what we should do. Authenticating the sender and receiver of all email would be a step.

      --

      There are no trails. There are no trees out here.
    2. Re:How about a real email client or real rules? by 1010011010 · · Score: 2, Informative
      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    3. Re:How about a real email client or real rules? by draziw · · Score: 1

      A line from my postfix header_checks: /^Content-(Type|Disposition):.*(file)?name=.*\.(as d|abd|bat|binhex|chm|cmd|com|dbx|dll|exe|hlp|hta|j s|jse|lnk|ocx|pif|scr|shb|shm|shs|tbb|vb|vbe|vbs|v bx|vxd|wab|wsf|wsh)/ REJECT Sorry, we do not accept .${3} file types.

      They don't reach my virus scanner...

      PS: SCO sucks. :)

    4. Re:How about a real email client or real rules? by ickris · · Score: 1

      Just to let you know, Pine currently has two Exploitable Overflows. The Description stats that PINE contains two exploitable vulnerabilities that can be triggered when a victim opens a specially crafted email sent by an attacker. Here is the link for the advisory by iDEFENSE http://www.idefense.com/advisory/09.10.03.txt

    5. Re:How about a real email client or real rules? by bourne · · Score: 1

      /been using pine since 1996...

      Better update it so that you don't [open] a specially crafted email sent by an attacker.

      "It would be trivial for this exploit to be fashioned into a worm, targeting e-mail addresses found in any readable text files (inbox, etc.)."

    6. Re:How about a real email client or real rules? by RobertB-DC · · Score: 1

      Do most users exchange executable files? How about just blocking them if they're executable...

      We have that -- the corporate Outlook server blocks all executable files.

      Trouble is, I'm in a programming group. We *do* send executable files to each other! .reg (Windows Registry update) files, too. They're all blocked by the server -- it displays a message saying "Outlook deleted the following unsafe attachments: theprogramyouwanted.exe"

      No problem, though... we just zip 'em up and send 'em. Giving the heck we went through when LoveLetter hit -- including messages to everyone from a corporate director saying "I Love You!" -- the inconvenience of zipping/unzipping is a small price to pay.

      Although shouldn't Outlook's message be a bit more truthful? "Outlook deleted the following unsafe attachments, which are only unsafe because you're running a virus portal instead of an email client..."

      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    7. Re:How about a real email client or real rules? by TheQuantumShift · · Score: 1

      Actually MSN blocks attachments that are executable. .exe .htm and a bunch of others are blocked. Of course most customers still like sending "a web page" (think save as... attach "usanumber1_funny.htm") and bitch and moan when they have to wait for their mail to be scanned and filtered before they get it...

      --

      Shift happens. Fire it up.
    8. Re:How about a real email client or real rules? by ATMAvatar · · Score: 1

      messages to everyone from a corporate director saying "I Love You!" -- the inconvenience of zipping/unzipping

      Did anyone else look at that funny when they first read it?

      --
      "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
    9. Re:How about a real email client or real rules? by gid · · Score: 1

      I just set up a procmail filter, drop the message, no bounce, no nothing, just gone, as it should be, I don't want any exe attachments, even if it is only some "cute game". Added this to my .procmailrc file:

      #roast all emails with executable attachments :0 B
      * ^ *Content-Disposition: attachment;
      * filename=".*\.(pif|exe|com|scr)" /dev/null

    10. Re:How about a real email client or real rules? by AnotherBlackHat · · Score: 1

      Do most users exchange executable files? How about just blocking them if they're executable...

      Most users don't, but enough do that blocking them by default isn't a good idea.

      Much better (though not perfect) is to rename executables,
      attach a message that explains that the executable was renamed,
      and why you should be very careful about executing attachments.
      (Maybe even suggest asking for confirmation from the sender that they intended to send it...)


      How about getting an email client that isn't known for it's ability to spread received infected email without the user having to even open the email?


      Amen.

      -- this is not a .sig
    11. Re:How about a real email client or real rules? by Homology · · Score: 1
      But your Postfix filter does a REJECT on the type of payload delivered by SoBig: an attachment with the extension pif. So, in truth, you are sending a reply to a forged FROM address. The Postfix rules are general rules, and when the shit hit the fans you got to change your rules to the situation.

      What you should do, of course, is to DISCARD e-mail with .pif attachments to stop making the SoBig virus less of an impact.

    12. Re:How about a real email client or real rules? by Zak3056 · · Score: 1

      There have been semi-successful email viruses where the user had to download a .zip attachment, decompress, run the executable, and click "yes" to install.

      Sure, we can remove capabilities in order to increase safety, but with users like that... I'm really not sure what we should do.


      Have you considered a cattle prod?

      --
      What part of "shall not be infringed" is so hard to understand?
    13. Re:How about a real email client or real rules? by ad0gg · · Score: 1
      How about getting an email client that isn't known for it's ability to spread received infected email without the user having to even open the email?

      Sobig has nothing to do what email client your running, its a trojan horse. An executable with its own smtp server that scans your computer for email addresses and emails its selfout through its own smtp server. Outlook xp by default blocks executables from attachment, but how long till new viruses start zipping their attachments.

      The problem here is the user. Users need to stop running every damn program they see.

      --

      Have you ever been to a turkish prison?

    14. Re:How about a real email client or real rules? by Asgard · · Score: 1

      As long as the REJECT is performed before the postfix daemon accepts delivery, then the burden of generating the bounce is on the sending daemon (ie the Sobig built-in smtpd) -- which is to say it won't happen.

    15. Re:How about a real email client or real rules? by Anonymous Coward · · Score: 0

      not if the reject happens right away, instead of bouncing.

      smtp has a (rarely implemented) reject system, where it can return a reject code before the client is disconnected.

      this is how rbl blacklisting works in postfix as well.

    16. Re:How about a real email client or real rules? by Homology · · Score: 1

      I did not forge sender when I tested this on the Postfix server, but I guess I should have considering SoBig features....

    17. Re:How about a real email client or real rules? by slyfox · · Score: 1

      .../been using pine since 1996...

      Oh, but wait; pine has been vulnerable in the past due to various buffer overflows and mime errors. For example, see
      CERT Vulnerability Note VU#780737. Granted, most users don't run Pine as root (thus limiting the damage), but it could still cause some real problems; that is, it could if everyone used unpatched versions of pine.

      The problem with Microsoft products is due to monoculture as much as bad software engineering.

    18. Re:How about a real email client or real rules? by Elwood+P+Dowd · · Score: 1

      Oh, I haven't witnessed any of my companies users doing that exactly. However, back when those viruses were in the wild (Klez, I think), I definitely got a million copies in my personal email. Someone was stupid enough to install it.

      --

      There are no trails. There are no trees out here.
    19. Re:How about a real email client or real rules? by swordfishBob · · Score: 1

      ... that's why we block execuatables, and examine inside zip files (and nested zips) to see what is really in them...

      --
      -- All your bass are below two Hz
    20. Re:How about a real email client or real rules? by draziw · · Score: 1

      Wrong. A reject in the header checks happens without taking delivery. No bounce is sent by my server.

      If you did the filtering client side, that would make a bounce (bad).

    21. Re:How about a real email client or real rules? by daVinci1980 · · Score: 1

      You go to all the trouble of zipping them? I just change the extension by one letter (usually I make it more l33t.)

      so thatprogramyouwanted.exe becomes thatprogramyouwanted.3x3.

      --
      I currently have no clever signature witicism to add here.
  9. Re:iHateSpam by trompete · · Score: 1

    If you don't want to spend any money at all, you should consider getting SpamBayes. I've tried both SpamBayes and iHateSpam, and I personally like SpamBayes better. It is also FREE. Both have nice Outlook plugins.

  10. Hallelujah! by PopeAlien · · Score: 4, Insightful

    Not only are they doubling traffic, they can help spread the virus.. I've recieved bounced email containing the virus, since the the return address is randomized this in effect helps to spread the virus. Why include the attachment in a bounce message?

    1. Re:Hallelujah! by Daniel_Staal · · Score: 1

      Hey, those are the bounces I like (not enough that I actually want to get them, but better then the rest). If they send the entire message back to you then you can at least tell the person who is infected. (Instead of most of the messages where you don't have any clue, since the bouncing machine stripped out all the useful data.)

      Oh, and since I got 10-50 times more bounce messages then the virus itself I am in full agreement with what I haven't read of the article. These bounce messages are a bigger problem at this point than the virus itself.

      --
      'Sensible' is a curse word.
    2. Re:Hallelujah! by mattdm · · Score: 1

      Yeah, and if it includes the virus, your own virus scanner can catch it and delete it with ease.

    3. Re:Hallelujah! by fname · · Score: 1

      I agree. I did not receive the virus directly from anyone, but I had dozens of emails sent to me warning about the infection on my computer (funny, since I still use Pine on that account). And a bunch of those actually contained the virus. As Jon Stewart might say, (rubbing eye) Waaaa? So not only are these folks sending more emai, they're often spreading the virus. Scratch that. They're knowingly spreading the virus. Aren't there laws about that sort of thing?

    4. Re:Hallelujah! by Anonymous Coward · · Score: 0
      Yes, there are laws against knowingly spreading viruses. At least in Italy it's up to 6 years jail-time!

      :-)
      ms

  11. Outlook by Bame+Flait · · Score: 0, Troll

    Nothing much can be said about security when you are using Outlook Express. Microsoft has always been quick to issue patches to cover up its bugs. It usually releases these patches on the Web. All you can do to keep your mails secure to the utmost extent is to keep a watch on these patches and update your OE as and when necessary. Please check that you have 128-bit encryption on your system. For this, please go to the `help' menu of your browser and then click `about Internet Explorer.' A dialog box will pop up. Look for the word Cypher strength. The cypher strength ideally should be 128bit. If it is anything less than that, then click on the link displayed next to it to upgrade it to 128. Cipher Strength is a security feature in browsers which provides encryption of information being transmitted across the Internet. Barring these security bugs, you can tweak your security to a great extent by applying file-level security to your mail box by using NTFS file system, for which you will have to have win2000 or XP as your primary OS.

    1. Re:Outlook by Anonymous Coward · · Score: 0

      The first step with Outlook or Outlook Express (assuming that moving to anything better is not an option) is to set the "Internet Security Zone" to be "Restricted".

      I would post steps, but, they move that around to hide it from version to version :(

    2. Re:Outlook by Seth+Finklestein · · Score: 2, Insightful
      1. Low-level format lusers' hard drives.
      2. Install Linux.
      3. Save $900 per seat on annual licenses for operating system, office suite, and anti-virus software.
      4. Profit.
      --
      I'm not Seth Finkelstein. I still speak the truth.
    3. Re:Outlook by Seth+Finklestein · · Score: 1

      Good post, Seth!

      --
      I'm not Seth Finkelstein. I still speak the truth.
    4. Re:Outlook by Seth+Finklestein · · Score: 1

      The $699 license fee is for servers. I pay only $199 per workstation. Also, that license is good forever, not for one year like Micro$soft's "license."

      Frankly, I believe that $199 is a perfectly fair price for Linux.

      --
      I'm not Seth Finkelstein. I still speak the truth.
  12. mmm, pie by kinzillah · · Score: 0, Offtopic

    I like pie. Pie is better than Outlook worms.

    --
    Douglas P. Price
    1. Re:mmm, pie by Anonymous Coward · · Score: 0

      I'm with you 99%.

  13. Letter contents incase of /.'ing by B5_geek · · Score: 3, Informative


    Why (some) anti-virus companies are to blame for the recent
    e-mail flood

    As everyone should now know, Sobig.F has generated a tremendous amount of e-mail traffic world-wide. However, part of the blame for this traffic should be placed on some of the anti-virus companies.

    What I am referring to is the large number of incorrectly configured mail filters that respond by sending a "virus alert" to the "From:" address. As Sobig.F falsifies the "From:" address, these e-mails just clutter up the mailboxes of innocent, non-infected people. These messages cause unnecessary annoyance and worry, as they typically (and incorrectly) claim that people have sent out a virus.

    When you get an e-mail, warning you of a Sobig.F infection, with a subject line similar to these:

    * *** detected and quarantined a virus in a message you sent.
    * Warning: E-mail viruses detected
    * Virus Detected by ***
    * This is an alert from ***

    it usually means that someone, somewhere has made a bad decision on how to react to infected mail, either by selecting a substandard product or by configuring it incorrectly.

    Worse yet, if mail filters send out one message for every copy of Sobig.F received, they are in effect doubling the amount of traffic. This makes them a part of the problem, not a part of the solution.

    The problem is that some commercial mail filters have this behaviour set as the default. At least one filter gives only two options: Always send a "virus alert" to the "From" address of every infected e-mail received or "pass the message through to the recipient". Clearly neither of these options are acceptable.

    I have only one word for this: Stupid!

    Acceptable behaviour would be one of the following:

    1. Have the mail filter properly distinguish between worms that falsify the "From:" address and ones that do not and only send a warning message when the "From:" address is likely to be genuine.

    2. Do not send the alerts at all.

    In fact, sending an alert automatically to the From: address for every virus or worm received by e-mail should not even be a selectable option.

    With Sobig.F scheduled to die out today, Sept. 10th, the problem might go away for a while - until the next similar worm appears. And this is the scary part. Sobig.F didn't really infect that many machines world-wide, maybe only 200.000 or so. This is only a fraction of the number of machines infected by Msblaster (Lovsan). Now imagine a worm combining the distribution method of Msblaster with the mass-mailing feature of Sobig.F. The flood of traffic might practically render the Internet unusable.

    Eventually, some virus author will create a virus like this, maybe this month, maybe in a few years, but it will happen. And when it does we do not need the anti-virus companies making a bad situation worse.

    I hope the "guilty" anti-virus producers will be updating their products in the near future, but this is not going to happen unless their customers request it.

    Fridrik Skulason ( frisk@f-prot.com )
    Founder of FRISK Software International

    --
    "The price good men pay for indifference to public affairs is to be ruled by evil men." ~Plato (427-347 BC)
    1. Re:Letter contents incase of /.'ing by secolactico · · Score: 1

      Wouldn't be better if the server simply returned an SMTP 550 when a virus is found? Too bad most AV plugins only work *after* the message has been accepted and not after the end of the DATA command.

      --
      No sig
    2. Re:Letter contents incase of /.'ing by 1010011010 · · Score: 1

      How about 551? It's what this milter returns.


      $ctx->setreply('551','5.7.1',"Attachment '$file' not allowed.");

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  14. opt-in by Douglas+Simmons · · Score: 1

    Agreed. My box is getting dozens of filtered SoBig notifications every day. I'm not that paranoid that the wicked screensaver emails I would otherwise be receiving might be false-positives, and I imagine the same is true for most others; but for those who want to know about everything that is addressed to them, the filterware out there ought to let them opt-in. This is an unnecessary waste of server/network resources that clutters my emailing experience more than it already is.

  15. No doubt! by tbase · · Score: 4, Interesting

    If the e-mail filter is smart enough to know it's Sobig.F, why isn't it smart enough to know the "from" is spoofed?!?!?

    I set our filters to just delete anything with an executable attachment, but that didn't to crap for the stupid "Virus Detected" warnings.

    One guy was sending us about 150 copies a day, and the others his PC sent out with our address as the "from" resulted in about 50-75 Virus warnings a day - from the first day it popped up until it expired. I had his IP address, and called and e-mailed his ISP (Birch.net) a dozen or more times, and they did squat. 150 x ~100k x # of people in his address book - not to mention the undeliverables and virus warnings - and they did nothing.

    --

    666-607: 6th floor apartment of the beast
    1. Re:No doubt! by spydir31 · · Score: 1

      Some filters do, you might want to try MailScanner which has an option to clean silently on a per virus name basis (and optionally still delivering a message to the postmaster)

    2. Re:No doubt! by Anonymous Coward · · Score: 0

      Why don't you just send all mail
      with Subject = Virus Detected to /dev/null?

    3. Re:No doubt! by Anonymous Coward · · Score: 1, Informative

      Some of this poor/bad config files and settings. Example, Amavis can notify the sender that they sent a virus. However, you can give a amavis a list or regexp of viruses that should skip the notify step. I bet most anti-virus products have a simmilar feature, but they must be turned on by default.

    4. Re:No doubt! by tbase · · Score: 1

      Wouldn't that tick off Dev Null?

      But seriously, being a small company, we outsource our hosting to pair Networks, Inc., and to be honest, I wear too many hats here to get that far into it. I pat myself on the back for just learning how to set a custom user prefs for SpamAssasin so even messages "from" people on our whitelist don't make it if they have an executable attachment or mention Viagra. That alone weeded out over 700 messages over the weekend.

      --

      666-607: 6th floor apartment of the beast
    5. Re:No doubt! by dosius · · Score: 1

      Kind of hard if every AV program has a different subject line, and then, every different language... :\

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
  16. Fuzzy Math by Akai · · Score: 4, Interesting

    The SoBig.(X) (all of 'em, been getting them for months, good thing Evolution doesn't care) are all around 100K a piece.

    A "your message was filtered" is maybe 2-3K including all headers (more likely under 1k), so responding to messages with Virus' in them adds 1-3% not 100% to the traffic.

    That being said, since most of the current generation of SoBig happily fake the "From" email address, a reply to the from address doesn't really help anyone either.

    So in the worst case scenario, a 3K reply to a fake email address results in a bounce message, so at the most you've got 5% overhead, and theoretically for that 6K of email, you've saved a user from getting infected, which would generate 100K*1000's of data.

    I'd say it's not too high a price to pay.

    --
    Please send all UCE to scally@devolution.com so I can f
    1. Re:Fuzzy Math by realdpk · · Score: 5, Insightful

      There's some flaws in the logic.

      First, there's a cost per message that you're not including. Every message I get I have to consider and read, or delete. I'm getting tons of virus bounces, even though I've never sent a virus - the virus uses forged headers. So, for me, someone who has no way to contract a virus, my "work"load has gone up noticably, and the price I pay went from $0 to $X where X is a positive number.

      Second, the autoresponder is not a necessary part of the virus removal. The savings is already there by blocking the virus from infecting the user's computer. The bounce is just an extra thing the anti-virus people put in to try to advertise their product.

      It's *pretty damn close* to being spam.

    2. Re:Fuzzy Math by Mr.+McGibby · · Score: 1

      I pay went from $0 to $X where X is a positive number.

      Yeah, epsilon.

      --
      Mad Software: Rantings on Developing So
    3. Re:Fuzzy Math by Anonymous Coward · · Score: 1, Insightful

      What about the responders that include the original message in the bounce?

      And as you mentioned with SoBig the From address is spoofed, so not only is the message just as bad as everyday spam, it may also contain the attached virus.

      It's not a matter of "price to pay", it's a matter of "why the hell would you have stupid behavior like this the default action?" Maybe you just missed that there was an article attached to this story that explained this?

    4. Re:Fuzzy Math by edwdig · · Score: 1

      The problem is some of the antivirus filters will mail you back to inform you that your message was infected, and will also include the full original message, including the attachment. So, the virus is being further distributed by bad antivirus software.

    5. Re:Fuzzy Math by realdpk · · Score: 1

      er, I should have elaborated a bit more. The cost per message is not just the mind-time, but the time spent negotiating TCP stuffs, then SMTP stuffs, and then delivering the message, etc etc. It's a lot of work for zero gain (except for the anti-virus software authors, potentially).

    6. Re:Fuzzy Math by Zak3056 · · Score: 2, Interesting

      A "your message was filtered" is maybe 2-3K including all headers (more likely under 1k), so responding to messages with Virus' in them adds 1-3% not 100% to the traffic.

      First off, disclaimer: My mail servers have been (until SoBig) configured to send "Hey, you sent us a virus" messages. We stopped this practice because SoBig is so damn prolific that it proved to us this was absolutely worthless and harmful.

      That said, there are some REALLY stupid people out there that not only bounce to the "sender," but are also kind enough to INCLUDE A COPY OF THE DAMN ATTACHMENT.

      These, ahem, "virus scanners" really DO increase the load by 100%, and worse yet, are actually SPREADING the virus!

      --
      What part of "shall not be infringed" is so hard to understand?
    7. Re:Fuzzy Math by MSG · · Score: 2, Informative

      A "your message was filtered" is maybe 2-3K including all headers (more likely under 1k), so responding to messages with Virus' in them adds 1-3% not 100% to the traffic.

      There are bigger problems than just the total amount of traffic. Lets say you run a domain that's in thousands and thousands of address books and Internet cache files... like "real.com". Now lets say that a multithreaded virus starts emailing itself as rapidly as possible to all of the addresses it can find... like SoBig.F.

      Care to guess what the result is? Something to the tune of 10,000 attempted connections PER MINUTE. That's way more than our mail servers are configured to accept (they're rate throttled). While load on the machines stayed acceptable due to their throttling incoming connections, access to port 25 was highly contended. People outside the company trying to send us mail obviously experienced delays. I can only imagine what was going on at better known domains.

      Here's the hitch: The overhead of accepting a connection is greater than the cost of the rest of the message. Judging by the messages that actually did get through, probably only 1000 connections per minute of the 10000 were the SoBig virus. The other 9000 were bounce notices from other systems. So, in our case the traffic increase wasn't 1-3%, and it wasn't 100%, it was 900%. There's no good reason for it, either. Those bounce messages don't protect anyone from getting infected, they just waste bandwidth.

    8. Re:Fuzzy Math by Snowdog668 · · Score: 4, Interesting

      You'd be right and I wouldn't care if I only got the headers. Unfortunately about 95% of the bounce messages I've gotten contain the original attachment as well. Thank goodness I check that account on webmail so I didn't have to wait to download the messages over dial-up(stuck in the great broadband wasteland). It was easy to get rid of from my point of view because all I had to do was was go down the list and mark all the e-mails that were 100k for deletion and get rid of them. If I had to actually download each message over my dial-up account because some sysadmin decided to bounce the entire message I'd be seriously pissed.

      --
      I wouldn't say I'm a bad gambler but the last time I went to Vegas I even lost a buck on the soda machine.
  17. I completely agree by PktLoss · · Score: 4, Insightful

    One member of our software development team ended up receiving over 10,000messages/hour during our peak load, about equally split between virus messages, and bounce backs/mailer daemon messages. The latter weren't blocked by the standard anti-spam solution.

    The messages generally contain no usefull information, and are deleted without reading.

    Spam catchers should be combined with anti virus solutions, to ensure that authentic messages do generate some sort of response, either to the sender or receiving, informing them of the infection. The technologies would mesh well in this case.

    1. Re:I completely agree by Zak3056 · · Score: 1

      Spam catchers should be combined with anti virus solutions, to ensure that authentic messages do generate some sort of response, either to the sender or receiving, informing them of the infection. The technologies would mesh well in this case.

      Take a look at Inflex by Paul Daniels. Supports sendmail and postfix, and does spam blocking, virus scanning, filename/filetype blocking, text blocking, etc.

      --
      What part of "shall not be infringed" is so hard to understand?
  18. 5xx is the answer by hey · · Score: 3, Informative
    1. Re:5xx is the answer by 1010011010 · · Score: 1
      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  19. As a mailing list manager... by winkydink · · Score: 1, Interesting
    I have many more complaints about misconfigured UNIX mail systems & poorly written vacation programs than I do about Outlook filters.

    This FRISK dude needs to go back and look at his assumptions:
    Worse yet, if mail filters send out one message for every copy of Sobig.F received, they are in effect doubling the amount of traffic.

    huh? If person A's infected machine sends out 100 emails, and the one received by person Q generates a reply to sender, how does this double the amount of traffic. Sheesh! Calm down.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:As a mailing list manager... by nacturation · · Score: 1

      huh? If person A's infected machine sends out 100 emails, and the one received by person Q generates a reply to sender, how does this double the amount of traffic. Sheesh! Calm down.

      In the off chance that you're not just trolling, you're clearly missing the obvious. Person A sends out 100 infected emails. Person Q1's antivirus generates an email to forged sender. Person Q2's antivirus generates an email... Person Q3's antivirus generates... 97 emails later ... Person Q100's antivirus generates an email.

      Ergo, 100 viruses sent out, 100 replies from autogenerated "you sent an email" messages. This assumes Q1 ... Q100 all have antivirus filters.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    2. Re:As a mailing list manager... by winkydink · · Score: 1
      No, I'm not trolling.

      Unless I misunderstand you (and I'm seriously jet-lagged), your assumption is that all Outlook clients are configured with broken mail filters? I'm sorry, that's just not true.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    3. Re:As a mailing list manager... by nacturation · · Score: 1

      Unless I misunderstand you (and I'm seriously jet-lagged), your assumption is that all Outlook clients are configured with broken mail filters? I'm sorry, that's just not true.

      Most, if not all, rejection notices I've received have come from the mail server, not from the client. A lot of ISPs now offer virus scanning as a free feature in order to compete with the other ISPs which have this standard. Companies have their corporate email gateways which, more often than not, have antivirus scanning. So email getting scanned for viruses, and not by the client program, is increasingly becoming the norm.

      So yes, you're correct that it doesn't double. Perhaps a 50% increase instead? Still, not insignificant.

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  20. We've started to filter bounce messages. by Future+Man+3000 · · Score: 2, Interesting
    All the bounces from viruses and faked spam 'From:' headers amount to about 5% of our worthless inbox content, so we've just decided to filter the stuff for a while until either the viruses die down or we determine that we really need the bounce messages for some reason.

    It's pretty rare that an e-mail that we send out does not eventually get to its recipient, and in most cases the e-mail is in response to something so the recipient will let us know if they aren't getting a message from us, so this system has been working out well so far.

    --

    I never vote for anyone. I always vote against.
    -- W.C. Fields

  21. Not entirely true by mrtroy · · Score: 1

    They arent entirely part of the problem. I think this report lacks some valuable data and misses a key point.

    What about all the emails these virus detectors PREVENT by warning the user about the potential virii in the emails.

    Remember, the average user isnt that smart. We dont want to prevent them from getting their mail. We do want to warn them. Not only this, the warning emails are likely just local anyways, so this isnt going to be too bad of a traffic increase.

    If everyone used even the worst email virus detection software, most of these worms would be stopped much quicker.

    Most worms that are using a lot of bandwidth are not email based, and scanning for other vulnerable machines.

    --
    [I can picture a world without war, without hate. I can picture us attacking that world, because they'd never expect it]
    1. Re:Not entirely true by Anonymous Coward · · Score: 0

      s/virii/viruses/

      (Using wrong Latin does not make you look more educated :))

    2. Re:Not entirely true by flea69 · · Score: 0

      That's isn't the point, the author is simply stating that antivirus software should be configured correctly and not send out bounce email's to the sender(obviously forged). No one is debating when anitivirus alerts a user to a potential virus, that is obviuosly a good thing. Most home users aren't part of the problem which the author is detailing, it is usually corporation which generate these ridiculous bounce emails.

  22. Not *too* opinionated, are we??? by Anonymous Coward · · Score: 0

    Nice rant. Sheesh, this guy makes McBride seem all warm and fuzzy.

  23. Sobig.F gone quiet by shoppa · · Score: 1
    On a related note, the flood (several hundred an hour) of Sobig.F's that I was getting since its onset stopped at 11PM EDT on 9-Sep-2003. The last bounces with my forged E-mail address as the sender came in about a half hour later. Media stories said that it would stop on 11-Sep-2003... but something seems to be off by a few days.

    Any sightings of Sobig.G in the wild yet? Everybody was predicting it to be released today.

  24. how to truely stop spam and viruses by Anonymous Coward · · Score: 0

    use pine. and whenever you goto a website that requires an email address type in root@website.com

  25. Spambayes rocks by turbotalon · · Score: 1

    I also use SpamBayes, filters like this are THE way to go. No extra traffic generated from all the notifications heading out, just a few weeks of learning and all works well. If EVERYONE used it, only the people who wanted a penis enlargement would actually recieve the email. hooray!

    --

    I'd rather have a bottle in front of me than a frontal lobotomy

  26. Another problem: User replies by Anonymous Coward · · Score: 0

    A related, but smaller, problem is users responding to the spoofed from address and complaining about being on someone's mailing list. I received a lot of these during the SoBig.F mess, and my system was never infected. (But obviously the system of one or more people who had me in their address book got the bug.)

  27. New virus tactics by JamesP · · Score: 1

    is adding to the bottom of the fake message "please send this email to everybody you know"

    --
    how long until /. fixes commenting on Chrome?
  28. Doubling messages, not traffic by fadden · · Score: 2, Informative

    The SoBig.F virus message was much larger than a "we found a virus" letter, because it included a copy of the virus itself. The number of messages bouncing around may have doubled, but the total bandwidth required did not.

    However, as the recipient of 300+ messages a day, I for one would be delighted if the virus scanners had an option to Just Shut Up when they find a specific virus. While I don't believe the scanners aggravated the problem -- indeed, by reducing its transmission, they certainly improved matters -- the bogus reject messages were a highly visible and easily avoidable irritant.

  29. And if you get enough of them... by NaugaHunter · · Score: 1

    ... you'll start getting "You're mailbox is near/over it's limit" messages.

    Are there any mailservers that can check if you've received a message previously? Maybe they should have a 'Sent' mailbox and check against them. It could clear it out every ten minutes of everything older than 24 hours, ensuring you'd get 1 notice a day max. If these filters are outside the server, it should be easy for them to offer this. Shouldn't it?

    --
    R: That voice. Where have I heard that voice before? B: In about 365 other episodes. But I don't know who it is either.
  30. Good for this guy... by fuqqer · · Score: 5, Interesting

    I work in Tech support for a telecommunications company and I get at least three calls per day regarding a message from Norton Antivirus. The message falsely states that they were a sender of the sobig.f virus. Of course, our users are completely up to date with their virus software and our e-mail servers catch the sobig virus. A big shame on you to Norton for having an e-mail enabled warning like that. It preys on the stupidity of end users.

    Granted, if nobody talked about AIDS, the infection rate would probably skyrocket too. So is it better that there be a symptom of the virus such as increased network traffic. Or is it better to not inform external users and try to repair in house?

    Maybe it offers a little job security too though.

    1. Re:Good for this guy... by Progman2000 · · Score: 1

      No, you missed something:

      Talking about AIDS does little. Not talking about AIDS does little. Promiscuous sex spreads AIDS. Abstinence stops the spread. Simple, yes?

      Similarly: Talking about viruses does little. Not talking about them does little (the people who would listen probably know already). Running Windows spreads viruses. Running anything else stops them.

      The increased network traffic is there without the extra e-mails anyway. Notifying the sysadmin of the infected boxen is, IMHO, a Good Thing [tm]. The trick is getting that message to the right person.

      Yeah, job security. Bear in mind that for many of us, our unofficial job is to make ourselves unnecessary. 8-)

  31. please mod parent down by Anonymous Coward · · Score: 0

    completely irrelevant, and sounds copy & pasted

  32. It's viewed as promotion by mcrbids · · Score: 5, Interesting

    One of my clients is an ISP - and they *want* the bounces to go out for the simple reason that it broadcasts to the world that "your mail is safe with us".

    So the bounce messages go something like "Our mail server detected a virus in an email you appear to have sent, and we protected our customer ... For more information about our services come to --URL--"

    I don't know if it's effective at all, but it sure doesn't cost much - the virus notification is essentially a mild form of SPAM which few people really get up in arms about.

    Just to understand, there are market conditions behind those virus notices...

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:It's viewed as promotion by lumpenprole · · Score: 1

      That seems remarkably ridiculous as it's their bandwidth that's getting toasted. I was on vacation in the deep maine woods when the sobig hit it's stride. obviously, all three of my main email accounts went over limit. It also tied up other email accounts getting bouncebacks from my isp's server. I think they were a little peeved at me.

      --
      Disclaimer: MINAA (Mummy! I'm Not An Animal!)
    2. Re:It's viewed as promotion by JoeBuck · · Score: 1

      It appeared to me that the virus companies were using their bounce messages to advertise their services. But since the virus companies know full well that all SoBigF viruses have a fake return address, isn't this false advertising?

    3. Re:It's viewed as promotion by EvilBudMan · · Score: 2

      >>I don't know if it's effective at all, but it sure doesn't cost much - the virus notification is essentially a mild form of SPAM which few people really get up in arms about.

      We'll count me as one of the few. I think that Symantec and Network Associates should be counted as spammers now because of this.

      Spam is Spam. There ain't no mild form.

    4. Re:It's viewed as promotion by Anonymous Coward · · Score: 0

      You work for a spammer. Hope you're proud.

    5. Re:It's viewed as promotion by Jokkey · · Score: 1
      One of my clients is an ISP - and they *want* the bounces to go out for the simple reason that it broadcasts to the world that "your mail is safe with us".

      Messages like that have the opposite effect on me. They broadcast, "We don't understand the concept of mass-mailing viruses that forge their sender addresses, so here's some junk mail for you."

      Of course, I'm also of the opinion that virus scanning ought to be a standard feature offered by ISPs (especially with excellent free software like MIMEDefang available to help), so advertisements of an ISP's virus scanning aren't going to impress me whole lot.

    6. Re:It's viewed as promotion by GigsVT · · Score: 1

      They broadcast, "We don't understand the concept of mass-mailing viruses that forge their sender addresses, so here's some junk mail for you."

      To people that know what the hell is going on inside the "magic boxes", yes.

      It's the unfortunate fact that the people making the AV buying decisions are often not part of that group that makes it worth sending trash messages.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  33. Um... by Realistic_Dragon · · Score: 2, Insightful

    Wouldn't it be better to blame those resposible for Outlook for Outlook worms? (Be it users who fail to patch, admins to deploy it, Microsoft for writing it on one drunken weekend that involved a lot of monkey hookers and a boat load of cocaine.)

    It's certainly better than blaming a _client_ problem on the _network_ which when it was designed didn't anticipate (understandably) a near monoculture of such vunerable products being deployed.

    --
    Beep beep.
    1. Re:Um... by jafiwam · · Score: 1

      It would be a lot better if Outlook were not vulnerable, and those people who had vulerable versions patched them.

      Note however, SoBig.F is not an Outlook exploit. It is a "stupid user" exploit that requires the user to click on the attachment. Mozilla Mail, Eudora and all others are just as vulnerable. (Windows operating system is the only common denominator.)

      Once installed on the machine, SoBig uses its own SMTP engine to send mail. True it uses messages from the contacts, but also from cached web page files and text files on the hard drive.

      The article submitter incorrectly implied that SoBig.F is an Outlook-only problem. It is not.

      http://www.sophos.com/virusinfo/analyses/w32sobigf .html

      and

      http://www.sophos.com/support/disinfection/sobigf. html (Question 6)

  34. mod parent up! by Anonymous Coward · · Score: 0

    good advice

  35. Just got my hand slapped by Data Security by RobertB-DC · · Score: 4, Interesting

    I just got a call from the Data Security guy in my office. I've had run-ins with him before, because their scans of my PC would occasionally find that I run Eudora for my personal email rather than routing it through the corporate virus portal known as Outlook Express. My bosses have been supportive -- as long as I get my work done, who the heck cares what I've got installed?

    Now, I get 50-100 messages from "helpful" virus checkers telling me that I sent them a virus. Duh, of course I didn't. But what's worse is when they try to help my by sending the damned virus back to me! So my Eudora inbox fills up with viruses. No problem, I just delete them, right?

    But we've got real-time virus scanning installed, and the admins take a dim view of tweaking it to skip certain directories. It finds that In.mbx contains a virus and kills the file. Poof, there goes my Eudora inbox. Frustrating, but it was full of junk anyway.

    This morning, though, I get a call from the head Data Security honcho. Norton called mommy when it found the virus, and did it often enough for me to show up on the admin guy's radar again. Now, I'm going to have to quit using Eudora at work, just because brain-dead virus protection is sending me viruses! I'd fight it again, but I have to agree -- if I keep downloading viruses, I'm part of the problem.

    Thanks for nothing, AV companies. All you're doing is keeping yourselves in business with false virus alerts. Or maybe that was the "2. ???" in between "1. Spread Viruses" and "3. Profit!"

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    1. Re:Just got my hand slapped by Data Security by Anonymous Coward · · Score: 0

      "...when they try to help my by sending the damned virus back to me!" Sorry, but that is just wrong. No anti-virus programs repsonds with the infected file/email attached.

    2. Re:Just got my hand slapped by Data Security by Czmyt · · Score: 1

      More like a brain-dead admin for not scanning your incoming e-mail and blocking the viruses.

    3. Re:Just got my hand slapped by Data Security by RobertB-DC · · Score: 1
      No anti-virus programs repsonds with the infected file/email attached.

      I figured I'd be able to test out your statement... but the cutoff date for the latest SoBig has passed, and I only have two bounce messages today! Either that, or Postini has added virus bounces to their spam blocker. Neither of the bounced messages includes a viral attachment, though one recipient's Outlook gateway attatched a text file:
      File attachment: details.pif

      The file attached to this email was removed because files of this type are not accepted for delivery by your email gateway.
      Perhaps you're right -- maybe MacAfee & co weren't sending me the viruses, it could have been something in the mail gateway software. But if I made such a mistake identifying the culprit, I'm probably not the only one.

      Ok, I've got to go close Eudora and turn the virus scanner back on before Data Security throws a fit. The things I do for Slashdot!
      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    4. Re:Just got my hand slapped by Data Security by Anonymous Coward · · Score: 0
      Maybe you should tell IS to fuck off. then you can use eudora allday long while you're unemployed.


      ass muncher.

    5. Re:Just got my hand slapped by Data Security by RobertB-DC · · Score: 1

      More like a brain-dead admin for not scanning your incoming e-mail and blocking the viruses.

      No, that was his point... the corporate Outlook server does scan incoming email to block viruses. The admin was upset that I was running a non-corporate-controlled email program (Eudora), and that he *couldn't* block the viruses.

      That's why I see his point -- we got hit by the RPC worm, and it was probably due to some sales dude plugging an infected laptop in behind the firewall. How can he tell them to submit to corporate virus control, and not at least complain when I use non-corporate email software?

      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    6. Re:Just got my hand slapped by Data Security by RollingThunder · · Score: 1

      What was his response when you pointed out his mail server wasn't filtering the damn viruses in the first place?

      The software you run has nothing to do with if people send you viruses. The SMTP server is supposed to block them... or does this guy think it's actually feasible to do endpoint virus filtering?

      Sorry, but I've seen too many people learn how to kill off their virus scanners because they think it's slowing their system down to a crawl. (Of course, it's not that Bonzi Buddy's fault, no - it's that pesky antivirus program)

    7. Re:Just got my hand slapped by Data Security by Czmyt · · Score: 1

      Okay, sorry, I get it. I'm surprised that they let you connect to outside POP/IMAP servers. To get around this, maybe you can use one of those e-mail services that will let you get your POP messages and view them through a Web page.

    8. Re:Just got my hand slapped by Data Security by RobertB-DC · · Score: 1

      To get around this, maybe you can use one of those e-mail services that will let you get your POP messages and view them through a Web page

      Actually, the only email I receive via Eudora is the mail sent to my public email addresses. Thanks to the generosity of the dixie-chicks.com host, that mail is filtered by Postini -- otherwise, it would be completely useless due to spam.

      My real email address -- the one I use to communicate with people I know personally -- is online, hosted by Neologism Productions, a high-quality, low-cost mom-and-pop operation out of Plano, Texas.

      I seldom have any spam problems there, even without filtering, though I get hit by an occasional dictionary/common-name attack. I inadvertently viewed a spam message sent to an alias, triggered a web bug, and started receiving 2-3 spams a day to that alias. That alias, sadly, is no more...

      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    9. Re:Just got my hand slapped by Data Security by Drathos · · Score: 1

      BS!

      I was getting 20-30 bounce back messages a day to one of my throw-away addresses. At least 75% of these contained the offending .pif attachment. Aside from the sheer quantity of incorrect messages received, I didn't mind (using pine on Linux, and I ended up filtering them myself), but I can't imagine how annoyed I'd've been if I had to download them over a dial-up account.

      I'm still not sure how that address got harvested for spoofing tho. It's for a forum account and the e-mail is not publicly viewable.

      --
      End of line..
    10. Re:Just got my hand slapped by Data Security by kelleher · · Score: 1

      I read your first post and nearly flipped. Read the rest of the thread, got to this post and realized you're one of the few people floating around /. that actually bothers to read "negative" responses instead of just flaming back. You now get why the corp SAs may seem like jerks half the time - it's their job to keep the company running, not keep a power user happy. Most of them will even admit to using all the "unsupported software" at home that they refuse to install at work.

    11. Re:Just got my hand slapped by Data Security by mbessey · · Score: 1

      "Sorry, but I've seen too many people learn how to kill off their virus scanners because they think it's slowing their system down to a crawl."

      Hey - it definitely happens. Yesterday, my system was running at 100% CPU utilization for no apparent reason, so I fired up Process Viewer, and I see that Norton AutoProtect is using 89% of the CPU. I have no idea what it was doing, since there weren't any windows showing any Norton-related activity.

      The best part is that I had AutoProtect *turned off* in Norton's preferences. What a great piece of software...

      -Mark

    12. Re:Just got my hand slapped by Data Security by Anonymous Coward · · Score: 0

      So, you think Eudora is immune to SoBig?

      Well, you're wrong. You deserve to have your mailbox deleted for being such a major dumbass.

    13. Re:Just got my hand slapped by Data Security by maggard · · Score: 1
      What was his response when you pointed out his mail server wasn't filtering the damn viruses in the first place?

      What part of this bozo installing his own email client and then downloading his own infected personal email from some non-company server to the company's desktop PC without going through the company systems eluded you?

      The corporate email filter may well have been working fine. Indeed it seems that the only thing saving the company from a possible nasty outbreak was that on-access scanner our protagonist is so bitter about.

      I'd also guess that after this bozo showing up often enough on the virus scans with mbox's full of infected emails there's going to be a discussion with his supervisors about this sort of activity, possible repercussions, and the phrase "career limiting behavior & attitude".

      Get those resumes ready folks.

      --
      I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
    14. Re:Just got my hand slapped by Data Security by RollingThunder · · Score: 1

      The one word "personal". I admit, I glossed past it.

      I had understood that he preferred to use Eudora instead of OE, for work. If he's pulling in unfiltered mail, then yeah - I can see the problem, and I have no sympathy for him on that front.

      His data people seem to be ass-backwards about it though. From his phrasing, the problem is that he's using Eudora for his personal mail - not that he's getting personal (unfiltered) mail at all. As long as you pull in clean mail (and your bosses are fine with you doing a modicum of personal items at work, which most are), then I don't care what you use to read it... but it better be secure.

  36. The worst of it is ... by JSkills · · Score: 1
    The worst of it is when you've got an email address like "webmaster at goofball.com" and thousands of people have you in their address book and some of them get the virus that spoofs YOU as the return email address.

    I'm still fielding like 400 auto-generated emails from various anti-virus software each day. The author's suggestion to simply stop the alerts is not that far fetched at all.

    Obligatory bad analogy: it's like pelting someone with rocks in order to warn them they're about to be run over by a car (and then continuing to pelt them with rocks even after the car has passed and is way down the block).

    1. Re:The worst of it is ... by stratjakt · · Score: 1

      Hey if I was crossing the road, listening to my KICK ASS WIFI IPOD and was about to get flattened by a car, I sure hope I get pelted with some rocks.

      But considering the headers are faked, it's like pelting a crowd of bystanders who aren't even near the road with rocks, and repainting the yellow center line so the car will hit them, a la Bugs Bunny.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:The worst of it is ... by JSkills · · Score: 1

      thank you for correcting my analogy - it was a bit flawed

  37. Not the problem by Spazmania · · Score: 2, Interesting

    The mail filters that send out a message for each virus message received are not the problem. Indeed, they're just following the basic requirements for bounced messages listed in RFC 2822.

    THE problem is the mail filters which also send a second message to postmaster@whatever domain. Whatever brainiac thought that one up should be shot.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    1. Re:Not the problem by Anonymous Coward · · Score: 0

      Well, whatever the RFC says, it makes no sense to send anything to the address in the "From" header in case of virus/spam since the address very likely fake.

    2. Re:Not the problem by Spazmania · · Score: 1

      The RFC mandates a reply to the envelope sender, not the From header. You can generally find the envelope sender in the Return-Path header. Sending to the From header is broken behavior.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  38. Thousands of Bounce Messages Bullshit by Czmyt · · Score: 1
    I've written to some of the people whose systems spew these bounce messages to complain. One of their admin's first told me that it was helpful in cases where people send a file that has a piggyback attachment. Ya, how often is that the case, 1 in 100000 times nowadays? Then he later said that it was good to inform people that there's a virus out there pretending to be from them. Ya, even if that's true, then send me a single bounce message, not 1000 of them!

    Either the antivirus software has to get a lot smarter about which viruses fake the headers (and not send bounce messages in those cases), or there needs to be a netiquette against sending bounce messages for virus infected messages in all cases, or these antivirus companies that produce this crappy software need to be added to SPEWS. I am really sick of this problem personally.

  39. His two minutes by muffen · · Score: 3, Insightful

    I find this most interesting.

    Until recently, no e-mail worms spoofed the email address. F-Prot obviously never had the functionality of replying to infected emails.

    Until just recently, it was really good to reply to the sender alerting him about the fact that he sent out a virus/worm. Where was F-Prot back then??

    The way I see it, it's been three steps.
    Step 1: No email worms.
    Step 2: Email worms that didn't spoof the sender (replying to sender is good).
    Step 3: Email worms that spoof the sender (replying to sender is bad).

    Seems to me that F-Prot is complaining that everyone hasn't reached step 3 yet (with spoofed sender addresses, infected emails shouldn't be replied to), even though we pretty much reached it just now. Before Sobig, even though there were worms that spoofed the sender, they were a minority. After Sobig, spoofing worms are a majority, which means that AV products need to change. This won't happen in a second like it did for F-Prot, because most AV vendors didn't skip step 2 like F-Prot did.

    This coming from a company who 95% of computer users never heard, and who never even added the functionality of replying to emails even though it was really good until just recently, makes me believe his just looking for his two minutes of fame.

    1. Re:His two minutes by Anonymous Coward · · Score: 0
      Until recently, no e-mail worms spoofed the email address.

      You consider "I love you" and KLEZ recent?!

      ~~~

    2. Re:His two minutes by Juggler · · Score: 5, Informative
      Not true, most worms and viruses have spoofed the From address for quite a long time now.

      Autoreplies have always been problematic at best, which anyone who's experienced the annoyance caused by vacation programs on public mailing lists can attest to. Autoreplies to automatically generated traffic have always been a no-no.

      Viruses and worms are clearly autogenerated traffic.

      Also, although 95% of computer users have never heard of FRISK, Fridrik has been a respected member of the A/V community since it very began and wrote one of the very first virus scanners.

      Disclaimer: I work for FRISK, writing said e-mail filter code. But I can tell you with authority that the decision was taken a long time ago.

    3. Re:His two minutes by Anonymous Coward · · Score: 0

      You should refrain from letting your hands type checks that your brain can't cash.

      The specific anti-virus product isn't (or shouldn't at least) in most cases responsible for replying to infected e-mails.

      F-Prot antivirus has been pluggable into a number of freely available email scanning systems (for example amavis) for a couple of years I believe, and has performed its job of scanning files and identifying virii well, it's not F-Prots (nor any other specific anti-virus products imo) place to reply about virus infected emails, its the administrator who should configure the email system whether reply emails are sent or not, if the antivirus program does detect a virus, in any case the antivirus program is of course limited to scanning files and reporting viruses, it does not replace entire email systems!

      At the moment there is available some sort of mailserver edition of F-Prot which comes bundled with plugins for popular MTAs, and infected-message replies are most likely implemented.

      You keep making statements about F-Prot skipping some features, and not having added the functionality of replying to emails, when you obviously don't know the first thing about virus/spam scanning email messages. Please read up before stating your premature assumptions as facts on the internet.

      What a troll!

    4. Re:His two minutes by Tripster · · Score: 1

      I remember using the F-Prot Antivirus software back in my DOS days for scanning files on my BBS, this was back in 1992, they've been around since 1986 I believe.

      Just because you're too young to know them doesn't mean they haven't always been there. Indeed, just go to their site and you will be able to download a FREE DOS version of their virus scanner to this day.

      They also offer a Linux version which is FREE for personal workstations, it's command line based.

      Oh, and when I was using it on the BBS, it was FREE for us SysOps as well as long as we offered the shareware version for download to help promote.

    5. Re:His two minutes by muffen · · Score: 1

      You should refrain from letting your hands type checks that your brain can't cash.

      Nice... I'm sorry to say I'm too tired to start a stupid postingwar on a messageboard.

      The specific anti-virus product isn't (or shouldn't at least) in most cases responsible for replying to infected e-mails.

      And this statement is based on your surveys.. right?

      You keep making statements about F-Prot skipping some features, and not having added the functionality of replying to emails, when you obviously don't know the first thing about virus/spam scanning email messages.

      Please tell me what it is I don't know about scanning, and how scanning is relevant to replying.

      What a troll!

      Yes, my post was a troll.

    6. Re:His two minutes by muffen · · Score: 1

      Just because you're too young to know them...

      How is my age in any way relevant to computer users in general?
      I do appreciate you telling me your F-Prot usage history though, I really appreciate it.

    7. Re:His two minutes by Anonymous Coward · · Score: 0

      The poster excused your lack of knowledge on F-Prot's history due to age. You would prefer an alternative?

    8. Re:His two minutes by Brainchild · · Score: 1
      This coming from a company who 95% of computer users never heard, and who never even added the functionality of replying to emails even though it was really good until just recently, makes me believe his just looking for his two minutes of fame.

      If you haven't heard of F-Prot, Fridrik Skulason, or Frisk Software International in connection with virus-scanning software, you've had your head some pretty nifty-smelling sand for over ten years. Back in 1992, F-Prot was one of the best virus-scanning software packages available for MS-DOS, and it was even freely downloadable over what was in those days called "the Internet".

      Fridrik Skulason has actually had a bit more than two minutes of recognition (viz. this History of Computer Viruses); F-Prot has been continually available and updated since 1990---by my reckoning, that's more like thirteen years.

      Beware of those who ascribe their own ignorance to 95% of everyone else.

      --

      :: "I am non-refutable." --Enik the Altrusian ::

    9. Re:His two minutes by Tripster · · Score: 1

      No offence to your age, I was just pointing out that this guy has had a few "2 minutes" when it comes to anti-virus software. F-Prot is more popular in Europe that here now I believe.

      They've always seemed like a more reasonable company to deal with compared to McAffee/Norton/etc. That and a general good attitude towards system admins since they know those are the people who recommend good stuff to others and those others tend to trust someone who knows computers in general.

      This guy does have a valid point, as soon as I saw the damage SoBig.F was causing I turned off my scanner notifications on all servers, seems useless to leave it on any longer since most of the recent viruses have been using false return addresses anyway. I kept the admin notification on for monitoring.

  40. Microsoft EULA Security Update enclosed: by Anonymous Coward · · Score: 4, Funny

    Critical Update:

    A security issue has been identified that could allow an attacker to compromise a computer running Microsoft Windows and install Linux on it. You can help protect your computer by installing this EULA from Microsoft. After you install this EULA, a NULL update will be downloaded for your benefit.

  41. No here is a better use by codepunk · · Score: 1

    Change the bounce messages to something like the following.

    Try our new penis enlargement patch and make your lady love you forever.

    Use the bounce messages as vehicle for spamming.

    --


    Got Code?
  42. Not doubling traffic. by Samurai+Cat! · · Score: 2, Insightful

    'If mail filters send out one message for every copy of Sobig.F received, they are in effect doubling the amount of traffic. This makes them a part of the problem, not a part of the solution.'

    Not quite. Fortunately the alert emails are (usually) just text, and not some several-kilobyte attachment. They may be doubling the messages, but certainly nowhere *near* the bandwidth used.

    One would hope the anti-virus tool folks could build in ways to sniff out "Oh, this is a SoBig-laden email" and *not* send out the completely useless alert to someone's address that happened to be the random "From" address used.

    --

    "People" using "unnecessary" quotes should be "shot".
    1. Re:Not doubling traffic. by kindbud · · Score: 1

      Not quite. Fortunately the alert emails are (usually) just text, and not some several-kilobyte attachment. They may be doubling the messages, but certainly nowhere *near* the bandwidth used.

      But they are doubling the sockets, file descriptors, and inode entries in the mail spool on mail servers all over the internet. The bandwidth utilization is not what brought my mail servers to their knees. It was resource exhaustion. This in turn, increased bandwidth as my servers started responding with 4xx temp fail codes, causing many, many messages to get retransmitted several times before making it through.

      --
      Edith Keeler Must Die
    2. Re:Not doubling traffic. by bedessen · · Score: 1

      I don't know what bounces you are getting, but all of them that *I* receive include a full copy of the attachment. Truly, a stunning show of incompetance.

  43. Proprietary Pish by Anonymous Coward · · Score: 0

    Funny thing is I have seen some mail servers bounce the sobig mail and include the entire mail - including the attached virus - in the reply.

    I envisage some mail servers are continually sending each other the sobig virus as they bounce each others bounces for containing the virus.

  44. Matter of education and responsibility by stopbit · · Score: 2, Informative

    Until the anti-virus software developers, M$ and the general e-mail population can out-wit a 12 year old script kiddie, no progress will be made.

    --
    ~insert tech sarcasm here~
  45. Bounces are good, just not for Sobig.F by Digital_Quartz · · Score: 1

    A bounce is a good thing, since it tells the sender of the virus "Hey, you've got a virus". This encourages the sender to remove the virus from their system, and results in a net reduction of network volume.

    The problem, of course, is that many of these email worms forge the from. But... the virus filter takes the time to identify that there is a virus, and the filter knows that it's Sobig.F, so why can't the filter also be smart enough to not send a bounce FOR Sobig.F? This seems like it should be trivial to implement.

    Ahh well... Speaking as someone who works at a data switch and router company, more network traffic is a good thing. :)

    1. Re:Bounces are good, just not for Sobig.F by pe1chl · · Score: 2, Insightful

      Warning messages to the sender were good some time ago, but should be removed from any scanner now.

      ALL "modern" viruses fake the return address.

  46. Why shouldn't ISPs block viruses? by indros13 · · Score: 1
    I am not a programmer, computer tech, or anything else. I am smart enough to figure out some decent filtering through Outlook Express that usually kills most virus emails and I have one of those real-time scanners going to pick up the stuff.

    However, why can't I opt with either my ISP or email provider to have virus emails deleted immediately from the server? It would seem to be economical for either to do so, because they would save server space and prevent the spread of the virus by keeping dumb users from opening the attachments.

    Furthermore, should they even have to ask? Virus emails are not really personal or private email, it's junk. I doubt there would be much complaint (from the average Joe) if the Post Office just started throwing away those stupid Valupak coupon things or other mail addressed to "our friend at ADDRESS."

    Again, I have no idea what is technically feasible, but perhaps someone could enlighten me as to what an ISP or mail provider could do to cut the spread of virus-laden email before the end user has a change to see who loves them...

    --
    Under capitalism man exploits man. Under communism it's the other way around.
    1. Re:Why shouldn't ISPs block viruses? by shish · · Score: 1

      Valid emails can be picked up as viruses, and valid viruses (eg me using back orifice to remotely fix a friend's PC) don't get through at all...

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    2. Re:Why shouldn't ISPs block viruses? by pe1chl · · Score: 1

      However, why can't I opt with either my ISP or email provider to have virus emails deleted immediately from the server?

      Because you have opted for the wrong ISP?
      My ISP offers this add-on mail virus scanning, and about half of the ISPs here do the same.

      In fact, my ISP has installed a "free" Sobig.F virus scanner for all subscribers. (the scanning for a complete list of virus has an extra charge)

  47. Simple by FreeLinux · · Score: 1

    helo valid?
    mailfrom: xxx
    rctpto: xxx
    data .exe|.bat|.cmd|.vb*|.scr|.jsp|.com|.sys|.bin|..... .

    550 For security reasons this form of message is denied on this system.

    connection closed.

    1. Re:Simple by 1010011010 · · Score: 1

      Here ya go, except that it returns 551, not 550, and says this:

      551 "5.7.1 Attachment '$file' not allowed"

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    2. Re:Simple by klaxor · · Score: 2, Insightful

      This has already been implemented; for this reason, I can't send executable attachments to some of the people I know...

      I'm a programmer. I write games in my spare time. I really don't feel like mailing a floppy to everyone (friends and family) who might find my game interesting.

      Yeah, I understand that most executable attachments are probably viruses. However, this doesn't justify the intrusion on my freedom - I would expect a company to just delete virus emails, rather than a blanket rejection of something that could be a virus, but might be very important to the recipient.

    3. Re:Simple by FreeLinux · · Score: 1

      Try replacing the extension on the attachment and include instructions in the email on how to change it back. Setup.txt or Setup.exe.txt will pass through most of these filters because it does not have an executable extension. Additionally, Windows will not be able to execute it as it will instead try to open the file in Notepad. Instructing your recipients to rename the file after saving it to disk is simple and easy, and they will be able to execute it after that. It's rather like having to do a chmod on Unix before you can execute.

      Now, this might change in the future when someone puts out a virus with the renamed extension and includes instructions to rename the virus and execute it. But, that virus hasn't surfaced yet and will probably not spread very well any way. So, until such time this technique will work to bypass most attachment filters.

    4. Re:Simple by pe1chl · · Score: 1

      Our mail virus scanner will detect this, and refuse your .exe that was renamed to .txt as an executable file (which is not allowed past the firewall).

      Renaming it, then zipping it and renaming the zip to .txt won't work either.
      Or the same repeated a number of times.

      Of course, commercial scanners often are too dumb to find things like that.

    5. Re:Simple by FreeLinux · · Score: 1

      Setup.exe.txt will pass through most of these filters

      It sounds like you have a most excellent scanner. There are many scanners that can unzip and check archives but, I was not aware of any that could decipher recursive zipping and renaming. Which scanner are you using?

    6. Re:Simple by pe1chl · · Score: 1

      A version of amavis that I fixed myself.
      But I think current versions of amavis do this as well.

  48. The need for digital signatures. by pope1 · · Score: 1

    With the way our mail system is now, mail servers accepting and routing mail from any client w/o the need for any real kind of authorization or identity matching, we are screwed.

    Most modern clients support digitally signing mail, either via PGP or S/MIME. This needs to become a lot more widespread, with 3rd party verification of signatures ala VeriSign/SSL-certs. When it is in place we can safely delete any mail we get w/o a real signature, and go about our business. If someone with a legit signature DOES join the dark side, they are stamped, labeled, and easily filtered.

    Does anyone see any arguments against digitally signed mail, besides the large over-head of layering security onto a system that started w/o any, by design?

    --
    /* * pope1 */
    1. Re:The need for digital signatures. by Zigg · · Score: 3, Insightful

      Does anyone see any arguments against digitally signed mail, besides the large over-head of layering security onto a system that started w/o any, by design?

      The fact that the private keys are going to be stored on PCs owned by people who don't grok public/private key care one bit. Not to mention that a new worm should have no trouble lifting those keys off the box and spraying them around for a new forge attack.

  49. Speaking of bad email filters... by Anonymous Coward · · Score: 4, Funny

    We have Mail Marshall here at work. I got the following mail from the system yesterday...

    MailMarshal (an automated content monitoring gateway) has stopped the following email for the following reason:

    It believes it may contain unacceptable language, or inappropriate material.

    Message: B000038072.00000001.mml
    From: xxx@xxx.com
    To: xxx@xxx.com
    Subject: Re: So Whuz Up?

    Please remove any inappropriate language and send it again.

    The blocked email will be automatically deleted after 5 days.

    MailMarshal Rule: Inbound Messages : Block Unacceptable Language Script Offensive Language (Basic) Triggered
    Expression: asshole Triggered 1 times weighting 5


    Email security by MailMarshal from Marshal Software.


    So the message tells both the ortiginal sender and I that it won't deliver the email because it contains the term "asshole". So it lets me know that by sending me an email telling me the exact same word that was supposed to be filtered? It seems like we've got a hypocrytical mail filter here :(

    1. Re:Speaking of bad email filters... by windex82 · · Score: 1

      I believe its because the person applying the mail filter will be wanting to get the feedback, most will be used by parents monitor their kids, watching what employees are sending, and receiving, and in general if THEY have chosen to block the words THEY should be mature enough to see the results, now if its sending a copy to the intended user and not just the admin thats a different story. It sends it to the original sender because, they have already used the word, so its fairly assumable they have no problems with such a word.

      You also have to remember, their not all designed for just single bad words. Some may use to monitor for phrases like "i killed" "i will kill" "going to buy crack"...

      starting to get the picture?

  50. Re:iHateSpam by Smitedogg · · Score: 1

    Ironic, you spam on a thread about spam...

  51. Manual Intervention Required by TwistedGreen · · Score: 1

    It seems that automatic filtering software is failing, and e-mail viruses are only becoming more and more clever, with ever more randomized characteristics. The solution to this problem is obvious: someone needs to be there to look through all the e-mail that goes through the Internet and filter out the viruses and spam that nobody wants.

    So how about this idea? The government mandates that all ISPs to have a group of people on-site full-time, 24/7, to scan through every e-mail message to go through their mail servers. If it is a known virus or spam e-mail, they would set the evil bit to true, and thus render it invisible to both future mail servers and recipients. Spam and viruses can be completely eliminated using this method!

    I would recommend having a team of seveal dozen with short, 4-hour shifts rotating throughout the day in order to minimize the effects of fatigue. Boredom shouldn't be a problem, due to the sheer stupidity of much e-mail that would have to be certified. In the future, this could even be outsourced to a work-at-home type environment, where all that is required is a computer with a capable internet connection and some time!

    This may even introduce a new way to tax e-mail, by adding a minute "certification charge" to have your e-mail certified genuine by a third party. Low monthly subsription rates could also be available, allowing you to send an unlimited number of e-mails at a fixed price.

    What a grand future these e-mail viruses have created! Thank you, Outlook!

  52. Agree 100% by tarnin · · Score: 1

    Seen this on my network at work. Most of the from addresses are faked anyway so were getting bounce backs from these anti-virus software daemons saying that we sent so and so a virus. Now, not only is our network underheavy load from the actual sobig.x virus but were also dealing with these bogus e-mails.

    Server load went from 55% usage up to 98% usage. 17% of all emails comming in were these bounce backs to either us or our customers. 17%!! This is totally unexceptable expectially when most of not all of the current breed of e-mail bourn virus's fake the e-mail address.

    Personaly, I think this option should just be removed totally from the software packages. Barring that, have it off by default not on. I have enough spam and virus emails comming in without having to deal with the extra load of warning emails from poorly configured virus walls.

  53. Here's how to do it for "free" by Anonymous Coward · · Score: 0

    See this comment from another discussion on protecting your mail server.

  54. Re:Brithday! by Anonymous Coward · · Score: 0

    By that logic, also a mean fisting was administered.

  55. marketing loves notices by Anonymous Coward · · Score: 1, Funny

    Marketing guys love email notices because it raises awareness that the product is working. This is independent of it being a good idea.

  56. Of course not. by SuiteSisterMary · · Score: 3, Interesting

    At no point should a response be generated for a virus. Maybe five years ago, when viruses tagged along with legitimate data, but nowadays, a virus generates it's own delivery system, and there's no point to a bounce.

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  57. Challenge/response sucks by letxa2000 · · Score: 3, Interesting
    Yup, I agree that the whole idea of "bounce" has been killed by spam and by viruses.

    The statement "If mail filters send out one message for every copy of Sobig.F received, they are in effect doubling the amount of traffic. This makes them a part of the problem, not a part of the solution" is also what I've been saying for months. This is a condemnation of challenge/response. Challenge/response is flawed conceptually in that it assumes the return address is correct. In an age of spam (which it supposedly addresses) and viruses it is absurd to believe the return address exists and sending email to the return address just multiplies the problem.

    Challenge/response was never well thought out. It shifts the burden of spam filtering to the person that sends email to that user, and tends to mailbomb innocent users that happen to have their addresses forged by spam or viruses. All so someone can supposedly enjoy a spam-free existance with no thought to the hassle they are creating for others and the spam that they are creating by mailbombibf C/R challenges to forged addresses.

    Hopefully with much better filters already available Challenge/response will just disappear. It's bad technology.

  58. Entourage on Mac by Perl-Pusher · · Score: 1

    Entourage has the absolute worst filters I've ever come across. I made the mistake of enabling the Junk filters and now it trashes every other good message and totally misses spam. I have rules for things in the address book but it totally ignores them. Some rules don't work at all, but when you highlight a bunch of messages, right - click and apply rule, suddenly it discovers that yes, those messages are in the rules. What is really bad is that once I enabled junk mail filtering, it still does it after un-enabling it! I'm going back to mail.app

  59. yesterday and the day before were really bad... by AssFace · · Score: 1

    The past two days had a ton of them - with that was the original email coming in, then the message sent to the user, the admin, and three other backup/side admins notifying that there was a virus. Then the pop-ups on two server consoles.

    It was getting annoying - you would think that I would just disable all that notification except the admin... but you'd be wrong.

    That is all just on our Exchange server though, no outside bandwidth.

    --

    There are some odd things afoot now, in the Villa Straylight.
  60. What is that?!? by Anonymous Coward · · Score: 0

    Anyone notice that white dot right below the banner ad at the top of the main /. page?? What is it??? Is it a secret message from an alien race?

  61. No kidding.. by nurb432 · · Score: 1

    This is news? Geesh.

    But perhaps with more awareness of the insanity this is causing, admins will change their filters to NOT bug people that have had their addresses faked..

    Actually at this point I get MORE of the 'kind notices' then actual infected emails. A lot more.

    --
    ---- Booth was a patriot ----
  62. huzzah by The+Unabageler · · Score: 1

    for the letter. i'm sick of these spam bounce mails cluttering up my caughtspam folder.

    --
    perl -e '$_="\007/4`\cp%2,".chr(127);s/./"\"\\c$&\""/gees; print'
  63. IT'S TIME FOR THE MICROSOFT SKULL FUCK!!!! by Trolling4Dollars · · Score: 1
    When you are feeling down and the worms are spreading round, FUCK the skull of Microsoft! FUCK the skull of Microsoft!

    When you have patches galore and your eyes are all sore, FUCK the skull of Microsoft! FUCK the skull of Microsoft!

    They say security's their focus, but their bug list's a swarm of locusts! FUCK the skull of Microsoft! FUCK the skull of Microsoft!

    Bill Gates can't write a program for 640K o RAM! FUCK the skull of Microsoft! FUCK the skull of Microsoft!!

    Although there's trusted computing and Palladium in our future, MS is such a target that even those will need some sutures!

    How can you trust something you can't see? (the code) Even Christians have a hard time convincing me!

    So no matter what they say, we all know MS is sooo teh ghey! FUCK the skull of Microsoft! FUCK the skull of Microsoft!

    Yep. It's a troll. Could someone set it music please? ;P

    1. Re:IT'S TIME FOR THE MICROSOFT SKULL FUCK!!!! by Anonymous Coward · · Score: 0

      and only an hour ago i had my 5 mod points. :P

  64. Use wormy E-mail filters by Anonymous Coward · · Score: 0

    I mean, come on!

    We aren't having problems with internet lice! Why should a lousy filter work? Use the right tool for the job and install some wormy filters and all will be okay.

  65. Virus mail autoreplies... by Anonymous Coward · · Score: 0

    Only a fuckin' moron configures his email antivirus system to autoreply to the claimed sender of incoming infected emails, and the average typical email sysadmin is, uhh, well... Oh, nevermind.

    1. Re:Virus mail autoreplies... by Spazmania · · Score: 1

      If you can't deliver to the listed recipient for any reason, the RFC states that you MUST return a message to the envelope sender. Just in case there is anything unclear about the word MUST, they go on to explain that MUST means that EVERY correctly written email software package will do so.

      Does the virus problem indicate the need for a change to the standards? Perhaps. But until the standards are changed they remain the standards and any program which doesn't perform to the standards remains broken.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  66. Bounces are spam and should be treated as such by Anonymous Coward · · Score: 0


    If the bounce mentions the virus scanners name then its promotion aka spam, just like the ones that tack it on outgoing mail, branding is all about pushing the products name into peoples minds

    how many people see messages such as

    "a virus was detected by superscannr (www.superscan.viruscompany.com) in your attachment it was removed, "

    or

    "this email was checked for all known viruses by superviruscanner, for more details visit www.superviruscanner.com"

    keep plugging that name into managers/IT buyers minds

  67. The response I got - it IS part of the problem by ctwxman · · Score: 5, Interesting

    I received hundreds of bouncebacks from one organization. So, I did a whois and wrote to the contact listed:
    My name is Geoff Fox and I am writing because I have received hundreds upon hundreds of message bounces from your **** mail server.
    These messages are not originating with me. These are SoBig virus generated and are spoofing my address as the return.
    I am asking nicely, but I need you to take action immediately. I am attaching a bounce message so you can see what I've received. From the headers it looks like they're actually coming from ***.com
    Sincerely, Geoff Fox

    I did get a response... but not what I had expected.

    Geoff, Thanks for raising the issue of the SoBig virus infection.
    From the information that you have provided, it does look like the infected machine is located at **** Architecs, Inc. of Harford, CT. Their contact information is provided below.
    Have your IT technical staff contact the admistrative contact or the technical contact below. They may not realize that they have a SoBig infected machine and that it needs to be cleaned.
    (whois stuff deleted)
    It was signed by their Director of IT Security.

    So, even at that level, he didn't realize he was doing something wrong... or that these bouncebacks came from him, not from the site that was infected. And, he felt it was my obligation to do something about it, not his!

    1. Re:The response I got - it IS part of the problem by Anonymous Coward · · Score: 0

      Were those virus-scanner notifications or SMTP bounces? In other words: "Some-fancy-virusscanner has detected that your mail to bl@blab.la contained a virus." or "Your message cannot be delivered: Over quota"? The first kind of bounce is unnecessary, as a virusscanner which can detect SoBig.F should know that the sender is faked. The other kind of bounce is required by internet-law (RFC) and is not as easily avoided. Actually both are required, but the first is a really obvious case in which broken behaviour is better.

    2. Re:The response I got - it IS part of the problem by ctwxman · · Score: 1

      It was bounce number 1 - You sent us a virus. But, of course, I didn't.

  68. Articles explaining how sobig works by jamesmartinluther · · Score: 1

    Some good reading material:

    http://www.lurhq.com/sobig.html
    http://www.lurh q.com/sobig-e.html
    http://www.lurhq.com/sobig-f.h tml

    - James

  69. Re: A thought by Anonymous Coward · · Score: 0

    Maybe you lunix fags could stop making heroes out of hackers, and start to look at them as the bottom feeding dregs that they are.

    Maybe if it wasn't so hip and trendy to h4x0r j00r b0x0r with your m4d sk1llz0rz


    Lunix fags? Hip and trendy? There's an oxymoron if I ever heard one!

  70. Re:iHateSpam by Anonymous Coward · · Score: 0

    if uHateSpam, I suggest you feed it to the Great Hole of Despair.

  71. Re:A thought by Sophrosyne · · Score: 1

    That is somewhat of an interesting thought... If I was still taking sociology classes I would love to do a study on the correlation between weight and virus writing in programmers.
    I don't know if anyone has been paying attention but the last wave of virus authors have been pretty fat.

  72. Replies to the replies? by rhiorg · · Score: 1

    Am I part of the problem if I send a reply to the sysadmin informing them that I don't have the virus and didn't transmit the initial message?

  73. Re:Replacing RAV for QMail on Linux? by blkwolf · · Score: 1
    What about all the emails these virus detectors PREVENT by warning the user about the potential virii in the emails.
    Remember, the average user isnt that smart. We dont want to prevent them from getting their mail. We do want to warn them. Not only this, the warning emails are likely just local anyways, so this isnt going to be too bad of a traffic increase.

    You didn't read the article did you? This isn't about AV software warning a user that an email they recieved might contain a virus. It's about AV software the sends a reply back to the supposed (sender) of the email saying they are infected.
    The problem here is that lately pretty much all email based viruses forge their From: address to make it look like the email came from what is actually an innocent party.

    I use Linux and OpenBSD on my worstations exclusively, with mail programs that can't even render html email etc. The chance of me sending out or spreading an email virus is almost zero, yet I recieved hundreds of bounces warning me that the email I sent out contained a virus, from people I never even heard let alone even sent an email to in the first place.

    "That" is the problem the article was refering to.

  74. Here's what can be done. by Animats · · Score: 3, Insightful
    All autoresponders must start validating the "Received" chain, like SpamCop does. The open source community can help by packaging up a library to do just that, and putting it into any open source packages that generate mail responses. Writers who review programs should downgrade those that have autoresponders. I suggest the term "spamming autoresponder" be used for any program that replies to mail autonomously without checking the "Received" chain.

    Messages from known spamming autoresponders should be blocked by spam filters. A publicly available list of canned text appearing in messages from spamming autoresponders should be made available and placed into mail filters.

    That should deal with the problem.

    1. Re:Here's what can be done. by stevel · · Score: 2, Interesting

      I don't see how validating the received chain helps. That will detect forged headers, but not a forged From address, which is what the viruses do. There is no way to reliably detect a forged From address by looking at the headers.

      Consider - I, and a lot of you too, I'm sure - routinely send out e-mail with a From address that has a domain unrelated to that of the outgoing SMTP server we are using. How can you tell the difference between such messages and those forged by viruses?

  75. What I do by metamatic · · Score: 1

    I bounce any "you have a virus" notification with a 5xx error, as I don't run Windows. Let the fuckwit admin whose system is sending the mail get buried under the bounces.

    Pretty soon it looks like I'll have to start bouncing "mailbox full" notifications similarly.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    1. Re:What I do by Anonymous Coward · · Score: 0

      Sorry to inform you, Howard Dean does suck. Badly. Lies too.

  76. FYI Taco and Mar by Abm0raz · · Score: 5, Informative

    Lousy E-mail Filters Complicating Outlook Worms

    SoBig.F is not an Outlook worm. It is a Windows worm. It does not require Outlook to run. It has it's own built in MTA and grabs email addresses from cached webpages and local text files as well as the Outlook/Express address book.

    -Ab

    --
    Nothing fails quite like prayer.
    1. Re:FYI Taco and Mar by smu · · Score: 1

      The headline is Mr. Taco's doing. The headline I submitted with the story was "Lousy e-mail filters add to the Sobig.F problem"

      I guess squeezing in random mentioning of Microsoft products is a part of the Slashdot Editorial Policy -- just to make sure we lowly /. readers click the precious words "Read More". ;-)

  77. Virus autobounces are stupid by siskbc · · Score: 2, Insightful
    but I find it a weak argument to blame the worm problem on anti-virus software without giving numbers of how much bounces actually added to the problem

    I don't. Their contribution to the problem is only limited to their marketshare. Any antivirus can block the viruses - but using these idiots over better competitors results in how many *illions of extra messages? Not to mention the confusion it creates on behalf of less savvy recipients. How many people paid for tech service on their "infected" computers only to discover they were fine?

    Under any circumstances, I don't find this behavior acceptable.

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Virus autobounces are stupid by pboulang · · Score: 2, Interesting
      It really isn't all that big of a deal. As said earlier, at MOST 1 email is generated. This effectively doubles the impact of something like SoBig. When looking at a virus that is spreading not linearly, but geometrically, this double-sized payload begins to have little total impact. We aren't talking MB of data, we're talking a couple KB per message.

      I suggest that at the very least, users get the message that there is something going on (even it it isn't there particular machine that is affected) and, knowing general users, they make admins aware: "What's this? Is this bad?!?" and anything to draw attention at the early stages of an outbreak (hmmm, maybe I should install patches) is a Good Thing(tm).

      --

      This comment is guaranteed*

      *not guaranteed

    2. Re:Virus autobounces are stupid by siskbc · · Score: 2, Insightful
      When looking at a virus that is spreading not linearly, but geometrically, this double-sized payload begins to have little total impact.

      Nope. Because the bounce rate is simply a linear factor of (market share of idiot AV vendor) * (virus propogation rage). So if the virus goes geometric, so does the bounce rate.

      We aren't talking MB of data, we're talking a couple KB per message.

      Remember the total overhead of sending a message as well.

      I suggest that at the very least, users get the message that there is something going on (even it it isn't there particular machine that is affected)

      That's *NOT* a good thing. If users get appropriate info, fine. But telling someone to upgrade when they could be just fine isn't good. People will start taking computers in for repair when they don't need them. Confusing people with constant virus warnings will make them blase about it and leave them with less information than they had before.

      is a Good Thing(tm).

      Like insider trading, Martha? ;)

      --

      -Looking for a job as a materials chemist or multivariat

    3. Re:Virus autobounces are stupid by pboulang · · Score: 2, Interesting
      When looking at a virus that is spreading not linearly, but geometrically, this double-sized payload begins to have little total impact.

      Nope. Because the bounce rate is simply a linear factor of (market share of idiot AV vendor) * (virus propogation rage). So if the virus goes geometric, so does the bounce rate.

      Gonna have to disagree with your conclusion. When you have x^y where x is the size/impact of a single letter and y is the branching factor (average number of recipients per message) than (x+1)^y isn't a great difference. You see what I am saying?

      I suggest that at the very least, users get the message that there is something going on (even it it isn't there particular machine that is affected)

      That's *NOT* a good thing. If users get appropriate info, fine. But telling someone to upgrade when they could be just fine isn't good. People will start taking computers in for repair when they don't need them. Confusing people with constant virus warnings will make them blase about it and leave them with less information than they had before.

      What does one do if they think they have a virus? If they are in a corporate environment, they ping the help desk (and that would be ONCE per person, regardless of the number of emails they get). If they are a home user, they make sure they have updated virus software. If they are clueless, then they will take it somewhere and get anti-virus software installed. which is what we really want. There is crappy software that is vulnerable, and if you run windows, you MUST run some kind of AV and update patches, etc. If they are confused or blase about having a virus, screw em. That is like keeping an open SPAM relay.
      --

      This comment is guaranteed*

      *not guaranteed

    4. Re:Virus autobounces are stupid by siskbc · · Score: 3, Insightful
      Gonna have to disagree with your conclusion. When you have x^y where x is the size/impact of a single letter and y is the branching factor (average number of recipients per message) than (x+1)^y isn't a great difference. You see what I am saying?

      No, the math's still off. If x is the so big rate, and y is the exponential propogation rate, and A is the AV copmany's market share (between 0 and 1), the rate of propogation of Sobig is x^y. The rate of propogation of bounces is A(x^y). So the propogation rate of sobig + bounces is (1+A)(x^y), not (x+1)^y. Actually, if I amended your math, it would be worse (your formula assumes that a bounce can be branched). There, it would be (x+Ax)^y. And that would be a phenomenal impact. The way you write the formula (x+1)^y, it assumes that only one bounce were ever sent. If that were the case, no one would worry. But it's not. And if you take the derivative of my amended version of your formula, which is the incremental impact per message sent, it increases exponentially too. Think about that. I can do the calculus too if you like. Either way, it's bad. At best the impact is a constant fraction of the sobig rate. At worst, they work together geometrically.

      What does one do if they think they have a virus? If they are in a corporate environment, they ping the help desk (and that would be ONCE per person, regardless of the number of emails they get).

      Yeah, and in a large environment of thousands of people, that's *exactly* what the help desk needs. Trust me, I know some of these people, and it's driving them nuts.

      If they are a home user, they make sure they have updated virus software. If they are clueless, then they will take it somewhere and get anti-virus software installed.

      And if they were already up-to-date, then they just paid money for nothing. And once they get up-to-date and know they're OK, and they keep getting messages, they learn to ignore them. So when another message comes out that they're not prepared for, they think they are.

      --

      -Looking for a job as a materials chemist or multivariat

    5. Re:Virus autobounces are stupid by JonathanX · · Score: 1

      As said earlier, at MOST 1 email is generated.

      Where does this idea come from? You'll get one bounce for each message that uses your address. I personally received 423 advertis^H^H^Hbounces during the outbreak. I only received 366 copies of Sobig.F. Sure, administrators could have disabled notification and I believe that responsible admins probably did, once they got finished with their latest game of whack-a-mole. Say what you want, but sending any sort of notification based on a known forged address is not just a case of ignorance. The AV vendors were fully aware that the headers were forged. They should have tailored their signatures to account for this and exempt these messages from notification. The fact that they didn't tells me that they considered it a free shot at email marketing...otherwise known as SPAM. I don't think a case can be made that they did this deliberately since the product was already configured to send the alerts. However, they were more than willing to look the other way while their products marketed themselves. The possibility that they were too short sighted to see this problem ahead of time remains a possibility, but that carries other implications that I really don't want to get into.

    6. Re:Virus autobounces are stupid by weave · · Score: 1

      grr, it is a big deal when user's keep calling the help desk wasting tech time asking what they are about, that they never sent that person a message, etc, etc...

    7. Re:Virus autobounces are stupid by BLAMM! · · Score: 1

      Gonna have to disagree with your conclusion. When you have x^y where x is the size/impact of a single letter and y is the branching factor (average number of recipients per message) than (x+1)^y isn't a great difference. You see what I am saying?

      And I have to disagree with your math.

      If x is the size/impact of a single letter, then including the impact of a bounce is (2x) not (x+1). And I call that a significant difference.

    8. Re:Virus autobounces are stupid by John+Miles · · Score: 1

      If x is the size/impact of a single letter, then including the impact of a bounce is (2x) not (x+1).

      That's true only if the bounce goes back to the original recipient. In the case of SoBig.F, the recipient of the bounce is forged, so it is indeed a case of geometric spreading.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    9. Re:Virus autobounces are stupid by John+Miles · · Score: 2, Insightful

      To clarify: those forged bounces are a major propagation vector for the virus, resulting in the aforementioned geometric nastiness.

      Bouncing mail with attachments intact is unimaginably dumb.

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    10. Re:Virus autobounces are stupid by Brendan+Byrd · · Score: 1

      I don't see how this is good advertising. That's basically telling me "Yes, this AV package is fucking stupid because it doesn't know that the virus spoofs the From headers." Therefore, I'd turn the other way when I see their AV packages at a software store.

    11. Re:Virus autobounces are stupid by JonathanX · · Score: 1

      You probably haven't collected your winnings from the latest Amsterdam lotto or ordered any magic penis enlargement dust either.

    12. Re:Virus autobounces are stupid by m_frankie_h · · Score: 1

      The problem is not in the traffic generated --- a typical antivirus bounce mail doesn't include the virus binary and is therefore much smaller.

      The problem is in the users getting these mails and starting to PANIC.

    13. Re:Virus autobounces are stupid by BLAMM! · · Score: 1

      That's true only if the bounce goes back to the original recipient. In the case of SoBig.F, the recipient of the bounce is forged, so it is indeed a case of geometric spreading.

      Ok, I see.

      Except I wasn't pursuing the impact on a single machine. I was looking at the affect on the net as a whole. A single letter causes X drain on the system. A bounce causes the same drain. If Y letters are sent by SoBig.F, they cause X*Y drain. If each letter generates a bounce, whether to the true originator or not, the effect is 2(X*Y) or twice the problem.

    14. Re:Virus autobounces are stupid by bedessen · · Score: 2, Insightful

      Only on slashdot would someone get moderated as interesting for saying that a phenominon that doubles the rate of junk emails is insignificant because the rate is already high to begin with.

      I don't care if it's growing linearly, exponentially, or factorially. Doubling it means twice as much crap for email administrators to deal with and is hardly "not all that big of a deal."

    15. Re:Virus autobounces are stupid by outsider007 · · Score: 1

      well, it's spam so you block it. even if it's people who know people that have you in their address list, they should be blocked because the person you both know has proven himself irresponsible. I think it's a good thing.

      --
      If you mod me down the terrorists will have won
    16. Re:Virus autobounces are stupid by pboulang · · Score: 2, Interesting
      Gonna have to disagree with your conclusion. When you have x^y where x is the size/impact of a single letter and y is the branching factor (average number of recipients per message) than (x+1)^y isn't a great difference. You see what I am saying?

      No, the math's still off. If x is the so big rate,

      Ok, your hypothetical is wrong, not what I was saying. X is the impact or cost of a single sobig email. This is how much? 600k? if for EACH sobig email X there is a "random" message saying "You sent spam" which cost about 2k, the total impact is X + epsilon which I indicated as 1, a small constant. Instead of 600K it is 602K. Please note that I am not even going to bother figuring in the cost of building/tearing down TCP/IP etc as you aren't concerned when one big image is split into multiple images on a web page are you?

      I think we need to look only at the normal case where for every sobig message sent that is "caught" an email is sent out. What I really wanted to point out wasn't when a bounce message is infectios (cause I agree wholeheartedly that sending that "back" infectable is dumb) but the case where a legitimate attempt to say "hey, there's and issue" is a couple KB is attempted.

      What does one do if they think they have a virus? If they are in a corporate environment, they ping the help desk (and that would be ONCE per person, regardless of the number of emails they get).

      Yeah, and in a large environment of thousands of people, that's *exactly* what the help desk needs. Trust me, I know some of these people, and it's driving them nuts.

      It is the JOB of people manning a help desk to correctly educate the users. It takes me as an outside consultant about 1 minute to explain it for even the dumbest users and nobody would run more than 50:1 user:hd ratio. A major virus breaks out, the phone is tied up for an hour. That is COMPLETELY acceptable.

      If they are a home user, they make sure they have updated virus software. If they are clueless, then they will take it somewhere and get anti-virus software installed.

      And if they were already up-to-date, then they just paid money for nothing. And once they get up-to-date and know they're OK, and they keep getting messages, they learn to ignore them. So when another message comes out that they're not prepared for, they think they are.

      Updating your virus software costs nothing. And if you need to pay because you don't have it, then are you saying that people should NOT have the latest AV SW?

      Yes, they don't understand when 50 emails come in saying they have a virus when they really don't... but they need to be responsible for finding out what this SoBig thing is, and every search engine and geek cousin or hired help knows.

      --

      This comment is guaranteed*

      *not guaranteed

    17. Re:Virus autobounces are stupid by nolife · · Score: 1

      Because every bounced message is an advertisement for the antivirus company. I consider it a different form of spamming.

      --
      Bad boys rape our young girls but Violet gives willingly.
    18. Re:Virus autobounces are stupid by pboulang · · Score: 1
      I personally received 423 advertis^H^H^Hbounces during the outbreak. I only received 366 copies of Sobig.F.
      I don't see why you think that these numbers need to be related. The 423 were from when a message was sent with you as a from: (and was stopped) and the 366 were where you were the to:

      Say what you want, but sending any sort of notification based on a known forged address is not just a case of ignorance. The AV vendors were fully aware that the headers were forged. They should have tailored their signatures to account for this and exempt these messages from notification. The fact that they didn't tells me that they considered it a free shot at email marketing...otherwise known as SPAM. I don't think a case can be made that they did this deliberately since the product was already configured to send the alerts. However, they were more than willing to look the other way while their products marketed themselves. The possibility that they were too short sighted to see this problem ahead of time remains a possibility, but that carries other implications that I really don't want to get into.
      I'm not sure what the AV companies were thinking. You may be right on this point. I'm not comfortable taking a "feature" (it was intended that way for years) and exploiting it puts the burden of SPAM on the AV companies.

      Now, if they came out with a free upgrade TOMORROW that fixes both the default behavior and figures out when it should or shouldn't tell the sender would that be soon enough for you to prove they are trying to work on this? It *is* a major product. Remember that when you complain today.

      ok, who am I trying to fool? They won't, they are, and viruses will continue, it's in their best interest, they wrote em, right?

      --

      This comment is guaranteed*

      *not guaranteed

    19. Re:Virus autobounces are stupid by pboulang · · Score: 1
      grr, it is a big deal when user's keep calling the help desk wasting tech time asking what they are about, that they never sent that person a message, etc, etc...
      It is their JOB to demystify computers, these boxes that turn otherwise intelligent people into kindergarteners. They should also in almost no time TURN off the problem by filtering out these messages.

      Frankly, the arrogant attitude amazes me... that's the one time in help desk world when you are appreciated: when you can explain something that is "weird" or confusing to a user.

      --

      This comment is guaranteed*

      *not guaranteed

    20. Re:Virus autobounces are stupid by poohknight · · Score: 1

      pboulang wrote:

      It is the JOB of people manning a help desk to correctly educate the users. It takes me as an outside consultant about 1 minute to explain it for even the dumbest users and nobody would run more than 50:1 user:hd ratio. A major virus breaks out, the phone is tied up for an hour. That is COMPLETELY acceptable.

      Hmmmm, let's see. I'll be conservative because I haven't looked at the total user numbers this month. 1400 users/4 help desk employees = 350:1 ratio. How about all employees in the IS department except for some managers? 1400 users/12 employees = 116.67:1 ratio. Count only users with e-mail? 1200/12 employees = 100:1 ratio.

      Tell me again that no one runs more than 50:1 user:hd ratio?

    21. Re:Virus autobounces are stupid by pboulang · · Score: 1
      ok. Let's think this through:

      If a 50KB virus gets sent out to an average of 15 people, in only 6 generations that would be 50*15 + 50*15*15 + 50*15*15*15, etc = 50(15^1 + 15^2 + 15^3 + 15^4 + 15^5 + 15^6) = total cost of 610,212,000KB or ~610GB

      Double the size of each would be ~1,200GB

      I say that isn't a huge impact because changing the number of people exploited by only 1 because they got scared and saw it first and reacted in time = 807,031,400KB or ~807GB

      The impact of DOUBLING the payload maybe only affected the total cost by about 1.3, not 2. Now take into account fact that most AV vendors don't send the whole email, but instead about 2k, then you have a much less of an issue.

      The interesting portion is that by wasting a little extra bandwidth at the beginning, I was hinting at the fact that you could reduce either the branch factor or the number of total generations.

      What I think is crap is that there are people whose job is Email Administrator (talk about your niche) that would have twice as much crap to deal with. OMG, it is soooo hard to right a 5XX DENY rule when you see the FROM: of a message is from "exchangeserver@xxxxxx.org" or somesuch.

      --

      This comment is guaranteed*

      *not guaranteed

    22. Re:Virus autobounces are stupid by pboulang · · Score: 1
      If you can handle a ratio that high, then I suggest that writing a memo detailing the issue and maybe having it sent out by the CEO so that it gets read wouldn't be too difficult to imagine?

      Seriously, if you have a ratio that high with windows machines (of course they are windows, cause that is what this whole thing is about, right?) then you can't handle a significant outage at all. You either have extremely good processes in place with some talented people or have gotten lucky. I don't, however, think you run a normal ratio?

      --

      This comment is guaranteed*

      *not guaranteed

    23. Re:Virus autobounces are stupid by Anonymous Coward · · Score: 0

      I Filter out the alerts just like spam. It isn't really that difficult.

    24. Re:Virus autobounces are stupid by E-Rock · · Score: 1

      I have to call bullshit on your conclusions on the purpose and abilities of the helpdesk. If helpdesk operators were supposed to be education and training providers, I've never see a properly configured call center. Anyway, if the users were trainable, no one would have gotten the virus. You had to *intentionally* open an unknown attachment in an unsolicited e-mail, even if it is forged to come from a friend of a friend who had you in their addressbook.

    25. Re:Virus autobounces are stupid by pboulang · · Score: 1
      A user calls, tells you they got an email that said they had sent out this Sobig thing to this person they never even heard of. Help desk is the first people they call and they should get a response that lets them know that they may see a lot of these, but here's how it works, the virus takes two random names from someone's address book, puts one as the sender and the other as the recipient. They don't have the email, but someone that has them in their address book does.

      This takes about 30 seconds and I haven't met a single person that couldn't understand that unless they don't understand To: and From: in which case they obviously don't have email of any kind.

      Are you saying it is beyond the abilities of a $10/hr person to explain that? Maybe you are saying that help desk SHOULDN'T explain anything to the user. A call center that can't handle this in under a minute is truly worthless. Yep, definitely a tier 2 job. Hell, "Call the CTO!" "I don't care, wake him!"

      Maybe the point is you *haven't* seen a properly managed call center, staffed appropriately.

      BTW, I was busy trolling today, don't be upset. I'm having fun at how many people I can irk with the simple beginning of "it's ok to have an anti-virus product that passes on viruses to others while protecting you." I mean come on, it would take all of a day to write the patch to disable automated responses when it is obvious that it is pointless to do so. Have a nice day. Don't be mad; just smile and take it like a man. Read my sig and groan. :)

      --

      This comment is guaranteed*

      *not guaranteed

    26. Re:Virus autobounces are stupid by siskbc · · Score: 1
      well, it's spam so you block it. even if it's people who know people that have you in their address list, they should be blocked because the person you both know has proven himself irresponsible. I think it's a good thing.

      Right. And if the general populace likes being as friendless and isolated as the typical /. reader, that'll be a peach. And what if that asshat's your boss?

      Logistically, you have to make that decision for each of your contacts. Logically, even that wouldn't work, as non-techy users 1) don't implement span blocks, and 2) the person whose name is on the header is NOT the one who's infected. So you'll have blocked your entire list for no reason. That's the entire point of this thread.

      --

      -Looking for a job as a materials chemist or multivariat

    27. Re:Virus autobounces are stupid by outsider007 · · Score: 1

      And what if that asshat's your boss?
      don't block your boss then.
      the person whose name is on the header is NOT the one who's infected
      so what? block them anyway. unless it's someone you want to get emails from.

      --
      If you mod me down the terrorists will have won
    28. Re:Virus autobounces are stupid by siskbc · · Score: 1
      so what? block them anyway. unless it's someone you want to get emails from.

      Good fucking plan. So you're going to block someone who's not causing the problem, while not blocking the people who are the problem, and setting up a whitelist with the rest of the world pretty much blacklisted. Go for it.

      --

      -Looking for a job as a materials chemist or multivariat

    29. Re:Virus autobounces are stupid by outsider007 · · Score: 1

      no, I am blocking the person who is causing the problem by banning everyone in his buddy list. problem solved.

      --
      If you mod me down the terrorists will have won
    30. Re:Virus autobounces are stupid by siskbc · · Score: 1
      no, I am blocking the person who is causing the problem by banning everyone in his buddy list. problem solved.

      But not him. Problem NOT solved. And really, for anyone who actually has a damn job, that's not an option.

      --

      -Looking for a job as a materials chemist or multivariat

  78. Fridrik Skulason / FRISK / F-prot by Jucius+Maximus · · Score: 1
    Just a side note: The F-Prot Antivirus program produced by Skulason's company is among the best I have seen. It handily puts Norton and McAfee in their places. It's what I put on my mother's computer. If you are looking for a good antivirus program for windows that's non-bloated and simply does its job with as little fluff as possible, check out F-prot. There are also linux and BSD versions.

    I am a satisfied customer, although sadly their business licenses have become a lot more $expensive lately.

  79. Troublesome? Yes, but necessary ... by ElektroHolunder · · Score: 4, Interesting

    I am currently looking into antivirus solutions for our company mailserver, and originally thought about disabling the bounce messages.

    But unfortunately it seems that it could be illegal in Germany to intercept a message without notifying the sender. As far as I understand it, eMail seems to be subject to the same regulations as snail mail here, so dropping the message silently could constitute a legal hazard ..

    1. Re:Troublesome? Yes, but necessary ... by Juggler · · Score: 2, Interesting
      In many countries it is illegal to for a communications carrier to drop messages (e.g. e-mail) without notifying someone. However, you can generally choose between notifing the sender and notifying the recipient.

      Notifying the recipient is the only technically "safe" course of action, since everything else may be forged and sending mail to it could be increasing the magnitude of the problem.

      If the recipient then requests that you discard all such warning messages for him, then that's probably also legal - so it boils down to how you word the contract with the recipient.

      I don't think law is really a practical obstacle in such cases. Additionally, in some countries in Europe (not sure about Germany) ISPs are granted specific permission to take steps to protect the network infrastructure from attacks, and virus outbreaks definately a form of attack.

      Disclaimer: I work for FRISK on e-mail filtering, but I'm not a lawyer. :-)

    2. Re:Troublesome? Yes, but necessary ... by Czmyt · · Score: 1

      Since the sender is an automated, malicious program with no mail reception capabilities, I do not understand how you could get in trouble by filtering these messages.

    3. Re:Troublesome? Yes, but necessary ... by ovidus+naso · · Score: 2, Insightful
      Solution: block it before the end of the SMTP exchange.

      Accept the email then scan it and notify concerned parties -> BAD.

      Refuse the message by giving an SMTP 5xx error instead of a 250 after the DATA part -> GOOD.

      Personnaly, I like the exim+exiscan combo.

      --
      ---------- ovidius naso
    4. Re:Troublesome? Yes, but necessary ... by Anonymous Coward · · Score: 0

      I'm using a A/V product based out of Germany on our server and have been quite happy with it.
      It advises the user that an 'questionable' email was intercepted and then caches the email on the server also sends message to sysadm to advise of the cached record.
      IF user wants the email it can be released
      Doesn't bounce back to the sender

      I believe the it's at www.antivir.de
      product is called antivir

      my 2 cents (canadian funds though)!

  80. I don't think they're complicating... by fok · · Score: 1

    I think they're helping the worms...!

    --
    \m/
  81. old news... by imipak · · Score: 1

    See the lengthy discusasion of this subject on NANOG a three weeks ago, when all these issues were flogged to death in a much more authoritative manner than will be the case in the comments around this post...

  82. One more thing. by FreeLinux · · Score: 1

    I've pretty much given up on beating this dead hosre but, I'll say it one more time for your benefit: Email was not intended to be a file transfer and or storage system. If you need to transfer files a better solution would be to make them available via HTTP or FTP and simply email the URL to the recipient. They can then click the link and download the file themselves rather than a mailbox with a gigabyte of messages that all have attachmented files.

    Last time: Email was never intended to be a file transfer or storage mechanism. Use it as it was originally intended and you will not have any problems or frustrations.

  83. underestimates the ramifications by jd142 · · Score: 1

    Not only does each virus email generate an autoresponse email, every user in our building emails me *every time* they receive an autoresponse about an infected file.

    Ok, so maybe it isn't every user every time, but boy does it feel like it. When you've explained to someone for the fourth time that the emails are junk, it gets frustrating.

  84. Message Headers should be Compulsory by gvc · · Score: 5, Insightful

    Last year, my wife received a spate of "you sent this virus" messages. Worse, a number of her associates received "this person tried to send you a virus" message, referring to her.

    I followed up with several of the administrators running the virus filters. In all cases, the administrators had quarantined the messages without headers so it was impossible to tell what machine really sent the message. I would have liked to know this information so as to have some hope of tracing the owner of the infected machine.

    I understand why users are unaware of headers. Microsoft's products go out of their way to hide them. In Outlook Express, to get headers you have to find the relevant show headers pull-down and even then the headers appear in a too-small non-resizable window. You have to clip the contents and paste into a real window before the headers can be read/forwarded.

    The "From:" field of email means no more than the snail-mail return address that you scribble on an envelope. The header, like the snail-mail postmark, tells the origin.

    What is the excuse for vendors of email software (filtering or end-user) perpetrating unawareness of this basic property of email?

    1. Re:Message Headers should be Compulsory by Poor+College+Student · · Score: 1
      What is the excuse for vendors of email software (filtering or end-user) perpetrating unawareness of this basic property of email?

      I have a hunch that the average Joe or Jane probably doesn't care about or what to do with tags such as:
      MessageID: H0007c9c151181e2.mail.provider@MHS
      Content-Transfer-Encoding: quoted-principle
      MIME-Version: 1.0

      Personally, I couldn't care less what version of MIME someones email client uses. I care primarily about sender, subject, and time.

    2. Re:Message Headers should be Compulsory by iso · · Score: 1

      Tell me about it! When this latest Microsoft virus went through a few weeks ago I didn't get any copies of the virus myself but a copy of the virus did spoof my email address as the reply-to address. So, one day I was the lucky recipient of 50 "YOU HAVE A VIRUS!!" emails. Great fun. Who sends out automated messages based on the (easily forgeable) "from" address!?

    3. Re:Message Headers should be Compulsory by danila · · Score: 1

      Do you know that these Joes and Janes do not know that e-mail addresses are easily spoofable. You can't do it in Outlook, but you can do it in any decent client. I don't know, why no one uses that yet, but I can send your client a message with your return address and call him a fucking asshole. Since most people are not aware that e-mail addresses can be forged, he will assume that you did it. I can also send him a request for some confidential documents with your From address and some other Reply-To field, which hopefully would be hidden.

      That's what you get by hiding extra functionality from users in this case.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
  85. Re: Forged From: viruses by frankie · · Score: 4, Informative
    Until recently, no e-mail worms spoofed the email address

    What is your definition of "recently"? Apparently it's about two years.

  86. an Idea by linuxislandsucks · · Score: 2, Interesting

    why not have the filter do a whois on the ip of sender and send the warning to the admin of that net block?

    seems like abetter solution as it gets the virus warning in hands of the person that can do soemthing about it rather than sent to people who have no virus on their systems..

    comeon how hard is it to parse the record gotten back from a whois query?

    --
    Don't Tread on OpenSource
  87. I SENT IT ANYWAYS, C.O.D. by Anonymous Coward · · Score: 0

    Love,
    Egg Troll

  88. amavisd-new doesn't send mail for Sobig, others by ddkilzer · · Score: 2, Informative

    Later versions of the amavisd-new mail scanner don't send mail to sender addresses from virii/worms that forge mail headers, even if you have it configured to do so.

  89. Server Side Virus Filter by 42 · · Score: 1

    What is an affordable server side virus filter? There are several out there I am guessing, but I am unsure about the reliability vs. cost. We currently use SpamAssassin for our spam filtering needs and are very pleased with it.

    What is a the de-facto standard for email virus filtering these days? (Something that a geek would be proud to have filtering their email)

    1. Re:Server Side Virus Filter by Czmyt · · Score: 1

      F-Prot software has a trial version. I like it. I dont know if it's the best but it works very well for me. I'll probably end up buying it.

  90. Or... by siskbc · · Score: 1

    ...if you prefer discrete integer variables, you could go with the number of chins. That kid had about 4.

    --

    -Looking for a job as a materials chemist or multivariat

  91. forward it back to the AV vender by Anonymous Coward · · Score: 0

    If you receive a message from AV product then send it back to the company who wrote the AV.
    Send it to sales@, support@, info@, etc. and tell them they should fix their program.

  92. What an incredibly simplified view! by NerveGas · · Score: 1

    Let's look at two cases. First, the virus goes through to an end user. We'll assume the chances are 1 out of 10 that the user will become infected, and generate another 2,000 messages. Number of messages sent per average user: 201.

    Now, let's say that a filter stops the message, and still sends a reply - but prevents infection. Number of messages sent: 2.

    So, it looks to me like even if the filter DOES send a reply, there's still a 100-fold DECREASE in load vs. not having a filter.

    Now, I'm not saying that virus filters SHOULD send the notification - that's open for debate. However, the simple statement that virus filters which DO send out notifications doubles the load is a tremendous simplification, and does not take into account the real-world DECREASE in messages sent when effective virus filters are in place.

    steve

    --
    Oh, you're not stuck, you're just unable to let go of the onion rings.
  93. Most Email antivirus solutions are just plain dumb by codeguy007 · · Score: 2, Interesting

    I remember the day that SoBig.F reared it's ugly head. I can into work and must have had 40-50 emails claiming I sent a virus to some person I have never heard of. It was so many I actually figured I better check and make sure I didn't have the virus.

    Even worse 1 in 4 of the messages sent the virus to me in the message bounce.

    But in reality antivirus software is playing a losing game, it tries to get out virus definitions to protect systems after the virus has been released. Not only that the viruses have much faster distribution rate than the definitions so it's a loosing battle. We need a new solution.

    I propose that we should call for a ban of Microsoft Lookout. In its short existence, it has become the most insecure piece of software every written -- surpassing Bind, Sendmail and even Wuftpd, programs much older than it.

    While we are at it lets call for banning direct access to the internet for all windows based systems. Let's face it. If you put a windows box bare on the net, eventually it is going to be compromised. Windows wasn't originally designed to work on the internet and Microsoft has shoehorned in the internet support without proper security measures taken.

    You can't rely on end users who are too afraid to install there own OS to properly secure and update the machine. Someone needs to do that for them and frankly Microsoft doesn't.

  94. Why is this news? by rossz · · Score: 1

    This has been a known problem since the first header forging virus/worm was released.

    On the Exim mail list, the big question wasn't how to stop sobig.f. It was never a problem. The discussion was on how best to filter out the "you have a virus" bounce messages that were flooding the admins.

    --
    -- Will program for bandwidth
  95. procmail recipes by Dominic_Mazzoni · · Score: 1

    Here are some procmail recipes to identify these bounce messages:

    * ^Subject: delivery fail
    * ^Subject: Delivery Status Notification
    * ^Subject: failure notice
    * ^Subject: mail system error
    * ^Subject: norton antivirus detected
    * ^Subject: returned mail
    * ^Subject: undeliverable mail
    * ^Subject: undeliverable:
    * ^Subject: undelivered mail
    * ^Subject: virus alert
    * ^Subject: virus detect
    * ^Subject: virus found in sent message
    * ^Subject: virus in your mail
    * ^Subject: virus warning
    * ^Subject: warning:.*virus
    * ^Subject: your e-mail.*virus

    I would recommend redirecting these messages to a separate folder rather than deleting them, as there's a small chance of false positives.

    BTW, how does one write a procmail rule that succeeds if ANY of the lines match, rather than if ALL? (I have all of the lines above in separate recipes, currently...)

    1. Re:procmail recipes by gvc · · Score: 1

      This list is way too aggressive for my taste. I want to see bona fide bounce messages.

      One filter that I found effective was to scan for a line containing "^From:" and my email address but not my name. Most legitimate bounce messages return at least the From header of the original message. Since all the mail clients I use include my name in the From line (and all viruses and spammers that have impersonated me to date don't) this is pretty effective.

  96. No-IP.com did it right by splitretina · · Score: 2, Interesting

    I use No-IP.com. Within a few hours of the worm spreading they had turned off bounce notifications of virus messages. I received a total of 10 SoBig worm notifications messages, and none of the actual worm.

    I think it's up to the ISP administrators to stay up to date with what is going on and to stop these sort of things in their tracks. That is why I get my email through a third party: so I don't have to deal with the bull. They have a responsiblity to their customers. I think No-IP did a great job living up to that responsibility.

    Frisk has been around for a long time, I used f-prot in DOS. But I think the letter he wrote is definitely a marketing ploy. They have recently updated their site to a more modern interface and it seems they are attempting to make some kind of mainstream market pull. I have the f-prot trial on my work windows xp box and honestly, it's pretty good. Fast and stable and less intrusive than Norton AV. So it might be good for it to work out for them.

    1. Re:No-IP.com did it right by dander · · Score: 0

      I've used their mail services. I havent received a single virus notification, and I know a few of my friends had sobig.

    2. Re:No-IP.com did it right by Anonymous Coward · · Score: 0

      Thats cool, Im glad to hear that their admin was not sitting on his/her ass with the feet on the desk waiting for the problem to go away.
      I have never heard of f-prot but anything is better than Norton.

  97. What I Think by Matty_ · · Score: 3, Informative

    I administrate a mail server with around 550 accounts on it. We got slammed by Sobig.F and eventually had to block it using header_checks in Postfix.

    This won't catch every virus-infected file attachment (like Word macro viruses), but the regex I put in place will block files with certain file extensions (e.g. pif, exe, etc.) What's nice is that the mail is rejected during the SMTP transaction and produces no residual mail traffic since the sending mail server is the worm's SMTP engine.

    So, for anyone using Postfix 2 who would like to stop most e-mail worms, using header_checks to scan MIME headers is a very effective way to protect your customers/users.

    1. Re:What I Think by Juggler · · Score: 1
      Yes, this is quite nice. Alot of people have been recommending this sort of thing in the discussion thread already.

      The only problem is... you can't be sure that the server trying offering the infected mail isn't just a relay. If it's a relay then you're effectively instructing it to resend the entire message - virus and all - to the sender, which is an innocent thrid party.

      This sort of scenario is the most common cause of the complaints about "A/V programs" which resend the entire virus, thus helping it spread.

      So you're just passing the buck. It's understandable and I agree that this is a much better approach than most. But the ideal behavior, from a global network point of view, would be to reliably detect the infection as a massmailer (using a good A/V scanner) and /dev/null the message.

      Disclaimer: I work for FRISK on e-mail related stuff. :-)

    2. Re:What I Think by Czmyt · · Score: 1

      Or nullroute the IP address of the last sender that's not a trusted relay.

  98. Cry me a river by maggard · · Score: 4, Insightful
    I just got a call from the Data Security guy in my office. I've had run-ins with him before, because their scans of my PC would occasionally find that I run Eudora for my personal email rather than routing it through the corporate virus portal known as Outlook Express.
    You on the clock? In the company office? Using company hardware? On an account with access to material the company would probably rather not get corrupted, infected, or randomly sent out to strangers?

    Uh huh.

    So you wanna read your personal email at the office. Fine if your company supports that.

    But then you just absolutely positively gotta use only your favorite email client, not the one already installed, not a web portal. The email client now installed by you, presumably licensed to you, that is not owned or supported by IS. The one that makes IS's day that much tougher by throwing one more ingredient into the stew that is the company's desktop computer.

    Now on top if it your personal email client reading your personal email is bringing in viruses to the company. Onto that corporate PC logged into the corporate network. And dammit those nasty folks in IS aren't willing to spend their time making exceptions to the virus scanning so your unique-in-the-company personal email client reading your personal, virus-infected email is exempted.

    Cry me a river.

    --
    I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
    1. Re:Cry me a river by ChadM · · Score: 1


      I know this is off topic, but why must so many people say "cry me a river" all the time? I see it at least once in every story posted to Slashdot as part of a rebuttal to something somebody else has said, and it seems the phrase is being used in increasing frequency since Justin Timberlake made a song called "Cry me a River". MY HEAD IS GOING TO EXPLODE IF YOU DONT STOP REMINDING ME OF THAT GODDAMN SONG, STOP IT!!!!!!!
      </RANT>

      You may now return to your regularly scheduled Slashdot comment reading.

  99. Have to agree by Tsu+Dho+Nimh · · Score: 1
    I was getting 200+ warnings a day that I had sent infected email, then came a wave of "we couldn't deliver your the virus-infected mail" warnings from the bad emails wiht my address forged into the headers ... then my ISP started filtering all virus bounces and the problem was over for me.

    The ISP, OTHO, uses a lot of CPU cycles filtering.

  100. Nice try, but .... by mr_z_beeblebrox · · Score: 1

    Most antivirus software is configurable as to what to do with the virus. I set mine to delete the attachment, the email and send no message (that is tight, but during worm activity that is the way to go). So, if he had problems with too much mail when filters engaged he should RTFM

    Replace user, press any key

    1. Re:Nice try, but .... by talks_to_birds · · Score: 1
      Nice try, but...

      All the virus-bounces I'm receiving are from brain-dead ISP's trying to filter and send out "helpful" messages to people who, because of forgery, didn't send the offending email in the first place.

      You'd think an ISP could do better, but since the worst of them begins with an "A" and ends with an "L", I'm not surprised...

      t_t_b

      --
      I'm on PJ's "enemies" list! Are you?
    2. Re:Nice try, but .... by 90XDoubleSide · · Score: 3, Interesting

      The real answer is that virus definition files should have a flag that is set for viruses that always use forged addresses that tells the antivirus never to send an email in reply to that virus.

      --
      "Reality is just a convenient measure of complexity" -Alvy Ray Smith
  101. They're stoppable at the SMTP level, too. by devphil · · Score: 1


    At least, that's what I've been told.

    SoBig's builtin MTA sends a syntactically-incorrect "HELO" line when connecting to a mail server. The SMTP grammar specifies a fully qualified name in the machine name following HELO, I think, and SoBig doesn't give one.

    This is hearsay, though. Can someone verify it?

    So, if true, you could simply drop the connection on poorly-formed HELO lines. But that would also disconnect a few legit-but-badly-written MTAs out there. (In my opinion, fuck 'em. It's lost past time to be using properly written software.)

    --
    You cannot apply a technological solution to a sociological problem. (Edwards' Law)
  102. Not always by Andy+Dodd · · Score: 1

    Some of the "worst offenders" will send the offending attachment back.

    So the reply is larger (original message + "we found a virus" stuff) AND it potentially spreads the virus to an uninfected machine.

    --
    retrorocket.o not found, launch anyway?
  103. What an incredibly simplified idiot! by porkchop_d_clown · · Score: 1

    What part of "forged originator address" don't you understand?

    The "you've got a virus" messages DON'T GO BACK TO THE INFECTED PERSON. Instead, they come to me, and I'm running a freaking Macintosh!

    1. Re:What an incredibly simplified idiot! by NerveGas · · Score: 1

      My point still stands.

      You get a few, or a LOT of messages that don't pertain to you. However, because the filters were in place, you got far FEWER messages than you would have received if the virus had been allowed to propagate.

      steve

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
  104. Not lousy, just misconfigured by onecrazyfoo · · Score: 3, Informative

    I would imagine that most of the virus scanners for mail servers out there can be configured to not send out the notification to the forged From address. The virus scanner I am familiar with - RAV, has this capability. I had ours configured to send out the notification until Klez and other viruses made it a worthless endeavour. Unless of course you are an ISP that has no qualms about using the opportunity to advertise.

    It would be nice if GeCAD would rewrite their software to stop the notice from being sent when the virus is Klez, Sobig, etc. But since GeCAD got bought out by Microsoft who will be discontinuing their product line, I know that will never happen. Hopefully someone else like Sophos will.

  105. Umm sobig isn't an outlook worm. by ad0gg · · Score: 1

    People need to stop calling sobig an outlook worm, it doesn't use outlook. It has its own smtp server, it scans your harddrive for emails addresses. Its a windows worm, and if you read the history on it. It spread via usenet first.

    --

    Have you ever been to a turkish prison?

  106. More than double by tgibbs · · Score: 1

    I received far more mistaken bounces--and virus-infected attachments--than original Sobig-sent copies

  107. 6 degrees of email seperation by Anonymous Coward · · Score: 1, Insightful

    I have seen this since Klez started doing it, and being on a mac, I knew I wasn't infected. I have thought about an application that might help finding out those who were originally infected by emailing the person who sent out the anitvirus message, to try and find out who this person was that we both knew. I guess in the end were all related to each others email by knowing somebody who knows somebody who knows somebody who sent it.

  108. You have been duped by dosius · · Score: 1

    SCOrdure has no reason to be asking you for $699 to continue to use Linux, or $199, or $32 for that matter until they show tangible and irrefutible proof that their "IP" (feh, ptui!) was used in Linux.

    Until then they won't get a red penny from me.

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
    1. Re:You have been duped by Seth+Finklestein · · Score: 1

      SCO paid my way out to Utah so that I could inspect the "offending code."

      It's the real deal, folks. Get out your checkbooks because SCO owns a large amount of code in Linux.

      Of course, I can't elaborate on what I saw. SCO made me sign a Non-Disclosure Agreement, or "NDA."

      --
      I'm not Seth Finkelstein. I still speak the truth.
  109. Problems at the top by yerricde · · Score: 1

    Second, get everyone to agree to get a key that's signed by a CA.

    Some individuals can't afford the annual fees that many existing CAs charge. And how can a new CA get its key into circulation?

    --
    Will I retire or break 10K?
  110. Wrong by Overly+Critical+Guy · · Score: 1

    Only after idiot users run the attachment.

    --
    "Sufferin' succotash."
  111. A detail by yerricde · · Score: 1

    So, if true, you could simply drop the connection on poorly-formed HELO lines.

    That could work, but remember to make sure that the MTA doesn't actually drop the connection until after the RCPT line; otherwise, it breaks the SMTP RFCs.

    --
    Will I retire or break 10K?
  112. It's Free Advertising by waynelorentz · · Score: 1

    The reason the AV companies put this capability into their systems isn't to be friendly and let people know their computers are infected -- it's freepub. Imagine if you were an anti-virus company and had a list of the e-mails of all the world's infected computers -- you could spam them and get some small percentage of new customers. This automates the process, and in the case of falsified headers, only helps them spam and scare even more people.

  113. "Does this build work any better?" by yerricde · · Score: 1

    Do most users exchange executable files?

    Hobbyist developers sometimes e-mail executable files to people who don't have a compiler installed. And if you don't have a compiler, a web browser, or an FTP client, how are you supposed to get one of those without receiving an executable through e-mail or spending an exorbitant sum on international postage?

    --
    Will I retire or break 10K?
  114. Not with header checking and sane virus policies by buchanmilne · · Score: 1

    We run postfix/amavisd-new with a commercial virus scanner (why not just a commercial virus gateway? Well, most of them aren't as flexible).

    So, first thing a virus find is our header checks for the common windows virus files (.vbs, etc etc). This catches *all* the Sobig.* stuff we have hitting the server, if the connecting client is Sobig itself, we save 100% of the traffic (ok, maybe 99.9%).

    Then, we have the antivirus, which will catch anything embedded in the kind of files our users want to receive (.doc, .zip etc).

    Then the antispam (spamassassin).

    If a virus is found, we notify the intended recipient (if they are local), quarantine the whole original mail, and notify our postmaster, but we don't notify the (potentially forged) sender. If the recipient actually knows the sender, they can inform them if they think it's a real concern.

    Now, I get a bounce from one of these ridiculous virus gateway implementations. Some of them return the *entire* original mail as an attachment. This breaks our header checks, and gets through to the AV, and gets me a notification. This is the *only* traffic I get as a result of Sobig.F, and is wasting my time due to the incompetence of other mail administrators (it's ok if it's a user, at least they can have an excuse).

    What I need now is a header check that matches Norton, and returns a suitable message.

    Anyway, it's nice to see at least one vendor agrees, but I need more ammunition to send with my complaints to the administrators of these broken mail virus solutions.

  115. This can sometimes be disabled by Linux_ho · · Score: 1

    Trend Micro's VirusScan for Linux does a good job for us. While it does send 'warning' messages to sender and recipient by default, these can be disabled. I turned them off the day Klez first reared its ugly head and started the address spoofing trend. I bet this is mostly just a matter of configuration/laziness.

    --
    include $sig;
    1;
  116. What if it's not a virus? by ananiasanom · · Score: 2, Insightful

    I'm as annoyed by this as anybody. I've received hundreds of "rejects", far more than actual copies of the virus.

    But people seem to be forgetting one thing: anti-virus software has false positives

    If anti-virus software eats infected emails without bouncing them, then it will eat some real emails without bouncing them either. This is very bad, as the sender doesn't know his email hasn't been received.

    I don't know the solution. The assumption that once you send an email it will get to its destination is eroding anyway, due to over-zealous anti-spam systems operated by people who think that setting them to reject all emails is a good way of making a point. DSN is becoming more widespread, though God knows what problems that might cause for us if it becomes the norm.

    1. Re:What if it's not a virus? by mabu · · Score: 1

      These anti-worm filters are only good if they're routinely updated with the worm signatures. Once the worm is identified, its behavior is also identified. It's irresponsible and negligent for a company to recognize a worm like Sobig, and filter it, while also knowing that the worm forges the e-mail headers and bouncing mail is totally counterproductive.

    2. Re:What if it's not a virus? by ananiasanom · · Score: 1

      You're still assuming that if the scanner "recognizes" a email as containing Sobig, it really does contain Sobig. The Risks Digest contains a number of past incidents where legitimate email is bounced because a virus scanner has incorrectly identified it as containing a particular virus. If scanners start dropping instead of bouncing mail, that problem becomes worse.

      That's not to say they must carry on regardless, the situation really has become intolerable. But it is worth recognizing that the bounce behaviour is there for a good reason, even if that reason is no longer good enough.

  117. right by Abm0raz · · Score: 1

    True, idiot users still have to run the attachment, but they can run it on any mailer that works with any(?) windows OS. That includes Mozilla, Groupwise, Eudora, Pegasus or any brand of web based mail clients. The attachment is the virus and it doesn't work through any mail client. It has it's own MTA built in.

    -Ab

    --
    Nothing fails quite like prayer.
    1. Re:right by sully67 · · Score: 1
      Newer versions of pegasus mail won't let you run executables straight from the mail client, if you try it will bring up a message warning that the attachment might be dangerous and that you have to save it first.

      That's not to say that some people won't do just that if sent a random virus executable.

    2. Re:right by Anonymous Coward · · Score: 0
      Newer versions of pegasus mail won't let you run executables straight from the mail client, if you try it will bring up a message warning that the attachment might be dangerous and that you have to save it first.

      If you turn the simple security setting on in Outlook Express it won't let you save or run executable attachments either.

  118. Mr. Obvious... by Mysticalfruit · · Score: 1

    Now imagine a worm combining the distribution method of Msblaster with the mass-mailing feature of Sobig.F. The flood of traffic might practically render the Internet unusable.

    Obviously, this guy must be on a different internet than the one I'm connected to right now... My gateway router is rotating it's logs twice a day at this point...

    As for his Blaster.Sobig.F worm, I'm sure as we speak, some knucklehead is working on that right now. It'll be the swissarmy knife of MS worms that'll just go down and try every current exploit. Then it'll just mail itself to everybody...

    --
    Yes Francis, the world has gone crazy.
  119. .x. by Anonymous Coward · · Score: 0

    Amen, Brother. For is it not better to give than to receive.

  120. True, However by Anonymous Coward · · Score: 0

    True, However most of these things are configurable as to what they do when you get a hit.

    You, the admin, set it to send you an email (or page, or whatever) everytime it gets a hit, it's your fault you get buried in a flood.

    Kinda like when you set your work email to forward all emails to your home email when you are on vacation, then the mail server crashes. Your home email got filled, so it sent rejections to the sender, your work email, which forwarded it to your home email, setting up an eternally increasing infinite loop. (At least till one of the mailservers crashes.)

    It's not the filter/antivirus/whatever software that's at fault here, it's just doing EXACTLY what you told it to, not what you want it to.

    Sorry for ranting, but I've dealt with so called admins (the real ones figure it out on their own) whine about their problems that they themselves caused and are too stupid to figure out. (And won't take responsibility for their own mistake either.)

  121. I get naming rights for the n0rton.atorply virus! by Anonymous Coward · · Score: 0

    I have received and deleted 152 emails infected with the Sobig virus.

    As of about 30 minutes ago, I have received and deleted 318 auto-replies from Norton telling me I have been sending emails containing the Sobig virus even though my system is clean.

    The cure is killing the patient.

  122. What's that? by JCMay · · Score: 1

    What's a "wormius?" If you use "wormii," there's got to be a singular form, "wormius." What's a "wormius?"

  123. So THAT'S why I got those emails... by DrLudicrous · · Score: 1
    Man, when that worm hit, I was getting all this email on my hotmail account. Couldn't figure out WHY I was getting it; this explains everything! Thanks to the guy who submitted this article, really takes a load off of my mind.

    What I'd like to know is how they were able to falsify their from address with legitimate emails? This is a direct result of spam- anytime I submit my hotmail account as my email address on web forms, I invariably will get spam as those companies sell my address. This is why I have the hotmail address- to keep my 'legit' accounts more or less spamfree. But even if I keep my legit accounts clean, the end result is still increased network traffic to my hotmail account, a direct result of spammers. Honestly, this is not just an annoyance problem now, it is starting to become an economic one too.

  124. Idea. by Electrawn · · Score: 1

    I think it fits near the SpongeBob theme song.

  125. Duped as in TROLL by Anonymous Coward · · Score: 0

    SETH FINKLESTEIN is a troll of SETH FINKELSTEIN!

  126. Oh COME ON by fleppir · · Score: 1

    You are telling me you didn't learn to ZIP THEM UP??????

    --
    I am the Barber of Seville.
  127. Re:Most Email antivirus solutions are just plain d by gilgongo · · Score: 1

    > But in reality antivirus software is playing a losing game

    There is a huge Emperor's New Clothes factor with the anti-Virus industry. Consumers say to eachother "I must have anti-virus. My virus databases are updated once every nano-second. I am secure... blah blah."

    But when was the last time your A-V system actually stopped a NEW virus before it did you significant damage?

    ExploreZip: We had Norton on all desktops and up-
    to-date. Screwed us up purdy good. We sent most users home at lunchtime.

    "I Love You" - same again. But this time, users asked if they could take the rest of the day off around about 11:00am.

    Klez - a pattern emerging...

    SoBig - SAFE! NO INFECTIONS! YIPEE! ... why?

    BECAUSE AFTER KLEZ WE DECIDED TO BAN ALL EXECUTABLES FILES, THAT'S WHY.

    I overheard our IT Director griping that Norton have almost doubled their bill for the renewal of our corporate license this year. Sounds like we might just tell them to fuck themselves.

    --
    "And the meaning of words; when they cease to function; when will it start worrying you?"
  128. Not that simple by Anonymous Coward · · Score: 1, Insightful

    To some of us, it is axiomatic that legitimate Email should *never* be dropped on the floor silently. When I send a message, either it must reach the recipient, or I must receive a bounce. Any other behavior is unacceptable.

    This guy is arguing that mail servers should silently drop Sobig-infested mail on the floor. But take that argument to its logical conclusion. If Sobig, why not all viruses? If all viruses, why not spam?

    The end result of this "logic" is that my mail will be silently dropped whenever some program *thinks* my message is a virus or spam. And I will never even be notified when my message is not delivered.

    Again, this is unacceptable. It is a cure worse than the disease.

    The real problem is that SMTP does not use strong authentication for envelope senders. Fixing this would require replacing the Internet mail infrastructure. Until that happens, I am happy to accept Sobig bounces in exchange for a reliable mail infrastructure.

    1. Re:Not that simple by Czmyt · · Score: 1
      There's no reason to pass on virus messages if they were generated automatically, as opposed to the old fashioned viruses that piggy-backed on document files.

      Do you think that systems should send bounce messages back when spam messages are detected? That creates a lot of useless traffic. If the message is spammy enough, it should be silently ignored. Otherwise, the intended recipient should get a chance to decide for themselves if they want to receive it.

      I don't think the cure is worse than the disease. If your message is important enough that need confirmation that it was received, you can use some other method to achieve confirmation. Or you can follow-up if action is not taken on your message. That is one thing that these stupid antivirus software companies have done inadvertantly: they killed the reliability of e-mail by spamming people with bounce messages that should only be used in real cases of undeliverable legitimate mail.

  129. Re:I completely agree - and another thing.. by Havokmon · · Score: 1
    The messages generally contain no usefull information, and are deleted without reading.

    I run an email service. I also bounce messages that are infected. Yes, it's a great way to get the word about about the service. No, I don't bounce faked FROM Addresses, IMHO, that's a good way to get bad PR.

    Anyways, I monitor 'bandwidth' usage. I had a customer who just signed up for a free account to stop viruses, and they almost immediately exceeded their bandwidth (15MB a month by default, and they were at 60MB in a week) After 40 'you are over quota' messages, I finally disabled his account. As far as I could tell, he was spamming with a perfect list, or just abusing the quotas.

    It turns out he is a business who was SWAMPED with those bounces from other providers, and completely missed all my automated notifications, and my very important "You will be disabled if you don't respond" notification.

    So he was disabled for two days before he realized what happened. Lost customers? I'm sure he had some legitimate email bounce. All because of mis-configured servers. Maybe he should keep a record of who is flooding him, and sue them.

    --
    "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
  130. Anti Virus developers are morons by mabu · · Score: 1

    You gotta love an anti-virus company that TRUSTS the "from" address of worm-embedded message.

    Talk about stupidity. During the Sobig mess, I must have received hundreds of erroneous warnings from stupid anti-virus programs telling me my computer was infected when it was not. What idiots.

  131. Far worse... by Jayfar · · Score: 1

    What about the anti-spam lameware products that CC spam complaints to multiple role accounts at each and every ISP and upstream with an even a distant cousin relation to the spam. I've counted over 100 CCs in some of these. As a NOC monkey at an ISP (well, of course they CC the NOC role addy and just about any standard ISP role account you can imagine), even though we have a responsive abuse role), my typical reaction is to LART the complainant and send my own abuse complaint to the luser's ISP.

  132. rejected without queueing by Anonymous Coward · · Score: 0

    Some (or most) mail relays will reject the message outright without queueing it, which means the sender machine is left with the task of creating the returned email, and it does not know the exact reason for the rejection.

  133. AV notification is a vector by DrSkwid · · Score: 1

    Some vendors send the complete email out to persons not sending it. The new recipient might then go "oh what was that then" and open the executable and themselves become infected.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:AV notification is a vector by pboulang · · Score: 1

      Agreed and that is a legitimate exploit. This does not account for a significant portion of the virus vector as MOST vendors send synopsis email back (in my experience)

      --

      This comment is guaranteed*

      *not guaranteed

    2. Re:AV notification is a vector by DrSkwid · · Score: 1

      I've often wondered why it's not a technique used as the primary disguise.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  134. whose fault is it really? by ummit · · Score: 1
    "Why blame the vendors of the e-mail filters for these bounces? It's not their fault. All we have to do is educate the users not to click on the viral attachments in the first place."

    Excuses, excuses.

  135. Big O by maestro156 · · Score: 2, Informative

    Examine the Computer Science principle of Big O.

    If you have an exponential function any constant multiplier or addition is thrown out of the equation as unimportant.

    O(2n) = O(n + k) = O(n)

    and so
    O((2x)^y) = O(x^y)

    The point is that the exponent is so important as to nullify the constant multiplier.

  136. Nice advertising... by Dimensio · · Score: 1

    So they're trying to sell me on an antivirus product that informs me of an infection when I'm not infected. Brilliant marketing move.

  137. I get about 1000+ virus bounces a day by Schwern · · Score: 2, Interesting

    I don't think I've gotten a single SoBig virus. Either they're not getting sent or something upstream is blocking them.

    OTOH, I get about 1000+ pieces of virus related junk. Its exceeded spam. About half is anti-virus software telling me they blocked a virus. The other half is various bounce messages and autoresponders from viruses going out to addresses that no longer exist or to list admin addresses, lists that require verification, etc... with my email address.

    How many legit pieces of email do I get a day? 100-200 maybe.

    The situation is absurd. If your email address is widely available (in my case, in the Perl documentation) you'll get clobbered. I had to franticly write a set of SpamAssassin rules to block the antivirus reponses to make my mail usable again.

    I've been archiving all my unfiltered, incoming mail since Feburary. 80,000 messages. If anyone seriously wants to run some statistics for how hard a popular email address gets hammered, I'll consider making it available.

  138. Exactly the Reason by Bruha · · Score: 1

    That I turned off security notifies at my company. Our Queue's were going well over 2000 and personally anyone dumb enough to accept or send .pif .bat and other file types deserve the viruses and no notices.

  139. one good thing about Sobig by ectoraige · · Score: 1

    The one good thing about SoBig is the fact that it runs it's own SMTP engine, and has predictable subjects. This let sendmail check the subject and reject it during the SMTP session, resulting in zero bounces.

    If is infinitely dumb on the part of the virus vendors to send out bounces when they *know* the virus fakes the from address.

    --
    Vs lbh pna ernq guvf, ybt bss abj. Tb bhgfvqr. Syl n xvgr.
  140. It'd be better if they weren't so condescending by Anonymous Coward · · Score: 0

    From: postmaster@aceadventure.com.sg
    Subject: Your mail server sent us a virus

    The Virus software on our mail server detected the W32/Sobig.F@mm virus.

    If your mail server had virus protection, it would have caused less work for our server and would have likely prevented one of your users from getting a virus in the first place!
    ------------
    From: me
    To: postmaster@aceadventure.com.sg

    Um no... We didn't send any viruses.

    If your server had BETTER virus protection it would not send virus notifications to spoofed sender addresses. This would *definitely* have prevented one of my users from phoning me and causing me more work!

    iptables -s 203.117.141.86 -j DROP

    Thank You,

    Postmaster.

  141. Simple self-healing solution: bounct to AV firms by KMSelf · · Score: 1

    There's a very simple expedient to hammer home the idiocy of virus autoresponders.

    Bounce virus notification messages you receive to the vendor responsible for the product. The next time a SoBig.F rolls around, and the AV vendors find that they have to deal with 1,235,000,000 additional daily emails[1], they might reconsider the merits of spewing warnings indescriminately.

    Some might take this a step further, and include a courtesy notice to Microsoft suggesting that they address security issues with their OS and application products.

    Indescriminate AV warnings aren't merely a hassle. I received ~1000 SoBig.F mails, and almost 200 warnings or bounces. Combined, this was over 35 MB of mail (my primary Internet access is over 56k dialup). A local large research university, during summer recess, received over 500,000 SoBig.F mails in one three day period.

    What's worse is companies whose nontechnical staff receive these warnings, then waste both their time and that of their IT staff chasing down false alarms. This wastes significant real resources, and dilutes the significance of genuine alerts.

    What I strongly suspect is that we're rapidly approproaching the time when all mail will need to be subjected to both virus and spam filtering, at SMTP time. Handling bounces at this stage would greatly reduce the current false notification problem.

    Notes:
    1. With 600 million email accounts, typical daily receipt being 35 messages and SoBig.F generating 1 in 17 mails, daily viral mail traffic works out to over one billion messages.

    --

    What part of "gestalt" don't you understand?

  142. SoBig trashed our servers... by Anonymous Coward · · Score: 0

    I'm the systems administrator of a promanent internet company. (There's a better than even chance that you've used our products.) We were unable to recieve email for a week due to the SoBig worm.

    We had our primary email server on the other end of a T1 which quickly became saturated. We were receiving an estimated 4 megabit/s during the peak of the worm due to the worm. (We deleted and/or deflected well over 4 million emails due to the worm.) We now have a filtering front end which is on the other end of a mondo big pipe, and should keep things to a reasonable level in the future.

    About 50% of our traffic (by bandwidth) was from faked bounces. We *might* have been able to weather the storm if so many anti-virus products didn't send out a 100k email from every intercepted copy of the worm! Even the emails without the attachment were enough to completely inundate our support account.

    So, I'd say that at least one of these two things should be done:
    First, virus programs should send to the *recipient* of the email an email telling them that such-and-who sent them a virus (instead of to the sender), or second, emails with viruses that have return addresses like "help@", "support@", "feedback@", "postmaster@", "admin@", "abuse@" or "bugs@" should be silently dropped. Furthermore, no infected attachment should *ever* be returned or forwarded under *any* circumstances.

  143. Really, that's not a benefit by siskbc · · Score: 1
    X + epsilon

    Ah, now that finally makes sense. For future reference, people typically find variable names like "1" a tad confusing.

    Please note that I am not even going to bother figuring in the cost of building/tearing down TCP/IP etc as you aren't concerned when one big image is split into multiple images on a web page are you?

    When we're talking about a system already getting clogged from attacks and stupid bounces, yes. I do think that, as usual, the human costs will be higher.

    What I really wanted to point out wasn't when a bounce message is infectios (cause I agree wholeheartedly that sending that "back" infectable is dumb)

    It is dumb, but it occurs. I'm not sure what fraction of the time.

    It is the JOB of people manning a help desk to correctly educate the users. It takes me as an outside consultant about 1 minute to explain it for even the dumbest users and nobody would run more than 50:1 user:hd ratio. A major virus breaks out, the phone is tied up for an hour. That is COMPLETELY acceptable.

    Come on, that's just insane. For one, even granting you the most amazing powers of explanation, the dumbest user is going to glaze over, stare, and nod. You might want to check for actual comprehension, I'd like to see this "stupidest user" a month later when they get a respnse from the next virus. And for what it's worth, your education defeated any purpose of the emails in terms of informative power. The bounce emails are thus either useless or harmful, depending on if they've had someone explain things to them.

    And it's not like the IT desk is sitting on their hands waiting for morons to call when a virus hits. Typically, they're damned busy. They really DO NOT need everyone calling them! It's damned easy for you to say, as an outside consultant, because your don't have to DEAL with it. You pick up the pieces later.

    Updating your virus software costs nothing. And if you need to pay because you don't have it, then are you saying that people should NOT have the latest AV SW?

    No, but a misinformation campaign is hardly a the best way to go about it, for one. And second, while updating AV is free, taking your computer into the shop (yes, dumb people really do that) because you can't figure out what's wrong with it (because nothing is!) is NOT free. If there were an efficient way to tell infected people they're infected, that's great. Or, if the email was more accurate, that would be better. Maybe it could say "This is an automatic message. Either you or someone who has emailed you in the past is infected.," That might be a tad irritating after a while. But what they're doing now is flat irresponsible because it confuses people, despite how well you THINK you're explaining these concepts. And not everyone has benefit of receiving the explanation.

    Yes, they don't understand when 50 emails come in saying they have a virus when they really don't... but they need to be responsible for finding out what this SoBig thing is, and every search engine and geek cousin or hired help knows.

    Bullshit. A car mechanic, for instance, has no more obligation to know all about the latest virus than you have to know about the latest Ford recall for a fan motor fuse. And this presupposes that they have the savvy and knowledge to ask the appropriate question in the first place! It may surprise you, but not everyone has a geek in the family. And most people want to treat their computer like an appliance, not a hobby. They have the right.

    Bottom line is there's no advantage to these emails. I would like to see stats on how many clueless people got that email and really got their shit together. I don't think it's happening. Regardless of how *bad* it is for networks, it's not *good*. And the only people typically skilled enough to use the information (ie, if I'm getting these messages I need to update AV) are those likely to be updating their AV *anyway*.

    So we'd all be better off if the AV companies added a bool to their virus defs that would clue their autoresponders into which virus forge headers.

    --

    -Looking for a job as a materials chemist or multivariat

  144. SIMPLE! by rew · · Score: 1

    When a virus scanner has an "ID" on a virus, the config for that virus should be able to say: DO NOT report to the sender. This flag should be on for "Sobig.F".

    But for a number of other virusses, the flag could be left off, so that people whose computer is infected DO get warnings.

  145. Re:OT: Helpdesk was: Virus autobounces are stupid by poohknight · · Score: 1

    We do have some talented people, but have also been very lucky. We probably couldn't handle an extremely large outage. It isn't like we want to operate with that high a ratio though. Since our current operations are (apparently) handling everything, management doesn't see a need to add more help desk positions.

    I've seen studies/surveys that indicate 50:1 is a good ratio to have. However the numbers in the surveys ranged all over, so I don't know that you can call 50:1 an average ratio.