Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: warn about a BCC field
Date: Sat, 14 Apr 2018 00:28:28 +0200	[thread overview]
Message-ID: <87lgdqn3lf.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87y3hq924h.fsf@mat.ucm.es> (Uwe Brauer's message of "Sat, 14 Apr 2018 00:23:58 +0200")

Uwe Brauer <oub@mat.ucm.es> writes:

> Well well. I just sent myself with gnus the following message
>
> From: Uwe Brauer <oub@mat.ucm.es>
> Subject: this
> To: Uwe Brauer <oub@mat.ucm.es> 
> Cc: Uwe Brauer <burrurr@gmail.com> 
> Date: Sat, 14 Apr 2018 00:14:28 +0200 (48 seconds ago)
> Bcc: oub.oub.oub@gmail.com
>
> As you can see that is a BCC field.
>
> Now when I open in my oub.oub.oubGmail.com account the message and
> indeed the BCC field is gone. I did the same with thunderbird and the
> same behavior. Odd no?

No, mail user agents are supposed to strip the Bcc header before
sending, and that's what Gnus is doing, so everything works as it
should.

The whole point of the Bcc header is that isn't not supposed to be sent
out.

> I see your point concerning mailing list, but what's about the other use
> case I just mentioned? What would you do in such a situation?
>
> However I just realized that my code is not failsafe. 
>
> As it seems I can't trust that such a mail (where I am not in the TO/CC)
> would include a bcc field, and then my hack would fail.
>
> Couldn't we set a variable (gnus-for-the-careless-repliers) 
> but then it is not clear to me what to search for? Any ideas how to deal
> with that?

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.

> It seems that most people are either not very often in such a situation
> or are just more careful then I am.

I think so.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2018-04-13 22:28 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
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 [this message]
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=87lgdqn3lf.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).