Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On 10/21/2010 9:52 AM, Charles Marcus wrote:
On 2010-10-20 8:55 PM, Barbara Duprey wrote:
In that regard, the modification of the Reply-To is, I think, more
likely to give a false sense of security than to fix the problem of
people not getting responses they would benefit from.
I totally disagree.

The only time this wouldn't work is if someone is using a mail client
taht doesn't respect the Reply-To header. As has been shown, virtually
all of the most popular mail clients in fact do respect it, so the times
that it didn't work would be the corner cases, not the norm.

However, since Florian has apparently investigated this and discovered
that the current list software cannot do this, it is a moot point... :(

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, but that header is itself duplicated in my response? 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.

--
E-mail to discuss+help@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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.