On 2011 Feb 11, at 17:56 , Vincent Fox wrote:
> On 2/11/2011 8:31 AM, Jan-Pieter Cornet wrote:
>> On the other hand, since you haven't updated ClamAV in over a year, leading 
>> to (significantly) decreased detection, maybe the scanning of email isn't 
>> top priority, and your mail scanning engine needs to fallback to letting 
>> mail through on scan errors.
>> 
> Forgive me for this but....
> 
> 3-4 days after v0.97 is released, v0.95 is considered obsolete and
> no longer worth testing databases for.  

Yes, that sucks. And the clamav team has admitted as much and promised to do 
something about it.

I didn't like that either, I am running 0.95 myself, so clamav stopped 
functioning. To remedy the situation, I dug into my archive and recovered an 
older, working, daily.cvd, and installed that on top of the broken one.

The reason I replied is that the OP mentioned that 'mail stopped because of 
this', somehow implicating it's ClamAV's fault. It isn't. There are a number of 
reasons that a virus scanner can fail, a bad database is just one of them. What 
I wanted to point out is: unless you consider virus scanning more important 
than the actual flowing of emails, you need to make sure that failures in the 
virus scanning don't stop your mail from functioning.

If scan failures do prevent your mail from being delivered, then right there is 
your first configuration error: go fix it so you don't depend on the virus 
scanner to always behave correctly, because it simply won't. There will always 
be unpredictable circumstances that make your virus scanner crash, so you must 
be prepared to deal with that.

If that makes you feel uneasy, because it might let unscanned mail through, put 
a monitoring mechanism in place that alerts you as soon as the virus scanning 
fails. Or get a second virus scanner, and use them both in parallel (that's 
what I do - also gives you a nice way to compare performance).

-- 
Jan-Pieter Cornet <joh...@xs4all.nl>
"People are continuously reinventing the flat tyre".




_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to