Hallo Mark,
Op zaterdag 02 juni 2007 schreef Mark Martinec aan
[email protected]:
>> User amavis:amavis also belong to group clamav.
MM> As Gary noticed, this is irrelevant, what matters is
MM> placing user clamav to the amavis group, as documented
MM> in the INSTALL document:
Actually, I did it both ways: amavis added to group clamav and clamav
added to group amavis.
MM> - some virus scanners run as daemons or change UID when checking
MM> files. It is easiest to run such virus scanners under the same
MM> UID/GID
This certainly solved the problem. I'm still wondering why it doesn't
work the other way, but I'll have another look at that later.
MM> If a different UID is preferred for an AV scanner, a
MM> solution
MM> for ClamAV is to add user clamav to the amavis group (e.g.:
MM> vscan:*:110:clamav in a file /etc/group), and then add:
MM> AllowSupplementaryGroups yes to clamd.conf.
That was put in, but did not solve it.
Thank you and Gary for your help.
Groeten,
Hans.
jdh punt beekhuizen bij duinheks punt xs4all punt nl
--- GoldED+/LNX 1.1.5/070407
* Origin: The Wizard is using MBSE/Linux (2:280/1018)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
