5/16/2023 0 Comments Spamassassin rules![]() ![]() The SpamAssassin 3.4.2 release in September 2019 was the first in over three years, but the developers say that "The project has picked up a new set of developers and is moving forward again.". In Summer 2004 the project became an Apache Software Foundation project and later officially renamed to Apache SpamAssassin. Mason rewrote all of Jeftovic's code from scratch and uploaded the resulting codebase to SourceForge on April 20, 2001. Apache SpamAssassin is highly configurable if used as a system-wide filter it can still be configured to support per-user preferences.Īpache SpamAssassin was created by Justin Mason, who had maintained a number of patches against an earlier program named x by Mark Jeftovic, which in turn was begun in August 1997. It can also be run by individual users on their own mailbox and integrates with several mail programs. The program can be integrated with the mail server to automatically filter all mail for a site. It is released under the Apache License 2.0 and is a part of the Apache Foundation since 2004. It uses a variety of spam-detection techniques, including DNS and fuzzy checksum techniques, Bayesian filtering, external programs, blacklists and online databases. 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./ 17 December 2022 3 months ago ( 17 December 2022)Īpache SpamAssassin is a computer program used for e-mail spam filtering. 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.
0 Comments
Leave a Reply. |