On Tue, 02 Sep 2003 at 22:55:18 -0700, Brian W. Antoine wrote: > At 11:17 PM 9/2/03, you wrote: > >My solution was to use Amavis-New/amavis-milter. Since getting it > >installed and running, I have had no problems whatsoever, and it's been > >running now for about 5 days. The nice thing about amavis as well, as > >there is built in spam assassin scanning, and it's all controlled by the > >amavisd.conf file, which you can tweak a bit. > > Yeah, I'd noticed that sourceforge itself used amavis instead of clamav-milter, > that should have been a red flag. I assume that amavis calls clamscan instead > of clamdscan, so even if something pukes, it only effects a single email instead > of taking out your mail server when clamd dies.
I'm not sure if you mean amavis really or _amavisd-new_. I don't know on amavis, but if you mean amavisd-new, I can add that it uses as many various AV scanners as needed. Usually clamd (not clamscan) as a "primary" scanner. When a primary scanner (clamd or other) fails, it uses any "backup" scanners available, like clamscan. So in normal situation clamscan is not used, only in emergency situation, which is good for performance. -- 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
