> > Mailman needs to have some sort of routine that checks against a
> > file containing already existing addresses ( anything aliased or
> > in /etc/passwd in most cases).
> 
> You can do this (somewhat) by trying a resolve on the MTA.

Unless it punts some unresolvable addresses to another host.  Our
account creation stuff (theoretically) checks against a master file
that's generated via cron containg /etc/passwd, /etc/mail/aliases*
entries and any other special case type stuff, so of course I'm
in favor of checking against a master list since it already exists
here.  :)

>   It allows a list to be created and configured, but does not
> instantiate the aliases or anything else to actually make it "live".
> 
>   At the end of the configuration/etc work, a "SUBMIT" button may be
> hit which sends an email to the mailman-owner with the URL for the
> list and the proposed aliases.  The mailman-owner than does whatever
> he wants with it (eg hand edit the aliases into
> ~mailman/data/aliases)..

Exactly.  A queue of list creation requests would be listed on a 
page with a 'deny/resolve' option (deny means I won't do it, resolve
means I just added the aliases).  Somewhat a la admindb stuff...

Hmmm...  Paul?  ;)

Chris