After trying to use the server today and Clamwin taking all the CPUSIGH...
I decided enough was enough and I would pull out the HOWTO and install ClamAV instead. Having uninstalled Clamwin and installing ClamAV, I noticed the installer had created 2 services, one for Clamav and one for freshclam (definitions updater).
So, all I did was add a scheduled task to run freshclam.exe once a day and told hMailServer (on the anti-virus tab) to use ClamWin and pointed the ClamScan executable box to C:\clamav\clamscan.exe and the path to ClamScan database to C:\clamav\data\main.cvd et vola!
You don't have to run FreshClam manually if the FreshClam service runs. If you're using the service you can configure the number of updates per day in the freshclam.conf file. Also, you have to point hMS to ClamD
Scan.exe, not ClamScan.exe otherwise the process will be not much faster than with ClamWin.
Now I have my system resources back and hopefully the red light on my server will stop coming on for no real reason other than the machine was almost always at max CPU usage. I used the GFI Virus Email Test
on a mailbox to check it was still doing it's job and it was!
Perhaps this thread should be the new ClamAV howto, it's a lot easier now, and the "old way" might put the less determined off!
You're right, the informations in the big how-to thread are meanwhile outdated. Actually I've promised to write a new how-to some day but as you've noticed, the installation procedure is now quite simple so I wouldn't even know what to write there. Also the next hMS version will include a native interface to ClamD and (because I doubt Martin will remove the ClamWin integration possibility) will hopefully warn in BIG RED
letters what can happen if someone uses ClamWin on a slightly loaded server.
Thanks for your comments and best regards,