..but in my situation I haven't group vscan but I have group 'amavis' and in this group is already present the user 'clamav' but the problem is still present ! :-( Thanks.
------ Salvatore. ----- Original Message ----- From: "Kevin" <[EMAIL PROTECTED]> To: "ClamAV users ML" <clamav-users@lists.clamav.net> Sent: Thursday, July 05, 2007 11:36 AM Subject: Re: [Clamav-users] amavisd-new + clamAV ? > Thank you for your help, > > Although i didn't see which one for primary virus scanning in clamd socket > of var/log/maillog, > I added clamav userid in vscan in /etc/group, then the receiving and > sending > the email becomes quite normal. > > /etc/group > ... > vscan:*:123:clamav > clamav:*:124: > .... > > I appreciate for your suggestion and sharing. > > Kevin > > > 2007/7/4, Chuck Swiger <[EMAIL PROTECTED]>: >> >> >> When you restart amavisd, check /var/log/maillog and see whether it then >> finds >> the clamd socket as the primary virus scanner, rather than just clamscan. >> >> Double-check which users amavisd and clamd are running as-- the default >> ports >> config seems to have clamd running as the "clamav" user, and >> amavisd+SpamAssassin as "vscan". Enabling in clamd.conf >> "AllowSupplimentaryGroups" option and adding the "clamav" userid to the >> vscan >> group in /etc/groups lets them talk. >> >> Regards, >> -- >> -Chuck >> > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
