First of all, I strongly recommend that you use Spamassassin instead. It can easily be configured to use Razor too, but has a battery of other tests. I catch far more spam with Spamassassin than I did with just Razor.

I used to use maildrop's 'xfilter' command to run 'spamc' (the command-line frontend for spamd, spamassassin's daemon). But several months ago I switched to using amavisd-new as a server-wide method to tag incoming spam (using Spamassassin) and viruses (using clamav). It wasn't the easiest thing to set up, but it wasn't brain surgery either (I'm running Postfix).

So now the only lines in my personal .mailfilter that are spam related are:

if ( /^X-Spam-Flag: *YES/:h ) { if ( /^X-Spam-Level:[ \t]+\*\*\*\*\*\*\*\*/:h ) { to "$DEFAULT/.Junk.definitely/" } else { to "$DEFAULT/.Junk.maybe/" } }

The lines above check if Spamassassin thought it was spam, and if so, routes it to one of two maildirs depending on how high its score was. X-Spam-Flag is inserted by Spamassassin automatically, if the score is above a user-defined threshold (I use 4.0, and 5.6 as the threshold for 'YES'). X-Spam-Level is a 'bargraph' of the spam level, a score of 8.0 or more would produce eight or more asterixes, and would put it in my 'definitely' maildir. If the spam scores more than 20, I have amavisd-new configured to bounce it and it wouldn't get as far as maildrop (20 is a very high score).

In about three months, I've had one email make it into the 'definitely' folder that shouldn't have, and it wouldn't have been a loss to have missed it. On my mix of emails, I get about 1 or 2 'maybe' per 100 'definitely' spam emails. Perhaps 3 or 4 will be missed and make it into my inbox (and they're often those really short spams, or HTML mail with a link to an external image. False positives are down around one in a few hundred, but I manually whitelist stuff I get regularly that's prone to being tagged as spam, so it should be that low.

HTH,

Paul

<snip>