From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Reply-to munging
Date: Mon, 02 Jul 2007 15:55:56 -0400 [thread overview]
Message-ID: <4689584C.4030500@cfl.rr.com> (raw)
In-Reply-To: <20070620144458.GH25016@agk.fab.redhat.com>
Alasdair G Kergon wrote:
> And here are some counter-arguments:
> http://www.metasystema.net/essays/reply-to.mhtml
And they would be wrong:
> The Principle of Minimal Bandwidth
I don't see how forcing a reply that otherwise was intended to go only
to one recipient to be sent out to the entire list saves bandwidth.
> Reply-To Munging Adds Something
No, it does not; it takes away something. If you want to reply publicly
then you use reply-to-all. It is up to the SENDER to set their
Reply-To: header if they do NOT want a reply going to them as well as
the list. They should make that choice, not the replier. Users also
are supposed to be able to use Reply-To: to direct replies to the
correct sender in the event that they forward a message on someone
else's behalf. Thirdly, munging the header breaks the reply
functionality of the client by making it behave like reply-to-all.
> It Doesn't Break Reasonable Mailers
Yes, it does. This argument boils down to "Breaking the reply function
isn't really breaking it because some mailers have added a
reply-ignoring-broken-munged-reply-to function that you can use
instead". If the headers weren't munged in the first place this option
would not be needed.
> Freedom of Choice
This one could not be more of a bold faced lie. The only "freedom" it
adds is the replier's freedom to take away the freedom of the sender and
force a reply only to the list despite their wishes otherwise, as
reflected by the reply-to: header they did or did not set.
> Some Mailers are Broken
Same fallacious argument as "It Doesn't Break Reasonable Mailers". It
is mailing lists that munge that are broken, not clients that have not
added a 3rd reply option specifically to deal with such broken lists.
> Principle of Least Total Work
Again, it is up to the poster to decide if they want a reply directly to
them, or only to the list, not the replier. If they want their own
reply, then give it to them.
> People are Responsible for Their Own Mistakes
This item simply dismisses the principal of least surprise in favor of
codling the ignorant. User mistakes are no longer their fault when your
mailing list causes an unexpected change in the behavior of their mailer.
next prev parent reply other threads:[~2007-07-02 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 22:02 Reply-to munging Phillip Susi
2007-06-20 14:44 ` Alasdair G Kergon
2007-07-02 19:55 ` Phillip Susi [this message]
2007-07-02 20:48 ` Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4689584C.4030500@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox