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.
It does not store any personal data.- This is archive documentation, which means it is not supported or valid for recent versions of Zimbra Collaboration. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
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.
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.