[Mailman-Developers] Proposed: remove address-obfuscation code from Mailman 3
barry at python.org
Mon Aug 31 23:00:10 CEST 2009
On Aug 31, 2009, at 4:48 PM, David Champion wrote:
> I'm going to embracing and extend something Barry suggested in
> private mail. He suggested a list setting that permits signed-in
> list subscribers to download raw archives if they have some
> 'archive-approved' status. What if that is a three-way switch:
> approved, unapproved, and blacklisted? New subscribers would always
> be unapproved. An unapproved subscriber who successfully posted to
> the list, clearing any approval mechanisms in place and subject to a
> list configuration option, would get approved for raw archive access.
> (Automatic posting-equals-approval would not be desirable for all
> lists, but it would for many.) An approved user could be blacklisted
> by moderator action or by an automated moderation filter. Coming off
> blacklist status would require manual action by the moderator.
> And there could be a form in the application to request approval or
> de-blacklisting, of course.
Launchpad's mailing lists have a very similar concept, although it's
not used for access to the archives. The concept there is called
"standing" and currently has four levels: excellent, good, poor, and
unknown. You start out with unknown standing, but after you prove
yourself (in much the same way as you describe above), you get to be
in good standing, which gives you other benefits, such as being able
to email a list you're not on without moderation. You can't get to
excellent standing on your own and there are currently no benefits of
excellent over good standing. Poor standing is much like your
The way I look at it is that Launchpad prototyped this concept and I
do think it could be useful in Mailman itself.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 832 bytes
Desc: This is a digitally signed message part
More information about the Mailman-Developers