Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: ignore bcc when followup
Date: Thu, 23 Feb 2017 14:10:54 +0000	[thread overview]
Message-ID: <87tw7lf15d.fsf@mat.ucm.es> (raw)
In-Reply-To: <87wpch1393.fsf@tullinup.koldfront.dk>

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

>>> "Adam" == Adam Sjøgren <asjo@koldfront.dk> writes:

   > Uwe writes:
   >>>>> "Adam" == Adam Sjøgren <asjo@koldfront.dk> writes:

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

   >> No they don't at least gnus does not, in my previous email the example I
   >> gave were generated by gnus, that is gnus display the BCC field, in a
   >> message which was sent my gnus, I wonder why he does not do it for you.

   > Gnus does not send the Bcc header neither to the recipient in To: nor to
   > the recipient in Bcc:.

For me it does, see the screenshots hope they will not be blocked



[-- Attachment #2: gnus-bcc.png --]
[-- Type: image/png, Size: 84494 bytes --]

[-- Attachment #3: seam-bcc1.png --]
[-- Type: image/png, Size: 152126 bytes --]

  reply	other threads:[~2017-02-23 14:10 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
2017-02-23 10:24       ` Uwe Brauer
2017-02-23 12:49         ` Adam Sjøgren
2017-02-23 14:10           ` Uwe Brauer [this message]
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=87tw7lf15d.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).