If the score is lower than the defined settings, by default the information about the tests passed and total score is still added to the email headers and can be used in post-processing for less severe actions, such as tagging the mail as suspicious.Īpache SpamAssassin allows for a per-user configuration of its behavior, even if installed as system-wide service the configuration can be read from a file or a database. In the default configuration, the content of the mail is appended as a MIME attachment, with a brief excerpt in the message body, and a description of the tests which resulted in the mail being classified as spam. If Apache SpamAssassin considers a message to be spam, it can be further rewritten. Usually a message will only be considered as spam if it matches multiple criteria matching just a single test will not usually be enough to reach the threshold. The higher the score, the higher the probability that the message is spam.Īpache SpamAssassin has an internal (configurable) score threshold to classify a message as spam. A message is matched against all tests and Apache SpamAssassin combines the results into a global score which is assigned to the message.
The scores can be positive or negative, with positive values indicating "spam" and negative "ham" (non-spam messages). The rules are called "tests" in the SpamAssassin documentation.Įach test has a score value that will be assigned to a message if it matches the test's criteria. Most rules are based on regular expressions that are matched against the body or header fields of the message, but Apache SpamAssassin also employs a number of other spam-fighting techniques. Mail filter programs such as procmail can be made to pipe all incoming mail through Apache SpamAssassin with an adjustment to a user's procmailrc file.Īpache SpamAssassin comes with a large set of rules which are applied to determine whether an email is spam or not. Typically either variant of the application is set up in a generic mail filter program, or it is called directly from a mail user agent that supports this, whenever new mail arrives. The client/server or embedded mode of operation has performance benefits, but under certain circumstances may introduce additional security risks. It can be run as a standalone application or as a subprogram of another application (such as a Milter, SA-Exim, Exiscan, MailScanner, MIMEDefang, Amavis) or as a client ( spamc) that communicates with a daemon ( spamd). Methods of usage Īpache SpamAssassin is a Perl-based application ( Mail::SpamAssassin in CPAN) which is usually used to filter all incoming mail for one or several users. It was announced that development of version 4.0.0 would become project's focus. In April, 2021, version 3.4.6 of SpamAssassin was released. In December 2019, version 3.4.3 of SpamAssassin was released. 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.".
#SPAMASSASSIN BLACKLISTS SOFTWARE#
In Summer 2004 the project became an Apache Software Foundation project and later officially renamed to Apache SpamAssassin.
#SPAMASSASSIN BLACKLISTS CODE#
Mason rewrote all of Jeftovic's code from scratch and uploaded the resulting codebase to SourceForge on April 20, 2001. Apache 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.
0 kommentar(er)
