Siegfried Schmitt <[log in to unmask]> says:
 
>I don't know exactly, but it might be sufficient to include the
>line
>
>   List-Id = NAME
>
>in your list header. This does of course not set up an automatic
>notification, but users will be able to subscribe to both NAME and
>NAME-L.
 
I should have been more specific in my original post, but the postmaster
of the site specifically does not want NAME@HOST to be a valid address
(owing to the aforementioned address conflict), only [log in to unmask]
However, we would like to arrange it so that a *command* to LISTSERV
(specifically a SUBSCRIBE command) would be recognized, but only to send
the pre-recorded message.
 
Thanks.
 
Shahrukh Merchant
 
================ My original request (part):
 
> One of our listserv lists needed to change from NAME to NAME-L (to avoid
> a name conflict with a user, since some domains were being merged).  Of
> course, subscription requests continue to arrive for the old name.
> As of now, all that happens is that the potential subscriber gets a
> message saying that there is no knowledge of list NAME, and the request
> is being forwarded to the nearest gateway (UGA, which, of course, says
> the same thing).  The result is that potential subscribers are lost.