Page 1 of 1
Clamav
Posted: Wed Nov 15, 2006 12:05 pm
by rex007can
Is there a howto for server 10.1 for configuring ONLY clamav, not the whole amavisd thing.
I only want virus scanning. Already got MailWasher taking care of spam.
Posted: Wed Nov 15, 2006 12:11 pm
by dkelly
Please go to
http://www.scalix.com/support/knowledgebase.html. If you use the search string "clamav", it will return a How To for you.
Cheers
Dave
Posted: Wed Nov 15, 2006 12:20 pm
by rex007can
Good.
Thanks.
By the way, when compiled on RedHat, Clamav installes clamdscan in /usr/local/bin, not in /usr/bin
It may be the same in other distros, haven't tried it.
The engine not being able to find clamdscan causes the server to put every incoming and outgoing message in the error queue.
Just so you know. (Don't ask me how I found out...)
Posted: Wed Nov 15, 2006 12:23 pm
by dkelly
rex007can wrote:Good.
Thanks.
By the way, when compiled on RedHat, Clamav installes clamdscan in /usr/local/bin, not in /usr/bin
It may be the same in other distros, haven't tried it.
The engine not being able to find clamdscan causes the server to put every incoming and outgoing message in the error queue.
Just so you know. (Don't ask me how I found out...)
If you are building from source ( rather than installing the RPM ), you need to use --prefix=/usr with the configure command otherwise it *will* be installed in /usr/local/bin
It's intentional that messages are added to the error queue if virus scanning is configured but not working correctly. Would you rather we allowed virus-infected messages through
Cheers
Dave
Posted: Wed Nov 15, 2006 12:39 pm
by rex007can
Would you rather we allowed virus-infected messages through
Not what I was implying.
I usually edit the omvscan.cfg file from the .../sys folder to point it at the right place. But I almost get caught every time I run an upgrade.
Posted: Wed Nov 15, 2006 12:58 pm
by rex007can
BTW:
Reply received: 503 "ClamAV" cannot scan Scalix-owned file Access denied. ERROR
Pid of logging process: 27680
Posted: Wed Nov 15, 2006 12:59 pm
by dkelly
Please read the HowTo.
There are specific instructions on making the clamav user part of the Scalix group to avoid this error.
Cheers
Dave
Posted: Wed Nov 15, 2006 1:26 pm
by rex007can
But I did make clamav part of the scalix group.
And I have clamd running as clamav
Must be something stupid.
Posted: Wed Nov 15, 2006 2:54 pm
by rex007can
Fixed...
Running clamd as root...