On Wed, 2004-08-04 at 23:01, Jeff Ramsey wrote: > On Aug 4, 2004, at 7:48 PM, <[EMAIL PROTECTED]> wrote: > > > > > ----- Original Message ----- > > From: "Cody Dabb" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, August 04, 2004 4:11 PM > > Subject: [Clamav-users] Amavis-new and Clamd > > > > > >> What is the best way to setup clamd with amavis-new? > >> > >> When email pass through our postfix server amavis gives the following > >> error: > >> > >> amavis[3414]: (03414-12) WARN: all primary virus scanners failed, > >> considering backups > >> > >> I have the clamd setup to be primary and backup AV scanner, it never > >> seems to scan for viruses coming in. > >> > >> Config files: > >> > >> /etc/amavisd.conf > >> > >> $unix_socketname = "/tmp/clamd"; #"$MYHOME/amavisd.sock"; # amavis > >> helper protocol socket > >> > >> @av_scanners = ( > >> > >> ### http://www.clamav.net/ > >> ['Clam Antivirus-clamd', > >> \&ask_daemon, ["CONTSCAN {}\n", "/tmp/clamd"], > >> qr/\bOK$/, qr/\bFOUND$/, > >> qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], > >> # # NOTE: run clamd under the same user as amavisd; match the socket > >> # # name (LocalSocket) in clamav.conf to the socket name in this entry > >> # # When running chrooted one may prefer: ["CONTSCAN > >> {}\n","$MYHOME/clamd"], > >> > >> @av_scanners_backup = ( > >> > >> ### http://www.clamav.net/ > >> ['Clam Antivirus - clamscan', 'clamscan', > >> '--stdout --no-summary -r {}', [0], [1], > >> qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], > >> > >> /etc/clamav.conf > >> > >> # which is only accessible for a user running daemon. > >> LocalSocket /tmp/clamd > >> > >> User vscan > >> > > > > Not an expert by any means but you should check the following: > > > > Is the socket file actually being created in /temp/clamd ? If not you > > probably have a permissions issue. > > > > Is vscan the Amivis user too? If not change the user to the Amavis > > user. > > > > > > Agreed. 95% of my startup issues were permission related. Just make > sure that all of the clam/amavis/mailserver run as the same user. Or, I > finally made a group called 'maildaemons', and made each pertenent > account a member of it. I changed the group on all related > files/directories to 'maildaemons'. Then I set the g+wr on all of the > config and queue directories, and set the g+wrx on all of the related > executables. It took me quite a while to get all of that set correctly, > but it works now. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Clamav-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/clamav-users >
That was the problem! I found it right after I sent in the email.:) Once I changed the unix socketname back on the amavis everything started to work. Thanks everyone. ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
