Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id GAA08600; Thu, 11 Dec 1997 06:00:40 -0500 (EST) Received: by CS.UTK.EDU (bulk_mailer v1.7); Thu, 11 Dec 1997 05:57:30 -0500 Received: by CS.UTK.EDU (cf v2.9s-UTK) id FAA08424; Thu, 11 Dec 1997 05:57:29 -0500 (EST) Received: from ester.dsv.su.se (ester.dsv.su.se [130.237.161.10]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id FAA08393; Thu, 11 Dec 1997 05:57:19 -0500 (EST) Received: from [166.49.1.63] (stat1-63.dc.ietf.org [166.49.1.63]) by ester.dsv.su.se (8.7.1/8.7.1) with ESMTP id MAA11941 for ; Thu, 11 Dec 1997 12:28:55 +0100 (MET) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 11 Dec 1997 12:30:00 +0100 To: IETF working group on revision of mail standards From: Jacob Palme Subject: New solution to the Reply-To issue I believe I have found a solution which does not have any of the major drawbacks of any of the previous solutions we have discussed on this issue. My new solution is not the very neatest solution, but it will work! Solution: Keep "Reply-To". Add both "Mail-Followup-To" and "Reply-To- Meaning", but do not include "Reply-All" in the value set for "Reply-To- Meaning". Advantages: 1. Mailing list owners can leave "Reply-To" and "Reply-To-Meaning" alone. 2. Old systems have their "Reply-To" without meaning, to do the best they can with it. 3. New systems can always see whether a "Reply-To" is of the new or the old variant: If there is a "Reply-To-Meaning", it is the new variant, otherwise it is the old variant. 4. The ambiguity of "Reply-To" is resolved by "Reply-to-Meaning". ------------------------------------------------------------------------ Jacob Palme (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme