[Python-Dev] Proposed: change to posting rules for python-dev

Kurt B. Kaiser kbk at shore.net
Fri Jan 30 19:44:02 EST 2004

"Tim Peters" <tim.one at comcast.net> writes:

> It would, but you could subscribe and then immediately disable email
> delivery for your subscription (so you'd still be a list member, and
> so allowed to post, but wouldn't get any email from the list).

This is an excellent method that I've used for a number of lists.
For people who just want to post occasionally, this works very well, and
I don't think it's asking to much to have them subscribe.

A problem arises when people try to post from Google Groups.  There
may be some lists where we want to encourage that, and they (c.l.p)
would need to stay open.

> It depends on which posts get bounced <wink>.  I get so many spams,
> worms, etc, that I wouldn't notice the difference if python-dev
> stopped leaking them.  Presumably other people would notice.

Yeah, but you want them for the spam file  :-)

Presumably, if you turned on your Spambayes you wouldn't see any.

The real problem is the archives.  On a low volume list, like
Idle-dev, the spam completely drowns the ham unless it's moderated
out. Once in the archive, it's an annoyance for all time.

The lists are screening direct spam pretty well.  The current
problem is all the MTA bounces complaining about the "virus you sent"
or "no such user".

Moderating the lists is taking a fair amount of admin time right now.
At least during storms, it seems reasonable to bounce non-subscribers
automatically.  The bounce will tell them what to do to get posted.


More information about the Python-Dev mailing list