At 10:59 PM -0700 2006-08-14, John W. Baxter wrote:
> Unfortunately, the would-be posters then have to be notified of the message
> status. Thus, while you're reducing moderator workload, the backscatter
> problem isn't solved.
No, it's not solved. However, by putting a semi-intelligent time
limiter on the thing (i.e., no more than one response per address per
day, or somesuch), the backscatter problem is at least contained to a
more tolerable level.
And this does get back to the balance thing that I was taking about
earlier. If doing your best to make sure that people know that their
message was rejected, or held for moderation, or whatever, is more
important to you (and your community), then you've got the option to
make those sorts of things happen. If eliminating all possibility of
backscatter is more important, you've got the option to do that, too.
The point here is to increase your options available to you, and to
also try to help reduce the load on list moderators and list owners
to a more tolerable level.
At least, that's the idea. I'm hoping that the reality will live up
to this theory.
--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
Founding Individual Sponsor of LOPSA. See <http://www.lopsa.org/>.
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
