Re: header-munging

Valdis.Kletnieks@vt.edu Wed, 07 August 1996 20:12 UTC

Received: from ietf.org by ietf.org id aa21715; 7 Aug 96 16:12 EDT
Received: from cnri by ietf.org id aa21711; 7 Aug 96 16:12 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa14269; 7 Aug 96 16:12 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id LAA00131; Wed, 7 Aug 1996 11:34:32 -0400
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71]) by list.cren.net (8.6.12/8.6.12) with ESMTP id LAA00101 for <ietf-smtp@list.cren.net>; Wed, 7 Aug 1996 11:34:20 -0400
Received: from localhost (valdis@LOCALHOST [127.0.0.1]) by black-ice.cc.vt.edu (8.7.5/8.7.3) with ESMTP id LAA27114; Wed, 7 Aug 1996 11:33:40 -0400
Message-Id: <199608071533.LAA27114@black-ice.cc.vt.edu>
Date: Wed, 07 Aug 1996 11:33:39 -0400
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Valdis.Kletnieks@vt.edu
To: "Randall C. Gellens" <RANDY@mpa15ab.mv.unisys.com>
Cc: ietf-smtp@list.cren.net
Subject: Re: header-munging
In-Reply-To: Your message of "Tue, 06 Aug 1996 15:16:35 PDT." <EJHR1635246945@MPA15AB>
References: <19960806213953026.AAA1272@bonn.software.com> <EJHR1635246945@MPA15AB>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="===_-1_Wed_Aug__7_11:33:38_EDT_1996"; micalc="pgp-md5"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
X-Mailer: exmh version 1.6.7 5/3/96
X-Url: http://black-ice.cc.vt.edu/~valdis/
X-Listprocessor-Version: 8.0 -- ListProcessor(tm) by CREN

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?

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".

What's wrong with this picture?
-- 
				Valdis Kletnieks
				Computer Systems Engineer
				Virginia Tech