+1

I'll have the guys look into it and get it updated. Thanks. 

Derek,

first of all thank you for updating ClamAV to 1.4.1 with SmarterMail build 9028.

But there's an issue with it after build 9028 is installed: The bin files should be placed in "C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Clam\bin64" but the installer puts them in a subfolder of this folder so that ClamAV isn't starting.

After installing build 9028 you have to move these files from the subfolder to "C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Clam\bin64" and then ClamAV will start.

Kind Regards

I verified this -- looks like the Windows package changed its zip structure. Not an issue on Windows as it downloads directly, as most Linux server installs do. We'll have a Build out today that resolves this moving forward: so you can move the files manually, or use today's Build. 

We now see two separate "ClamAV - clamd" processes running under the MailService process.

Is that expected?

I can't confirm that there are two separate processes. But I didn't try the new build of SmarterMail. I'm sill on build 9028 and moved the bin files to the right folder.

Michael, was that on an upgrade?

@derek that's right.

We updated from Build 9028 to Build 9032

Now we see two ClamAV processes in Task Manager under MailService (see attachment)

Interesting. We'll need to keep testing, but on a couple of upgrades we've just seen a single Clamd process. 

I installed 9032 over 9028 and I only have one clamAV running.

Updating to build 9035 worked without manually moving the bin files. And I don't see two ClamAV processes running.

Uninstalled 9032. One ClamAV process remained. But couldn't get it's properties. Ended task on it. I'm thinking it was just hung. Restarted machine. Installed 9035. Now only one ClamAV process. So perhaps something just corrupted on the Build 9028 to Build 9032 update maybe ClamAV wasn't really there, but hung somehow. Anyhow, seems normal for now. Thx all.

Why is this in the delivery log?

02:35:53.058 Updating ClamAV database...
02:35:53.246 Updating the ClamAV database has completed successfully