Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id FAA05462; Thu, 17 Aug 1995 05:33:16 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 17 Aug 1995 05:33:15 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from vall.dsv.su.se by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id FAA05438; Thu, 17 Aug 1995 05:33:12 -0400 Received: from ester.dsv.su.se (ester.dsv.su.se [130.237.161.10]) by vall.dsv.su.se (8.6.10/8.6.9) with SMTP id LAA24940; Thu, 17 Aug 1995 11:33:09 +0200 Received: by ester.dsv.su.se (4.1/SMI-4.1) id AA27822; Thu, 17 Aug 95 11:33:08 +0200 Date: Thu, 17 Aug 1995 11:33:07 +0200 (MET DST) From: Jacob Palme X-Sender: jpalme@ester To: Keith Moore Cc: ietf-drums , moore@CS.UTK.EDU Subject: Re: "Reply-To" In-Reply-To: <199508161751.NAA24405@wilma.cs.utk.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Aug 1995, Keith Moore wrote: > I don't think we can afford to give the sender so many options. > A reply-to header that expresses the sender's wishes is sufficient > in 95% of the cases. The other 5% of the cases will need half a > dozen different headers to satisfy them -- which won't work anyway > because they're not widely used. Things get even worse if we try > to handle the cases where the list manager also wants to specify > where replies go. I agree. Let us define "Reply-To" to handle the 95 % cases. The problem is that all do not seem to agree on which this 95 % cases are. Both you and I seem to be of the opinion that "Reply-To" is not meant to be used for rerouting of messages to the distribution list in which the replied-to message was sent. However, other people seem to be of the opinion that this is exactly what "Reply-To" is meant to be used for! ------------------------------------------------------------------------ Jacob Palme (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme