After fiddling about with this for hours, I think I finally have something working.  At least for now!

But let me first explain what I've done.  When I first installed this, I followed the instructions here:
http://clamav.elektrapro.com/doc/html/node23.html

Which says to start clamav-milter like this:
/usr/local/sbin/clamav-milter -blo /var/run/clmilter.sock

Well, that worked - at first.  But for some reason, over time, everything seemed to get stuck with enormous timeout periods for sending mail through the SMTP server.  I used the shell script that came with clamav-milter to stop it - and noticed there were tons of PID's, none of which actually existed.

Everytime I tried to restart it, I would get more error messages in my log files, and again, those huge long periods trying to send mail.  (By the way, I'm using Sendmail).

So then I read the INSTALL file in the clamav-milter directory that comes with Clamav.  This is in the instructions:

"Add to /etc/sysconfig/clamav-milter
        CLAMAV_FLAGS="--max-children=2 local:/var/run/clamav.sock"
or if clamd is on a different machine
        CLAMAV_FLAGS="--max-children=2 --server=192.168.1.9 local:/var/run/clamav.sock"

You should have received a script to put into /etc/init.d with this software."

When I did that, I was gettting more errors about 'unsafe socket'.  Well of course... what the instructions SHOULD say, I think, is this instead:

"Add to /etc/sysconfig/clamav-milter
        CLAMAV_FLAGS="--max-children=2 local:/var/run/clmilter.sock"
                                                                                        ^^^^^^

NOT clamav.sock!!

Well, I suppose you could, if that's what you put in your sendmail.mc file - but that's not what the instructions say to put in there.

Anyhow, once I changed that, then shutdown clamd, clamav-milter, and then restarted in this order:
/etc/init.d/clamd.sh
/etc/init.d/clamav-milter.sh
sendmail

everything started to seem to work better.  I'm just crossing my fingers that by morning, it won't have run out of steam again, and be causing more SMTP issues.

If I tried to restart clamav-milter.sh before restarting clamd, then I still had errors.

I hope this helps anyone else who might be having some issues getting it all to work. 

Should I expect that in time, I'll have to restart everything again?  What would cause the performance of this (the SMTP issues) to degrade in 8 hours?  We're using a box with an AMD 2400+ processor, 1 GB Ram, and about 250 users, and it also serves as our Primary DNS, but that's really all it's used for.  I'd think it should be just cruising along nicely and able to handle a whole lot!

Are there any other tweaks to clamav-milter and/or clamd I should try?

Thanks!

-- 
Ian Scott <[EMAIL PROTECTED]>
Goal Centered Internet Solutions
http://www.pairowoodies.com

All About Fly Fishing
http://www.about-flyfishing.com

PGP/GPG Key ID: 319CE936

Reply via email to