Mailing lists at MIT come in two varieties --- Moira and Mailman. Moira lists don't have spam filtering, moderation, built-in archiving, or a number of other features. Mailman has far more features, but mostly requires administration through a web interface (which many people dislike) and Mailman lists cannot be used for access control (in AFS, or to own other lists).
Mailman lists can be administered through the Mailman web interface.
For people uncomfortable with the command line, the standard tool for Moira list management is Webmoira. It's reasonably straightforward and has decent built-in help. It doesn't support membership ACLs, though (which allow giving somebody permission to modify a list's membership but nothing else about it).
At the command line, the usual list management tool is
blanche listname to view the members of
blanche listname -i to see the owner, description, and various other pieces of useful information. Use
man blanche to see additional documentation.
Ordinarily, you would use one of the clients above to work with Moira. Behind the scenes, they all make certain "queries" to moira to get and set information. In some cases, it may be useful to make those queries directly, for example because none of the clients expose it.
mrtest command lets you connect to Moira and make queries.
qy command in the
ops locker is a thin wrapper over
mrtest that automatically connects, authenticates, and then runs a specified query.
To find the available queries, you can run
qy _list_queries. Most queries have a long name and a four letter abbreviation. To see what parameters a query takes, use
qy _help query-name.
Many queries will return a large number of records. To display only certain fields, use
-f field1,field2,.... To display all fields on one line, use
Most list queries are more convenient to make using
blanche. Two big exceptions are
glom). The former allows you to see what objects (lists, machines, filesystems, etc.) in Moira an object (list, user, etc.) controls. The latter allows you to what lists an object is on.
You can use them like
qy gaus rlist sipb-acl. That finds what objects the list (
list) sipb-acl (
sipb-acl) can recursively (
r) administer (
gaus). The third argument (
sipb-acl) should be the name of the object that you're trying to examine. The second argument (
list) is in two parts. The second part should indicate what type of object the third argument is ---
kerberos. That can be prefixed with
r to indicate that we're interested in control via another list, or left alone to indicate that we only care about direct ownership. Finally, the first argument should be the query (
gaus to what something controls or `glom' to find what lists something is on).