MailScanner broken suddenly?!?!

[Raymond Dijkxhoorn]

Hi!

> Can you explain to me exactly what the problem is and what you have
> found and diagnosed about it please?

> This thread has got very long and convoluted. I use clamav or
> clamavmodule on all my servers, and though clamscan seems to take 20
> seconds or so to load the sigs at the moment, nothing worse than that is
> happening on my systems.
> So what is the problem?

Most of the old users have only the line to monitor the .cvd files. In the 
new default config you are now sending along, this is fixed. There you 
have:

Monitors for ClamAV Updates = /usr/local/share/clamav/*.inc/* /usr/local/share/clamav/*.cvd

And thats fine.

*ALL* users that were stuck now have not updated their config. Perhaps the 
udate config script should overwrite this value or something, donno, 
but they should really monitor both else they get in trouble after 
every update of the clamav main files.

Thats what was happening today, they reversed back from the 
incremental files to a new release of the main files.

See clamsite:

ClamAV Virus Databases:
main.cvd ver. 44 released on 20 Jul 2007 18:01 +0200
daily.cvd ver. 3709 released on 20 Jul 2007 19:59 +0000

So a lot of sites got issues after 20:00 and some more who just missed the 
update and now have the problems an hour later ;)

So in short, the NEW MailScanner distributions allready have this issue 
fixed. Old users, taht dont manually edit this part of their config are 
stuck, and really SHOULD update it ;) To avoid more discussion after the 
next main database update ;)

Bye,
Raymond.