Community Discussions and Support
ClamWall - ClamD closing and reopening with Merc32 4.72

Sure enough!  I updated ClamAV and things are working properly now!

Thanks for the quick response!

 

Charlie

  ~~~

<P>Sure enough!  I updated ClamAV and things are working properly now!</P><P>Thanks for the quick response!</P><P> </P><P>Charlie</P><P>  ~~~</P>

We recently updated our Mercury32 server from 4.62 to 4.72.  We had Clamwall running previously and ClamD would open a command prompt window that would remain open.  You could look at this prompt window and see what ClamD was doing.  When we updated Mercury32, we updated Clamwall (Spamhalter and Greywall also).  When it came to the .ini files we saved the defaults and checked them against our previous .ini versions.  We had made some site specific changes, so we renamed the original .ini files and copied our old ones back.  I noticed a difference that may be affecting this.  The default .ini has: ClamSelf=0 and our .ini had ClamSelf=1

Since our update, the command prompt window loads (I am assuming as it is scanning an incoming email) then UNLOADS and shortly there after it reloads.

Is this part of the update?  Is it more efficient that way (it would seem that there would be more overhead - loading and unloading the program)?

What IS the best (most efficient) way to have ClamAV scan the emails?

 

Thanks for your assistance,

 

Charlie Fastner

  ~~~ 

<P>We recently updated our Mercury32 server from 4.62 to 4.72.  We had Clamwall running previously and ClamD would open a command prompt window that would remain open.  You could look at this prompt window and see what ClamD was doing.  When we updated Mercury32, we updated Clamwall (Spamhalter and Greywall also).  When it came to the .ini files we saved the defaults and checked them against our previous .ini versions.  We had made some site specific changes, so we renamed the original .ini files and copied our old ones back.  I noticed a difference that may be affecting this.  The default .ini has: ClamSelf=0 and our .ini had ClamSelf=1</P><P>Since our update, the command prompt window loads (I am assuming as it is scanning an incoming email) then UNLOADS and shortly there after it reloads.</P><P>Is this part of the update?  Is it more efficient that way (it would seem that there would be more overhead - loading and unloading the program)?</P><P>What IS the best (most efficient) way to have ClamAV scan the emails?</P><P> </P><P>Thanks for your assistance,</P><P> </P><P>Charlie Fastner</P><P>  ~~~ </P>

What IS the best (most efficient) way to have ClamAV scan the emails?

Without opening the command prompt window at all.  Select "Hide ClamAV console windows" in the ClamAV tab.

 

<blockquote>What IS the best (most efficient) way to have ClamAV scan the emails?</blockquote><p>Without opening the command prompt window at all.  Select "Hide ClamAV console windows" in the ClamAV tab. </p><p> </p>

You've mentioned that you upgraded ClamWall but have you also updated ClamAV to the current version (0.95.2)? If not you have to enable the legacy protocol support in ClamWall otherwise it can't connect to ClamD.

Best regards,

Nico

<P>You've mentioned that you upgraded ClamWall but have you also updated ClamAV to the current version (0.95.2)? If not you have to enable the legacy protocol support in ClamWall otherwise it can't connect to ClamD.</P><P>Best regards,</P><P>Nico</P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft