On Tue, 2006-10-24 at 05:40, Nigel Horne wrote: > On Mon, 2006-10-23 at 15:42 -0300, Nicholas Anderson wrote: > > Oct 22 04:44:28 manguinhos sm-mta[7136]: k9M7iSBm007136: Milter > > (clmilter): local socket name /var/run/clamav/milter.sock unsafe > > Oct 22 04:44:28 manguinhos sm-mta[7136]: k9M7iSBm007136: Milter > > (clmilter): to error state
I've started seeing the same thing using v0.88.4 on a RedHat 9 box. The weird thing is that it has been very stable in the past. This just started happening about a week ago - maybe some new type of virus email is crashing clamd or something? The biggest problem for me is that once clamav-milter dies, sendmail stops accepting mail altogether. Does anyone know of a work around that would allow sendmail to keep going even though clamav-milter or clamd has died? Or perhaps there's way to have clamav-milter and clamd automatically restart when they die? Here's a sample from my log: Oct 25 11:28:03 nimon sendmail[28310]: k9PGS39v028310: Milter (clamav-milter): local socket name /var/clamav/clmilter.socket unsafe Oct 25 11:28:04 nimon sendmail[28310]: k9PGS39v028310: Milter (clamav-milter): to error state -Steve _______________________________________________ http://lurker.clamav.net/list/clamav-users.html