Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id IAA10724; Fri, 15 Sep 1995 08:57:14 -0400
X-Resent-To: drums@CS.UTK.EDU ; Fri, 15 Sep 1995 08:57:13 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from SEARN.SUNET.SE by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id IAA10717; Fri, 15 Sep 1995 08:57:07 -0400
Message-Id: <199509151257.IAA10717@CS.UTK.EDU>
Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R2)
   with BSMTP id 1744; Fri, 15 Sep 95 14:57:11 +0200
Received: from SEARN.SUNET.SE (NJE origin ERIC@SEARN) by SEARN.SUNET.SE (LMail V1.2b/1.8b) with RFC822 id 8142; Fri, 15 Sep 1995 14:57:11 +0200
Date:        Fri, 15 Sep 1995 14:56:16 +0200
From: Eric Thomas <ERIC@SEARN.SUNET.SE>
Subject:     Re: summing up: the meaning of the reply-to header
To: Mark Crispin <MRC@Panda.COM>, "Brent B. Welch" <Brent.Welch@eng.sun.com>
cc: Keith Moore <moore@CS.UTK.EDU>, drums@CS.UTK.EDU
In-Reply-To: Message of Thu, 14 Sep 1995 18:03:44 -0700 from "Brent B. Welch"
             <Brent.Welch@eng.sun.com>

It would break  a lot of software  to suddenly require fields to  be in a
certain  order. Incidentally,  all  the MUAs  I have  ever  used put  the
Resent-* headers at the *top*.

  Eric