[BlueOnyx:19327] Re: ClamAV issues with AV-SPAM package

[Jim Matysek]

Thanks, Chris. I did a restart of clamav-milter and clamd from 
/etc/rc.d/init.d (neither was running), then turned ClamAV back on via 
the GUI and sent a test message. It got similar problems in the log. I 
then re-stared clamav-milter again, sent another message and it got 
through. Odd.

I also restarted milter-greylist, which was running but I also have 
disabled via the GUI for a similar reason from a while ago (it was 
running). I'll tackle re-enabling that one tomorrow. I like the way that 
stops a lot more spam, but I get complaints whenever someone is on the 
phone with a vendor who sends them an email confirmation and they can't 
confirm that it got through while they are on the phone due to the 
greylist back-off time. That can be annoying.

-jim

> Hi Jim,
>
> On 3/14/2016 9:15 PM, Jim Matysek wrote:
>> Tonight I updated my AV-SPAM package from 6.1.0-8 to 6.1.0-9. I noticed
>> before updating that I had ClamAV turned off. After updating, I turned
>> it back on, and no mail gets through the server. Here's some of the maillog:
>>
>> Mar 14 22:01:22 admin clamav-milter[25224]: +++ Started at Mon Mar 14
>> 22:01:22 2016
>> Mar 14 22:01:22 admin clamav-milter[25331]: No clamd server appears to
>> be available
>> Mar 14 22:01:22 admin clamav-milter[25331]: ClamAV: accept() returned
>> invalid socket (Socket operation on non-socket), try again
>> I remember that I had a similar problem after I installed the last
>> AV-SPAM package.
>> Any ideas on where to look or what to try?
> Yeah, we have seen this almost regularly with new installations of Clam
> as well as upgrades.   The symptoms are almost always just as you describe.
>
> If you issue a manual restart via CLI then that should address the
> problem for you.   Once restarted, everything appears good again until
> the next update.  Which could suggest a little troubleshooting may need
> to be done on the installer.
>
> Try a manual restart of the Clam milter (as well as greylist milter, if
> you're using it) and your email ought to go through.
>