Well, I posted this a few days ago, and one person responded. Ive already
tried grepping our local listserv disk, and querying with wildcards.
I think it boils down to 2 possibilities.
 
(1) The subsciber is gatewaying their subscription from another listserv
    through us.
 
(2) Someone hasn't updated their bitnode tables, listserv sees we are
    a backbone server, and sends it to us to distribute.
 
Whats the best way to investigate these two possibilites.
 
PS: Ive tried trapping a note ... looking in the listserv's trash ...
    and compiled a list of about 70 lists that could be candidates
    but i don't want to rev them all, and most i would have to
    ask the listowners to do it for me since im not authorized
    to rev the list.
 
Thanks ahead of time. Eric Mann. Listserv maintainer at UIUCVMD
 ========================================================================
Return-Path: <@VMD.CSO.UIUC.EDU:[log in to unmask]>
Received: from VMD.CSO.UIUC.EDU (NJE origin LISTSERV@UIUCVMD) by
          VMD.CSO.UIUC.EDU (LMail V1.1d/1.7f) with BSMTP id 4329; Tue,
          12 Apr 1994 22:00:11 -0500
Date:         Tue, 12 Apr 1994 22:00:11 -0500
From:         BITNET list server at UIUCVMD (1.7f) <[log in to unmask]>
Subject:      Message ("Error occurred while processing file 3316 from...")
To:           Eric Mann <[log in to unmask]>
 
Error occurred while processing file 3316 from LISTSERV@UIUCVMD:
 
  Received a transferred file from myself, possibly destined to [log in to unmask]
  The destination node  ("NUACC" - assuming it is valid)  is probably not in
  the routing tables, which you might want to check.