Strange CLAMD errors

[Rick Cooper]

If you were using the old clamd (clamdscan) support, you need to configure
the new clamd parameters in MailScanner.con to  match your clamd.conf. The
latest MailScanner calls clamd directly not via clamdscan. Look at the
change log

Rick

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of emm1
 > Sent: Tuesday, July 10, 2007 11:06 AM
 > To: MailScanner discussion
 > Subject: Strange CLAMD errors
 > 
 > Hello, after I upgraded to 4.61.7 on my FreeBSD 6.2 box I am seeing
 > those errors.
 > I have checked to see if clamd is running and it is. Any ideas?
 > 
 > Jul 10 15:00:31 mainframe MailScanner[12276]: New Batch: Scanning 1
 > messages, 3973 bytes
 > Jul 10 15:00:31 mainframe MailScanner[12276]: Expired 1 records from
 > the SpamAssassin cache
 > Jul 10 15:00:34 mainframe MailScanner[12276]: Virus and Content
 > Scanning: Starting
 > Jul 10 15:00:34 mainframe MailScanner[13026]: ERROR:: COULD NOT
 > CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON
 > Jul 10 15:00:34 mainframe MailScanner[12276]: ERROR:: COULD NOT
 > CONNECT TO CLAMD, RECOMMEND RESTARTING DAEMON :: .
 > Jul 10 15:00:34 mainframe MailScanner[12276]: Virus Scanning: Clamd
 > found 1 infections
 > Jul 10 15:00:34 mainframe MailScanner[12276]: Virus 
 > Scanning: Found 1 viruses
 > Jul 10 15:00:34 mainframe MailScanner[12276]: Uninfected: 
 > Delivered 1 messages
 > -- 
 > MailScanner mailing list
 > mailscanner at lists.mailscanner.info
 > http://lists.mailscanner.info/mailman/listinfo/mailscanner
 > 
 > Before posting, read http://wiki.mailscanner.info/posting
 > 
 > Support MailScanner development - buy the book off the website! 
 > 
 > --
 > This message has been scanned for viruses and
 > dangerous content by MailScanner, and is
 > believed to be clean.
 > 
 > 


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