On 10/3/07, Ian Eiloart <[EMAIL PROTECTED]> wrote: > > 1. We can drop the concept altogether. > > Sounds reasonable to me.
I've used it before as a site admin to mail lists saying that the list will be closed for whatever reason (since it supports using the site password to approve stuff). Personally, I think a combination of 2, 3 & 4 - each user can set a GPG/etc key or a password they use for approving messages. Then MM would check the signature and or the Approved psuedo/header against the key/pass of the users who have high enough privileges (site admins, site staff, list admins, list moderators, etc). -- bye, pabs http://wiki.debian.org/PaulWise http://docs.indymedia.org/view/Main/PaulWise _______________________________________________ Mailman-Developers mailing list [email protected] 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
