You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by jm...@jmason.org on 2004/07/23 06:07:19 UTC

SpamAssassin 3.0.0-pre3 is released!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

*** THIS IS A PRE-RELEASE ONLY, NOT THE FINAL 3.0.0 RELEASE ***

SpamAssassin 3.0.0-pre3 is released!  SpamAssassin 3.0.0 is a major update
and includes a number of new email and anti-spam technologies.

SpamAssassin is a mail filter which uses advanced statistical and
heuristic tests to identify spam (also known as unsolicited bulk email).

Highlights of the release
- - -------------------------

 - SpamAssassin is now part of the Apache Software Foundation, bringing an
   improved and clearer software license, the 2.0 version of the Apache
   License.

 - We added a new architecture which allows third-parties to easily add
   plugin modules.

 - There is now SQL database support for both the Bayes and auto-whitelist
   subsystems, allowing more large sites to easily deploy SpamAssassin.

 - A more accurate simulation of email client handling of MIME and HTML
   improves our accuracy.  In addition, there is better detection and
   handling of spammer techniques used to trick email clients and filters.

 - Web sites contained in the message body are checked against network
   databases of domains that advertise with spam.

 - SpamAssassin now includes support for SPF (the Sender Policy Framework,
   http://spf.pobox.com/).

Downloading
- - -----------

Pick it up from:

  http://old.SpamAssassin.org/released/Mail-SpamAssassin-3.0.0-pre3.tar.gz
  http://old.SpamAssassin.org/released/Mail-SpamAssassin-3.0.0-pre3.tar.bz2
  http://old.SpamAssassin.org/released/Mail-SpamAssassin-3.0.0-pre3.zip

md5sum:

  c2b2506fb4dd8ba8869e6dd6ed633e8f  Mail-SpamAssassin-3.0.0-pre3.tar.bz2
  ef54126e47734c2c446a22ed77f5cdd3  Mail-SpamAssassin-3.0.0-pre3.tar.gz
  d892bee323264e5a71aa4af718ac05b0  Mail-SpamAssassin-3.0.0-pre3.zip

sha1sum:

  410c5bb9c6203a39500613f5191e375b0b93146a  Mail-SpamAssassin-3.0.0-pre3.tar.bz2
  56d3f5ba687a0d1ab1c7fc491527d995ffc86761  Mail-SpamAssassin-3.0.0-pre3.tar.gz
  9acc52df5022edf24ffce992e5c3f6d3dac1185b  Mail-SpamAssassin-3.0.0-pre3.zip

The release files also have a .asc accompanying them.  The file serves
as an external GPG signature for the given release file.  The signing
key is available via the wwwkeys.pgp.net key server, as well as
http://www.spamassassin.org/released/GPG-SIGNING-KEY

The key information is:

pub  1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@spamassassin.o
rg>
     Key fingerprint =3D 26C9 00A4 6DD4 0CD5 AD24  F6D7 DEE0 1987 265F A05B

Important installation notes
- - ----------------------------

- - - The SpamAssassin 2.6x release series was the last set of releases to
  officially support perl versions earlier than perl 5.6.1.  If you are
  using an earlier version of perl, you will need to upgrade before you
  can use the 3.0.0 version of SpamAssassin.

- - - SpamAssassin 3.0.0 has a significantly different API (Application
  Program Interface) from the 2.x series of code.  This means that if you
  use SpamAssassin through a third-party utility (milter, etc,) you need
  to make sure you have an updated version which supports 3.0.0.

- - - The --auto-whitelist and -a options for "spamd" and "spamassassin" to
  turn on the auto-whitelist have been removed and replaced by the
  "use_auto_whitelist" configuration option which is also now turned on by
  default.

- - - The "rewrite_subject" configuration setting was deprecated and is now
  removed. Instead, using "rewrite_header Subject [your desired setting]".
  e.g.

    rewrite_subject ****SPAM(_SCORE_)****

  becomes

    rewrite_header Subject ****SPAM(_SCORE_)****

- - - The Bayesian storage modules have been completely re-written and now
  include Berkeley DB (DBM) storage as well as SQL based storage (see
  sql/README.bayes for more information).  In addition, a new format has
  been introduced for the bayes database that stores tokens in fixed
  length hashes.  All DBM databases should be automatically converted to
  this new format the first time they are opened for write.  You can
  manually perform the upgrade by running "sa-learn --sync" from the
  command line.

  The "sa-learn --rebuild" command has been deprecated; please use
  "sa-learn --sync" instead.  The --rebuild option will remain temporarily
  for backwards compatibility.

- - - "spamd" now has a default max-children setting of 5; no more than 5
  child scanner processes will be run in parallel.  Previously, there was
  no default limit unless you specified the "-m" switch when starting
  spamd.

- - - If you are using a UNIX machine with all database files on local disks,
  and no sharing of those databases across NFS filesystems, you can use a
  more efficient, but non-NFS-safe, locking mechanism.   Do this by adding
  the line "lock_method flock" to the /etc/mail/spamassassin/local.cf
  file. This is strongly recommended if you're not using NFS, as it is
  much faster than the NFS-safe locker.

- - - Please note that the use of the following command line parameters for
  spamassassin and spamd have been deprecated and are now removed.  If you
  currently use these flags, please remove them:

    in the 2.6x series: --add-from, --pipe, -F, -P, --stop-at-threshold, -S
    in the 3.0.x series: --auto-whitelist, -a

- - - The following flags are deprecated and will be removed in a future major
  release: --whitelist-factory, -M, --warning-from, -w, --log-to-mbox, -l.

- - - SpamAssassin runs in "taint mode" by default for improved security.
  Certain third-party modules, such as Razor v2, may be incompatible with
  taint mode. For Razor v2, you will need to be using v2.40 of
  razor-agents or higher which allows taint mode by default.  Earlier
  versions which are patched to allow taint mode may be used as well.

- - - Finally, 2.6x deprecated the use of the "check_bayes_db" script, and it
  is now no longer available.  Please see the sa-learn man/pod
  documentation for more info.

Summary of major changes since 2.6x
- - -----------------------------------

Licensing:

  - Relicensed using Apache License v2.0, instead of dual GPL/PAL licensing,
    since we are now an Apache Incubator project.

New rules:

  - SPF testing, if the Mail::SPF::Query module is installed.

  - added new rules and code to combat Bayes poisoning text and random
    hash-busters; Habeas rules now verify against the Habeas user
    list, to combat forged marks used in spam.

  - URIDNSBL rules.  These do DNSBL lookups on URLs, allowing URLs found
    in the message body to be used in spam determination.  Added the SURBL
    blocklist (http://www.surbl.org/).

  - Spamhaus XBL and a variety of new DNSBL rules

  - Hashcash support.

  - added Bob Menschel's 'longwords' rules

  - added 'backhair' rule, technique based on Jennifer Wheeler's ruleset

  - added Matt Kettler's 'antidrug' ruleset

  - added anti-fraud rules from Matt Yackley

  - added some hostname-based blocklist tests based on the envelope
    sender address.

  - a *lot* of other new rules, too many to detail here

Spamd:

  - spamd now uses a 'preforking' model instead of 'fork per message'.

  - new log format, detailing message-id, resent-message-id, the tests hit,
    autolearn status, and several other things in a mass-check compatible
    format, to provide more information for spamd log-summarizer scripts.

Infrastructure:

  - Plugins.  Third-party modules can now be written and loaded dynamically
    from inside SpamAssassin, to provide support for entirely new rule types
    or eval tests.

  - SQL support for Bayes and AWL storage, thanks to Michael Parker.
    See sql/README.bayes and sql/README.awl for additional information.

  - ground-up rewrite of the MIME parser.  Now deals correctly with complex
    MIME structures, including entire message/rfc822 message attachments.

  - rules can now test the "MAIL FROM:" address used in the SMTP transaction,
    if it was logged to the message headers, using the "EnvelopeFrom"
    pseudoheader.  This allows rules such as SPF to be applied.

  - Added optional faster but NFS-unsafe Bayes locking mechanism, using
    "lock_method flock"

  - support for parsing mbx mailboxes, as used by UW IMAP. Thanks to John
    Newman for this patch.

  - refactored configuration parser to split parser code from configuration
    settings.

  - Bayes databases can now be backed up and restored using --backup and
    --restore.

  - Config files can now include other files using the "include" command.

  - replaced GA-based evolver with fast Perceptron score generation tool by
    Henry Stern; scores can now be generated much more quickly.

  - The "spamassassin" script can now check collections of mail en masse.  This
    lets us do things like 'spamassassin -d --mbox file1' and have the
    functionality go over the entire mbox file. same for checks, adding to
    white/black-lists, etc.

Translations: 

  - Dutch translation, thanks to Jesse Houwing

  - Polish translations from Jerzy Szczudlowski and radek at alter dot pl

  - French translations, Michel Bouissou

  - German translations, Daniel Roethlisberger

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFBAI72QTcbUG5Y7woRAg1aAKDe6pMdQu3GLYcku/oFXaIuzVlaCQCg45wE
8F2tQeuZD5XoSQLCqKDkBeU=
=BtwE
-----END PGP SIGNATURE-----


Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Michael Parker <pa...@pobox.com>.
On Fri, Jul 23, 2004 at 10:29:30AM -0700, Daniel Quinlan wrote:
> 
> I suggest we roll a pre4 release and allow people to submit mass-check
> logs with either pre3 or pre4 (recommending pre4).
> 

+1

Michael

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Jul 23, 2004 at 10:29:30AM -0700, Dan Quinlan wrote:
> So, the first tarball got pushed out and not the second?

yeah.

> I suggest we roll a pre4 release and allow people to submit mass-check
> logs with either pre3 or pre4 (recommending pre4).

It doesn't matter to me really as far as mass-checks go, I don't think
there's anything that wasn't included that will affect the results.

a pre4 may be good for testing purposes though.

So I'm +0.

-- 
Randomly Generated Tagline:
"Given enough time and money, Microsoft will eventually 'invent' Unix.
  no chance.  they only have a finite number of monkeys." - Thomas Lakofski

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Daniel Quinlan <qu...@pathname.com>.
Theo Van Dinter <fe...@kluge.net> writes:

> or the fixes to the URIBL scores.  I don't think this requires a new
> preX release, but ...

So, the first tarball got pushed out and not the second?

I suggest we roll a pre4 release and allow people to submit mass-check
logs with either pre3 or pre4 (recommending pre4).

Daniel

-- 
Daniel Quinlan
http://www.pathname.com/~quinlan/

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Jul 23, 2004 at 11:42:20AM -0400, Theo Van Dinter wrote:
> As for changes, it looks like the Changes file wasn't updated... :(

Ok, so...  pre3 isn't quite right.

First, the pre3 Changes file wasn't committed to svn, it had the final
pre2 commit at the top.  That also caused the nightly version update to
fail, btw, since the modified Changes was sitting in version/cvshead...
So I copied it from bugzilla and committed it and fixed the nightly issue.

Second, in IRC we discussed how the first pre3 tarball was made from
r23166, but how there were a few more tickets to close and commit
before the release -- implying we needed to wait for those, then roll
a new tarball.

Sure enough, the now released pre3 tarball is still r23166, and the other
commits (up through r23174) are therefore not in there.  That means pre3
does not include:

bug 3604 (spamc documentation)
bug 3586 (bsd setuid() workaround/Mac OS X documentation)
bug 3554 (list warning/error for deprecated/removed options)
bug 3588 (german translations)
bug 3621 (spamcop reporting)

or the fixes to the URIBL scores.  I don't think this requires a new
preX release, but ...


-- 
Randomly Generated Tagline:
Mmm...incapacitating.
 
        		-- Homer Simpson
 		   The Springfield Connection

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Jul 23, 2004 at 01:05:57AM -0600, LuKreme wrote:
> Any summary of changes since pre2?  like is the ()'s being replaced by 
> []'s fixed?

There is no ticket for the paren/bracket thing, so it hasn't changed.

As for changes, it looks like the Changes file wasn't updated... :(

-- 
Randomly Generated Tagline:
"I thought you were dead.
  Yeah ... I get that a lot."    - From the movie "Alien: Resurrection"

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by LuKreme <kr...@kreme.com>.
On 22 Jul 2004, at 22:07, jm@jmason.org wrote:
> Summary of major changes since 2.6x
> - - -----------------------------------

Any summary of changes since pre2?  like is the ()'s being replaced by 
[]'s fixed?

>
-- 
I want a party where all the women wear new dresses and all the men 
drink beer.  -- Jason Gaes


Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Jeff Chan <je...@surbl.org>.
On Thursday, July 22, 2004, 10:05:38 PM, Daniel Quinlan wrote:
> Jeff Chan <je...@surbl.org> writes:

>> which could be a little confusing since uridnsbl, urirhsbl and
>> urirhssub do different things but are in the same .pm.  If I were
>> explaining it, I'd say uridnsbl can be used with RBLs containing
>> name server addresses such as sbl.spamhaus.org, and urirhsbl and
>> urirhssub can be used with RBLs that contain URI domains such as
>> SURBLs. 

> How about this?

>    - URIDNSBL rules.  These are network tests of URLs found in the
>      message body.  URLs are checked using both SURBL
>      <http://www.surbl.org/> and SBL <http://www.spamhaus.org>.

Works for me.  sbl.spamhaus.org might be a little more
specific, yet ok since sbl is so widely known already.

Jeff C.


Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Daniel Quinlan <qu...@pathname.com>.
Jeff Chan <je...@surbl.org> writes:

> which could be a little confusing since uridnsbl, urirhsbl and
> urirhssub do different things but are in the same .pm.  If I were
> explaining it, I'd say uridnsbl can be used with RBLs containing
> name server addresses such as sbl.spamhaus.org, and urirhsbl and
> urirhssub can be used with RBLs that contain URI domains such as
> SURBLs. 

Wow, that's wordy for an announcement.  ;-)

How about this?

   - URIDNSBL rules.  These are network tests of URLs found in the
     message body.  URLs are checked using both SURBL
     <http://www.surbl.org/> and SBL <http://www.spamhaus.org>.

Daniel

-- 
Daniel Quinlan
http://www.pathname.com/~quinlan/

Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Jeff Chan <je...@surbl.org>.
On Thursday, July 22, 2004, 9:21:12 PM, Theo Dinter wrote:
> Just some notes:

> On Thu, Jul 22, 2004 at 09:07:19PM -0700, Justin Mason wrote:
>>  - SpamAssassin now includes support for SPF (the Sender Policy Framework,
>>    http://spf.pobox.com/).

> should probably also mention SURBL, since that's getting to be a big thing now.

It's in there, under URIDNSBL:

>   - URIDNSBL rules.  These do DNSBL lookups on URLs, allowing URLs found
>     in the message body to be used in spam determination.  Added the SURBL
>     blocklist (http://www.surbl.org/).

which could be a little confusing since uridnsbl, urirhsbl and
urirhssub do different things but are in the same .pm.  If I were
explaining it, I'd say uridnsbl can be used with RBLs containing
name server addresses such as sbl.spamhaus.org, and urirhsbl and
urirhssub can be used with RBLs that contain URI domains such as
SURBLs. 

Jeff C.


Re: SpamAssassin 3.0.0-pre3 is released!

Posted by Theo Van Dinter <fe...@kluge.net>.
Just some notes:

On Thu, Jul 22, 2004 at 09:07:19PM -0700, Justin Mason wrote:
>  - SpamAssassin now includes support for SPF (the Sender Policy Framework,
>    http://spf.pobox.com/).

should probably also mention SURBL, since that's getting to be a big thing now.

> pub  1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <release@spamassassin.o
> rg>

doh (wrapping).

> - - - The "rewrite_subject" configuration setting was deprecated and is now
>   removed. Instead, using "rewrite_header Subject [your desired setting]".
>   e.g.
> 
>     rewrite_subject ****SPAM(_SCORE_)****
> 
>   becomes
> 
>     rewrite_header Subject ****SPAM(_SCORE_)****

rewrite_subject w/ _SCORE_ never worked.  it was _HITS_ in 2.6x.
we should mention that "hits" was replaced with "score" everywhere,
so default X-Spam-Status (for filtering) and the header macro are two
places people may want to check.

-- 
Randomly Generated Tagline:
"Every use of Linux is a proper use of Linux."   - John "Maddog" Hall