From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Reply-To -> CC?
Date: Wed, 23 Dec 2020 09:26:48 +0300 [thread overview]
Message-ID: <X+LjKHoeqRmLuZg0@protected.rcdrun.com> (raw)
In-Reply-To: <877dp9tc8b.fsf@codeisgreat.org>
* Pankaj Jangid <pankaj@codeisgreat.org> [2020-12-23 06:48]:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Is there an alternative solution to this problem, "Email Groups" or
> > something like that? (No, we don't want to use a messenger instead)
>
> Only guaranteed solution is that everybody a memberber of a group and
> the From and To (both) the headers are pointing to the group email
> address in each message.
>
> I guess this you need to setup yourself somewhere. I am not aware of a
> hosted solution for this.
There is solution.
Example in `mutt' email client https://www.mutt.org is that I may
specify which email addresses are mailing list addresses and then I
may use the L key for list-reply as it will know how to reply to the
list.
And if I set $followup_to variable, it will add the header
Mail-Followup-To: and you may read about that header:
https://cr.yp.to/proto/replyto.html
From mutt manual:
*3.97. followup_to
Type: boolean
Default: yes
Controls whether or not the "Mail-Followup-To:" header field is
generated when sending mail. When set, Mutt will generate this field
when you are replying to a known mailing list, specified with the
"[2031]subscribe" or "[2032]lists" commands.
This field has two purposes. First, preventing you from receiving
duplicate copies of replies to messages which you send to mailing
lists, and second, ensuring that you do get a reply separately for any
messages sent to known lists to which you are not subscribed.
The header will contain only the list's address for subscribed lists,
and both the list address and your own email address for unsubscribed
lists. Without this header, a group reply to your message sent to a
subscribed list will be sent to both the list and your address,
resulting in two copies of the same email for you.
next prev parent reply other threads:[~2020-12-23 6:26 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
2020-12-20 5:27 ` Michael Heerdegen
2020-12-23 3:47 ` Pankaj Jangid
2020-12-23 6:26 ` Jean Louis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X+LjKHoeqRmLuZg0@protected.rcdrun.com \
--to=bugs@gnu.support \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.