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

(NOTE: this is a maintainance release of the 3.0.x branch.  If you are
already running the more up-to-date, stable 3.1.0, pay no attention!
This is only for people who are stuck on 3.0.x for some reason.)

We got enough votes for those tarballs we voted on last week, so it's an
official release now.  Here are the checksums:

md5sum of archive files:
  0d6066561db3e4efff73f00c34584cb8  Mail-SpamAssassin-3.0.5.tar.bz2
  12c9f14ffaeb5cb3b5801cc5b5231cdd  Mail-SpamAssassin-3.0.5.tar.gz
  e0d0e556d5929bb209aedc91ccdb2358  Mail-SpamAssassin-3.0.5.zip
  
sha1sum of archive files:
  30dcfce390a311dfff9430c1b00ae4f7e4357ca8  Mail-SpamAssassin-3.0.5.tar.bz2
  99051775deb4566077fdca57a274531bade19bc8  Mail-SpamAssassin-3.0.5.tar.gz
  7632e774d111764f041efb9e42453fc38885a1c2  Mail-SpamAssassin-3.0.5.zip

And they're available at http://www.apache.org/dist/spamassassin/ .

Abbreviated changelog:

- - bug 4464: Trivial doco change
- - bug 4346: Skip large messages in sa-learn
- - bug 4570: Optimize a regexp that was  blowing perl stack trying to parse
  very long headers
- - Bug 4275: Fix some incorrectly case-insensitive URL parsing regexps
- - bug 3712: more efficient parsing of messages with lots of newlines in
  header
- - bug 4065: Recognize new outlook express msgid format
- - bug 4390: Recognize URLs obfuscated using backslashes
- - bug 4439: Fix removal of markup when there are DOS newlines
- - bug 4565: new Yahoo server naming is causing FORGED_YAHOO_RCVD false
  positives
- - bug 4522: URI parsing with JIS encoding
- - bug 4655: fix redhat init script for spamd to be smarter about stopping
  processes
- - bug 4190: race condition in round-robin forking algorithm
- - bug 4535: parse mime content boundary with -- correctly
- - bug 3949: fix ALL_TRUSTED misfires

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

iD8DBQFDllKcMJF5cimLx9ARAicsAJ9scH3eWPq7rf3g2usGIPjZnf5cQQCglK8g
WdqjzNMaHzszmTI5xT8nHjk=
=aU+H
-----END PGP SIGNATURE-----

Reply via email to