Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA19597; Tue, 15 Aug 1995 11:01:02 -0400 X-Resent-To: drums@CS.UTK.EDU ; Tue, 15 Aug 1995 11:01:01 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from panix4.panix.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id LAA19582; Tue, 15 Aug 1995 11:00:58 -0400 Received: from panix2.panix.com (panix2.panix.com [198.7.0.3]) by panix4.panix.com (8.6.12/8.6.12+PanixU1.1) with SMTP id LAA20031; Tue, 15 Aug 1995 11:00:36 -0400 Message-Id: <199508151500.LAA20031@panix4.panix.com> To: Eric Allman cc: Robert Elz , ietf-drums Subject: Re: "Reply-To" In-reply-to: Your message of "Tue, 15 Aug 1995 07:18:44 PDT." <199508151418.HAA07478@mastodon.CS.Berkeley.EDU> Reply-To: perry@piermont.com X-Reposting-Policy: redistribute only with permission Date: Tue, 15 Aug 1995 11:00:34 -0400 From: "Perry E. Metzger" Eric Allman writes: > I have to agree with Robert's logic here -- I had forgotten that > From: is settable (and can even be multi-valued). 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. In fact, this is probably > the single most useful purpose for the header. Not to quibble, but there is another very useful purpose: those of us who have lots of places we send mail from but only one we get it delivered to tend to use Reply-To: for the purpose of pointing our mail at one spot and not to indicate "please only send me the reply". I've been using it as such for years now and it seems to have always worked. (This very message is being sent by way of Panix, an ISP in NYC, but has a Reply-to: perry@piermont.com on it.) .pm