Does anybody know why LISTSERV occasionally does this to peered lists?
If it's understood, what's the cure?  (It doesn't happen all the time,
just maybe once every few weeks)
 
                                   Valdis Kletnieks
 
Here's the mail as it came across:
 
Received: from VTVM1 by vtvm1.cc.vt.edu (Mailer R2.05) with BSMTP id 3533; Mon,
 05 Mar 90 11:04:35 EST
Received: from CUNYVM.CUNY.EDU by VTVM1.CC.VT.EDU (IBM VM SMTP R1.2.1MX) with
 TCP; Mon, 05 Mar 90 11:04:32 EST
Received: from CUNYVM.BITNET by CUNYVM.CUNY.EDU (IBM VM SMTP R1.2.2MX) with
 BSMTP id 2830; Mon, 05 Mar 90 11:03:27 EST
Received: from CUNYVM.BITNET by CUNYVM.BITNET (Mailer R2.03B) with BSMTP id
 8647; Mon, 05 Mar 90 10:54:44 EST
Date:         Mon, 5 Mar 90 10:54:46 EST
Reply-To:     IBM TCP/IP For VM List <[log in to unmask]>
Sender:       IBM TCP/IP For VM List <[log in to unmask]>
From:         "1.6d Revised List Processor"
 <[log in to unmask]>
Subject:      Output of your job "IBMTCP-L"
To:           Multiple recipients of list IBMTCP-L <IBMTCP-L@CUNYVM>
 
> Hi,
Unknown command -- "HI,". Try HELP.
 
All subsequent commands have been flushed.
 
Summary of resource utilization
-------------------------------
 CPU time:        0.10 sec                 Device I/O:     8
 Overhead CPU:    0.01 sec                 Paging I/O:     3
 CPU model:       3090                     DASD model:  3380