Actually, the other way around, add amavis to the clamav group,
usermod -G clamav amavis
then add:
AllowSupplementaryGroups
to the clamd.conf file, and restart both clamd and amavis-new.
gpasswd works differently, and is safer to use in this case than usermod. If someone does not capitalize the "G" it can lead to problems. gpasswd -a user group
But let me be more succinct. They easiest way to solve file permission issues when trying to get amavisd-new and clamd working together is to make the clamav user a member of your amavisd-new group. For example, if your clamav user is 'clamav' and your amavisd-new group is 'vscan', you can easily accomplish this by running:
# gpasswd -a clamav vscan
to verify, run # groups clamav
There are at least a few other things that MUST be done. 1) Verify the value after CONTSCAN in amavisd.conf matches the LocalSocket setting in clamd.conf. Change it in amavisd.conf if it does not match. 2) Make sure LocalSocket is enabled and TCPSocket is disabled in clamd.conf. 3) Make sure AllowSupplementaryGroups is enabled in clamd.conf
and restart both clamd and amavis-new.
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfeeŽ Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
