Message-Id: <199803271003.FAA01724@lust.cs.utk.edu>
From: Keith Moore <moore@cs.utk.edu>
To: "Woodhouse, Gregory J." <gregory.woodhouse@med.va.gov>
cc: Detailed Revision/Update of Message Standards <drums@cs.utk.edu>,
        "'Chris Newman'" <Chris.Newman@innosoft.com>, moore@lust.cs.utk.edu
Subject: Re: A simple proposal: Reply-To-Complete 
In-reply-to: Your message of "Thu, 26 Mar 1998 11:11:07 CST."
             <2107E82D78C2D1118A340000F8033450BFA0@VHAISFEXC1> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 27 Mar 1998 05:03:50 -0500
Sender: moore@cs.utk.edu

> I like this idea, though I'm not sure I understand how it is intnded to
> work. Suppose you have a message with a header which includes
> 
> From: person-1
> To: person-2
> Cc: list-1
> Include-Author-On-Group-Reply: no
> 
> Now, let's suppose both person-1 and person-2 are members of list-1
> (perhaps person-1 didn't know person-2 was a member of list-1 and so
> included both him/her and the list as recipients). A reply would then go
> to list-1 and person-2, but not person-1. There would still be a
> duplicate.
> 
> This is an impovement, but it doesn't really solve the problem. 

Suppose you have two aliases, A and B, and for some reason I send a
message to both of those addresses.  Unless your MUA or message store
does duplicate suppression, you'll get two copies of the message.  My
MUA cannot eliminate the duplicate because there's no way for my MUA
to know that A and B are equivalent.

But while Include-Author-On-Group-Reply cannot eliminate all
duplicates, it can eliminate one of the primary sources of duplicates.

Note that this is much the same as

Dont-cc-author-when-replying-to:<address>

except that the latter works even if the reply is not a "group"
reply... e.g.  even if the responder decides to reply only to some
manually chosen subset of the recipients.

Keith