Do you run clamd as root, and is the local socket path accessible by the qmail user?Actually, it technically is clamscan, but for the installation i used (www.qmailrocks.org) a step in there says to copy clamscan to clamdscan so running clamscan and clamdscan effectively means the same thing. So yes technically you are correct, but for my setup, my statement is correct as well. Not to mention that using the original clamdscan (which is now clamdscan.orig on my system) gives me an error and will not scan any files.
[EMAIL PROTECTED] jmaul]# clamdscan.orig /home/jmaul: Can't access the file ERROR
It does this for ANY file i try to scan.
Thanks for the reply though.
Jim
You really should use (the real) clamdscan, as it is magnitudes faster.
Hi all,
I think you should say clamscan with --mbox because I haven't found --mbox flag for clamdscan isn't it?
Nevertheless if a similar flag exist flag exist for clamdscan (0.65 release) I will be very interrested in.
There isn't such a switch form clamdscan (use clamav.conf's "ScanMail" directive), and won't be until clamd gets his new network protocol.
Thomas
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
