Looking at the antivirus logs it appears that Clam times out all of the time and does not check the file for a virus. It also leaves the files in the scratch directory which is growing.

Reading previous postings I made sure that I was configured correctly, clam is running with administrator permissions and I modified the registry to give it an additional 10 seconds moving it from 20 to 30 seconds before timeout.

While it is not that busy of a mail server I would hate to go longer than 30 seconds. Is this normal?

The ClamAV that is installed with MailEnable runs as a service and we pass it the message file to check. You can check it is working ok through a command prompt. Open a prompt, navigate to the ClamAV directory and you can use the clamdscan.exe to scan a file like:

There is something wrong if it times out, as when it runs as a service the virus definitions are kept in memory and scanning is fairly fast. There was a bug in ClamAV though that it failed on specially crafted messages (I think it was due to MIME boundaries), so there was a Clam update. This is included in the new beta we have at

https://www.mailenable.com/beta

So I would recommend you try the command line to make sure it is scanning files fast enough and check the scratch directory files to see if they are actually valid. If they are not valid, then update the server to the beta to get the new Clam.

The errors seem to indicate that the file is being locked by anther process and not able to be removed. Do you have another Antivirus program running on the server with resident AV scanning enabled? If so you need to exclude the "MailEnable" folder.