From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: ignore bcc when followup
Date: Thu, 23 Feb 2017 13:49:12 +0100 [thread overview]
Message-ID: <87wpch1393.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <8760k1i4qw.fsf@mat.ucm.es>
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:.
Example:
I am sending this email from Gnus:
To: asjoegren@gmail.com
Bcc: asjo@mcom.com
Subject: Test of Bcc
From: asjo@koldfront.dk (Adam Sjøgren)
Gcc: nnml+archive:mail-2017
Organization: koldfront - analysis & revolution, Copenhagen, Denmark
OpenPGP: id=476630590A231909B0A0961A49D0746121BDE416; url=https://asjo.koldfront.dk/gpg.asc
--text follows this line--
Test of Bcc
--
"We are all in the gutter, but some of us are looking Adam Sjøgren
at the stars." asjo@koldfront.dk
This is the conversation between Gnus and the mail server:
220 tullinup.koldfront.dk ESMTP Postfix (Debian/GNU).
EHLO tullinup.
250-tullinup.koldfront.dk.
250-PIPELINING.
250-SIZE 209715200.
250-VRFY.
250-ETRN.
250-STARTTLS.
250-ENHANCEDSTATUSCODES.
250-8BITMIME.
250-DSN.
250 SMTPUTF8.
MAIL FROM:<asjo@koldfront.dk> SIZE=1032.
250 2.1.0 Ok.
RCPT TO:<asjo@mcom.com>.
250 2.1.5 Ok.
RCPT TO:<asjoegren@gmail.com>.
250 2.1.5 Ok.
DATA.
354 End data with <CR><LF>.<CR><LF>.
From: asjo@koldfront.dk (Adam =?utf-8?Q?Sj=C3=B8gren?=)
To: asjoegren@gmail.com.
Subject: Test of Bcc.
Organization: koldfront - analysis & revolution, Copenhagen, Denmark.
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux).
X-Hashcash: 1:21:170223:asjoegren@gmail.com::qtSNPl6AEL11AAqE:000000000000000000000000000000000000000000mh2T.
OpenPGP: id=476630590A231909B0A0961A49D0746121BDE416; url=https://asjo.koldfront.dk/gpg.asc.
X-Face: )qY&CseJ?.:=8F#^~GcSA?F=9eu'{KAFfL1C3/A&:nE?PW\i65"ba0NS)97,Q(^@xk}n4Ou.
rPuR#V8I(J_@~H($[ym:`K_+]*kjvW>xH5jbgLBVFGXY:(#4P>zVBklLbdL&XxL\M)%T}3S/IS9lMJ.
^St'=VZBR<gm`!Dj`dIpp?+$"$l_'JKDN\w-jB;fo0Qy}Tbw.
Date: Thu, 23 Feb 2017 13:44:15 +0100.
Message-ID: <87y3wx13hc.fsf@tullinup.koldfront.dk>.
MIME-Version: 1.0.
Content-Type: text/plain; charset=utf-8.
Content-Transfer-Encoding: quoted-printable.
.
Test of Bcc.
.
--=20.
"We are all in the gutter, but some of us are looking Adam Sj=C3=B8=.
gren.
at the stars." asjo@koldfront.dk.
..
250 2.0.0 Ok: queued as 8542210053471.
As you can see, Gnus does NOT send the Bcc-header, it sends the email
without the Bcc-header to the two recipients.
It does, however, store the Bcc header in the *local copy* of the email,
so *you* can see that you did in fact Bcc.
Best regards,
Adam
--
"It's not denial. I'm just very selective about the Adam Sjøgren
reality I accept." asjo@koldfront.dk
next prev parent reply other threads:[~2017-02-23 12:49 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 [this message]
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=87wpch1393.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).