Quoting David Boltz <[EMAIL PROTECTED]>: > Thank you for the information. I have given it a try and setup the > clamd.conf file to connect to the already existing spf-milter. I then
Huh? No way that would work! You didn't read what I wrote, or you way misunderstood it. > changed the clamav-wrapper to use clamdscan instead of clamscan. I That would work, if done right (remove the options being passed, etc). But it would probably be easier, and certainly better, to upgrade to a version of MailScanner that has native clamd support instead. > then restarted MailScanner and it seems to be ok because if I run "top > -d1 | grep clam" I see that calmav-wrapper and clamdscan is being > called. The only problem I see is that if I go to MailWatch and check > the clamav status I get a bunch of warnings. followed by the > information I want. It appears that this is caused by the > clamav-wrapper file but I'm not sure why. Any ideas? Because clamav-wrapper is meant for clamscan, and hence passing parameters to it. You need to stop it from doing this, since clamdscan/clamd uses the clamd.conf file instead for this purpose. -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns! _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
