Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu> schrieb/wrote:
Or to put it another way: MUAs really need a "reply author" button,
but they don't have one. The typical "reply" button doesn't quite
work like it should because the "narrow reply" really doesn't map to
what the recipient is likely to want to do.
(The only time I ever use (narrow) "reply" is when I really want
"reply to author".
Granted, there are very few cases when a "narrow reply" is not a "reply
to the from address". But there are examples:
. The more common case is where Reply-To is an alternative address for
the author. You could use this address in From, too, but some
environments (MUA, ISP, whatever) unfortunatly don't allow this.
| From: jdoe(_at_)homeprovider(_dot_)example(_dot_)net
| To: discusss(_at_)lists(_dot_)example(_dot_)com
| Reply-To: john(_dot_)doe(_at_)example(_dot_)com
| Mail-Followup-To: discuss(_at_)lists(_dot_)example(_dot_)com
Whether we like it or not, this use is quite common.
. The author is actually writing on behalf of a different person or
a group of persons. In this case, "narrow replies" often should be
direct not to the author but to the person(s) on behalf of which the
message was written.
| From: john(_dot_)doe(_at_)example(_dot_)com
| To: discusss(_at_)lists(_dot_)example(_dot_)com,
announce(_at_)lists(_dot_)example(_dot_)com
| Reply-To: info(_at_)example(_dot_)com
| Mail-Followup-To: discuss(_at_)lists(_dot_)example(_dot_)com
| From: john(_dot_)doe(_at_)example(_dot_)com
| To: discusss(_at_)lists(_dot_)example(_dot_)com,
announce(_at_)lists(_dot_)example(_dot_)com
| CC: big(_dot_)boss(_at_)example(_dot_)com
| Reply-To: big(_dot_)boss(_at_)example(_dot_)com
| Mail-Followup-To: discuss(_at_)lists(_dot_)example(_dot_)com
Claus
--
http://www.faerber.muc.de