On Mon, Apr 21, 2025 at 5:16 PM Allen Robinson
<[email protected]> wrote:
>
>
>
> On Sun, Apr 20, 2025, 6:02 a.m. Dave Crocker <[email protected]> wrote:
>>
>> On 4/20/2025 11:02 AM, Eliot Lear wrote:
>>
>> What system actually does this?  Following the first method in Section 3.6.3 
>> of RFC 5322 and a practice that goes as far back as RFC 822, Neither 
>> Sendmail nor GMail, for instance, retain the BCC field in the message.  Is 
>> this a matter of tracing how a message got exploded (say, when a mailing 
>> list was Bcc'd)?
>>
>>
>> sigh.  Haven't looked at the behavior of this in quite a few years.  Your 
>> note prompted my doing some testing and, alas, all the combinations I tried 
>> produced received messages having no BCC field.
>>
>> Sad.
>>
>> I noted why it is good to have the field visible to a BCC recipient. And why 
>> I think the ideal is that their copy show their address in it.
>
> Slightly off-topic, but it's interesting to me. How were you testing this 
> through Gmail? Using the android app to send an email with BCC seems to work 
> the way you expect it to, with a Bcc field present in the message delivered 
> to that recipient.

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.

Francesco

>>
>> 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]
>
> _______________________________________________
> Ietf-dkim mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to