On Sat, 2010-02-27 at 09:56 +0200, Török Edwin wrote:
> >
> > [ch...@localhost Virus]$ clamdscan - > fd[12]: Email.Trojan.GZC FOUND
> >
> > --- SCAN SUMMARY ---
> > Infected files: 1
> > Time: 0.191 sec (0 m 0 s)
> >
> > Is there a reason behind this?
>
> Email.* signatures ar
On 02/27/2010 12:56 AM, Chris wrote:
> I'm a bit confused, sometimes that's not hard to do. I'm running the
> ClamAv plugin with SpamAssassin and one spam was marked with the above
> virus. When saving just the infected attachment and running
>
> [ch...@localhost Virus]$ clamdscan - fd[12]: OK
>
I'm a bit confused, sometimes that's not hard to do. I'm running the
ClamAv plugin with SpamAssassin and one spam was marked with the above
virus. When saving just the infected attachment and running
[ch...@localhost Virus]$ clamdscan -
signature.asc
Description: This is a digitally signed messa
Tomasz Kojm wrote:
> On Fri, 29 May 2009 17:21:49 +0800
> cc wrote:
>
>> /var/tmp#freshclam -V
>> ClamAV update process started at Fri May 29 17:21:04 2009
>> main.cld is up to date (version: 51, sigs: 545035, f-level: 42, builder:
>> sven)
>> daily.cld is up to date (version: 9404, sigs: 24411,
On Fri, 29 May 2009 17:21:49 +0800
cc wrote:
> /var/tmp#freshclam -V
> ClamAV update process started at Fri May 29 17:21:04 2009
> main.cld is up to date (version: 51, sigs: 545035, f-level: 42, builder:
> sven)
> daily.cld is up to date (version: 9404, sigs: 24411, f-level: 42,
> builder: guit
Hi,
I received a typical virus-infected e-mail (UPS-type) but neither
NOD32 nor ClamAV (0.95) could detect it.
So I moved the file to system with an updated ClamAV system (0.95.1).
(ClamAV 0.95.1/9404/Fri May 29 11:17:02 2009). I ran freshclam.
Scanned both the ZIP and unzipped file on a Linux s
