On Mon, 16 Aug 2004, Todd Lyons wrote:
It shouldn't, however change if a virus is accepted - since sendmail should be tempfailing mail until the milters are functioning.
Incorrect, depending on how you define your milter call for sendmail.
So by not specifying an F=T setting, you're telling it to pass it through in the event of clamav-milter failure. I'm not sure what the case would be if clamav-milter was still fully functional, but clamd failed.
It does bad things, by default (tempfailing the mail, as I recall). The fix is to give the --dont-scan-on-error option to your clamav-milter.
My full set of clamav-milter flags are: CLAMAV_FLAGS="--quiet --headers --noxheader --dont-log-clean --dont-scan-on-error --max-children=10 local:/var/run/clamav/clmilter.sock"
I have found that setting the --max-children flag to 10 or a close value of 10 may put a little bit slow your SMTP service.
I don't like very much the --dont-scan-on-error option, what are the benefits of using it?
Best Regards, Matías.
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
