On 4/21/2025 5:27 PM, Francesco Gennai wrote:
It is slightly off-topic, but it's interesting to me too. In this case it is probable that the android app sends a separate copy of the email for each BCC address (with the related BCC header). I tested Gmail as an SMTP client for message submission and it works as above, by sending a separate copy for each BCC address.
There are at least two different issues. One is getting bcc mail delivered so that non-bcc recipients do not see that there were bcc recipients. All the scenarios accomplish this. The details of how a sending site accomplishes this can vary, but there is no indication that any system malfunctions about this.
Separately is the question of what a bcc recipient /sees/. I've noted benefits in the recipient's seeing the field and my own belief is that it is better for them to see their address in that field. But one can debate the choices.
Allen sent me a message to my gmail account and indeed, the message had a bcc. He sent another to my dhc@ and the bcc was not in the delivered message. Presumably stripped by my receiving platform provider.
d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net bluesky: @dcrocker.bsky.social mast: @[email protected]
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
