Re: header-munging

"Randall C. Gellens" <RANDY@mpa15ab.mv.unisys.com> Wed, 07 August 1996 20:22 UTC

Received: from ietf.org by ietf.org id aa21843; 7 Aug 96 16:22 EDT
Received: from cnri by ietf.org id aa21839; 7 Aug 96 16:22 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa14418; 7 Aug 96 16:22 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id PAA05452; Wed, 7 Aug 1996 15:32:42 -0400
Received: from bbmail1.unisys.com (192-63-2005.unisys.com [192.63.200.5]) by list.cren.net (8.6.12/8.6.12) with ESMTP id PAA05439 for <ietf-smtp@LIST.CREN.NET>; Wed, 7 Aug 1996 15:32:32 -0400
Received: from mvdns1.mv.unisys.com (mvdns1.mv.unisys.com [192.59.253.100]) by bbmail1.unisys.com (8.7.3/8.6.12) with SMTP id TAA06040; Wed, 7 Aug 1996 19:32:21 GMT
Received: from MPA15AB.MV.UNISYS.COM by mvdns1.mv.unisys.com (4.1/SMI-4.1-1.8) id AA23192; Wed, 7 Aug 96 19:32:19 GMT
Message-Id: <EJIO2919FD3447@MPA15AB>
Date: Wed, 07 Aug 1996 12:29:19 -0700
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: "Randall C. Gellens" <RANDY@mpa15ab.mv.unisys.com>
To: Valdis Kletnieks <Valdis.Kletnieks%vt.edu@mv.unisys.com>
Cc: IETF SMTP <ietf-smtp%LIST.CREN.NET@mv.unisys.com>
Subject: Re: header-munging
In-Reply-To: Your message of "07 Aug 1996 11:33:39 -0400"
References: <199608071533.LAA27114@black-ice.cc.vt.edu>, <19960806213953026.AAA1272@bonn.software.com> <EJHR1635246945@MPA15AB>
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

On 07 Aug 1996 11:33:39 -0400, Valdis.Kletnieks@vt.edu wrote:

> On Tue, 06 Aug 1996 15:16:35 PDT, "Randall C. Gellens" said:
> > Examples of clients which fail to
> > produce Message-ID and/or proper Date
> > headers are everywhere, as are
> > examples of servers which munge messages
> > (often all messages) in an attempt to fix them.
>
> So what you're saying is that we should trust the people who wrote the
> broken MUAs to update them, and get *that* correct, when they can't
> get the *current* RFC's implemented correctly?

I'm saying to MUA writers who, for whatever reason, feel they can't
generate proper Message-ID, Date, or other headers, to please give the
MTA permission to fix the message.

Knowing that a message is being submitted allows an MTA to do more than
fix obviously broken headers.  It can do other replacements/editing that
may be needed for messages which go outside the company, for example.

> Sounds suspiciously like going to a mechanic, telling them "Since you
> broke the carburetor accidentally the LAST time you worked on the
> engine, I want you to replace the whole engine so it works".

If you insist on a car mechanic analogy, I think it's closer to having
the guy who is replacing the tires say "Have this car checked by an
expert -- I only do tires."

> What's wrong with this picture?

The sarcasm?



--
|Randall Gellens             |                    randy@mv.unisys.com|
|(714) 380-6350              | fax (714)597-8053 can add ,,,,,,,,6350|
|Opinions are personal;  facts are suspect;   I speak only for myself|