jef moskot wrote: > On Mon, 18 Jun 2007, Dennis Peterson wrote: >> Clamscan is a terrible tool to use in real time with email. > > I would recommend it for low volume servers with cycles to burn, given > that the other option is a daemon that can potentially fail. Neither is > entirely ideal, but we should take the wide variety of environments into > account. > > Maybe the default recommendation should be clamdscan, but clamscan is not > an unreasonable choice in certain circumstances.
If you can sort out how to restart a heavy weight application for each message there's probably no impediment to figuring out how to restart a daemon should it fail. I did it in just a few lines of shell script run out of cron. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
