![]() ![]() This will set the score to 5 no matter what the default was. If you have a custom rule that adds points and attached a zip too large to be scanned, your X-Spam-Status header might look. Nor does it affect Spam points you might add through custom rules. If you set that to block zip attachments, that will work regardless of message size. To set your own definite score, simply remove the brackets so the rule looks like: Understand that this setting in no way affects the Attachment Filter. So if the default scoring for the test ‘SUBJ_ALL_CAPS’ was 1, it would now be 6. In this case, the number in brackets means that the spam score should be increased by 5 from the default. SUBJ_ALL_CAPS is the test name which can be found in the official Spam Assassin wiki here. Edit the original user_prefs and add the lines below – the rules you want to edit along with the scores will probably be different.Make a backup of user_prefs and call it something like user_prefs.bak.Browse to the following directory (your directory structure could well be different from the one I post here but it should be similar at least) /home/yourusername/.spamassassin – this directory is above the www directory so if you don’t see this then you probably don’t have access.connect to your host using a file transfer client such as filezilla. If Spamassassin is to operate best on the full SMTP message received then it should be adding the final RETURN-PATH header (as it does) BEFORE it then passes it to Spamassassin.I write this article because I know some hosting providers (such as Namecheap) provide Spam Assassin as an ‘out of the box’ anti-spam solution and I know that some of the cpanel menus that support Spam Assassin aren’t as intuitive or helpful as they could be to help guide this process. The linter is suggesting to use multiples, not fractions in arithmetic meta rules. 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 article will show you very briefly how to assign your own scores for Spam Assassin tests or simply influence the default rule set. 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.If you use spamassassin here what you can do to create a simple rule to find words and rate the message with a desired score, which will (probably) mark it as a spam. ![]() ![]()
0 Comments
Leave a Reply. |