On 11/16/2010 8:15 AM, dave wrote: > My update around 12hrs ago seems to have started triggering on > MBL_142932.UNOFFICIAL at an alarming rate. > > I wonder if anyone else has noticed this? > > On the premise that there was a 'mistake' I've updated defs a few times > already, but the issue remains. > > Anyone know if this is something worth reporting? That database didn't even load (using Gerard Seibert's script) Date: Mon, 15 Nov 2010 03:14:53 -0600 (CST) ********** WARNING ********** Unable to install: mbl.ndb Clamscan exited with error code 2 -- René Berber