I've just installed and configured SpamAssassin under DirectAdmin, and I wanted to share a bit about the process. First of all, the instructions for installing SpamAssassin are available on the DirectAdmin site: http://help.directadmin.com/item.php?id=36 I modified the setup script to select the current version of SpamAssassin (3.1.7) rather than what was documented in the script (3.1.4). The script did work fine using the DirectAdmin site to pick up the necessary perl modules, so if you make this modification only pick up the SpamAssassin tarball from its site. As a note, the wget I added to spam.sh (replacing getFile $FILE) was: Code: wget http://mirrors.combose.com/apache/spamassassin/source/Mail-SpamAssassin-3.1.7.tar.gz The script does all the compiling and installation for you. No separate init script is created to start the SpamAssassin daemon spamd; it is instead started from the exim init script. Once installed, you must go into your DirectAdmin control panel and enable SpamAssassin for each domain separately. Once you click on "enable", a form will come up that you must set a few options on and click "save'. Once saved, you'll find a directory called ".spamassassin" will be created in the home directory of the DirectAdmin account owner for that domain, and a minimal user_prefs file will be created. If you choose to have your spam put into a "spam" folder as I did, you'll find there will be a subdirectory under that directory called "user_spam" with filenames such as "[email protected] I do occasionally peek at the subject lines of the email using a one-liner on the command line (via ssh): Code: % grep "^Subj" [email protected] This lets me page through the subjects and quickly figure out if there might be any false positives. None so far, which mirrors my experience on my home server where SpamAssassin has been in use for three years. You can also choose to receive the email with the subject line modified to include a "## SPAM ##" at the front, or pass it through with just the spam headers added, or just have it deleted immediately. A modern email client like Thunderbird can filter the spam into a separate spam folder for you if you choose to have the spam included in your downloads. You can add some additional rulesets that make SpamAssassin catch more spam, at the possible expense of some false positives. The Rules Emporium has a number of useful rulesets: http://www.rulesemporium.com/ Read the notes for each ruleset file carefully; there are some that have a big impact upon resource usage and others that are known to have false positives. If you wish to use Bayesian filtering, you can hit the ground running by training SpamAssassin with several hundred known spam and known ham emails and putting the data into your .spamassassin directory. This is the most effective way to make the Bayesian filter work right off the bat. I found instructions on how to transfer my bayes database from my home server to the VPS (using "sa-learn --backup" and "sa-learn --restore"); note that just copying over the bayes_seen and bayes_toks files directly didn't work. You can initialize your bayes database using a public corpus of spam and ham which is better than not having it but is probably not quite as good as using your own spam and ham. If you have your own, use it, so long as it's a few hundered messages each of spam and ham. Lastly, I don't care for negative scoring when using bayes. What this means is that the total score of an email can be reduced by a few points if the bayes engine gets few or no hits against its database. So I modifiy the rules that govern this by adding these lines to the user_prefs file: score BAYES_00 0.0001 0.0001 0.0001 0.0001 score BAYES_05 0.0001 0.0001 0.0001 0.0001 score BAYES_20 0.0001 0.0001 0.0001 0.0001 score BAYES_40 0.0001 0.0001 0.0001 0.0001 The scores in the last two columns by default are negative; I essentially zero them out. That's it; enjoy!