[quote user="jessicarabbit"]The ClamAV world seems in flux. ClamAV now seems to be Immunet.[/quote]
ClamAV is still ClamAV and they produce a Windows version of the product available here. Immunet was a separate company who developed a 'cloud-based' Windows anti-virus product with ClamAV. The Immunet version is not suitable for use with Mercury.
[quote]In an effort to get ClamWall running, I ended up downloading ClamWin and pointed ClamWall to the bin directory. The Question then became "Is it working". I have not figured out how to tell.[/quote]
ClamWin from www.clamwin.com is a different product that does not contain the clamD module that Mercury needs.
You can go to http://sourceforge.net/projects/clamav/files/clamav/win32/ and download the latest ClamAV version - *i386* for 32-bit or *x86_64* for 64-bit install.
(There are other Windows versions at http://oss.netfarm.it/clamav/ and http://hideout.ath.cx/ClamAV/, although the last one has not been updated for some time.)
[quote]One of the things I love about Mercury is what I call "Visibility". It is reasonably easy to tell what it is doing or not doing. Please extend this concept for what ever resource we are using to do anti-virus checking and display some form of verification, status, log entry, etc. that the virus checker is alive and processing the mail. This goes for the other add-ons as well.[/quote]
One thing you can do is examine the ClamWall log file regularly and look for error lines. There may be tools out there to automate that task as well.
<P>[quote user="jessicarabbit"]The ClamAV world seems in flux. ClamAV now seems to be Immunet.[/quote]</P>
<P>ClamAV is still ClamAV and they produce a Windows version of the product available <A class="" title="ClamAV Windows version" href="http://sourceforge.net/projects/clamav/files/clamav/win32/" target=_blank mce_href="http://sourceforge.net/projects/clamav/files/clamav/win32/">here</A>. Immunet was a separate company who developed a 'cloud-based' Windows anti-virus product with ClamAV.&nbsp; The Immunet version is not suitable for use with Mercury. </P>
<P>[quote]In an effort to get ClamWall running,&nbsp;I ended up downloading ClamWin and pointed ClamWall to the bin directory. The Question then became "Is it working". I have not figured out how to tell.[/quote]</P>
<P>ClamWin from <A href="http://www.clamwin.com/">www.clamwin.com</A> is a different product that does not contain the clamD module that Mercury needs.</P>
<P>You can go to <A href="http://sourceforge.net/projects/clamav/files/clamav/win32/">http://sourceforge.net/projects/clamav/files/clamav/win32/</A>&nbsp;and download the latest ClamAV version - *i386* for 32-bit or *x86_64* for 64-bit install.</P>
<P>(There are other Windows&nbsp;versions at <A href="http://oss.netfarm.it/clamav/">http://oss.netfarm.it/clamav/</A>&nbsp;and <A href="http://hideout.ath.cx/ClamAV/">http://hideout.ath.cx/ClamAV/</A>, although the last one has not been updated for some time.)</P>
<P>[quote]One of the things I love about Mercury is what I call "Visibility". It is reasonably easy to tell what it is doing or not doing. Please extend this concept for what ever resource we are using to do anti-virus checking&nbsp;and display some form of verification, status, log entry, etc.&nbsp;that the virus checker is alive and processing the mail. This goes for the other add-ons as well.[/quote]</P>
<P>One thing you can do is examine the ClamWall log file regularly and look for error lines.&nbsp; There may be tools out there&nbsp;to automate that task as well.</P>