Can't get clamd working???
Gerry Doris
gdoris at rogers.com
Wed Jun 6 04:19:09 IST 2007
René Berber wrote:
> Gerry Doris wrote:
>
> [snip]
>> virus.scanners.conf has the following entry for clamd
>>
>> clamd /bin/false /usr/local/sbin
>
> Wrong, the original file had:
>
> clamd /bin/false /usr/local
>
My clamd is located in /usr/local/sbin. It is NOT in /usr/local
>> and MailScanner.conf has these lines
>>
>> Clamd Port = 3310
>> Clamd Socket = /tmp/clamd
>> Clamd Lock File =
>> Clamd Use Threads = no
>>
>>
>> What am I missing!!!
>
> Virus Scanners = clamd
>
> if auto doesn't work for you, and it probably won't: how do you expect it to
> choose between the 3 options for clamav if any one can be used?
I stated in my original email that I had the following line...
Virus Scanners = clamd trend f-prot bitdefender
I'm running four virus scanners (this is a test system). For some
reason MailScanner finds clamavmodule but not clamd. It also finds the
other 3 scanners without problems.
More information about the MailScanner
mailing list