emerging amavisd-new requires that clam antivirus also get emerged. However, the amavisd-new config relies on the command-line form of clam, which tends to be slower than the daemonised form. Moreover, the amavisd.conf file leaves the clamd form commented out, and doesn't even match where the clamd config points to for the socket. Reproducible: Always Steps to Reproduce: Expected Results: 1. At least enable the clamd config section in amavisd.conf so someone who flags START_CLAMD=yes doesn't have to scratch their head. 2. Make clamd and amavisd agree on the socket location for clamd. (amavis -> /var/run/clamav/clamd ; clamd -> /tmp/clamd) 3. Possibly add a local USE flag of mail-server, which would set START_CLAMD to yes and enable the amavisd clamd section so that amavisd gets a faster scanner than a command-line fork.
amavisd-new requires any antivirus package to be installed, but if you have none, it'll pull clam. it is configured by default to not talk to any antivirus software, you have to manually enable it. and the default example points to a clam daemon. the only inconsistancy I see is the socket location (why does the clam socket go into /tmp??).
Duncan, what's up! I made an attempt to reorganize this for the new release of amavisd-new. My next stop is to add a local USE variable to clamav (I think). Let me know what you think of this new release. See Bug 56233 for details. Thanks for the bug submission as always :)
As Max notes amavisd-new can work with multiple virus scanners, you need simply edit amavis' conf and uncomment the primary definition for clamav to use the clamav daemon. You'll likely need to do some extra tweaking with clamav's socket and permissions to get it going.
With the current situation and the dependency on virtual/antivirus I think the situation is ok. First priority is getting an up to date ebuild in portage then later we could consider the integration Cory is proposing.
Closing this for now see comment #4.
