Hello all:
 
Sorry folks: your warnings about the loop reached our node after
23:00 (local time), and I had a meeting early this morning.
 
I have REViewed the headers from the 8 servers hosting the list MAILBOOK
and checked our keywords and entries:
 
      RICE <---> OHSTVMA <---> DEAR <---> EB0UB011
       |
       V
      UGA <---> RUTVM1 <---> CLVM
       |
       V
    CANADA01
 
 
Our list has the setting      Files = no
(so have MAILBOOK@UGA, MAILBOOK@CANADA01 and MAILBOOK@RUTVM1),
and this is probably an error.
I'm sorry if Richard has requested in the past to have it changed
to   Files = yes   (I have done so today).
 
Anyway, my guess is that this should not be the cause of the loop.
This should only inhibit file distribution (am I wrong ? ), and other
MAILBOOK lists have the same keyword setting.
Our MAILBOOK OLDLIST reveals that the list was locked (and later
stored) on 01/10/88 03:11 (by Richard himself, I suppose).
 
 
The console records registered by our LISTSERV show the following:
 
 
 PUN FILE 6922 FROM RSCS     COPY 001   NOHOLD
 14 Mar 1988 21:54:58 Processing file (6922) from LISTSERV@FINHUTC
 14 Mar 1988 21:54:59 From LISTSERV@FINHUTC: DIST FROM=LISTSERV@WVNVM ACK=None T
  MAILBOOK@EB0UB011 MAILBOOK@OHSTVMA YFERENC@ (...)
 14 Mar 1988 21:55:00 Distributing file "NETWORKS HELPMAIL" from [log in to unmask]
 .
 14 Mar 1988 21:55:01 File "NETWORKS HELPMAIL" distributed to [log in to unmask]
 14 Mar 1988 21:55:02 File "NETWORKS HELPMAIL" distributed to [log in to unmask]
 14 Mar 1988 21:55:02 End of distribution
 
 
and there are -of course- a lot of instances of the above lines.
 
 
If I can do something to help stop the loop please tell me so.
 
Best regards,  Miguel.