Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Fri, 13 Apr 2018 22:29:43 +0200	[thread overview]
Message-ID: <87vacualzc.fsf@mat.ucm.es> (raw)
In-Reply-To: <87d0z51px0.fsf@mouse.gnus.org>

>>> "Lars" == Lars Ingebrigtsen <larsi@gnus.org> writes:

   > Uwe Brauer <oub@mat.ucm.es> 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 <user@ucm.es>
Subject: Blabla
To: User2 <user2@ucm.es>
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 <user@ucm.es>
Subject: Blabla
CC: User2 <user2@ucm.es>
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 




  parent reply	other threads:[~2018-04-13 20:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 12:06 Uwe Brauer
2018-04-11 19:52 ` Lars Ingebrigtsen
2018-04-11 21:25   ` Dan Christensen
2018-04-13 18:44   ` Uwe Brauer
2018-04-13 20:29   ` Uwe Brauer [this message]
2018-04-13 20:38     ` Lars Ingebrigtsen
2018-04-13 20:59       ` Uwe Brauer
2018-04-13 21:15         ` Lars Ingebrigtsen
2018-04-13 22:23           ` Uwe Brauer
2018-04-13 22:28             ` Lars Ingebrigtsen
2018-04-14  7:15               ` Uwe Brauer
2018-04-14  9:54                 ` Adam Sjøgren
2018-04-14 10:12                   ` Uwe Brauer
2018-04-14 10:38                     ` Adam Sjøgren
2018-04-14 17:05               ` Uwe Brauer
2018-04-14 17:58                 ` Lars Ingebrigtsen
2018-04-19 11:58                   ` [Partial solution: how to warn about a possible BCC field] (was: warn about a BCC field) Uwe Brauer
2018-04-13 22:31           ` warn about a BCC field Uwe Brauer
2018-04-13 22:42             ` Adam Sjøgren
2018-04-14  7:09               ` Uwe Brauer

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=87vacualzc.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).