From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Reply-To -> CC? Date: Wed, 23 Dec 2020 13:43:04 +0300 Message-ID: References: <87pn352ogh.fsf@web.de> <20201222124834.GC11075@no.workgroup> <87y2hprthx.fsf@web.de> <87o8ilrmze.fsf@web.de> <87pn31ym6g.fsf@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28993"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Dec 23 11:45:37 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ks1eC-0007Rb-T5 for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 23 Dec 2020 11:45:36 +0100 Original-Received: from localhost ([::1]:36210 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ks1eB-0000TM-Uk for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 23 Dec 2020 05:45:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47738) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks1dP-0000T7-6m for help-gnu-emacs@gnu.org; Wed, 23 Dec 2020 05:44:47 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:46263) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks1dM-00057v-OI for help-gnu-emacs@gnu.org; Wed, 23 Dec 2020 05:44:46 -0500 Original-Received: from localhost ([::ffff:41.202.241.37]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001818C.000000005FE31F99.000059E5; Wed, 23 Dec 2020 03:44:41 -0700 Mail-Followup-To: Jean Louis , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87pn31ym6g.fsf@iki.fi> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:126688 Archived-At: * Teemu Likonen [2020-12-23 11:15]: > * 2020-12-23 08:38:13+0100, Michael Heerdegen wrote: > > > My case is a private conversation between me and the dog school, and a > > third person I want to CC (in some sense of receiving at least) all > > messages of the conversation (the third person is not the dog). > > > > Would you recommend Mail-Followup-To in this case, too? Can I specify > > multiple addresses there? > > Header Mail-Followup-To is not in email RFC 5322 (nor older 2822). It is > is supported by some free software hacker email clients but user can't > rely on it. It can be some convenience at some situations, at best. It does not matter, you can adopt it right away to minimize some problems with the hand editing. What I wish to say, we do not need a "standard" to make it little easier for others. The Mail-Followup-To is just making it little easier to avoid Cc-ing people who need not be Cc-ed or to find out the mailing list address. Person could as well do it by hand. I see my habbit was bad to use group reply, from now on I will use list reply, and honor other people's Mail-Followup-To header. It is kind to do so. > "Reply-To" can have several addresses but it is just a suggestion > where replies be sent. No person or email client program is required > to honour "Reply-To". Sure, good thing to switch conversation from one email address to other, but correspondent may not honor it, so I do it for as long as necessary or even tell to person to answer me on different email address. > - Reply to all: Reply message will be send to the original sender (see > above) and all addresses in the original message's "To" and "Cc" > headers. That is what I was using, but that is not quite correct in mailing lists. From now on I will use list reply that recognizes the mailing list as I configured it, and I reply to the list, not to sender. > Those two options work reliably. Those options are settable by every email user if they want it. People do not know how maybe, but email has headers, and back in time headers were edited by users. Today they can still be edited. > If we wish to have an email conversation between several people we > need to include all participants in our own messages and probably > need to remind other people to choose "reply to all" option. That is > pretty much all we can do. Other fancier features may work in some > hacker communities. We are hacker community here. Please see settings for Thunderbird for Mail-Followup-To: https://wiki.mozilla.org/Thunderbird:Help_Documentation:Mail-Followup-To_and_Mail-Reply-To In message mode, there is also Follow-up header: https://www.gnu.org/software/emacs/manual/html_node/emacs/Header-Editing.html so it means it can be also customized and provided. Also search here for "followup": https://www.gnu.org/software/emacs/manual/html_mono/message.html Quote: The message-use-followup-to variable says what to do about Followup-To headers. If it is use, always use the value. If it is ask (which is the default), ask whether to use the value. If it is t, use the value unless it is ‘poster’. If it is nil, don’t use the value.