On Sun, 2012-09-02 at 17:25 -0700, Todd Lyons wrote:
> On Sun, Sep 2, 2012 at 4:36 PM, Always Learning <exim@???> wrote:
> >
> > I want to use CLAM in Exim 4.63/4.72 on Centos 5 & 6.
> > Would the correct syntax for defining Clam in Exim be:-
> > av_scanner = clamd:/var/run/clamd/clamd.pid
> CentOS58[root@ivwm52 ~]# grep clam /etc/exim/*
> /etc/exim/exim.conf:av_scanner = clamd:/var/clamav/clamd.sock
On Centos 5.8 (Exim 4.63) and Centos 6.2 (Exim 4.72) I get, for the same
command:-
/etc/exim/exim.conf:av_scanner = clamd:/var/run/clamd.exim/clamd.sock
The reason I did not mention /var/run/clamav/clamd.sock was because
the file was empty.
Does one have to place the socket number in clamd.sock or will Exim or
Clam do that automatically after the first AV check ?
> > or
> > av_scanner = 127.0.0.1: 3310: local
Whoops. Probably better as
av_scanner = clamd:127.0.0.1 3310: local
> This will also work in that it will try to connect to a virus scanning
> daemon listening on 127.0.0.1 port 3310 and it assumes that it's
> "local" so it only passes the filename or filenames that it wants to
> to scan and waits for a response.
>
> As you can see by my example, I prefer the former.
Thank you very much.
Paul.
still learning :-)
--
Paul.
England,
EU.
