SEWALL@UCONNVM.BITNET (Murph Sewall) (12/03/88)
What IS it about andrew.cmu.EDU that crashes LISTSERV's ability to parse
Sender and From lines? At first I thought the cause probably was one of
those impossibly long "names" which some folks like to use, but then I
noticed that this error occurs (without fail) on EVERY mailing from
andrew.cmu (It seems to be a FUBAR header line).
==> NOTE <== at least one message from andrew.cmu (apparently) arrived last
week with one of those "please respond directly" requests but *no sig*
(assuring no hope of response from BITNet readers).
The phenomenon occurs on more than one list too (from different LISTSERVs),
so it's not simply a mailer or LISTSERV at a particular site running amok.
As I recall, mail direct to me from andrew.edu has LOTS and LOTS of headers,
but isn't otherwise unusual (mail from Ric Nauen arrives here with lots of
headers too, so I doubt that the volume of headers alone is the problem.
-------------------------------------------------------------------------
Received: from YALEVM.YCC.YALE.EDU by UCONNVM.BITNET (Mailer X1.25) with BSMTP
id 7194; Fri, 02 Dec 88 13:57:13 EST
Received: by YALEVM (Mailer X1.24) id 3019; Fri, 02 Dec 88 13:58:06 EST
Date: Fri, 2 Dec 88 10:37:30 LCL
Reply-To: Info-Apple@BRL.MIL
Sender: INFO-APP Info-Apple List <INFO-APP@NDSUVM1>
Comments: <Parser> W: Invalid RFC822 field -- "51>; TUE,
29 NOV 88 11:". Rest of header flushed.
Comments: <Parser> E: "From:"/"Sender:" field is missing.
From: Undetermined origin c/o Postmaster <POSTMASTER@NDSUVM1>
To: Murph Sewall <SEWALL@UCONNVM>
[body of message deleted]
Ross Comer
BITNET: rc3h+@andrew.cmu.edu