From: Justin Sheehy <dworkin@ccs.neu.edu>
Subject: Re: Mail-Copies-To: never
Date: 07 Apr 1997 13:11:36 -0400 [thread overview]
Message-ID: <vnd7mie21x3.fsf@garathorm.ccs.neu.edu> (raw)
In-Reply-To: Kai Grossjohann's message of 07 Apr 1997 17:33:35 +0200
Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:
> I like to send a courtesy copy to the originator of a news article.
> So I habitually type "F", edit the message, then type "C-c C-t C-c
> C-c" to send the message. However, C-c C-t unconditionally sends a
> copy to the sender even if s/he has put "Mail-Copies-To: never" in the
> original posting.
>
> What do you all do to avoid this problem?
I avoid this problem by not causing it.
Generally, it works quite well if you _only_ send a discourtesy copy
if the originator asked for one, or if other circumstances demand it.
This ends up bothering a lot less people. When someone begins a
thread in news, they usually expect followups to be in news.
Courtesy copies are unneeded expect when explicitly desired by the
originator.
-Justin
next prev parent reply other threads:[~1997-04-07 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-07 15:33 Kai Grossjohann
1997-04-07 17:11 ` Justin Sheehy [this message]
1997-04-07 18:37 ` Michael Welsh Duggan
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=vnd7mie21x3.fsf@garathorm.ccs.neu.edu \
--to=dworkin@ccs.neu.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).