Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: ignore bcc when followup
Date: Wed, 22 Feb 2017 23:23:56 +0100	[thread overview]
Message-ID: <8737f5dfur.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87ino1hpu1.fsf@mat.ucm.es>

Uwe writes:

>    > (How do you even receive an email with a Bcc header in it? Usually they
>    > aren't sent - what email program sent it?)
>
> The email in equation was sent to me from someone using apple mail

That is odd behaviour of Apple Mail, I think.

Gnus, mutt and Gmail all remove the Bcc header from both the email sent
to the original recipient AND from the blind carbon copy.

I've never seen a Bcc-header on an incoming email. Guess I don't know
anybody Bcc'ing me from Apple Mail :-)

This does, however, make it harder to detect when to warn - if the
incoming email is to a mailing list, your address might very well not be
present in neither To nor Cc, but you don't want a warning.


  Best regards,

    Adam

-- 
 "A cat has nine lives, but a bullfrog croaks                 Adam Sjøgren
  every day."                                            asjo@koldfront.dk




  parent reply	other threads:[~2017-02-22 22:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 13:50 Uwe Brauer
2017-02-22 19:10 ` SOLVED (was: ignore bcc when followup) Uwe Brauer
2017-02-23  7:46   ` SOLVED David Engster
2017-02-23  8:41     ` Bcc Adam Sjøgren
2017-02-23 18:21       ` Bcc David Engster
2017-02-22 19:54 ` ignore bcc when followup Adam Sjøgren
2017-02-22 21:34   ` Uwe Brauer
2017-02-22 22:03     ` Adam Sjøgren
2017-02-22 22:23     ` Adam Sjøgren [this message]
2017-02-23 10:24       ` Uwe Brauer
2017-02-23 12:49         ` Adam Sjøgren
2017-02-23 14:10           ` Uwe Brauer
2017-02-23 14:54             ` Adam Sjøgren
2017-02-23 15:33               ` 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=8737f5dfur.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).