Steven Stern wrote:

On second thought, maybe I should have a chance to look at incoming messages
rather than bouncing them with a 550. I've removed the -b from the
clamav-milter startup.  I've replaced it with --quarantine=/var/spool/clamav.
Is this what's necessary to quarantine messages in /var/spool/clamav?

old:
CLAMAV_FLAGS=" -lo --b --max-children=10 --force-scan --quiet --dont-log-clean
--server=localhost local:/var/run/clamav/clamav-milter.sock"


new:
CLAMAV_FLAGS=" -lo --quarantine-dir=/var/spool/clamav --max-children=10
--force-scan --quiet --dont-log-clean --server=localhost
local:/var/run/clamav/clamav-milter.sock"



You must use LocalSocket for communication between clamd and clamav-milter to get
--quarantine-dir working.


Edit clamav.conf and CLAMAV_FLAGS.

Petr




------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to