amavis-new supports courierfilters natively -- just select the appropriate options in /etc/amavisd.conf including the socket location (e.g. set it to .../allfilters dir), make sure it's running as group 'courier', and fire it up. The only trick is that when courier is restarted, there'll be a stale socket file for amavisd, which is why I added the 3 lines for my previous message to my init.d/courier script. I had looked at amavis-ng and it just was problematic, for me.

I would write an amavis-new how-to, but it's too simple for that. Install amavis-new. Install dependencies (e.g. the ~15 perl modules). Make sure it's running in the same group as courier, and as your virus scanning daemon. Fire it up.

The only drawback to this approach is that you can't modify messages coming in on the wire. I'm just fine with this, because we'd rather not deliver "you got a virus" messages to our users -- we're 5xx'ing them.

I'd love to integrate spamassassin via amavis-new as well, but I haven't had a chance to figure out how amavis-new handles the "I have 2 recipients with different spam settings" scenario. Anyone else done this? It might be easy, just haven't tried.

best, Jeff