clamd configuration?

[Rick Cooper]

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 > Behalf Of Chris Yuzik
 > Sent: Tuesday, July 03, 2007 7:23 PM
 > To: MailScanner discussion
 > Subject: Re: clamd configuration?
 > 
 > Ryan Lane wrote:
 > > Chris Yuzik wrote:
 > >> # grep -i clamd /etc/MailScanner/MailScanner.conf | grep -v '^#'
 > >> Virus Scanners = clamd
 > >> Clamd Port = 3310
 > >> Clamd Socket = /tmp/clamd
 > >> Clamd Lock File = /var/lock/subsys/clamd
 > >> Clamd Use Threads = yes
 > >
[...]
 > >
 > > I'm running this on centos 4.5 with clamav/clamd from dag's repo.
 > I went through the config file for clamd and found that the TCP port 
 > wasn't enabled for the daemon, so I uncommented out the line, and 
 > restarted clamd. Still not working.
 > 
 > Oy.
 > 
 > Not sure what to do next.
 > 

Please run MailScanner in debug mode, show what is output from the clamd
section, and if possible the clamd.conf, remember that is where the clam
daemon is getting it's parameter. If MailScanner cannot reach clamd there
will be alerts even if you are not in debug mode. Also note if you supply a
path to the socket the port is not used. If you are not using unix sockets
(/tmp/clamd or /tmp/clamd.sock, etc) then you should have an IP address
(probably 127.0.0.1) for the socket address.

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.