#Spamassassin score range how to
#Spamassassin score range install

Rm -rf /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/cur/*Ĭd /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/new Rm -rf /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/new/*Ĭd /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/cur Rm -rf /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/cur/*Ĭd /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/new Now create a script that looks like this:Ĭd /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/cur You might want to implement Squirrelmail Spam Buttons to make this easier. You should encourage your users to forward spam to the spam address and any false positives to the not-spam address. You can do this by setting up a couple of email accounts on your server called and Forward all your spam mail to one and non-spam mail to the other, alright you might not want to forward all of your real mail to it but the more ham Spam Assassin has for comparison, the better. You will need a collection of spam messages and a collection of ham messages. In order for this to be effective you need to train Spam Assassin. SpamAssassin can score messages based on the words in a message because certain words are more probable to turn up in spam and others are more probable to show up in ham. You can do this using Jake's spamd script or by doing: Add them using CPAN as you see above.Īfter you make any changes you need to restart the SpamAssassin service. If you see any errors, correct them before you restart the spamd service! The most likely thing you will see are missing perl modules. pre file so new rules will be applied or basically make any changes to the SpamAssassin configuration files you must check that all the syntax is OK: cf file in /usr/share/spamassassin) or add a module to a. You can find lots and lots of alternative rule sets at Rules Emporiumand you might want to join a SpamAssassin mailing list to keep your self up to date on the fight against spam while you are at it.

Loadplugin Mail::SpamAssassin::Plugin::URIDNSBL Some of the files will only be used if the appropriate module is loaded, for instance 25_uribl.cf will only run if you have added If you are, for instance, a pharmaceutical retailer you probably want to lower the scores for the various drugs cf files. How each of them will add (or subtract) points from the mail's spam score is set by 50_scores.cf. The /usr/share/spamassassin/*.cf files are custom rule sets designed for catching spam using your installed modules. If you are using the latest version of SpamAssassin-toaster then everything you need should already be installed.

#Spamassassin score range how to

Here's how to find out what perl modules you have.

#Spamassassin score range install

# install Mail::SpamAssassin::Plugin::URIDNSBL Installing a plugin using CPAN goes like this: You can find a list of available plugins on CPAN. Loadplugin Mail::SpamAssassin::Plugin::MIMEHeader pre files tell SpamAssassin what plugins to load for applying different tests. The settings in here will apply to all users on your system. The local.cf file contains basic settings, like the score you must reach before a message is considered spam, what the subject line should be changed to if the score is reached (ie add ***SPAM*** to the subject) and whether Bayes Scoring should be used.

The SpamAssassin-Toaster uses the following configuration files:

5.1 Multi-domain sa-learn ham/spam script.

4 How to reset Spam Assassin Bayes Training.

2.1 Use bounce a message to feed SA bayes.