![]() 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. 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. You are using these rules at your own risk. Please test the rules in your environment before using them in production. Please note that the rules, while they work for me just fine, might not suit your needs and may create false positive. 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). handcrafted custom ruleset for spamassassin. ![]() ![]()
0 Comments
Leave a Reply. |