Roger Burns writes:
 
> I'm getting an error notice which in part says that the user is served
> out.  However, if I do a SERVE <user@address> command, Listserv says the
> user has *not* been served out.  Any advice?
 
        I've frequently had a similar problem.  Recently, it was suggested
to me that the VMS interactive SEND command that I use to communicate with
UMDD comes through in all CAPS, even though I don't send it that way, and
that perhaps listserv's SERVE feature is case sensitive.  In the case Roger
Burns cited, his message to listserv was quoted in all caps:
 
>> SERVE [log in to unmask]
>[log in to unmask] had not had his access to LISTSERV suspended.
 
whereas the message explaining that there was a problem with the
envelope did not have the address all in caps:
 
> The following mail message could not be forwarded
> to MCI Mail for the following Recipients:
>
>         To: 0003791576 <[log in to unmask]>
 
        IS the serve command case sensitive?  Could this be the source of
Roger's problem?  If so, it may also explain *my* difficulties.
 
        Joan Korenman, WMST-L Listowner   KORENMAN@UMBC
        Univ. of MD. Baltimore County     [log in to unmask]
        Baltimore, Maryland 21228-5398