Just FYI: SpamAssassin 3.1.7 was released on 10th of October. :-) It's a maintenance release containing only one bugfix. From the release announcement (http://www.nabble.com/ANNOUNCE%3A-Apache-SpamAssassin-3.1.7-available%21-tf2415849.html): --- 3.1.7 is a "quick-fix" release; it contains only a fix for one bug, introduced accidentally in 3.1.6: - bug 5119: if admins had set rule scores in the site configuration in /etc, sa-update would fail. Back out this change ---
Ok, I'm testing out this latest user-contributed layman stanza. :-) Get it while it's fresh: layman -o -f http://jaba.mbnet.fi/portage/layman-jmf.xml -a jaba
I'm using SA 3.1.3 because my systems use the "stable" tree. I need to use a recent version of FuzzyOcr (a SA plugin) which requires at least 3.1.4. Unfortunately, there are too many reports of problems with SA versions previous to 3.1.7, so the best thing would be to use 3.1.7. I would like to push the inclusion of SA 3.1.7 in the portage tree. Thanks.
For some reason i never got the announce email this last go around (and obviously missed this bug). sa has been bumped in the tree. as far as stable requests go, ask your arch of choice to stable it ;)
