> So ClamAV as a package won't silently 'not work' for the safety of > users - and this has been the justification for their approach to > this issue. But at the very same time they are recommending a setup > which will silently not scan mail if there's a problem with ClamAV.
I guess it depends on the definition of "silent" and which point of view is pertinent. Just 30 minutes ago I was battling one of our clam installs. Being a higher usage (outgoing only) server, the upgrade from 0.95.x to 0.96 just happened after I was happy that everything was working well on the others. Long story short, the active clamav-milter.conf was pointing to the wrong directory for the socket (but it was similar enough I didn't notice on first (or fourth) glance). Sendmail couldn't connect to clamd thru the milter. Everything else worked fine, mail kept flowing, spamassassin went about its business, but nothing was clammed for 20 minutes. So from the remote point of view, mail kept flowing, and the errors were "silent." The log files, of course, were not silent.
signature.asc
Description: PGP signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
