On Wed, 03 Sep 2003 at 7:51:32 -0700, Brian W. Antoine wrote: > At 11:21 PM 9/2/03, you wrote: > >I'm not sure of the status for clamav-milter, but IIRC it's clamd dying in most cases, due to problems in the mbox.c code. ALl my clamd problems went away after I disabled the "ScanMail" option in clamav.conf. > > Ok, am I missing something here? Isn't the "ScanMail" option needed because > we're trying to scan for viri in incoming mail? >
ScanMail isn't really needed when one uses amavisd-new (or other "deMIMEr"). That's amavisd-new's job to extract files from mail messages. > Besides the clamd issue, I really wish milter writers > would provide a way to fail more gracefully. Blocking all incoming mail might be > an option for an individual user, but an ISP would probably want an option to > simply let the mail flow unchecked while a warning was sent to somebody. Waking > up to discover that your mail servers have been offline all night and your users > are raising hell is not a good way to start a day. Again: when amavisd-new can't use any "primary" AV scanner (like clamd), it goes to "backup" scanners (like clamscan). Mail flow is _not_ stopped. > Of course the best option would be for the code not to fail in the first place, > but ... :) Sure, but "nobody's perfect" ;-) . -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only [EMAIL PROTECTED] http://www.lodz.tpsa.pl/ | ones and zeros. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
