Yesterday ClamAV released a signature that disabled all versions of the program older than 0.95. If you are running ClamWall this will cause the daemon to try to start clamd for every message. The resulting timeouts will more or less make Mercury core stop working even though it indicates that it's active.
The fix is to get an updated version of ClamAV (for instance here: http://hideout.ath.cx/ClamAV/) and install it. You will probably need to update the data files using freshclam as well.
- - -
Thanks to Grant Root for pointing this out!
<p>Yesterday ClamAV released a signature that disabled all versions of the program older than 0.95. If you are running ClamWall this will cause the daemon to try to start clamd for every message. The resulting timeouts will more or less make Mercury core stop working even though it indicates that it's active.
</p><div>The fix is to get an updated version of ClamAV (for instance here:<a mce_href="http://hideout.ath.cx/ClamAV/ClamAV-096.exe%29" eudora="AUTOURL" mce_real_href="javascript:void(0);" href="http://hideout.ath.cx/ClamAV/ClamAV-096.exe%29"> http://hideout.ath.cx/ClamAV/)</a> and install it. You will probably need to update the data files using freshclam as well.</div><div>&nbsp;</div><div>- - -</div><p><font size="1"><i>Thanks to Grant Root for pointing this out! </i></font>
</p>