OK, this is 2.60 release candidate 2; it should work pretty excellently, but we want to give it a day or two before it gets an official thumbs-up. You can download it from http://SpamAssassin.org/released/ -- note: the release candidates are not listed on the SA Download page and will not be available via CPAN.
MD5sum: 4c5685922f51831791d9e93b9a1c7b41 Mail-SpamAssassin-2.60-rc2.tar.gz e3a6e7fff3173d342d8180a249db1903 Mail-SpamAssassin-2.60-rc2.zip There are also GPG signatures available. You can get the signing key at http://www.spamassassin.org/released/GPG-SIGNING-KEY, or via the wwwkeys.pgp.net keyserver. The signing key is: pub 1024D/265FA05B 2003-06-09 SpamAssassin Signing Key <[EMAIL PROTECTED]> uid SpamAssassin Signing Key <[EMAIL PROTECTED]> Changes since 2.50: - DNSBLs overhauled; lots of new lists, including SORBS and SpamCop BL - RBL timeouts are now handled much more efficiently; if one RBL is taking much longer than all the others, it will be ignored - now reduces amount of IP addresses queried by inferring trust relationships between Received headers - generalised Received-header parser to more easily detect HELO string forgery and faked relay lines - default report updated to list the hostname of the machine where SpamAssassin is running; also asks installer for administrative address or URL, to reduce user confusion - workaround for red hat kernel with NPTL reporting "application bug" in spamd due to use of waitpid() when SIGCHLD is set to SIG_IGN - new Bayes tweaks -- tokenization of partial address elements. - dccifd support added. - much more flexible header rewriting, with a simple template system - new bayes backend, including new database format, expiry code, ability to learn messages to the journal, etc. - lots of bugs fixed and new rules added. ;) Bayes FYI: 2.60 has a new Bayes backend and database format. Your old database(s) will automatically be upgraded the first time 2.60 tries to write to the DB, and any journal, if it exists, will be wiped out without being synced. So, what you want to do is something like this: - stop running spamassassin/spamd (ie: you don't want it to be running during the upgrade) - run "sa-learn --rebuild", this will sync your journal. - upgrade SA to 2.60 - run "sa-learn --rebuild", this will cause the db format to be upgraded - start running spamassassin/spamd again Obviously the steps will be different depending on your environment, but you get the idea. :) Bayes FYI 2: Because of the new database format, "check_bayes_db" will no longer function properly. The functionality from that script was added to sa-learn via the "--dump" parameter. Please see the sa-learn man/pod documentation for more info. Changes since 2.60-rc1, if anyone's curious: - update docs to suggest HTML::Parser 3.29 or later (3.31 is out as of this writing, the newer versions deal better with HTML comments) - osirusoft tests weren't running due to parent test having a 0 score in set1 - bug 2338: work around bad srand() setting from Razor2 - revert behavior of MIME_BASE64_LATIN after accidental commit - Makefile.PL was requiring Sys::Syslog instead of Sys::Hostname (broke on Windows machines) - bug 2334: make the trusted_networks code not call gethostbyname() if local_tests_only (aka: -L) is set. - bug 2206: if a dnsbl request timed out, there would be an undefined reference error in Dns.pm which caused the whole check to fail. this typically caused mail to pass with no markup.
pgp00000.pgp
Description: PGP signature
