>        Does anyone know if it is possible to have one LISTSERV LIST use
>two names?  For example, if I own a list called EVENS-L then people can
>subscribe and post to [log in to unmask]  However, people often send to
>EVANS-L@ASUACAD by mistake.  Is there any way to have one list respond to
>both of these addresses?
 
>I believe so: by use of the list's definition keyword LIST-ID=
>Caveat emptor!
 
Here's a more complete description, based on *one* attempt (which
worked):
 
In the header of the list (whose primary name is EVENS-L), set the
keyword:
 
* List-Id= EVANS-L
 
[Although this is not applicable in your case, note that List-Id is not
limited to 8 characters on VM systems, so this is also a way of having
a more descriptive list address.]
 
However, you should probably also want to set the keyword List-Address,
which allows you to select which of the two addresses (primary or the
List-Id alias) you want to be the "visible" one, i.e., the one that will
show up in the Sender/To/Reply-To fields.  In your case, EVANS-L is a
mis-spelling that you don't want to perpetuate, so you would add the
line
 
* List-Address= Listname
 
so that EVENS-L would continue to be the visible address
(the other option here would be *List-Address= List-Id
which would make EVANS-L the visible address--there are also other
parameters that also let you specify different formats for the domain
portion of the address).
 
This takes effect only "overnight"; presumably some scheduled job runs
that updates all the mailer aliases based on changes to List-Id's and
the like.  If this did NOT take effect overnight then see the attached
excerpt from Eric Thomas on the likely reason (which your listserv
maintainer will probably have to fix).
 
Shahrukh Merchant
[log in to unmask]
================================================================
>Date:         Thu, 9 Feb 1995 20:46:54 +0100
>From: Eric Thomas <[log in to unmask]>
>Subject:      Re: List-ID= doesn't seem to work
>
>With the  versions that require  an overnight  wait, you are  supposed to
>have a  daily call  to one "LSVLDELT"  in the WAKEPARM  FILE. If  for any
>reason this call  has been removed, the list never  "matures". In 1.8b or
>even FIX18AX2  the "maturing" business is  gone and the LSVLDELT  call is
>done internally, removing the opportunity to delete it accidentally :-)
>
>  Eric