3476368 - Using a BCC Header On Cloud for Customer

You want to use a custom BCC Header on Emails.

SAP Cloud for Customer

When you hit "send" in your email client, it talks to the mail server using a protocol called SMTP (Simple Mail Transfer Protocol). The SMTP protocol doesn’t actually know or care about To, CC, or BCC fields – it just wants a list of recipients, in this Case, all the addresses from the To, CC, and BCC fields are combined. 

The email client issues an SMTP `RCPT TO:` command for each recipient — regardless if they were in To, CC, or BCC.
As a result, when the message is in transit, there’s no distinction between who was To, CC, or BCC from the perspective of the server or the protocol.

As a workaround, you could include a custom header (such as `BCC_HEADER`) in the email message that lists, for example, the addresses that were BCCed.
This way, when someone (or an automated process) receives or processes the message, they can detect BCC recipients from this custom header.

However, you should not use this workaround for general emails if you truly want to keep BCCs secret. Adding a BCC header defeats privacy, because anyone who receives the message can see those addresses.
This method is only suitable if all recipients are trusted, or you’re using it internally (for example, automated processing within a company’s mail system or for logging purposes).

KBA , LOD-CRM-SRP , Service Request Processing , Problem