To prove ownership of a Moira list ... you need to set yourself as the
memacl in the case that the ownership list is not visible; you need to
add daemon.archiver if the list itself is not visible; in some cases you
need to do both. Therefore:

- Web interface that merely attempts to blanche -i $LIST, and possibly
recursively blanche the owner list

- Script that tries (ignoring failure) to blanche $LIST -a
daemon.archiver -MA $USER, pokes the web interface, and then removes
daemon.archiver and restores the memacl

(Alternatively, instead of setting the MA, we could alter the description by doing something like adding a space to the end)

This way, if the requestor (as a USER, a KERBEROS, or as a recursive
member of a visible list) is either owner or memacl, they can admin the
list.

---

To prove ownership of a Mailman list ... you mention the list to
web interface, which confirms that it is a Mailman list, contacts
$LIST-owner with a nonce, and expects a reply with that nonce (standard
e-mail confirmation runaround). 

---

In either case you need to add $LIST-$NONCE@archiver to the mail
recipients.

---

Proving your access gives you the current a-bit over the archive, and
revokes everyone else's a-bits. All a-bits expire at 6 AM Sunday
morning (so that ownership cruft doesn't accumulate).

All other access (adding and removing admins, and adding and removing
read and delete? access) can be done over IMAP. There will be a thin web
layer to proxy requests to IMAP for people who like this.

Global spamscore threshold. Later we can make this per-list by adding an
IMAP command?

---

To use the server, point a k5IMAP client at archiver.mit.edu. You'll see
all lists you have bits on.