At 09:00 AM 12/20/2004, you wrote:
Todd Lyons wrote: > [EMAIL PROTECTED] wanted us to know: > > >>>>I am running Qmail+Qmail-Scanner+ClamAV on a FreeBSD 5.3 machine and >>>>followed the qmailrocks.org directions to the tee. When running > > > Unless it's been fixed recently, that howto tells you to have clamdscan > symlinked to clamscan. That's a very inefficient way to use it on a > mail server unless you have very low traffic. > > Is that in fact what you did? If not, then ignore this email.
This is not the case anymore. The Howto has been changed and now uses the real clamdscan.
-Jim
This is still the case on freebsd, it fixed my problem after reading this message, rename clamdscan to clamdscan.org ln -s /usr/local/bin/clamscan /usr/local/bin/clamdscan
All of a sudden my emails are being scanned and it caught the test_installation.sh emails.
But you're not fixing the real problem, which is most likely
a) a communication problem between the client (clamdscan) and the server (clamd), eg a wrong socket path, or
b) a permissions problem, where clamd can't read the files it's supposed to scan. Clamd needs read privileges (qmr.org states the user has to be "qscand")
I can't tell which one it is without the actual error message. Additionally, I can't find from a quick glance thru qmr.org how they set up clamav's client/server communication, and if qmailscanner runs chrooted (and where).
Thomas _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
