Apache SpamAssassin 3.2.0 released!
For those of you who missed it, we released Apache SpamAssassin 3.2.0 on May 2nd after a few RCs and a bit of pestering people to test it out. Most of the bugs people encountered in the final release were with their integration software not adhering to API requirements that haven’t changed in ages. There’s a few other bugs that will be fixed in a soon to be released (I hope) 3.2.1… nothing of major concern to most people that would prevent you from upgrading to 3.2.0 now though.
Justin Mason outlined a number of key features introduced in 3.2.0 in his posting here. Two other things I’d add off the top of my head are the support of Mail::SPF which is the current SPF reference implementation (it does away with a lot of legacy crude present in Mail::SPF::Query and generally works a lot better) and the new “whitelist_auth” option that allows a user to whitelist a sender that passes any of DKIM, DomainKeys or SPF. It’s basically whitelist_from_dkim, whitelist_from_dk and whitelist_spf all rolled into one. The benefit is that an end-user doesn’t have to know which (or keep track of changes in which) form of email auth a user/domain is using.
It looks like I was pretty close on calling the release time frame too. In this post, on September 1, 2006, I guessed at late winter or early spring. I went skiing the last week of April and we released during the first week of May. Can’t get much better than that! I just hope I didn’t delay the release on some subconscious level.
Oh, the newest release of SpamAssassin will catch more spam (than older versions) for you too. Go figure.
Add comment May 27th, 2007
