From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] mailinglists in CC
Date: Thu, 19 Aug 2010 15:49:21 +0300 [thread overview]
Message-ID: <1282221210-sup-5773@tilus.net> (raw)
In-Reply-To: <1282218941-sup-4503@duck>
Israel Herraiz, 2010-08-19 14:58:
> It's really annoying to send a message to the list instead of to a
> single person by accident.
>
> In any case, mailing lists can set a Reply-To header
Whoa!
Mailing lists _can_ do that, but they should not. Ironically you
happend to mention one of the reasons why they should not. :D
Let's consider the max damage done by modifying vs. not modifying
reply-to: If the header is unmangled the user may in certain
sircumstances accidentally send private mail instead of list mail.
That's an annoyance at most. If the header is mangled by list server
the user may in certain sircumstances accidentally send list mail
instead of private mail. That may cost the user a lot of goodwill,
money or her job. Ergo, list setting reply-to header violates the
principle of least damage.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-08-19 13:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 10:52 Philipp
2010-08-19 11:58 ` Israel Herraiz
2010-08-19 12:27 ` Erin Sheldon
2010-08-19 12:40 ` Philipp Überbacher
2010-08-19 13:07 ` Tero Tilus
2010-08-19 13:21 ` Helge Titlestad
2010-08-19 18:31 ` Tero Tilus
2010-08-19 14:26 ` Philipp Überbacher
2010-08-19 18:24 ` Tero Tilus
2010-08-19 19:19 ` Philipp Überbacher
2010-08-19 20:11 ` wagnerdm
2010-08-19 12:29 ` Philipp Überbacher
2010-08-19 12:49 ` Tero Tilus [this message]
2010-08-19 13:39 ` Israel Herraiz
2010-08-19 12:33 ` Tero Tilus
2010-08-19 12:58 ` Philipp Überbacher
2010-08-19 13:41 ` Israel Herraiz
2010-08-19 14:10 ` Philipp Überbacher
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=1282221210-sup-5773@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.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