On Tue, Dec 7, 2010 at 3:22 AM, Rimas Kudelis <rq@akl.lt> wrote:
2010.12.07 10:01, Daniel Faber rašė:
> On 05.12.2010 21:10, Rimas Kudelis wrote:
>
>> I find this extremely unnecessary and confusing to have both links –
>> "Add Reply-To" and "Add Mail-Reply-To" – in the compose page. If
>> Roundcube developers believe in Mail-Reply-To's usefullness, then a
>> single link (Add Reply address) should simply add both headers. If you
>> don't believe in this header, or think this should be up to somebody
>> (admin or user) to decide, then either remove it, or make it an option
>> (either in the config file or in the interface). But don't just drop
>> both of these headers on users and expect them to do what's right,
>> because most of them will not.
> I agree that having both Reply-To and Mail-Reply-To will confuse most users.
>
> -1 for "a single link [...] should simply add both headers"
> This is not transparent and will do the wrong thing in some cases.
>
> +1 for make it configurable (and disabled by default) if Mail-Reply-To
> is shown.  Reply-To should always be available since it's the most
> common of these headers.

My point was that both headers are designated to do the same, so what's
the point to let the user add one and not add the other? What cases do
you have in mind where this would produce undesired results?

And specifically to avoid confusion, I suggested renaming using wording
like "Add Reply Address" instead of "Add $Header-Name".


"Send replies to:" 

And amusing sidenote: Gmail defaults to sending replies to this list to the original sender.  Thunderbird defaults to sending to the list.

I have yet to truly get which does which, so I accidentally sent this directly to Rimas originally.....  Yet one more reason to get RCD setup and running for my future email usage - then I can have an offline/online email reader where *I* get to tell it how to behave[since I can code PHP and change it to do what I want]