Michael Dankov wrote: > > Clamd+clamav-milter are quite unstable when clamd sessions are timed out. > More timeouts, more unstability. Current default behavior of clamav-milter > is to connect to clamd as soon as sendmail receives "mail from: <[EMAIL PROTECTED]>" > from mail client. Some mail clients (dial-upers, spammers, overloaded mail > hosts) may send a message for 2 hours and more... Having timeout of 180 sec > is definitely too low for clamav-milter default mail scanning. > > You have two options: (1) increase this timeout to a big value. 7200 was > not enough for me: I still had 1-2 timouts per 24 hours. (2) use option > --quarantine-dir=/var/quarantine when starting clamav-milter. Then milter > will pre-save message into a temporary file in that directory, and pass it > to clamd only after it is really ready for scan. As a side effect :) > infected messages will be left in that dir for your review.
I've put the quarantine-dir flag in now, so hopefully that'll cure it. Thanks for the advice. Mike. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
