savesraka.blogg.se

1. #SPAMASSASSIN SCORE HOW TO#
2. #SPAMASSASSIN SCORE INSTALL#
3. #SPAMASSASSIN SCORE UPDATE#
4. #SPAMASSASSIN SCORE ARCHIVE#

# This is the right place to customize your installation of SpamAssassin. The following is a copy of the default salocal.cf The above line will use the configuration that's configured within the zimbraMtaMyNetworks on the server. %%uncomment VAR:zimbraMtaMyNetworks%%trusted_networks %%zimbraMtaMyNetworks%% You will find the salocal.cf file at /opt/zimbra/conf Within the salocal.cf file add the following line. There is no way to exclude internal IP addresses from being scanned by the spam filter, but you can configure the system to lower the score to prevent false positives for trusted IP addresses.

#SPAMASSASSIN SCORE HOW TO#

How To Decrease Spam Score on Internal IP addresses Most of the scores are stored within 50.score.cf. You will find the configuration files within: The following is a link of the rules that can be applied by the spam engine and their definitions: In the example above the top four test that were triggered by this message were DOS_OUTLOOK_TO_MX, score of 2.845, RCVD_IN_BRBL_LASTEXT score of 1.449, RCVD_IN_PBL score of 3.335 and RCVD_IN_RP_RNBL score of 1.31 which has a total score of 8.939. If this score exceeds the required score then the message will be marked as spam. Adding all the scores, will give you the total score. This section will list each test that was triggered by the message and the score that was applied by the test. When reading the X-Spam_Status there is a section called test. The following is an example of a message that received a score of 10.535 which exceeded the 6.6 threshold. When the message triggers a policy it will be reported within the header within X-spam-Status. We recommend making notes on all custom configuration. Also any custom configuration to these files will be removed.

#SPAMASSASSIN SCORE UPDATE#

Within the upgrade process Zimbra will update the spam configuration files with the latest files that have been released by SpamAssassin, because of this your spam scores could change.

#SPAMASSASSIN SCORE ARCHIVE#

If you’d still like more information on SpamAssassin, a good place to go is SpamAssassin Rule Help, and you can always pop over to the SpamAssassin site itself.- This is archive documentation, which means it is not supported or valid for recent versions of Zimbra Collaboration. Immediately after editing your configuration file to ensure that you haven’t introduced any errors or typos into the ruleset! You can do the opposite instead, as shown here: header ITS_DEREK ALL =~ ITS_DEREK -100įinally, you can also reassign the scoring of built-in rules too, by simply restating the score: score SUBJ_FREE_CAP 4.0įinally, don’t forget to always run the command spamassassin -lint I just try to use sufficiently mnemonic rule names.ĭon’t be fooled into thinking that you can only match rules and have things be more spammy. The first thing you’ll notice is that I don’t bother with the description field. Here are two actual rules from my own SpamAssassin rule set: rawbody BECAUSE_OPTIN /because you opted-in/i Having shown that, I use rawbody rather than body so that it catches words that appear in HTML formatted messages and messages with base64 or any other encoding scheme. In this case, any message that contains “Vioxx” (without regard to the mix of upper and lower case, which is what the ‘i’ accomplishes in the pattern) will be given a score of +10, which might by itself make this an undelivered spam message (it actually depends on what threshold you specify in your configuration file). A commensurate scoring for the rule if matchedĪs a simple example, here’s a rule that applies against the body of messages that are being filtered: body NO_VIOXX /vioxx/iĭescription NO_VIOXX messages that contain the word Vioxx.A 2-5 word description of the rule for SpamAssassin reports (optional),.Your local SpamAssassin rules should be stored in a file called /etc/mail/spamassassin/local.cf if you want the rules applied to every user on the system, or ~/.spamassassin/user_pref if you want to have them only apply to your own email.

#SPAMASSASSIN SCORE INSTALL#

While I’m also a big fan of SpamAssassin, I’m the first to admit that the rules can be more than a bit confusing, and when you have a bad rule, odd things can occur, especially if you don’t actually test your rules before you install them.