You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Theo Van Dinter <fe...@apache.org> on 2006/05/26 02:42:47 UTC

ANNOUNCE: Apache SpamAssassin 3.1.2 available!

Apache SpamAssassin 3.1.2 is now available!  This is a maintainance
release of the 3.1.x branch.

Downloads are available from:
  http://spamassassin.apache.org/downloads.cgi?update=200605251700

The release file will also be available via CPAN in the near future.

md5sum of archive files:
  e1fb14def1265d6d7351ba27b5940da2  Mail-SpamAssassin-3.1.2.tar.bz2
  f255d8e887ea7961939d40b184e82054  Mail-SpamAssassin-3.1.2.tar.gz
  9af9f2db1526baaa01b6b14a9b0e057a  Mail-SpamAssassin-3.1.2.zip

sha1sum of archive files:
  aad32b73f2870182fe8f2dd5277e94d0da91b196  Mail-SpamAssassin-3.1.2.tar.bz2
  ea5e1e9755e294ee9edb238144ac831602d10027  Mail-SpamAssassin-3.1.2.tar.gz
  c00da67f7dd9d9df7f9e148c7530586711991f46  Mail-SpamAssassin-3.1.2.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://spamassassin.apache.org/released/GPG-SIGNING-KEY

The key information is:

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

3.1.2 includes a large number of bug fixes and documentation updates.
Here is an abbreviated changelog (since 3.1.1) for major updates (see
the Changes file for a complete list):

- bug 4802: implement DKIM plugin, including whitelist_from_dkim support
- bug 3838: work around Perl bug causing captured RE variables to become
  tainted -- thanks to Mark Martinec for pointing out the bug with
  Perl itself
- bug 4850: re-enable the Razor2 plugin by default due to a service
  policy change
- bug 4826: Razor2 plugin needs to load Mail::SpamAssassin::Timeout module
- bug 4827: M::SA::first_existing_path() would return the last array
  entry passed in if none of the paths were found.  Now return undef
  instead and handle the error when it happens.
- bug 4813: generally open RE causes sendmail received header get read
  in as qmail in error
- bug 4839: Logger.pm converts control chars including tab into
  underscores which confuses a bunch of users when checking debug output.
  Convert tab into space instead, etc.
- bug 4884: if a null message is passed in, there are several variables
  which end up undefined causing warnings.  fake an empty message if no
  input is given.
- bug 4793: when replacing tags in a message (_TAG_), leave the tags
  that don't exist alone instead of just removing them
- bug 4861, 4760: handle dccifd and dccproc failover properly, backport
  relays_internal and relays_external code, backport bug 4760 fix so
  that it's not possible to be in internal_networks without being in
  trusted_networks as well
- bug 4901: deal more properly with failures in bgsend().  also, use
  the proper variable to show when errors occur.
- bug 4867: fetchmail changed header formats at some point making Received
  parsing fail in certain conditions
- bug 4699: use M::SA::Timeout for spamd copy_config call and allow for empty $@ values
- bug 3754: if there's a problem opening a file via sa-learn or
  spamassassin, return an error exit value.

Re: ANNOUNCE: Apache SpamAssassin 3.1.2 available!

Posted by Kai Schaetzl <ma...@conactive.com>.
Theo Van Dinter wrote on Thu, 25 May 2006 20:42:47 -0400:

> Apache SpamAssassin 3.1.2 is now available!

rpm built, installed, linted, checked, running fine it seems.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com




Re: ANNOUNCE: Apache SpamAssassin 3.1.2 available!

Posted by jdow <jd...@earthlink.net>.
From: "Theo Van Dinter" <fe...@apache.org>

> Apache SpamAssassin 3.1.2 is now available!  This is a maintainance
> release of the 3.1.x branch.

Whine, you mean I have to put in the special print code that Loren
needs for properly creating rules in yet ANOTHER release?

<grump>

{^_-}