This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
The blind carbon copy (Bcc) recipients for this message.
Microsoft CDO for Exchange 2000 Library
DLL Implemented In
[Visual Basic]Property BCC As String
[C++]HRESULT get_BCC(BSTR* pVal);
HRESULT put_BCC(BSTR Val);
- Returns the value of the BCC property as a reference to a BSTR.
- Sets the value of the BCC property to the value of the BSTR.
This property is also available as the urn:schemas:mailheader:bcc and urn:schemas:httpmail:bcc fields.
The string in the BCC property can represent a single recipient or multiple recipients. Each address in the list must be a full messaging address, for example,
where User is the friendly name and <UserAddress@example.com> is the actual e-mail address.
Commas separate multiple recipients in the list:
"User1" <User1@example.com>, "User2" <User2@example.com>, "User3" <User3@example.com>
Commas are not used as separators when enclosed in double quotation marks, such as:
"Dan K. Bacon, Jr." <email@example.com>
The friendly name must include the quotation marks in the property; thus, when setting this property, you will need to use double quotation marks or other appropriate techniques to include them.
The following are examples of setting this property:
iMsg.To = " ""Dan K. Bacon, Jr."" <firstname.lastname@example.org>, ""Brenda Diaz"" <email@example.com>"
in Microsoft Visual Basic, or
pMsg->put_To(_bstr_t("\"Dan K. Bacon, Jr.\" <firstname.lastname@example.org>, \"Brenda Diaz\" <email@example.com>"));
In keeping with the privacy intended by blind copies, BCC is regarded as an envelope property rather than a message property. Accordingly, the corresponding header field and its contents are removed when the message is delivered, and you should always expect the BCC property to be empty on a received message.
The default value of BCC is an empty string.