unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Reply-To -> CC?
Date: Sun, 20 Dec 2020 04:49:50 +0000	[thread overview]
Message-ID: <87h7ohytch.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: 87pn352ogh.fsf@web.de

Michael Heerdegen <michael_heerdegen@web.de> wrote:

> I'm using Gnus.  That's actually the only connection of this question to
> Emacs, sorry.

> My question: Is it possible to setup the message header of a message to
> person A so that a person B is CC'd, and to specify something in the
> Reply-To header so that when A responds, the message is send to me and
> also automatically CC'd to B again?  Or can this be forced in some other
> way?

> I ask because some people's MUAs seem to silently drop the CC'd address
> and those people then fall out of the discussion.

AFAIK: It is not possible to preset a Cc: header, but you
can preset the To: header with Reply-To: which can hold
/multiple/ mail addresses, e. g. the message's author and B.

(Of course, with regard to your original problem, there is
also the human factor: If I get a message that the author
Cced to B, I don't necessarily assume that my answer should
be Cced to B as well; perhaps the author only wanted B to
see the author's message.  Therefore it might be useful to
spell out in each message who should be kept in the loop and
why (or use a ticketing system :-)).)

Tim




  parent reply	other threads:[~2020-12-20  4:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  2:36 Reply-To -> CC? Michael Heerdegen
2020-12-20  3:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20  4:00 ` Pankaj Jangid
2020-12-20  4:34   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20  5:20     ` Pankaj Jangid
2020-12-20  5:19   ` Michael Heerdegen
2020-12-20  5:23     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-20  5:24     ` Pankaj Jangid
2020-12-20  5:38       ` Michael Heerdegen
2020-12-20  7:03         ` Eric Abrahamsen
2020-12-20  8:26           ` Pankaj Jangid
2020-12-20 17:47             ` Eric Abrahamsen
2020-12-21  3:53               ` Pankaj Jangid
2020-12-21 23:03                 ` Eric Abrahamsen
2020-12-22 11:29                   ` True
2020-12-22 17:13                     ` Eric Abrahamsen
2020-12-20  4:49 ` Tim Landscheidt [this message]
2020-12-20  5:27   ` Michael Heerdegen
2020-12-23  3:47     ` Pankaj Jangid
2020-12-23  6:26       ` Jean Louis
2020-12-23  6:28       ` Jean Louis
2020-12-22 12:48 ` Gregor Zattler
2020-12-23  5:17   ` Michael Heerdegen
2020-12-23  5:54     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-23  6:30     ` Jean Louis
2020-12-23  7:38       ` Michael Heerdegen
2020-12-23  8:13         ` Teemu Likonen
2020-12-23 10:43           ` Jean Louis
2020-12-23 11:11             ` Teemu Likonen
2020-12-23 11:49               ` Jean Louis
2020-12-23 12:14                 ` Teemu Likonen
2020-12-23 12:32                   ` Pankaj Jangid
2020-12-24  4:03           ` Michael Heerdegen
2020-12-23 10:18         ` Jean Louis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7ohytch.fsf@passepartout.tim-landscheidt.de \
    --to=tim@tim-landscheidt.de \
    --cc=help-gnu-emacs@gnu.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).