>>>>> "BS" == Bill Silvert <firstname.lastname@example.org> writes:
BS> It would be nice if we could identify a core set of basic tools that a
BS> list-owner needs, and facilitate those so that the list-owner can do
BS> just a few essential things, and can let the mail server administrator
BS> handle the rest.
Unfortunately that's going to differ for every list. We can tag a set of
konfig options as 'BASIC' and set it up so that by default the owner only
sees that set unless they ask for more.
BS> it would be great if the list-owner could fire off a command
BS> moderate LISTNAME PASSWORD
Haven't we been here before? First off, no "password as second argument"
crud; "approve" is universal. Second, we already have a method to set
individual config variables:
approve password configset listname moderate = yes
Admittedly not as compact, but there's no retrieval of the config file
Now, I can't imagine that you want to have two commands for every variable
(moderate/unmoderate) that the list owner might want to set that way.
After a fashion, it gets as difficult to remember the name of the command
as it does to remember the name of the variable. Plus the list owner's
help text would be getting a bit long if you added another hundred commands
BTW, adding commands like this really is trivial if you see the need to do
it at your site.