This one time, at band camp, Paul Traina said:
> That was the first thing I checked too, sorry for not including it.
> 
> The directory and milter socket appear to be good:
> 
> [EMAIL PROTECTED] ls -ld /var/run/clamav
> drwxr-xr-x  2 clamav clamav 224 Feb  3 15:50 /var/run/clamav
> 
> [EMAIL PROTECTED] ls -l /var/run/clamav/clamav-milter.ctl
> srwx------  1 clamav clamav 0 Feb  3 15:50 /var/run/clamav/clamav-milter.ctl
> 
> [EMAIL PROTECTED] ps -w -f -u clamav                        
> UID        PID  PPID  C STIME TTY          TIME CMD
> clamav    4723     1  0  2004 ?        00:00:00 /usr/bin/freshclam -d --quiet 
> -p /var/run/clamav/freshclam.pid
> clamav    4263     1  0 Feb03 ?        00:00:00 /usr/bin/freshclam -d --quiet 
> -p /var/run/clamav/freshclam.pid
> clamav    4571     1  0 Feb03 ?        00:00:00 /usr/sbin/clamd
> clamav    6939     1  0 Feb03 ?        00:00:00 /usr/sbin/clamav-milter 
> --max-children=4 -olCqn --external --pidfile /var/run/clamav

I do hope that line is truncated :)  But otherwise it looks fine.

The only thing I can suggest at this point would be first: restart the
milter, to make sure it's not just hung or something (sendmail will also
give this cryptic warning when it can't actually communicate with the
socket).  Second, turn up debugging in both sendmail and clamav-milter -
try the usual LogVerbose, Debug, LogSyslog, whatever will finally get
soem debug information out of it.  For sendmail, I think it's
MilterLogLevel that you want.
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        [EMAIL PROTECTED] |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

Attachment: pgpPTS8VvD72D.pgp
Description: PGP signature

Reply via email to