Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-25 Thread Jonathan
Doubtful - we've been catching the same Netskys both before and after these slipped through. Hundreds of em. Jonathan At 06:43 AM 2/25/2004, you wrote: I realize this generally does mean it's corrupt -- but you're missing the "scary" part. If I scan the file that came in with the same instal

Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-25 Thread R. Scott Perry
I realize this generally does mean it's corrupt -- but you're missing the "scary" part. If I scan the file that came in with the same install of F-Prot, (from the mail server), it catches it as Netsky. If scanning it from F-Prot on the mailserver catches it, it should get caught when Declude V

Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-24 Thread Jonathan
I realize this generally does mean it's corrupt -- but you're missing the "scary" part. If I scan the file that came in with the same install of F-Prot, (from the mail server), it catches it as Netsky. Jonathan At 06:23 AM 2/23/2004, you wrote: We've gotten several, here are a couple: 02/18/2

Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-23 Thread R. Scott Perry
We've gotten several, here are a couple: 02/18/2004 10:33:12 Q93c835e1004873e1 Scanned: Virus Free [MIME: 2 22065] 02/18/2004 15:56:37 Qdf95a7880150b2de Scanned: Virus Free [MIME: 2 22057] Running F-Prot, Mcafee and now AVG. The "Virus Free" message means that none of the virus scanners detected a

Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-22 Thread Jonathan
We've gotten several, here are a couple: 02/18/2004 10:33:12 Q93c835e1004873e1 Scanned: Virus Free [MIME: 2 22065] 02/18/2004 15:56:37 Qdf95a7880150b2de Scanned: Virus Free [MIME: 2 22057] Running F-Prot, Mcafee and now AVG. Jonathan At 07:53 AM 2/21/2004, you wrote: Has anyone seen a lot of W32

Re: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-21 Thread R. Scott Perry
Has anyone seen a lot of W32.Netsky.B slipping through? No. > Why didn't declude tag it? I don't see any errors in the vir* logs, and others have been getting infected notices. What does the Declude Virus log file say for that E-mail? -Scott -

RE: [Declude.Virus] W32.Netsky.B@mm Slipping through

2004-02-20 Thread Jonathan
Sidenote to the above .. I ran F-Prot (right from the mail server, actually) on one of the files from quarantine. stuff.com.dont-execute Infection: W32/[EMAIL PROTECTED] Results of virus scanning: Files: 1 MBRs: 1 Boot sectors: 1 Objects scanned: 3 Infected: 1 Why didn't declude tag it? I don'