I have a few users using Clamwin in association with some older versions of OUtlook. Whenever the OLAddin is running it hogs resources and slows evreything down.

Is there a fix for this

If ClamWin works okay for you on newer versions of Outlook, the best fix is to install the newer version.

Regards,

Gee Bob thanks, why didnt I think of spending $400 a user to upgrade their office without looking for a more cost effective solution!!!!

Sorry - wasn't talking about budgets! Just how many users are you talking about? And why do some users have the newer Outlook and some don't? While we're at it, ClamWin is still beta software, and as a general rule, you shouldn't use beta software for business or critical applications. If you do, problems like this (or worse) can manifest.

Regards,

Sorry Bob, you caught me on one of those days where users moan at you because of their problems and all see the solution as buying new stuff but the guys with the cheque books don't want to spend anything. End result users are pissed off at me cos they can see the solution and see it as my fault that the upgrades haven't been done.

The reason people are on different versions is probably universal for small companies, someone starts and gets bought a new machine that comes with office, then a year later more people start and get new machines that come with office, only now its a different version of office.

The main reason for posting was to alert people, especially those at Clamwin, that with, in this case at least, Office 2003, the OLAddin claims 110,000K+ of memory usage, way more than any other application. It bogs down Outlook and turns a 2-3 second load time into a 2-3 minute load time.

I wasn't sure if there was a setting I could change to reduce the demand or any other way of getting round this problem. If there is then the only problem I have is all the false positives

Alch and Sherpya were looking at the false positives a while ago. I haven't heard of anything of their progress. The only thing we can do at present is keep the infected files option set to Report Only (not Quarantine or Remove), and, of course, report false positives to Clam AV at http://www.clamav.net/sendvirus/ on the web. Clam needs more Windows software on the false positive "farm" they use to check before the signatures are released. They could also use more equipment, but they have budget constraints also.

As for the problem with older versions of Outlook, you might try some web searching to see if someone has found a way to mitigate it. And, of course, be sure scanning priority is set to Low. Perhaps Clam/ClamWin could do some CPU throttling in the future. Microsoft does a good job limiting CPU use with their Security Essentials now in beta.

Regards,

I'm running Windows XP Pro - fully patched and Office 2007 Enterprise also fully patched and OlAddin.exe is hogging up more than 100MB of RAM. The only thing that I have found that solves the issue is open Outlook -> Tools -> Trust Center -> Add Ins -> Manage COM Add Ins (at the bottom) and then uncheck Clamwin Antivirus.

CAVEAT - This disables the scanning of your emails and email attachments

[/img]