> If this was done (properly) by design, I guess "newlist" should insist
> on all-lowercase list names, though.

Just to be a pain, I'll add my $.00001 worth (advice comes cheap -- it would
be $.02 if I provided a solution).

Anyhow, RFC 822 says that the localpart of an addr-spec is comprised of
either an atom or quoted-string. 

   atom = 1+<any CHAR except specials, SPACE, and CTLs>
   specials = ()<>@,;:\".[]
   quoted-string = basically the same, but spaces allowed
                   if enclosed in quotes

That means that upper case is fine and dandy...  So the best way to
probably handle this is to allow the list to be created with mixed cases
(or all upper), but then translate this internally to lowercase for all
functions using the list name.  This way your passing the buck to the
MTA instead.

Otherwise are you guaranteed that all addresses will be translated to lower
case when they come in?  sendmail does this with any aliases, but what if
a list is running out of an account with '+' addressing instead (I know, it's
a stretch).  But forcing all addresses to be lowercase when the list is
created isn't quite RFC-compliant.

That said, I don't know why people insist on mixing case in their addresses. 
It just confuses people...

Chris