Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA03291; Thu, 24 Aug 1995 12:16:25 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 24 Aug 1995 12:16:23 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from rome.software.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id MAA03280; Thu, 24 Aug 1995 12:16:20 -0400 Received: from rome.software.com ([198.17.234.100]) by rome.software.com (post.office MTA v1.7 ID# 0-10001) with ESMTP id AAA7692; Thu, 24 Aug 1995 09:15:32 -0700 X-Mailer: exmh version 1.5.3 12/28/94 To: Keith Moore cc: Eric Thomas , drums@CS.UTK.EDU Subject: Re: Getting back on track (a.k.a. Reply-To:) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 24 Aug 1995 09:15:30 -0700 From: michael.derrico@software.com (Michael D'Errico) Message-ID: <19950824161531.AAA7692@rome.software.com> Sorry for perpetuating this thread, but I just got an idea about how to solve the Reply-To problem, although it is not in the scope of DRUMS. It seems to me that the problem with Reply-To and mailing lists is that MUAs don't have a good concept of what a mailing list is. If they provided: Reply to Sender *Reply to List* Reply to All then the ambiguity of who the sender is (is it the list or the author?) goes away. Of course there is the problem of correctly identifying which messages are from mailing lists (so that the Reply-to-List button is enabled). I don't know of any active WG tackling mailing list behavior, but if there was a way to flag a message as being from a list, perhaps with a new header instead of looking for owner-* or *-request return-paths, then this could be gradually implemented and "Reply-to: the-list" headers would eventually go away. Mike