Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id PAA13247; Tue, 15 Aug 1995 15:56:57 -0400
X-Resent-To: drums@CS.UTK.EDU ; Tue, 15 Aug 1995 15:56:56 EDT
Errors-to: owner-drums@CS.UTK.EDU
Received: from info.cren.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id PAA13238; Tue, 15 Aug 1995 15:56:54 -0400
Received: from [192.52.179.12] (conklin-180c.cren.net [192.52.179.12]) by info.cren.net (8.6.12/8.6.4 (CREN)) with SMTP id PAA12715; Tue, 15 Aug 1995 15:55:12 -0400
Message-Id: <199508151955.PAA12715@info.cren.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 15 Aug 1995 15:57:56 +0100
To: Eric Allman <eric@CS.Berkeley.EDU>, Robert Elz <kre@munnari.oz.au>
From: conklin@info.cren.net (Jim Conklin)
Subject: Re: "Reply-To"
Cc: ietf-drums <drums@CS.UTK.EDU>

At  7:18 AM 8/15/95 -0700, Eric Allman wrote:
> I certainly
>have seen Reply-To: commonly used to indicate "please send
>replies to me only and not to the distribution list" -- that is,
>Reply-To: and From: are identical.

  At least as common (much more common in my personal experience) is its
use to force replies to go to a list instead of the From: address, a
feature that's handy for lists with inexperienced networkers whose replies
would by default go to the originator of a list message rather than to the
list as intended.  While this is a pain for experienced folks, it's
frequently considered helpful by less experienced users of lists.

Jim