From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Wed, 11 Apr 2018 21:52:43 +0200 [thread overview]
Message-ID: <87d0z51px0.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87d1eaa0q2.fsf@mat.ucm.es> (Uwe Brauer's message of "Wed, 22 Feb 2017 12:06:45 +0000")
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?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-11 19:52 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 [this message]
2018-04-11 21:25 ` Dan Christensen
2018-04-13 18:44 ` Uwe Brauer
2018-04-13 20:29 ` Uwe Brauer
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=87d0z51px0.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--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).