From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87958 Path: news.gmane.org!.POSTED!not-for-mail From: Uwe Brauer Newsgroups: gmane.emacs.gnus.general Subject: Re: warn about a BCC field Date: Fri, 13 Apr 2018 22:29:43 +0200 Message-ID: <87vacualzc.fsf@mat.ucm.es> References: <87d1eaa0q2.fsf@mat.ucm.es> <87d0z51px0.fsf@mouse.gnus.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1523651340 1826 195.159.176.226 (13 Apr 2018 20:29:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Apr 2018 20:29:00 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+m36172@lists.math.uh.edu Fri Apr 13 22:28:55 2018 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048034.atla03.us.yomura.com ([107.189.48.34]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f75JX-0000Jy-Ek for ding-account@gmane.org; Fri, 13 Apr 2018 22:28:55 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048034.atla03.us.yomura.com (Halon) with ESMTPS id 8bef8f15-3f59-11e8-950a-b499baa2b07a; Fri, 13 Apr 2018 20:30:47 +0000 (UTC) Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.90_1) (envelope-from ) id 1f75Kc-0003oz-0G; Fri, 13 Apr 2018 15:30:02 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1f75KY-0003oG-Dt for ding@lists.math.uh.edu; Fri, 13 Apr 2018 15:29:58 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.90_1) (envelope-from ) id 1f75KT-0003ek-Kb for ding@lists.math.uh.edu; Fri, 13 Apr 2018 15:29:58 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1f75KS-0006l8-8x for ding@gnus.org; Fri, 13 Apr 2018 22:29:52 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1f75IH-000759-Tf for ding@gnus.org; Fri, 13 Apr 2018 22:27:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 61 Original-X-Complaints-To: usenet@blaine.gmane.org Mail-Copies-To: never Cancel-Lock: sha1:yqwQ78tsIMIi7IcxzprIws5hJrw= X-Spam-Score: -0.9 (/) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87958 Archived-At: >>> "Lars" == Lars Ingebrigtsen writes: > Uwe Brauer writes: >> I suppose I receive a message which contains a bcc field. Now I don't >> want by mistake hit, gnus-summary-followup-with-original because then >> the original recipient will get into the CC field. Is there a way to be >> warned about that? > Hm. That's not supposed to happen at all -- that function is not > supposed to put the Bcc recipients into the Cc header. > Does Gnus really do that? I investigated further and indeed there is a problem. As I said my university switched to gmail. Now someone sent me, using his Apple Mail app, a mail with the following headers From: User1 Subject: Blabla To: User2 Date: Wed, 22 Feb 2017 08:39:23 +0100 (1 year, 7 weeks, 1 day ago) Bcc: oub@mat.ucm.es So you see I am only on the BCC field which is displayed. Now I hit F (as I do automatically and which in this case was a big mistake because it results in To: User1 Subject: Blabla CC: User2 Date: Wed, 22 Feb 2017 08:39:23 +0100 (1 year, 7 weeks, 1 day ago) Bcc: oub@mat.ucm.es And resulted in a somehow uncomfortable situation. Meanwhile I did the following (defun my-check-bcc () "Try to avoid painful situations when using followup, and there is a Bcc field." (interactive) (cond ((and gnus-article-reply (message-with-reply-buffer (re-search-forward "^Bcc:\\|BCC:\\|bcc:" nil t))) (condition-case nil (progn (message-remove-header "cc") (message-goto-body) (message "There is a BCC field, we have deleted it!!!")) (error (progn (message "Followup??"))))))) (add-hook 'gnus-message-setup-hook 'my-check-bcc) Any thoughts or comments? Uwe Brauer