janssen@parc.xerox.com (Bill Janssen) (10/26/90)
---------- Forwarded message begins here ----------
X-Andrew-Authenticated-As: 0;holmes.parc.xerox.com;Operator
Return-Path: <halasz@xerox.com>
Received: from spade.parc.xerox.com by pooh.parc.xerox.com with SMTP
(5.61+/IDA-1.2.8/gandalf) id AA21704; Wed, 24 Oct 90 18:39:58 PDT
Received: by spade.parc.xerox.com id <274>; Wed, 24 Oct 1990 18:39:44 PDT
Received: from
Messages.7.14.N.CUILIB.3.45.SNAP.NOT.LINKED.spade.parc.xerox.com.sun4.40
via MS.5.6.spade.parc.xerox.com.sun4_40;
Wed, 24 Oct 1990 18:39:39 -0700 (PDT)
Message-Id: <0b9Y9PQB0KEOQHoIcY@spade.parc.xerox.com>
Date: Thu, 25 Oct 1990 01:39:39 PDT
Sender: Frank Halasz <halasz@parc.xerox.com>
From: Frank Halasz <halasz@parc.xerox.com>
To: janssen@parc.xerox.com, vanmelle@parc.xerox.com, briggs@parc.xerox.com
Subject: Fwd: Invalid message header (Warning)
References: <90Oct24.182458pdt.274@spade.parc.xerox.com>
Looks like Andrew generates an illegal separator character in the
References field when there is more than one reference.
This was sent using Zmailer, which is why I suppose its just coming to
our attention now.
-- Frank
---------- Forwarded message begins here ----------
Return-Path: <mailer-daemon@xerox.com>
Received: from spade.parc.xerox.com by piglet.parc.xerox.com with SMTP
(5.61+/IDA-1.2.8/gandalf) id AA24076; Wed, 24 Oct 90 18:25:10 PDT
Received: by spade.parc.xerox.com id <274>; Wed, 24 Oct 1990 18:24:58 PDT
To: Frank Halasz <halasz@parc.xerox.com>
From: The Post Office <postmaster@parc.xerox.com>
Sender: mailer-daemon@parc.xerox.com
Subject: Invalid message header (Warning)
Cc: The Post Office <postoffice@parc.xerox.com>
Message-Id: <90Oct24.182458pdt.274@spade.parc.xerox.com>
Date: Wed, 24 Oct 1990 18:24:42 PDT
A copy of your message is being returned to you because it arrived with
an illegal header according to the RFC822/976 protocol specification.
If you do not recognize the source of the bad header, perhaps you should
ask a postmaster at your site.
Your message had separate information about its recipients, so it has
been transmitted properly with a warning replacing the bad addresses.
The following annotated header(s) illustrate where the error(s) occurred:
Error in "References" header address:
<0b9XbdwB0KEO0HoEtL@spade.parc.xerox.com>,<ob9XdagB0KGW8Jae0V@holmes.parc.xero
x.com>
^-illegal reference separator
The entire original message file follows.
-----------------------------------------
to janssen@parc.xerox.com
to Frank Halasz <halasz@spade.parc.xerox.com>
Received: from
Messages.7.14.N.CUILIB.3.45.SNAP.NOT.LINKED.spade.parc.xerox.com.sun4.40
via MS.5.6.spade.parc.xerox.com.sun4_40;
Wed, 24 Oct 1990 18:24:26 -0700 (PDT)
Message-ID: <sb9Xv_sB0KEOIHoHpb@spade.parc.xerox.com>
Date: Wed, 24 Oct 1990 18:24:26 -0700 (PDT)
From: Frank Halasz <halasz@spade.parc.xerox.com>
To: Bill Janssen <janssen@parc.xerox.com>
Subject: Re:
In-Reply-To: <ob9XdagB0KGW8Jae0V@holmes.parc.xerox.com>
References: <0b9XbdwB0KEO0HoEtL@spade.parc.xerox.com>,
<ob9XdagB0KGW8Jae0V@holmes.parc.xerox.com>
Oh.
-- FrankCraig_Everhart@TRANSARC.COM (10/26/90)
I submitted a fix for this to the ITC on 7 September, and Gary immediately incorporated it into the ITC sources. The cutoff date for patch 7 was 4 September. The fix will apparently be coming out as patch 8. (It's a one-line fix, deleting the comma in the quoted string on line 155 of ams/libs/ms/reply.c .) Craig