[...] > It is important to start clamd with a user id that has > enough privileges to scan the files that are submitted to it. In your > case that would appear to be what ever user Amavisd runs as.
Even better: create a separate user:group for clamav, add that user to amavisd's group (by means of the /etc/group entry like "amavis:x:105:clamav") and use AllowSupplementaryGroups in clamd.conf. This way clamd will be able to read amavisd's files without giving to amavisd too much power over clamd. -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only tomek at lodz.tpsa.pl | ones and zeros. tomek at clamav.net http://www.ClamAV.net/ A GPL virus scanner _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
