On 10/21/2010 9:51 PM, Charles Marcus wrote:
On 10/21/2010 5:18 PM, Barbara Duprey wrote:
I'd just like to make sure I'm clear on this, OK? If I get a message
with a Reply-To header, and respond to it using Reply, not only does the
response go to those in the Reply-To header,
Yes it goes to everyone in the Reply-To header...
but that header is itself duplicated in my response?
Egads, no! Why would you think that?
It goes to the list and to the OP with whatever you have set for your
Reply-To for this account (usually blank)...
I didn't -- but for the Reply-To addressing to carry through the thread it would have to. That's
what I was saying before would cause the false sense of security, and you disagreed.
And the Reply-To header is also carried through if I use Reply All?
That header inheritance is the part I didn't think was necessarily
happening.
I'd have to experiment with how it behaves with a Reply-To when Reply
All is clicked... I imagine some clients may behave differently...
I didn't say it would be perfect, but at least any responses to the OP's
initial question would go to both the list and the OP (if the Reply-To
is set properly.
And yes, you can set this manually if you like...
OK, then I'm back to my initial position -- since informative responses can easily come deeper in
the thread, this technique (even if it were supported by the list manager capabilities) would lead
to such responses failing to reach the OP without additional action by the responder. However, if
the OP is given information about use of nabble, say (either by the moderator supplying general
instructions, or a list member supplying a specific link to the thread), then the OP has access to
*all* responses and no cc'ing would ever be required. This possibility is supported even with no
changes made through the list manager.
--
E-mail to discuss+h...@documentfoundation.org for instructions on how to
unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be
deleted
