Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA29269; Thu, 17 Aug 1995 11:12:52 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 17 Aug 1995 11:12:47 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from SEARN.SUNET.SE by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id LAA29261; Thu, 17 Aug 1995 11:12:42 -0400 Message-Id: <199508171512.LAA29261@CS.UTK.EDU> Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R2) with BSMTP id 6811; Thu, 17 Aug 95 17:08:03 +0200 Received: from SEARN.SUNET.SE (NJE origin ERIC@SEARN) by SEARN.SUNET.SE (LMail V1.2b/1.8b) with RFC822 id 8312; Thu, 17 Aug 1995 17:08:03 +0200 Date: Thu, 17 Aug 1995 16:58:34 +0200 From: Eric Thomas Subject: Re: "Reply-To" To: Jim Conklin , Keith Moore cc: Jacob Palme , ietf-drums In-Reply-To: Message of Thu, 17 Aug 1995 01:43:52 -0400 from moore@CS.UTK.EDU On Thu, 17 Aug 1995 01:43:52 -0400 Keith Moore said: >However, lists should have a "good reason" for mucking with these >headers (and thus obscuring the Sender's identity or intent), and there >should perhaps be some advice that a list which mungs such headers >should indicate that it has so. I can guarantee that anything this group might state along these lines will be completely ignored, except for a noticeable increase in the level of flaming between a vocal minority of techies and the developers of the major mailing list packages. >Most users don't have the depth of expertise required to know why a >particular design decision makes sense. Most users find this kind of statement insulting when the design decision results in a loss of functionality. While users may not understand design decisions, they do understand gratuitous removal of functionality that has been around for years and works fine. Mailing lists have been "mucking" with headers on a large scale since at least 1986. They aren't going to stop doing that unless a clearly superior method of dealing with the issues specific to mailing lists is brought about. Simply stating that header "mucking" is Not Needed Without A Darn Good Reason doesn't provide any such superior alternative. In correct English, this discussion is a complete waste of time. Eric