Seve Ho wrote:
I am trying to use Clamav-milter with sendmail. I found it cannot clean
up it socket file(.sock) opened after killing the milter process.(I use
kill -9 to kill the process, is there other prosper way to stop the
milter?) And this make me have to remove the .sock file first bef
Never mind,
I got it
- Original Message -
From:
Bit Fuzzy
To: [EMAIL PROTECTED]
Sent: Sunday, March 07, 2004 10:56
PM
Subject: [Clamav-users] Trashscan
Question
I have a question regarding Trashscan, and I'm hoping
someone has tried this.
I am trying to use Clamav-milter with sendmail. I found it cannot clean
up it socket file(.sock) opened after killing the milter process.(I use
kill -9 to kill the process, is there other prosper way to stop the
milter?) And this make me have to remove the .sock file first before
restarting.
On Sunday 07 March 2004 4:09 pm, Greg Ennis wrote:
> Everyone,
>
> Worm.SomeFool.Gen-1 was not picked up by clamscan using ClamAV version
> 0.65.
>
> It appears to me that clamscan on my system is not performing in the same
> manner as your web site even with current main and daily files.
You s
Tim B wrote:
Mike Fedyk wrote:
Tim B wrote:
I'm sure this idea has been knocked around before, but with the way
MyDoom, Bagle (beagle), and NeySky have gone through so many versions
with minor variations of their email message, has anyone thougth
about adding bayes style checking?
It wouldn't
On Sunday 07 March 2004 4:09 pm, Greg Ennis wrote:
> Everyone,
>
> Worm.SomeFool.Gen-1 was not picked up by clamscan using ClamAV version
> 0.65.
>
> It appears to me that clamscan on my system is not performing in the same
> manner as your web site even with current main and daily files.
You s
I have a question regarding Trashscan, and I'm hoping
someone has tried this.
Is it possible for trashscan to provide the name of the
virus found in the notification email?
I've tried contacting [EMAIL PROTECTED] regarding this issue, but
the address is invalid.
Mike Fedyk wrote:
Tim B wrote:
I'm sure this idea has been knocked around before, but with the way
MyDoom, Bagle (beagle), and NeySky have gone through so many versions
with minor variations of their email message, has anyone thougth about
adding bayes style checking?
It wouldn't be a definate
Sorry to be REALLY REALLY un-cool and reply to my own post (twice!)!
I found that I had to put in a proxy for the updates to work...
I'm not sure why this is (freshclam had been working for months without
it).. ?
Jon
---
This SF.Net email
Tim B wrote:
I'm sure this idea has been knocked around before, but with the way
MyDoom, Bagle (beagle), and NeySky have gone through so many versions
with minor variations of their email message, has anyone thougth about
adding bayes style checking?
It wouldn't be a definate positive, but inst
Sorry to be un-cool and reply to my own post!
I was getting the 'Malformed CVD header detected' error with my 0.65
installation.
I just installed 0.67 and am getting the same error:
-bash-2.05b$ bin/clamscan --version
clamscan / ClamAV version 0.67
-bash-2.05b$ bin/freshclam
ClamAV update proce
Hi guys,
I know this has been discussed before, but as far as i can tell in the
archives, no real resolution was found.
My freshclam had been happily working the last couple of months, but 3
days ago i started getting the "Malformed CVD header detected" error
(see below).
I am using Redhat/Fe
On Fri, 5 Mar 2004 19:37:13 -0500 (EST)
Charles Sprickman <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm looking at implementing clamav for a somewhat large userbase. Due
Please defer it for some time - an initial implementation of the ICAP
protocol should be available in this month.
--
oo
On Mar 7, 2004, at 3:12 AM, David Strainchamps wrote:
with the command : clamscan -r /
but although i exclude the dir /dev the error occur always
That command does not exclude /dev since /dev is a subdirectory of /
Rick V.
---
This SF.Net ema
On Sun, 2004-03-07 at 01:12, David Strainchamps wrote:
> The error appear when i scan all the disk
> with the command : clamscan -r /
> but although i exclude the dir /dev the error occur always
Oh I see. Sounds like perhaps the --exclude option on clamscan has a
bug in it.
>
>
>
> >
>
>
>
On Sunday 07 March 2004 4:09 pm, Greg Ennis wrote:
> Everyone,
>
> Worm.SomeFool.Gen-1 was not picked up by clamscan using ClamAV version
> 0.65.
>
> It appears to me that clamscan on my system is not performing in the same
> manner as your web site even with current main and daily files.
You sh
Everyone,
Worm.SomeFool.Gen-1 was not picked up by clamscan using ClamAV version 0.65. My
system identified the file as having executable code and prevented delivery until
checks could be made. My main.cvd, and daily.cvd files seemed to be current but I
ran freshclam and received a report that
I'm sure this idea has been knocked around before, but with the way
MyDoom, Bagle (beagle), and NeySky have gone through so many versions
with minor variations of their email message, has anyone thougth about
adding bayes style checking?
It wouldn't be a definate positive, but instead a this is
Le dimanche, 7 mars 2004, à 08:53 Europe/Paris, Michael Torrie a écrit :
On Sun, 2004-03-07 at 00:24, David Strainchamps wrote:
davidstr# clamscan -r -l /users/davidstr/virus /dev/fd
ERROR: Can't open file /dev/fd/3
Bus error
I was as root
when i want to remove this file
davidstr# rm /dev/fd/3
On Sun, 2004-03-07 at 00:24, David Strainchamps wrote:
>
> davidstr# clamscan -r -l /users/davidstr/virus /dev/fd
> ERROR: Can't open file /dev/fd/3
> Bus error
>
> I was as root
>
> when i want to remove this file
>
> davidstr# rm /dev/fd/3
> rm: /dev/fd/3: Bad file descriptor
>
> Can anybody
20 matches
Mail list logo
