From: David Engster <deng@randomsample.de>
To: asjo@koldfront.dk (Adam Sjøgren)
Cc: ding@gnus.org
Subject: Re: Bcc
Date: Thu, 23 Feb 2017 19:21:36 +0100 [thread overview]
Message-ID: <87fuj4g43z.fsf@randomsample.de> (raw)
In-Reply-To: <87o9xt2tab.fsf_-_@tullinup.koldfront.dk> ("Adam \=\?iso-8859-1\?Q\?Sj\=F8gren\=22's\?\= message of "Thu, 23 Feb 2017 09:41:32 +0100")
Adam Sjøgren writes:
> David writes:
>
>> Some MUAs send a separate mail for the people in the Bcc
>
> Which MUAs do not do this?
>
> Isn't that the definition of what Bcc does?
To my knowledge, there's no definition how BCC is actually
implemented. RFC822 only states that the BCC header must not reach the
primary/secondary recipients (and it explicitly does not say whether the
BCC header should be seen by the tertiary recipients, as I've written to
Uwe).
I'm gone from system administration quite a while, so things might have
changed, but I remember that there were long discussions who is actually
responsible for *implementing* the BCC behavior: the MUA or the
MTA. Many MTAs take it upon themselves to handle BCC: they strip the BCC
header and then forwarded the mails to all recipients. I remember that
Exim did *not* do that by default, which a quick search shows still
surprises people:
https://www.bentasker.co.uk/documentation/linux/301-avoiding-bcc-leaks-with-exim
Now that might not be a proper MUA, but I'm pretty sure I've seen MUAs
back in the day that delegated BCC handling to the MTA. They probably
changed that when Exim became popular.
-David
next prev parent reply other threads:[~2017-02-23 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 13:50 ignore bcc when followup 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 ` David Engster [this message]
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
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=87fuj4g43z.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=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).