|
From: | Carl Peterson |
Subject: | Re: mea máxima culpa |
Date: | Thu, 12 Sep 2013 15:03:15 -0400 |
Not sure about that. The information usually is available in theheaders, and as far as I can tell, Gmail does preserve and maintain it
as well. So unless someone "breaks the chain", it would seem like a
poor choice not to actually use it.
>> Don't use "Reply to sender" if you don't want to reply to the sender.Poor choice of user interface then.
>
>
> (1) 99% of the time, if I'm replying to a message, I'm intending to
> reply to the list. Defaults are usually selected to in some way
> minimize effort, which brings me to (2), I'm lazy. Reply all requires
> extra mouse-clicks.
Not really. I was suggesting _adding_ a Reply-To header, but one that
>> > As a matter of consistency, I think both the individual messages
>> > and the digest should reply to the list, or neither.
>>
>> Do you mean to imply that the digest _does_ add an explicit Reply-To:
>> header and it goes to the list? That would indeed be on the less
>> than sane side.
>
> I have no idea what the digest does or doesn't do. I am replying to
> your prior statement, "Maybe the reply-to header of the digest should
> not even point to the list?" As Tim pointed out, the non-digest
> messages do not and your proposal would be logically consistent with
> that.
does not go back to the list.
As I said, replies from a digest rarely make sense because of breaking
> I am simply stating a preference for the reply-to of both to do so.
the message threading.
[Prev in Thread] | Current Thread | [Next in Thread] |