Marc Shannon found  a problem in LISTSERV's handling  of 'command' mailfiles:
when he sends mail  to [log in to unmask] (== listserv@cmuccvma), LISTSERV
replies with a mailfile saying "List te.cc.cm does not exist" (the message came
from [log in to unmask]). The reason for this  is that LISTSERV does not "know"
that CMUCCVMA == vma.cc.cmu.edu, and the  mail file is therefore not treated as
a command. It is therefore supposed to be a normal mailing file, and the corres
ponding (and truncated) list does not  exist, of course. The listname is picked
from the list,  where it has been  put by LSVPROF before  transferring the file
from the list userid. Now a reply  of "List (distcode) does not exist" seems to
be very unfriendly... Why don't I pick the listname from the "To:" header? Just
because of those darned mailing from ARPAland which do not have the destination
userid in the  "To:" field, when they  have a "To:" field at  all... *sigh* You
get a mess commensurate with the protocol you've chosen (RFC822) :-(
 
  Eric