From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87974 Path: news.gmane.org!.POSTED!not-for-mail From: Uwe Brauer Newsgroups: gmane.emacs.gnus.general Subject: Re: warn about a BCC field Date: Sat, 14 Apr 2018 19:05:15 +0200 Message-ID: <87k1t9iur8.fsf@mat.ucm.es> References: <87d1eaa0q2.fsf@mat.ucm.es> <87d0z51px0.fsf@mouse.gnus.org> <87vacualzc.fsf@mat.ucm.es> <87k1tasuz9.fsf@mouse.gnus.org> <87lgdqakkw.fsf@mat.ucm.es> <87woxayfj8.fsf@mouse.gnus.org> <87y3hq924h.fsf@mat.ucm.es> <87lgdqn3lf.fsf@mouse.gnus.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1523725471 22367 195.159.176.226 (14 Apr 2018 17:04:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 14 Apr 2018 17:04:31 +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+m36188@lists.math.uh.edu Sat Apr 14 19:04:27 2018 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048035.atla03.us.yomura.com ([107.189.48.35]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f7ObC-0005eL-2u for ding-account@gmane.org; Sat, 14 Apr 2018 19:04:26 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048035.atla03.us.yomura.com (Halon) with ESMTPS id 235f00f4-4006-11e8-a660-b499baabecb2; Sat, 14 Apr 2018 17:06:14 +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 1f7OcC-0007ck-5P; Sat, 14 Apr 2018 12:05:28 -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 1f7Oc8-0007cB-IF for ding@lists.math.uh.edu; Sat, 14 Apr 2018 12:05:24 -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 1f7Oc7-0003TH-5L for ding@lists.math.uh.edu; Sat, 14 Apr 2018 12:05:24 -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 1f7Oc5-0003nI-Rw for ding@gnus.org; Sat, 14 Apr 2018 19:05:21 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1f7OZx-0004Hd-Vj for ding@gnus.org; Sat, 14 Apr 2018 19:03:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 25 Original-X-Complaints-To: usenet@blaine.gmane.org Mail-Copies-To: never Cancel-Lock: sha1:7HvVsCj/lrMSxRsq+G8GgOsb+Mg= X-Spam-Score: 1.0 (+) X-Spam-Report: SpamAssassin (3.4.1 2015-04-28) analysis follows Bayesian score: 0.2312 Ham tokens: 0.000-159--6006h-0s--0d--H*M:fsf, 0.000-13--490h-0s--0d--H*UA:Emacs, 0.000-13--483h-0s--0d--H*u:Emacs, 0.000-11--388h-0s--0d--H*u:Gnus, 0.000-11--388h-0s--0d--H*UA:linux Spam tokens: 0.997-31123--580h-25325s--0d--H*r:quimby.gnus.org, 0.997-18316--351h-14911s--0d--Hx-spam-relays-internal:sk:junkmas, 0.997-18316--351h-14911s--0d--HX-Envelope-From:sk:junkmas, 0.997-18316--351h-14911s--0d--H*RT:sk:junkmas, 0.995-32071--973h-26396s--0d--HTo:D*gnus.org Autolearn status: no autolearn_force=no 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 BAYES_40 BODY: Bayes spam probability is 20 to 40% [score: 0.2312] 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87974 Archived-At: > Uwe Brauer writes: > Just look for your email address in the headers. If it's not there, > it's dangerous for you to do a wide reply on it. I thought about this point. As it turns out (thanks an experiment I did with Adam), you were right, BCC is not, usually ,included in the message, only in some wired gmail setting. Now, that makes my approach useless in the general case. Moreover my approach was based on a function which I put in the setup-hook so it checked for a BCC field once the reply buffer was generated. But if I want to deal with the general case I should check before creating the reply buffer. How do I do that? I mean which function can the article buffer and extract the information for the TO and CC fields? Thanks Uwe Brauer