

Those collaborative network keep an up-to-date catalogue of know mail checksum to be recognized as spam. In the last section, we disable collaborative network such as pyzor, razor2 and dcc.

In the next section, we tell spamassassin to use bayes classifier and to improve itself by auto-learning from the messages it will analyse.

Open the file with your favorite text editor and add the following lines: allowuserrules 1 rewritesubject 1, This is all you really need to add to get started. Locate the spamassassin/local.cf file, which is usually at /etc/mail/spamassassin/local.cf. To be able to use the _SCORE_ in the rewrite_header directive, we need to set report_safe to 0. Next, we set some global options for SpamAssassin. So email with a score lower than 2 won’t be modified. You will also need a text editor, the guide below installs.
SPAMASSASSIN POSTFIX INSTALL
Here, we set spamassassin’ spamd default settings to rewrite email subject to, where _SCORE_ is the score attributed to the email by spamassassin after running different tests, only if the actual score is greater or equal to 2.0. You need to install postfix (the SMTP server) and SpamAssassin (the SPAM filter) onto your server. Postfix Admin a Web Based Management tool for. pfqueue Postfix queue management utility. #If this option is set to 0, incoming spam is only modified by adding some "X-Spam-" headers and no changes will be made to the body. Also has the option for spamassassin and clamav for mail scanning. #to be able to use _SCORE_ we need report_safe set to 0
