does anyone else have a problem with f-prot updating... my system says it
can not find the server
Bennie
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 01, 2002 4:41 PM
Subject: Re: [Declude.Virus] Badtrans got through
* I'm running Declude 1.34 with F-prot with definitions dated 1/28/02. The
version of Badtrans that was caught by Norton on the desktop was reported
as [EMAIL PROTECTED]
Which version of F-Prot? You need 3.11 in order to catch some variants of
Badtrans.
-Scott
---
F-Prot is version 3.11 - I've definitely seen other variants of Badtrans,
and this one, .enc. get caught in the past.
At 11:47 AM 2/1/2002, you wrote:
* I'm running Declude 1.34 with F-prot with definitions dated 1/28/02.
The version of Badtrans that was caught by Norton on the desktop was
: [Declude.Virus] Badtrans got through...
F-Prot is version 3.11 - I've definitely seen other variants of Badtrans,
and this one, .enc. get caught in the past.
At 11:47 AM 2/1/2002, you wrote:
* I'm running Declude 1.34 with F-prot with definitions dated 1/28/02.
The version of Badtrans that was caught
We caught it on 1/31/02 with Declude 1.35a, F-Prot 3.11 1/30/02 defs.
-Linette
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jeff Lesperance
Sent: Friday, February 01, 2002 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.Virus] Badtrans got
* The Declude log reported that Q file as Virus Free [MIME: 0 0]
There's a clue.
It looks like the E-mail may have been severely malformed, so that the
attachments could not be view (or possibly in a plaintext segment). The 0
0 means that Declude detected 0 attachments.
You don't happen to
