🚀 go-pugleaf

Why are illegal mail headers being sent out by MIT-VAX?  Particularily,
the dual from line is rather annoying.
------- Forwarded Message
Return-Path: <@MIT-MC:allegra!hou3c!ka@MIT-VAX>
Received: from MIT-MC (mit-mc.arpa) by sri-tsc.arpa at Tue, 24 Apr 84 00:03:44 pst
Date: 24 Apr 1984 02:22:53-EST
From: allegra!hou3c!ka@mit-vax
Received: by allegra.UUCP (4.12/4.7)	id AA04407; Mon, 23 Apr 84 15:46:26 est
To: Header-People@MIT-MC.ARPA
Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP
From: allegra!hou3c!ka (Kenneth Almquist)
Subject: Re:  Malformed headers
Message-Id: <479@hou3c.UUCP>
Date: Fri, 20-Apr-84 18:24:10 EST
In-Reply-To: <8404201601.AA05840@wisc-crys.arpa>
Organization: Bell Labs, Holmdel, NJ

UUCP mail does not conform to RFC 822.  (Actually, no written standard
for UUCP mail exists, which is one reason for trying to phase it out.)
Context-sensitive parsing is not an "ad hoc" solution; it is a recog-
nition of this situation.

It should be possible to write mail gateway software that will leave
all the exclamation points on the UUCP side.  E. g. this mail could
be given a from line reading "From: ka@hou3c.UUCP" and a return path
reading "Return-Path: <@mit-vax.ARPA,@allegra.UUCP:ka@hou3c.UUCP>".
Alternatively, the full return path could be included in the from line
as well as the return path line.  Are either of these approaches reason-
able?  How many existing mailers will be able to reply to such letters?
				Kenneth Almquist



------- End of Forwarded Message