In article <[log in to unmask]>, you say:
>
>A recent subscription to SCIFRAUD@ALBNYVM1 resulted in the following
>acknowledgement (quoted in part):
>...
>Dear networker,
>
>  As of Wednesday, March  the 6th of 1991, you have been  added to the
>LISTSERV
>distribution   list   SCIFRAUD   (Discussion    of   Fraud   in   Science)
>by
>"[log in to unmask] Vincent Cate" <ACH13@ALBNYVMS>.
>...
>The string "[log in to unmask]" appears nowhere in SCIFRAUD LIST.  However, in
>SIGNUP FILE, there is the entry
>
>ACH13@ALBNYVMS [log in to unmask] Vincent Cate
>
>so it must have been there that LISTSERV picked up the name.
>
>1.  How did it get there?
   I can answer this!  I've done it myself a few times.  This happens when
an owner types SUB instead of ADD.  The clue is that the address is part
of the name now.  In other words:
   Instead of   TELL LISTSERV ADD SCIFRAUD [log in to unmask] Vincent Cate
the owner types TELL LISTSERV SUB SCIFRAUD [log in to unmask] Vincent Cate
   Of course                  SUB listname username
is the form and LISTSERV takes the owner's address as the one to use.
   It is easy to correct.  Just do an ADD or SUB for the aflicted owner
with the correct name.  Then do an ADD for the original user that got
missed!
          Ed.  TELL LISTSERV ADD SCIFRAUD ACH13@ALBNYVMS owner name
               TELL LISTSERV ADD SCIFRAUD [log in to unmask] Vincent Cate
 
>2.  Why is LISTSERV taking the owner's name from there instead of the more
>authoritative SCIFRAUD LIST?
 
    Eric will have to answer this.  It may either be a feature or have to do
with efficiency...    Marty