From owner-freebsd-bugs  Mon Jan 13 15:10:05 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA13750
          for bugs-outgoing; Mon, 13 Jan 1997 15:10:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA13741;
          Mon, 13 Jan 1997 15:10:02 -0800 (PST)
Date: Mon, 13 Jan 1997 15:10:02 -0800 (PST)
Message-Id: <199701132310.PAA13741@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: misc/2481: Gnats creates malformed Resent-Reply-To: headers
Reply-To: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR misc/2481; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: fenner@parc.xerox.com, joerg_wunsch@uriah.heep.sax.de
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: misc/2481: Gnats creates malformed Resent-Reply-To: headers
Date: Mon, 13 Jan 1997 15:02:10 PST

 >I think it should also preserve the Reply-To header literally for
 >followups if one was present.
 
 Only because most MUA's don't grok Resent-* at all.  RFC822 says that
 Resent-* fields, if present, are to be treated as "more recent" than
 the original versions.  It carefully avoids specifying which fields
 to use when replying, so we can't claim that MUA's that skip
 Resent-Reply-To are violating anything, but the Resent-* fields are
 there so that forwarders don't have to modify existing fields...
 
 (Perhaps the easiest solution is to stop using Resent-* because of
 its ambiguous semantics to MUA's...)
 
   Bill