> WARN: all primary virus scanners failed, considering backups
> I looked on the clamav web site and found this statement:
> clamscan is enabled automatically if clamscan binary is found at
> amavisd-new starup time. clamd is activated by uncommenting its entry in
> the @av_scanners list, file /etc/amavisd.conf.
> I see in my amavisd.conf file that the 'Clam Antivirus-clamd' entry
> under @av_scanners is commented out, should it not be?
You should uncomment it. As you do it, pay attention to the comments
immediately following the clamd entry in amavisd.conf - they tell you
how to get clamd and amavisd working together. In a nutshell, you need
to make sure that filename of clamd socket is correct in amavisd.conf
and that clamd runs as the same user who is running amavisd. Besides
changing clamav.conf this involves some tinkering with file/directory
permissions (of clamav files/directories), but this is all pretty
> clamscan is what amavisd is resorting to after the Warning, is this a
> bad thing?
They say that virus scanning via clamd is faster than via clamscan, but
I haven't really done any measurements.
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* Windows NT - the world's only 80 MB solitaire game!
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"