From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: ignore bcc when followup
Date: Wed, 22 Feb 2017 21:34:46 +0000 [thread overview]
Message-ID: <87ino1hpu1.fsf@mat.ucm.es> (raw)
In-Reply-To: <87o9xuc87b.fsf@tullinup.koldfront.dk>
>>> "Adam" == Adam Sjøgren <asjo@koldfront.dk> writes:
> Uwe writes:
>> as longer as I think about it: At least optionally the BCC field should
>> be ignored in the reply even when calling followup.
> Uhm, do you get a Bcc-header when you follow up to an email with a
> Bcc-header in it?
No. I am saying (see below my experiment.)
I receive an email which goes like
From: Joe
To: John
Bcc: Uwe
Now I, Uwe hit, by mistake, followup, instead of reply, then they mail
looks at it should
From: Uwe
To: Joe
CC: John
Which is bad, because John did not know that mail was sent to me. I
should have used reply instead of followup, but since a lot of people
complained that I hit reply instead of followup, I know hit followup
automatically.
So my small function will save me such embarrassing situations in the
future.
Did I explain myself?
Below the experiments I did.
All can I say I sent an email to myself, with a bcc to another email
Here is what I received
,----
|
| From: Uwe Brauer <oub@mat.ucm.es>
| Subject: test bcc
| To: Uwe Brauer <oub@mat.ucm.es>
| Date: Wed, 22 Feb 2017 21:26:58 +0000 (1 minute, 5 seconds ago)
| Bcc: oub.oub.oub@gmail.com
| Reply-To: Uwe Brauer <oub@mat.ucm.es>
|
| adfadf
`----
And the other way around
,----
| From: Uwe Brauer <oub@mat.ucm.es>
| Subject: test 2
| To: Uwe Brauer <oub.oub.oub@gmail.com>
| Date: Wed, 22 Feb 2017 21:27:30 +0000 (48 seconds ago)
| Bcc: oub@mat.ucm.es
| Reply-To: Uwe Brauer <oub@mat.ucm.es>
|
| This is true
`----
> I don't.
> (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
> I just made an experiment: I sent myself an email, edited it after
> receipt, adding a Bcc (and Gcc, just for fun) header, and hit F.
> The headers in the follow up that did not include the Bcc (nor the Gcc)
> from the email.
> Original headers:
> From: Adam Sjøgren <asjoegren@gmail.com>
> Subject: Test
> To: Adam Sjøgren <asjo@koldfront.dk>
> Date: Wed, 22 Feb 2017 20:51:10 +0100 (1 minute, 24 seconds ago)
> Bcc: test@koldfront.dk
> Gcc: abba@koldfront.dk
> Attachment: [3. text/html]...
> Follow up headers:
> To: Adam Sjøgren <asjoegren@gmail.com>
> Subject: Re: Test
> 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
> X-Now-Playing: Den vänstra stranden, Då som nu för alltid (Kent)
> X-Hashcash: 1:21:170222:asjoegren@gmail.com::BVrk/jbmN3tCC90h:000000000000000000000000000000000000000000JJU3
> --text follows this line--
> How did you make Gnus include them?
> Best regards,
> Adam
next prev parent reply other threads:[~2017-02-22 21:34 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 [this message]
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
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=87ino1hpu1.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).