From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30757 invoked from network); 15 Dec 2023 01:43:21 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 15 Dec 2023 01:43:21 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1rDxEU-001TXY-2K for ml@inbox.vuxu.org; Thu, 14 Dec 2023 19:43:18 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96.2) (envelope-from ) id 1rDxEU-002MuX-0w for ml@inbox.vuxu.org; Thu, 14 Dec 2023 19:43:18 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96.2) (envelope-from ) id 1rDxER-002MuO-1Y for ding@lists.math.uh.edu; Thu, 14 Dec 2023 19:43:15 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from ) id 1rDxEM-004N4H-1s for ding@lists.math.uh.edu; Thu, 14 Dec 2023 19:43:15 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Qx/vcNM2+kPN3/BJeTOafiG7RjrSJsvPPXRgVfGD0rU=; b=ohHIbNRhbNK3NdB1AS2Dh4Hos4 8jlBpZAkGh4ZQLZp7/ESOXIfVITmqa+tRY6hSCniZQzNPgzf02Fq+zVOd647eeVAen23M1BQyCA9x Z6gmdQIkBnqcF8nTfZeKrP+Y4npVf8niQf836nWeLpulXTQwAn368cwrZCN5Z5qJogIw=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rDxED-0001tN-Py for ding@gnus.org; Fri, 15 Dec 2023 02:43:05 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1rDxEB-0007U1-BR for ding@gnus.org; Fri, 15 Dec 2023 02:42:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: mail/post forwarding now has an option to forward all original headers Date: Thu, 14 Dec 2023 17:42:50 -0800 Message-ID: <8734w4gs11.fsf@ericabrahamsen.net> References: <87ttonjnz9.fsf@ericabrahamsen.net> <874jgn2ros.fsf@dataswamp.org> <87msudj0nn.fsf@ericabrahamsen.net> <87bkatnjup.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:wQM/6r3hZNEOXiLZik3khPkoFPY= List-ID: Precedence: bulk Emanuel Berg writes: > Eric Abrahamsen wrote: > >>>> Just FYI, I've just added a symblic-prefix option ('a) to >>>> `gnus-summary-mail-forward' and >>>> `gnus-summary-post-forward', which temporarily sets >>>> `message-forward-included-headers' to nil. >>> >>> Maybe related, >>> >>> People have sometimes been annoyed I don't keep the e-mails >>> in a CC when I reply on mailing lists, I have never >>> understood why this doesn't happen. Like in this case, >>> I suppose these >>> >>> >>> >>> >>> should appear in the CC? But the only headers I see after >>> `gnus-article-followup-with-original' are >>> >>> Newsgroups: gmane.emacs.gnus.general >>> Subject: Re: mail/post forwarding now has an option to >>> forward all original headers >>> To: >>> From: Emanuel Berg >>> Gcc: nnml:mail.sent >>> >>> I have `message-forward-ignored-headers' at its original >>> value, and also tried `message-forward-included-headers' >>> both at its original value and now nil, inspired by >>> this post. >> >> This has to do with replies, not forwarding. This stuff is >> governed by the "wideness" of the reply, not the headers. > > I use `gnus-article-followup-with-original', should you use > something else? When you reply via newsgroup posting (which is implied by the "followup"), then headers don't come into play, only the "newsgroups" header, and the message is sent via NNTP to those groups. There's no CC to anybody else. If you reply via mail, then you will send an email to everyone in the To/CC/BCC headers, and there's where you'll see commands with "reply" and "(very) wide" in the name. It only gets a bit confusing because if you reply to an article that originally arrived via NNTP, often the email goes to an email address that can transport the message over to the NNTP newsgroup, so it looks like you did both a followup (to the group) and a reply (to individual posters). The whole thing gets a little strange.