From: Glynn Clements <glynn@gclements.plus.com>
To: Herta Van den Eynde <herta.vandeneynde@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Fwd: wrong default route
Date: Tue, 8 Jul 2008 22:09:30 +0100 [thread overview]
Message-ID: <18547.55178.673887.918601@cerise.gclements.plus.com> (raw)
In-Reply-To: <fff5b0760807081327q1d1ebe64w6ec512a30b7e0636@mail.gmail.com>
Herta Van den Eynde wrote:
> Apologies for using "Reply" instead of "Reply to all". I'm used to
> mailinglists putting the mailinglist's address in the reply-to field.
> Any reason why this mailing list does not do that?
Because the Reply-To header "belongs" to the author.
Occasionally, it may be desirable to post private replies, and
"stealing" the Reply-To header prevents that (mail clients won't let
you reply to the From address if a Reply-To header exists).
Not only does a forced Reply-To header prevent the message from being
sent directly to the user, but will cause it to be sent to a public
mailing list instead. If the reply was intending to be private, the
message may well contain information which shouldn't be made public.
The author can always choose to add their own Reply-To header if they
never want to receive off-list replies.
Having the mailing list set its own Reply-To header is a workaround
for "non-technical" lists, where many of the subscribers may not
understand the difference between "reply" and "follow-up".
Presumably the vger admins (naïvely) assumed that a list targeted to
Linux sysadmins doesn't need such workarounds.
--
Glynn Clements <glynn@gclements.plus.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-08 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 14:21 new member - test post Jake Ravenwood
2008-07-08 14:25 ` wrong default route Jake Ravenwood
[not found] ` <fff5b0760807080803w6b7b5f44l42a096b7ca2d8d61@mail.gmail.com>
2008-07-08 20:27 ` Fwd: " Herta Van den Eynde
2008-07-08 21:09 ` Glynn Clements [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 15:24 Jake Ravenwood
[not found] ` <fff5b0760807080833k3680d1cbk8c8fcb02c9c83b45@mail.gmail.com>
2008-07-08 20:27 ` Fwd: " Herta Van den Eynde
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=18547.55178.673887.918601@cerise.gclements.plus.com \
--to=glynn@gclements.plus.com \
--cc=herta.vandeneynde@gmail.com \
--cc=linux-admin@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).