We have been successfully using clamassassin, in combination with clamav, for several months. In an effort to reduce the load on our mail server, we installed clamd and changed from the use of clamscan to clamdscan.
With clamd started, and /usr/local/bin/clamassassin variable CLAMSCAN set to /usr/local/clamdscan...incoming email "hangs up" and I finally get the message "ERROR: ScanStream: accept timeout" in /var/log/clamav/clamd.log. Thinking that maybe there is a permission problem somewhere, I commented out TCPAddr (127.0.0.1) and TCPPort (3310) from /etc/clamav.conf and used the LocalSocket option (/var/run/clamav/clamd.sock). Now email goes through just fine, and quickly. Can someone help me explain this behavior? I apologize if this should be directed to the clamassassin list . For clamav and clamd I am using 0.74-1-1 and for clamassassin I am using 1.1.1. The mail server is Fedora Core 1. I am using the binary package for clamav/clamd from Dag Wierrs. The user/group running the clamd daemon is clamav. ----------------------------------------------------------------- Mike McCandless [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
