Re: [Mailman-Users] Mailman questions (moderation capabilities, mostly)
![](https://secure.gravatar.com/avatar/0486cf9fb94e8cec8713e1aba06f587b.jpg?s=120&d=mm&r=g)
RDB wrote:
The list is adjusted via the administrative web interface. You never need people to log into your machine simply to admin a list.
The server admin needs to log in to create new lists and configure the MTA, but once a list is built... it's all web.
This does imply that your moderators would have the ability to reconfigure the list parameters, so there is a bit more consideration than simply "are they prudent enough to moderate message content". Usually not a problem, IMO, because if they are moderating, then they're probably quite responabile and dedicated to a successful mailing list.
The moderators (list admins) require a special password to get to the admin interface. So yes... it is shielded from the public.
Cheers, -g
-- Greg Stein, http://www.lyra.org/
![](https://secure.gravatar.com/avatar/2c8c190d22516d815d1fce72874ee51c.jpg?s=120&d=mm&r=g)
At 03:07 PM 3/30/99 -0800, Greg Stein wrote: [Regarding how you actually do a preapproved list]
Totally side note... I can't think of a situation where you want to have "moderators" who are not also "admins". However, if someone really wanted to do this, they could use Apache to place further authorization requirements on the /mailman/admin/ urls, leaving the /mailman/admindb/ urls at the default state. This means that the "true admins" would need two passwords to get in to the actual admin config interface.
This is a variation on something Greg S proposed for locking down archives to admins-only; you would use the <Location> section of Apache config in both cases (and is still a cool idea).
gregc
![](https://secure.gravatar.com/avatar/2c8c190d22516d815d1fce72874ee51c.jpg?s=120&d=mm&r=g)
At 03:07 PM 3/30/99 -0800, Greg Stein wrote: [Regarding how you actually do a preapproved list]
Totally side note... I can't think of a situation where you want to have "moderators" who are not also "admins". However, if someone really wanted to do this, they could use Apache to place further authorization requirements on the /mailman/admin/ urls, leaving the /mailman/admindb/ urls at the default state. This means that the "true admins" would need two passwords to get in to the actual admin config interface.
This is a variation on something Greg S proposed for locking down archives to admins-only; you would use the <Location> section of Apache config in both cases (and is still a cool idea).
gregc
participants (2)
-
Greg Connor
-
Greg Stein