SpamAssassin
From Wikipedia, the free encyclopedia
SpamAssassin | |
Developer: | The SpamAssassin team |
---|---|
Latest release: | 3.1.7 / October 08, 2006 |
OS: | Cross-platform |
Use: | Email spam filter |
License: | Apache License 2.0 |
Website: | spamassassin.apache.org |
SpamAssassin is a computer program released freely under the Apache License 2.0 used for e-mail spam filtering based on content-matching rules, which also supports DNS-based, checksum-based and statistical filtering, supported by external programs and online databases.
SpamAssassin is generally regarded as one of the most effective spam filters[citation needed], especially when used in combination with spam databases. Even simple text-matching alone may, for most users, be sufficient to correctly classify a majority of incoming mail.
Contents |
[edit] History
SpamAssassin was created by Justin Mason who had maintained a number of patches against an earlier program named filter.plx by Mark Jeftovic, which in turn was begun in August 1997. Mason rewrote all of Jeftovic's code from scratch and uploaded the resulting codebase to SourceForge.net on April 20, 2001.
[edit] Methods of usage
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 can be run as a standalone application or as a client (spamc) that communicates with a daemon (spamd). The latter mode of operation has performance benefits, but under certain circumstances may introduce additional security risks.
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. Mail filter programs such as procmail can be made to pipe all incoming mail through SpamAssassin with an adjustment to user's .procmailrc file.
[edit] Anti-spam techniques
SpamAssassin comes with a large set of rules which are applied to determine whether an email is spam or not. To decide, specific fields within the email header and the email body are typically searched for certain regular expressions, and if these expressions match, the email is assigned a certain score, depending on the test, and several (customizable) headers are added to the mail. The total score resulting from all tests or other criteria can then be used by the end user or by the ISP to set the conditions under which email is moved to a separate spam folder, deleted, flagged etc.
Each test has a label and a description. The label is usually an all upper case identifier separated with underscores, such as "LIMITED_TIME_ONLY", with the description for that label being "Offers a limited time offer". A mail that passes that test (in this case, contains certain variants of the "limited time only" phrase) might be assigned a score of +0.3. With a spam threshold of 5 (default as of version 2.55), several other tests would usually have to pass for the mail to be classified as spam. On the other hand, some tests, such as those for invalid message IDs or years, result in a very high score being assigned, where even a single test can almost put a mail "over the edge".
When a mail's total score is higher than the "required_score" setting in SpamAssassin's configuration, the mail is treated as spam and rewritten according to several options. 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 the score is lower than the defined settings, by default the information about the passed tests 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.
The user can customize these filters using a file "user_prefs" in their home directory. Within this file, they can specify individuals whose emails are never considered spam, or change the scores for certain rules. The user can also define a list of languages which they want to receive mail in, and SpamAssassin then assigns a higher score to all mails that appear to be written in another language. This can be very useful to users receiving a lot of foreign spam but never actually corresponding with people in that language.
[edit] Network-based filtering methods
SpamAssassin also supports:
- DNS-based blackhole lists
- URI blacklists such as SURBL or URIBL.com which track spam websites
- checksum-based filters such as the Distributed Checksum Clearinghouses and Vipul's Razor
- Hashcash
- Sender Policy Framework
as a means to tell 'ham' from 'spam'.
More methods can be added reasonably easily by writing a Perl plug-in for SpamAssassin.
[edit] Bayesian filtering
SpamAssassin by default tries to reinforce its own rules through Bayesian filtering, but Bayesian learning is most effective with actual user input. Typically, the user is expected to "feed" example spam mails and example "ham" (useful) mails to the filter, which can then learn the difference between the two. For this purpose, SpamAssassin provides the command-line tool sa-learn, which can be instructed to learn a single mail or an entire mailbox as either ham or spam.
Typically, the user will move unrecognized spam to a separate folder for a while, and then run sa-learn on the folder of non-spam and on the folder of spam separately. Alternatively, if the mail user agent supports it, sa-learn can be called for individual emails. Regardless of the method used to perform the learning, SpamAssassin's Bayesian test will subsequently assign a higher score to e-mails that are similar to previously received spam (or, more precisely, to those emails that are different from non-spam in ways similar to previously received spam e-mails).
[edit] Licensing and usage elsewhere
SpamAssassin is open source, licensed under the Apache License 2.0. Versions prior to 3.0 are dual-licensed under the Artistic License and the GNU General Public License.
The following open source products have support for SpamAssassin:
- Citadel - email/groupware server contains built-in support for SpamAssassin integration
- MailScanner - "A Free Anti-Virus and Anti-Spam Filter"
- SpamAssassin for Win32 is a Windows build of spamc/spamd as well as a POP3 proxy
- SpamGrinderProxy is a Windows service that integrates SpamAssassin into POP3 e-mail clients and SMTP servers
- KMail supports SpamAssassin and other spam filters, through some modular filters.
SpamAssassin has also been used in many commercial products including:
- Byteplant No Spam Today! is a SMTP and POP3 SpamAssassin proxy for Windows and Linux
- McAfee uses SpamAssassin in its anti-spam tool SpamKiller
- Spamnix is also based on SpamAssassin
- Kerio MailServer uses SpamEliminator, which is based on SpamAssassin, for heuristic spam filtering
- Tenon Post.Office uses SpamAssassin through a SMTP filter plug-in
- Guinevere contains the SpamAssassin code for filtering e-mail for the GroupWise message server
- MailLaunder is a hosted spam and virus solution that uses SpamAssassin as part of the filtering process
- Atmail uses the SpamAssassin engine and adds a webmail interface for tweaking spam settings
- http://www.icewarp.com Merak Email Server by IceWarp
- Proxmox Mail Gateway is a spam and virus filter (software appliance) which uses SpamAssassin as part of the filtering process
[edit] Testing Spamassassin
Most implementations of SpamAssassin will trigger on the GTUBE, a 68 byte string not unlike the antivirus EICAR test file. If this string is inserted in a RFC 822 formatted message and passed through the SpamAssassin engine, SpamAssassin will trigger with a weight of 1000.
[edit] External links
- SpamAssassin official homepage
- SpamAssassin Wiki
- links for german users
- sa-update Automatically updating SA
- SpamAssassin Rules Emporium (SARE) containing many very good rules for filtering with SA.
- OpenProtect's SpamAssassin sa-update channel to automatically update SA with the newest and best SARE rules.
- MIMEDefang - MIMEDefang is a framework for filtering e-mail.
Top level Projects: Apache HTTP Server · Ant · APR · Beehive · Cocoon · Directory · Excalibur · Forrest · Geronimo · Gump · iBATIS · Jackrabbit · James · Lenya · Maven · MyFaces · mod_perl · SpamAssassin · Struts · TCL · Tomcat · Axis · XMLBeans · Tapestry · HiveMind · WebWork 2 · Harmony
Jakarta Project: BCEL · BSF · Cactus · Commons · ECS · HttpComponents · JCS · JMeter · ORO · POI · Regexp · Slide · Taglibs · Turbine · Velocity
Apache DB: Derby · Torque · DdlUtils · OJB · JDO
Apache Portals: Jetspeed 1 · Jetspeed 2 · Graffito · Pluto · WSRP4J
Apache Lucene: Lucene Java · Nutch · Hadoop · Lucene4c · Lucy
Apache XML: AxKit · Xalan · Xerces
Apache Logging': Log4j · Log4Cxx · Log4Perl · Log4PLSQL
Apache Incubator: Yoko · WADI · OpenEJB · ServiceMix · ActiveMQ · OFBiz · Wicket · Log4Net · Log4PHP · Roller
License: Apache License • Website: apache.org