On Sun, 2005-01-02 at 16:18 +0000, Nigel Horne wrote:
> On Sunday 02 Jan 2005 13:17, Ed Stover wrote:
>
> > > 5) What arguments are you giving to clamav-milter on startup?
> > clamav_clamd_enable="YES"
> > clamav_milter_enable="YES"
> > #clamav_milter_flags="-HfNPlo -U/var/mail/infected"
> > clamav_milter_flags="-lo -U/var/mail/infected"
> > clamav_freshclam_enable="YES"
> > clamav_freshclam_flags="-dc 24"
>
> You have not defined the input socket from sendmail to clamav-milter,
> e.g.
> /var/run/clamav/clmilter.sock which you set in sendmail.mc by not
> clamav_milter_flags.
>
> See also .../clamav-milter/INSTALL
>
bash-2.05b# ps -ax |grep clam
53649 ?? Ss 0:03.93 /usr/local/sbin/clamd
53655 ?? Is 0:00.19 /usr/local/bin/freshclam -dc 24 --daemon
54006 ?? Ss 0:01.77 /usr/local/sbin/clamav-milter -lo
-U/var/mail/infected /var/run/clamav/clmilter.sock
Thats because on the FreeBSD port in
the /usr/local/etc/rc.d/clamav-milter.sh file it allways includes it by
default.
(excerpt:
# read settings, set default values
load_rc_config $name
: ${clamav_milter_enable="NO"}
: ${clamav_milter_socket="/var/run/clamav/clmilter.sock"}
: ${clamav_milter_flags="--postmaster-only --local --outgoing
--max-children=50"}
end of exceprt)
> > > 10) Do you have LogSyslog enabled, and if so what's happening in
> the
> > > logfiles?
>
Thats what is driving me nuts, because I had a older version of clam
running just fine. I got tired of getting the " you must update " from
fresh-clam and decided to update. I am not seeing any changes in my
syslog or any changes in my maillog that indcated a wrong permision any
where.
> You answered the first part of this, but not the second.
>
>
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
