Am 16.01.2013 20:52, schrieb Cor Bosman:
On Jan 16, 2013, at 3:38 PM, Michael Heydekamp listuser@freexp.de wrote:
Am 16.01.2013 12:42, schrieb Cor Bosman:
The response will only go to michael, and not to the list unless you do reply-all.
But then it still doesn't go "michael", THAT's the issue.
Right next to the Reply-All button, there is a small carrot pointing down. If you select that, and then "Reply-All" you will reply to both.
That does work on Philip Rhoades' message, it doesn't work on mine (scenario 1.2). Probably because RC eliminates any recipient address which is identical with the sender's address.
But anyway, this can't be the solution:
- Most users are used to simply click on the Reply button, as they can
expect that a "Reply-To:" header will be respected. They can't know that this isn't (always) the case in Roundcube. And even if they would know it (and if they would be aware of the logic): They can't even see the "Mail-Reply-To:" header, unless they would take a look into the source of the message.
So shall we now always need to load the message source first, before we can decide which button we need to use?
- Even if you are used to use the Reply-all button by just clicking on it,
you still don't reply to all. That's even more strange. By clicking this button, I already stated that I want to reply to all addresses, why do I need to emphasize it again (and even more) by selecting one of two choices?
- To get the idea, that you need to use this or that button/option, you
have to be aware of the existence of all headers (here: "Mail-Reply-To:") and their two-way implication. This can only be achieved by looking into the message source upon every reply.
Sorry, but this is not what you can expect from an average user. And not even from me (I can of course do it, but I don't want to do it).
Thanks for your other comments, I'll look closely into them.
But as a still general guideline, "Reply-To:" is "Reply-To:" and it is RFC-wise meant as such. To completely ignore it, is IMO not the right way to go.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany