From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: No Cc on wide reply
Date: 24 Jul 2000 11:05:41 -0400 [thread overview]
Message-ID: <m37labk1q2.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Stainless Steel Rat's message of "23 Jul 2000 11:17:24 -0400"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) on Sun, 23 Jul 2000
> | I think the header might be useful in a posting to a mailing list.
> | Maybe the author doesn't want to receive two copies of the replies,
> | and is subscribed to the mailing list.
>
> Reply-To is used in a mail message to direct replies to someone other than
> the originator. Using Mail-Copies-To to duplicate this behavior is
> redundant.
OTOH, setting Reply-To to point to a mailing list is misuse of
Reply-To as well.[0] (Even when it's done by users instead of the
list software, I say.) Mail-Followup-To[1] is a solution designed
specifically for this problem. Gnus should support it, but I'm not
sure whether it would necessitate a distinction between wide reply to
news and wide reply to mail.
[0] <URL:http://hackvan.com/pub/stig/rants/reply-to-considered-harmful.html>
[1] <URL:http://cr.yp.to/proto/replyto.html>
paul
next prev parent reply other threads:[~2000-07-24 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-22 4:11 Harry Putnam
2000-07-22 12:03 ` Kai Großjohann
2000-07-22 13:43 ` Harry Putnam
2000-07-22 14:02 ` Stainless Steel Rat
2000-07-23 9:43 ` Kai Großjohann
2000-07-23 15:17 ` Stainless Steel Rat
2000-07-24 9:22 ` Simon Josefsson
2000-07-24 16:46 ` Stainless Steel Rat
[not found] ` <vaf7la4ud2k.fsf@lucy.cs.uni-dortmund.de>
2000-07-30 14:30 ` Stainless Steel Rat
2000-07-24 15:05 ` Paul Jarc [this message]
2000-07-24 16:47 ` Stainless Steel Rat
2000-07-25 6:55 ` Kai Großjohann
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=m37labk1q2.fsf@multivac.student.cwru.edu \
--to=prj@po.cwru.edu \
/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 NNTP newsgroup(s).