While the RFC 822 header in this case is definitely wrong (it was
left in that state by a DECnet gateway), it seems like LISTSERV
is overreacting somewhat by refusing to process the message.
It did, after all, arrive in LISTSERV's mailbox.  Also, the <W>
suggested to me a warning, leading me to believe that the error
had been noted and ignored.  In fact, the unsubscribe command
was not processed.
 
== Forwarded Mail ==
 
Received: from LIST.NIH.GOV by NIHCU (Mailer) id 1277;
              Tue, 10 Jan 95  08:51:55 EST
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id
 1276; Tue, 10 Jan 95 08:50:34 EST
Date:         Tue, 10 Jan 1995 08:50:34 -0500
From:         BITNET list server at NIHLIST (1.8a) <[log in to unmask]>
Subject:      Problem processing mail file from $MAILER@NIHLIST
To:           [log in to unmask],
              Roger Fajman <[log in to unmask]>,
              Tom Mason <[log in to unmask]>
 
Error occurred while processing file 1269 from $MAILER@NIHLIST: "Command
mailfile contains invalid RFC822 fields and could not be parsed".
 
RFC822 parser messages follow:
 
<W> Incorrect or incomplete address field found and ignored.
 
------------------- Message causing the problem (11 lines) --------------------
Received: from NIHLIST by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id
 1268; Tue, 10 Jan 95 08:50:22 EST
Received: from dxi.nih.gov by LIST.NIH.GOV (IBM VM SMTP V2R2) with TCP;
   Tue, 10 Jan 95 08:50:20 EST
Date: Tue, 10 Jan 95 08:49:09 -0500
Message-Id: <[log in to unmask]>
From: [log in to unmask]
To: dxi::"[log in to unmask]"
Subject: UNSUBSCRIBE CURE
 
UNSUBSCRIBE CURE