Article ID: 2653006 - Last Review: December 27, 2011 - Revision: 2.0

How Exchange Hosted Archive handles blind carbon copy (Bcc) recipients

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

On This Page

Expand all | Collapse all

SUMMARY

This article describes how Microsoft Exchange Hosted Archive (EHA) handles email messages for blind carbon copy (Bcc) recipients.
Back to the top

MORE INFORMATION

Journaling types

There are three kinds of journaling in EHA:
  • Message-only journaling

    Message-only journaling captures all messages from users on a specific mailbox database and sends a copy of the message to a specified journal mailbox. By default, when message-only journaling is enabled, Microsoft Exchange Server does not account for Bcc recipients, recipients from transport forwarding rules, or recipients from distribution group expansions.
  • Bcc journaling

    Bcc journaling is the same as message-only journaling but has the added ability to capture Bcc recipients. When Bcc journaling is enabled, Exchange Server captures all recipients (To, Cc, Bcc). If this recipient list includes hidden distribution lists, query-based distribution lists or distribution lists that are expanded on another server, the recipients for these lists are not included in the journaled mail. This functionality is enabled by setting a registry subkey.
  • Envelope journaling

    Envelope journaling differs from message-only journaling and Bcc journaling because envelope journaling enables you to archive transport envelope information (P1 message headers). This includes information about the recipients who actually received the message. This information includes Bcc recipients and recipients from distribution groups.
Back to the top

Which type is best for you?

For compliance purposes, we recommend that you enable envelope journaling to make sure that both the Bcc recipients and the recipients from distribution groups are captured. This is only a recommendation. The kind of journaling that you enable depends on your organization, the compliance needs of your organization, and your environment.

Important Contact your compliance officer or expert to determine the kind of journaling that is appropriate for your organization.
Back to the top

Scenarios

The following scenarios are examples of how the behavior of Bcc recipients differs, depending on the kind of journaling that is selected by an organization.

Note The following table explains the terms that the example scenarios use.
Collapse this tableExpand this table
Term DefinitionExample
Internal emailAn email message that is sent within your organizationUser1@contoso.com to User2@contoso.com
External outgoing (also known as "outbound")An email message that is sent outside your organizationUser1@contoso.com to UserName@hotmail.com
External incoming (also known as "inbound")An incoming email message that is sent from another organizationUserName@hotmail.com to User1@contoso.com
Internal Bcc recipientA person in your organization who is in the Bcc list of an email messageTo: User1@contoso.com
Cc:
Bcc: User2@contoso.com
External Bcc recipient

A person in another organization who is in the Bcc list of an email messageTo: User1@contoso.com
Cc:
Bcc: UserName@hotmail.com

Scenario 1

Collapse this tableExpand this table
Service subscribed toKind of journalingKind of emailBcc recipientResult (Is Bcc captured in the archive?)Viewable by
Filtering and archivingMessage-onlyInternalInternalNot captured
External outgoingInternalNot captured
External outgoingExternalIs capturedSender, Supervisor, Compliance Manager

Note Supervisor only sees the external Bcc if the email message that is looked at belongs to a subordinate of the Supervisor.
External incomingInternalIs capturedRecipient, Supervisor, Compliance Manager
External incomingExternalSometimes capturedRecipient, Supervisor, Compliance Manager

Scenario 2

Collapse this tableExpand this table
Service subscribed toKind of journalingKind of emailBcc recipientResult (Is Bcc captured in the archive?)Viewable by
Filtering and archivingBcc or envelope External outgoingInternalIs capturedSender, Compliance Manager
InternalInternalIs capturedSender, Compliance Manager
External outgoingExternalIs capturedSender, Compliance Manager
External incomingInternalIs capturedCompliance Manager
External incomingExternalSometimes captured

Note Whether the Bcc recipient is captured depends on whether the external Bcc recipient receives the email message through the network. If the email message is sent from your network, the message is captured. If the email message goes through an external network, the message is not captured.
Compliance Manager

Scenario 3

Collapse this tableExpand this table
Service subscribed toKind of journalingKind of emailBcc recipientResult (Is Bcc captured in the archive?)Viewable by
Archiving onlyMessage-onlyInternalInternalIs not captured
External outgoingInternalIs not captured
External outgoingExternalIs not captured
External incomingInternalIs not captured
External incomingExternalIs not captured

Scenario 4

Collapse this tableExpand this table
Service subscribed toKind of journalingKind of emailBcc recipientResult (Is Bcc captured in the archive?)Viewable by
Archiving onlyBcc or envelope InternalInternalIs capturedSender, Supervisor, Compliance Manager
External outgoingInternalIs capturedSender, Supervisor, Compliance Manager
External outgoingExternalIs capturedSender, Supervisor, Compliance Manager
External incomingInternalIs capturedSupervisor, Compliance Manager
External incomingExternalBcc is not captured in the Archive.

Note If the external organization that is sending the message subscribes to outgoing filtering, the Bcc recipients are captured.		Supervisor, Compliance Manager

Back to the top
APPLIES TO
  • Microsoft Forefront Online Protection for Exchange
  • Microsoft Exchange Hosted Archive
Back to the top
Keywords: 
vkbportal225 vkbportal230 KB2653006
Back to the top