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

On Apr 8, 2009, at 1:01 AM, skip@pobox.com wrote:

Sorry about the rather broad distribution. A few people have inquired recently about this code.

I *think* I successfully migrated my cron/gate_news changes to the
mailman 2.2 branch. The modified mailman2.2 branch is available here:

bzr+ssh://smontanaro@bazaar.launchpad.net/%7Esmontanaro/mailman/ SpamBayes/

Probably better to use:

lp:~smontanaro/mailman/SpamBayes

and let bzr figure the rest out.

(I have no idea how these strange URLs work. You'll probably need
to snip out the "smontanaro@" bit. What you might replace it with I have no
clue or if the protocol needs to be changed.)

The cron/gate_news file has been changed to run incoming Usenet
messages through the SpamBayes classifier. There is also a spambayes.ini
file to use as a template. This simple change worked wonders on the python-list@python.org mailing list. I still see complaints about
spam from time-to-time. I think, "what spam?". When I investigate I always
find it's a user on the Usenet side of the bridge who is complaining.

There is still absolutely no training support. You will have to
wrangle that somehow else. Either the mboxtrain or tte scripts which come
with the SpamBayes distribution should do the trick if you have some
collected ham and spam. If you need some help, contact me offline or send email to spambayes@python.org.

This is very cool, thanks Skip. Let's try to coordinate to finish the
port to Mailman 3.

Barry

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAknckLcACgkQ2YZpQepbvXFVYACguHtxJ6/TCAfnRpBw/Tu3EOJP 1LcAoJud9tiXwiJhdlIPP3u0ZnBZshN0 =IhHY -----END PGP SIGNATURE-----