(2)
Your rating: Now say why...
- Download Now
983 KB -
Visit Developer's Site
SpamAssassin Group
SpamAssassin is a mail filter which attempts to identify spam using a variety of mechanisms including text analysis, Bayesian filtering, DNS blocklists, and collaborative filtering databases.
Using its rule base, it uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and non-spam
Using its rule base, it uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and non-spam
What's New
Version 3.3.2:
- Bug #6353: Fix FH_FROMEML_NOTLD, add MISSING_FROM
- Bug #6427: Spamc windows header library missing two defines.
- Bug #6476: patch to fix missing sa-awl man page bug
- Bug #6470: Small change in windows to exit stating that the exit statusis unknown. Thanks to Daniel Lemke for many of these small win32 patches.
- Bug #6314: Complete removal of spamassassin.spec
- Bug #6589: Errors in man pages
- Bug #6588: Small bug in the regexp caught by Jose Borges Ferreira in
- Bug #6515: spamd timeout_child option overrides time_limit configurationoption with nastier behaviour
- Bug #6490: Mail::SpamAssassin::Plugin::SPF - Two enhancement issues
- Bug #6562: NULL reference bug in libspamc. Quick workaround to avoid a crash.
- Bug #6454: wrong status test on $sth->rows in BayesStore::PgSQL
- Bug #6418: Cannot Log to stderr without timestamps
- Bug #6403: GMail should use ESMTPSA to indicate that it is in fact authenticated, but doesn't
- Bug #6229: TextCat is too case sensitive
- Bug #6241: mkrules does not understand newer options and "else"
- Bug #6382: add missing unwhitelist_from_dkim, remove facebook andlinkedin from dkim whitelisting
- Bug #5744: some documentation fixes
- Bug #6447: new feature to bayes autolearning: learn-on-error
- Bug #6566: X-Ham-Report default wording ("has identified this incomingemail as possible spam") is confusing and inaccurate
- Bug #6468: splice() offset past end of array in HTML.pm
- Bug #6377: win32: spamd signal handling
- Bug #6376: win32: consider negative pids under windows in spamds waitpid
- Bug #6375: win32: posix macro not implemented - spamd
- Bug #6336: "Illegal octal digit 9" received during rules compile
- Bug #6526: Disable rfc-ignorant.org
- Bug #6531: clear_uridnsbl_skip_domain feature to allow admin override ofdefault configuration
- Bug #5491: MIME_QP_LONG_LINE triggering on valid email
- Bug #6558: body rules having "tflags multiple" may cause infinite loopwhen compiled - a workaround
- Bug #6557: Use same age limits in ruleqa as in sa-updates
- Bug #6548: spamd protocol examples are wrong
- Bug #6500: clear_originating_ip_headers seems to be broken
- Bug #6565: check_rbl_sub rules - all dots need to be escaped - commitfelicity/70_dnswl.cf and felicity/70_iadb.cf too
- Bug #6565: check_rbl_sub rules - all dots need to be escaped
- Bug #6578: Move TLD regexp to RegistrarBoundaries and make FreeMail use it
- Bug #6392: fix one more case of a 'goto into a construct' this oneoccured with sa-compile
- Bug #6443: Metadata Headers are Case-Sensitive
- Bug #5690: tune BAD_ENC_HEADER score down
- Bug #6022, tune TVD_RCVD_IP score down
- Bug #6394: too high score for FREEMAIL_ENVFROM_END_DIGIT
- Bug #6499: and mailing list: wrapped scores for rulesDKIMDOMAIN_IN_DWL*, ACCESSDB and SHORTCIRCUIT into a suitableifplugin/endif to avoid lint warnings; removed score for nonexistentrule SUBJ_RE_NUM.
- Bug #6242: merge the boundary fix in r931527 to the 3.3 branch
- Bug #6460: RCVD_ILLEGAL_IP false positives
- Bug #6506: Modifying a list while traversing it with a foreach
- Bug #6488: Lint errors with Perl 5.12.1 in AntiVirus.pm
- Bug #6467: Remove assigned 223/8 from RCVD_ILLEGAL_IP
- Bug #6419: Resolve rounding issue irregularity with spamd/spamc
- Bug #5894: spamd doesn't use vpopmail virtual users' dirs - removed oneextra space
- Bug #6416: avoid undef warnings in AutoWhitelist.pm as a result ofincorrect Received header field or its incorrect parsing
- Bug #6415: Open of auto-whitelist file failed: Insecure dependency in eval
- Bug #6299: update, enhance, and expand RCVD_ILLEGAL_IP from
- Bug #6392: Test suite fails with perl 5.12.0
- Bug #6412: remove .yu TLD and add .me SLDs
- Bug #6395: backport - improved URI parsing
- Bug #6393: make File::Copy module load conditional on 'sa-learn--upgrade' with DBM files, not very commonly used
Version 3.3.2:
- Bug #6353: Fix FH_FROMEML_NOTLD, add MISSING_FROM
- Bug #6427: Spamc windows header library missing two defines.
- Bug #6476: patch to fix missing sa-awl man page bug
- Bug #6470: Small change in windows to exit stating that the exit statusis unknown. Thanks to Daniel Lemke for many of these small win32 patches.
- Bug #6314: Complete removal of spamassassin.spec
- Bug #6589: more...
Requirements
- PPC / Intel
- Mac OS X 10.2 or later
- Perl
SpamAssassin User Discussion (Write a Review)
Overall:
(3)
(3)
-
-
-
SpamAssassin is a mail filter which attempts to identify spam using a variety of mechanisms including text analysis, Bayesian filtering, DNS blocklists, and collaborative filtering databases.
Using its rule base, it uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and non-spam in between 95% and 100% of cases, depending on what kind of mail you get and your training of its Bayesian filter. Specifically, SpamAssassin has been shown to produce around 0.9% false negatives (spam that was missed) and around 0.1% false positives (ham incorrectly marked as spam). See the rules/STATISTICS*.txt files for more information.
Using its rule base, it uses a wide range of heuristic tests on mail headers and body text to identify "spam", also known as unsolicited commercial email.
Once identified, the mail can then be optionally tagged as spam for later filtering using the user's own mail user-agent application.
SpamAssassin typically differentiates successfully between spam and non-spam in between 95% and 100% of cases, depending on what kind of mail you get and your training of its Bayesian filter. Specifically, SpamAssassin has been shown to produce around 0.9% false negatives (spam that was missed) and around 0.1% false positives (ham incorrectly marked as spam). See the rules/STATISTICS*.txt files for more information.
Copyright © 2012 MacUpdate LLC
- -
-7
+4
+683
-6
+14
Anonymous reviewed on 20 Dec 2004
Anonymous reviewed on 22 Sep 2004
Constantin reviewed on 22 Sep 2004
The new approach of blacklisting spam according what web-sites it is pointing to is brilliant, as it makes it that much harder for internet scum to succeed overcoming spam filters.
Anonymous reviewed on 05 Aug 2004
+2
+62
Joel Mueller reviewed on 09 Dec 2003
I only wish that SpamAssassin would be built to support client-side configuration based on a single domain so that shared hosting companies could more easily allow their clients to configure it.