We are using clamscan.exe to scan e-mail on our Mercury/32 mail server. We have an occasional but persistent problem in which some messages are blocked because clamscan aborts the scan for some unknown reason. Here's an example of a scan result when this happens:

Scanning aborted...

----------- SCAN SUMMARY -----------
Known viruses: 8782
Engine version: 0.90.1
Scanned directories: 0
Scanned files: 0
Skipped non-executable files: 0
Infected files: 0
Data scanned: 0.00 MB

The program never says why scanning was aborted. As you can see, the number of known viruses is incorrect. When we've had the problem today, the incorrect count has ranged from 254 to 64256. The correct number right now is 112127. The problem has occurred about five times so far today. The first three were within a few seconds of each other, as were the second two occasions. I'm guessing this is not a coincidence.

I've attempted to configure our realtime virus scanner to avoid scanning the ClamWin directories, including the virus db directory, so I don't think that's a problem.

Any thoughts on why this is happening or how I might figure it out and fix it? Thanks.

upgrade to 0.90.1.1, 0.90.1 has a bug in db sig updating, or wait for coming 0.90.2

Upgrading to 0.90.1.1 did not fix the problem. I've now installed 0.90.2 and am waiting to see what that will do.

We're still seeing the "Scanning aborted" problem with version 0.90.2. It doesn't happen every day, but when it does it lasts for less than 10 seconds, apparently aborting scanning on all messages during that period, then resumes normal operation again. Any ideas? Is there a way to get a log to tell exactly WHY it's aborting the scan? Thanks.

no clue about "scanning aborted", for virus defs I suggest you to wipe all files in db directory and re-download it by calling the updater