ietf-822
[Top] [All Lists]

Re: Understanding response protocols

2004-09-18 13:47:01

Hallo,

Bruce Lilly <blilly(_at_)erols(_dot_)com> schrieb/wrote:
Claus Färber wrote:
Further, it does not allow something like this:
| From: jdoe(_at_)example(_dot_)com
| To: product-announce(_at_)list(_dot_)example(_dot_)com, 
product-discuss(_at_)list(_dot_)example(_dot_)com
| Reply-To: info(_at_)example(_dot_)coom
| Mail-Followup-To: product-discuss(_at_)list(_dot_)example(_dot_)com

"No, it does not work with existing UAs." Most UAs ignore illegal
fields such as "Mail-Followup-To".

When discussing a new potential standard, it does not make sense to
slanderously refer to proposed fields as "illegal". They field is
currently undefined but the idea of introducing a new spec is to change  
that.

And the following achieves what I believe you intended using only
standard header fields, with (as discussed) the From field for
narrow responses, Reply-To for default responses, and a user-edited
selection from all addresses for a wide response:

From: info(_at_)example(_dot_)com
Sender: jdoe(_at_)example(_dot_)com
To: product-announce(_at_)list(_dot_)example(_dot_)com, 
product-discuss(_at_)list(_dot_)example(_dot_)com
Reply-To: product-discuss(_at_)list(_dot_)example(_dot_)com

A user agent following established practice will send narrow replies to
"product-discuss(_at_)list(_dot_)example(_dot_)com" (Reply-To) and broad 
replies to
"produxt-announce(_at_)list(_dot_)example(_dot_)com, 
product-discuss(_at_)list(_dot_)example(_dot_)com"  
(To, Reply-To), which is also wrong.


                      | narrow replies       |  broad replies
                      | w/ leagacy software  |  w/ leagacy software
----------------------+----------------------+-----------------------
From/Reply-To +       | Reply-To (correct)   |  To (maybe correct)
Mail-Followup-To      |                      |  Reply-To (wrong)
----------------------+----------------------+------------------------
Sender/From +         | Reply-To (wrong)     |  Reply-To (correct)
Reply-To              |                      |  To (wrong)

IOW: Both solutions are not backwards-compatible wrt broad replies but
your proposal (it's not the existing standard because it adds additional
semantics to the existing header fields) also breaks narrow replies (and
Mail<->Netnews gateways).

Please note that you can't put two addresses in the From field either,  
in case that the message has been jointly written by two authors (e.g.  
"jdoe(_at_)example(_dot_)com" and "jane(_at_)example(_dot_)org").

Claus