[sylpheed:37317] Re: Email standard for BCC behaviour
Jeremy Cook
funjulietaco at jcook.la
Fri Jul 26 01:00:07 JST 2024
On Thu Jul 25 2024 8:53 AM, Paul wrote:
> On Thu, 25 Jul 2024 08:52:48 -0600
> "Gene Goldenfeld" <genegold at fastmail.com> wrote:
>
>> So this is determined by the sender’s program, e.g., Sylpheed and Gmail,
>> and not the recipients’?
>
> No, it's the server's job. The MUA sets the Bcc header, the MTA deals with it.
> A server that reveals the Bcc header to any recipient is a broken server.
>
> The 'B' stands for 'blind', it's called blind for a reason.
>
> There's no mystery to this, it's really simple to grasp, no recipient should
> see the Bcc header or its contents.
Paul, I agree that no recipient should ever see the BCC header, but what do you
make of this part of the RFC:
"When a message is a reply to another message... If a "Bcc:" field is present in
the original message, addresses in that field MAY appear in the "Bcc:" field of
the reply, but they SHOULD NOT appear in the "To:" or "Cc:" fields."
This is really confusing me.
More information about the Sylpheed
mailing list