I think  it is  simply a  matter of doing  whatever is  best for  the end
users. If  this Unix list  server is not going  to have the  same command
syntax  as the  BITNET one  (and  judging from  the help  file, the  only
compatible commands  so far are  HELP and LISTS :-)  ), it should  have a
different name in order to avoid  confusing the users. I don't think it's
in the interest of anybody to  have these Unix servers receive and reject
tons of  SUBSCRIBE, REVIEW, SIGNOFF et  al: it will just  waste bandwidth
and CPU time - and make the users angry.
 
If  on the  other hand  the author  is willing  to change  the syntax  to
conform  to  that of  LISTSERV  and  can commit  enough  of  his time  to
implement a larger subset of the  LISTSERV functions into his server, the
name should probably remain as it is. Note that I am not trying to impose
the syntax of  my software or to stifle the  creativity or imagination of
its author; I am  merely stating, once more, that it  is not desirable to
have the  new software known under  the name of "LISTSERV"  if it behaves
differently enough to confuse the users.
 
  Eric