On Mon, 19 Jul 2004 at 7:38:56 -0500, John Fleming wrote:
> - Original Message -
> From: "John Fleming" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 18, 2004 10:14 PM
> Subject: [Clamav-users] Clamdscan Error 2
>
> > ClamAV (clamd) was working fine until I updated D
have you tried installing from source??
On Mon, 19 Jul 2004 07:38:56 -0500, John Fleming <[EMAIL PROTECTED]> wrote:
>
> - Original Message -
> From: "John Fleming" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 18, 2004 10:14 PM
> Subject: [Clamav-users] Clamdscan Erro
- Original Message -
From: "John Fleming" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 18, 2004 10:14 PM
Subject: [Clamav-users] Clamdscan Error 2
> ClamAV (clamd) was working fine until I updated Debian unstable today.
Now
> I'm getting the following header added to A
On Fri, Feb 20, 2004 at 06:46:45PM -0500, Michael H. Martel said:
> --On Friday, February 20, 2004 5:33 PM +0100 Tomasz Kojm
> <[EMAIL PROTECTED]> wrote:
>
> >Don't use procmail and clamav globally - such a solution is
> >completely inefficient. You should scan the mail directly on the MTA
> >leve
--On Friday, February 20, 2004 5:33 PM +0100 Tomasz Kojm <[EMAIL PROTECTED]>
wrote:
Don't use procmail and clamav globally - such a solution is completely
inefficient. You should scan the mail directly on the MTA level.
You're suggesting something like the milter option yes ? Is it really
going
Interesting. If you follow this path, I would be very interested in seeing
your proc recipe.
james
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Kojm
Sent: Friday, February 20, 2004 10:34 AM
To: [EMAIL PROTECTED]
Subject: Re: [Clamav-users
On Fri, 20 Feb 2004 06:31:42 -0500
"Michael H. Martel" <[EMAIL PROTECTED]> wrote:
> however, I want to invoke it in /etc/procmailrc as a global for all
> users. When I do this, clamdscan returns the error :
Don't use procmail and clamav globally - such a solution is completely
inefficient. You sh
On Thu, 04 Dec 2003 22:13 , Thomas Lamy <[EMAIL PROTECTED]> sent:
>McKeever Chris wrote:
>
>> # clamdscan --version
>> clamdscan / ClamAV version 0.65
>>
>>
>> ]# clamdscan
>> connect(): No such file or directory
>> ERROR: Can't connect to clamd.
>>
>> --- SCAN SUMMARY ---
>>
McKeever Chris wrote:
# clamdscan --version
clamdscan / ClamAV version 0.65
]# clamdscan
connect(): No such file or directory
ERROR: Can't connect to clamd.
--- SCAN SUMMARY ---
Infected files: 0
Time: 0.001 sec (0 m 0 s)
any ideas? clamav.conf file? or permissions issues?
I sugge
