What can we do about all the spam that the list is getting?

[srf99]

What can we do about all the spam that comp.lang.python is getting?
Things are getting pretty bad.

 

[Mensanator]

What can we do about all the spam that comp.lang.python is getting?
Things are getting pretty bad.

Buy Google and make them fix it.

 

[Mark Shroyer]

Buy Google and make them fix it.

I've had pretty good luck with MT-NewsWatcher, a freeware Mac newsreader
that performs Bayesian spam filtering. Thunderbird's Usenet reader also
offers Bayesian filtering, which presumably works just as well for
classifying Usenet spam as it does at handling email spam.

So download a "real" NNTP client for whatever platform you're on and
give its spam filter a shot; clearly Google is not interested in
fighting spam itself.

 

[Mark Shroyer]

Plonking anything posted via google.groups is the simplest
answer.

Yes, but it's hard to give him that advice with a straight face until
I've convinced him to stop using Google Groups to begin with

 

[glen stark]

When using Google Groups can one kill all posts made via Google Groups?
Presuming he has no burning need to see his own posts (something that
can't be said for everybody in the history of Usenet), it might still be
a viable approach.

The problem is, if we had followed that advice, none of us would have seen
his post.

 

[ajaksu]

What can we do about all the spam that comp.lang.python is getting?
Things are getting pretty bad.

I'm reporting most spam, but I don't have high hopes Google cares. We
could start a new group (non-usenet Google Groups allow message
removal), but I guess most people would rather simply plonk GG posts.

Perhaps we could find a way to tag spam threads that would auto-plonk
those threads in our preferred reader (email, newsreader and
Greasemonkey killfile)? This has the drawback that spam posted to ham
threads would be hard to block...

Regards,
Daniel

P.S.: I prefer posting from Google Groups, I'd rather avoid posting at
all than having to use a different client...