STR 1) compose new message using gmail IMAP account on TB (in brackets: Account names per comment 0) From: sender@gmail.com (A2) To: opento@gmail.com (A1) BCC: sender@gmail.com (A2), blind1@gmail.com (A3) 2) Send 3) check resulting sent/incoming messages if there's any BCC leakage to other parties a) check received message in Inbox of other party opento@gmail.com b) check received message in Inbox of other party blind1@gmail.com c) check received message in your own Inbox (sender@gmail.com) from bcc to self d) check your own sent message in Sent of sender@gmail.com Actual result - TLDR; **There is no leakage of BCC recipients to any other party.** Only the sender will know all BCC recipients. - The message sent via BCC to self and "received" in sender's inbox (From: sender@gmail, BCC: sender@gmail) shows all BCC recipients. This may differ from other providers, but it does not constitute Bcc leakage as the sender already knows all the BCC recipients from composing the message. Technically, iirc (and the source seems to confirm that), Google does not even bother sending the bcc-to-sender/self message through the net, but just labels the sent message also as inbox, keeping only one physical message. - Obviously the sent message in sender's sent folder has all BCC recipients. a) received message in inbox of opento@gmail.com: ``` Delivered-To: opento@gmail.com To: opento@gmail.com No Bcc header. ``` b) received message in inbox of blind1@gmail.com: ``` Delivered-To: blind1@gmail.com To: opento@gmail.com No Bcc header. ``` c) received message in inbox of sender@gmail.com (bcc to self) ``` Delivered-To: sender@gmail.com To: opento@gmail.com BCC: sender@gmail.com, blind1@gmail.com (no leakage, this is the sender's inbox, see explanation above). ``` Expected Result = Actual Result - Do not leak Bcc recipients to any other party who is not the sender.
Bug 1691445 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
**STR** 1) compose new message using gmail IMAP account on TB (in brackets: Account names per comment 0) From: sender@gmail.com (A2) To: opento@gmail.com (A1) BCC: sender@gmail.com (A2), blind1@gmail.com (A3) 2) Send 3) check resulting sent/incoming messages if there's any BCC leakage to other parties a) check received message in Inbox of other party opento@gmail.com b) check received message in Inbox of other party blind1@gmail.com c) check received message in your own Inbox (sender@gmail.com) from bcc to self d) check your own sent message in Sent of sender@gmail.com **Actual result** - TLDR; **There is no leakage of BCC recipients to any other party.** Only the sender will know all BCC recipients. - The message sent via BCC to self and "received" in sender's inbox (From: sender@gmail, BCC: sender@gmail) shows all BCC recipients. This may differ from other providers, but it does not constitute Bcc leakage as the sender already knows all the BCC recipients from composing the message. Technically, iirc (and the source seems to confirm that), Google does not even bother sending the bcc-to-sender/self message through the net, but just labels the sent message also as inbox, keeping only one physical message. - Obviously the sent message in sender's sent folder has all BCC recipients. a) received message in inbox of opento@gmail.com: ``` Delivered-To: opento@gmail.com To: opento@gmail.com No Bcc header. ``` b) received message in inbox of blind1@gmail.com: ``` Delivered-To: blind1@gmail.com To: opento@gmail.com No Bcc header. ``` c) received message in inbox of sender@gmail.com (bcc to self) ``` Delivered-To: sender@gmail.com To: opento@gmail.com BCC: sender@gmail.com, blind1@gmail.com (no leakage, this is the sender's inbox, see explanation above). ``` **Expected Result** (same as Actual Result) - Do not leak Bcc recipients to any other party who is not the sender.