<div>
Just to clarify,<br />
<br />
instead of adding each user individually, can we do this by selecting a spreadsheet, and everyone who is member of that spreadsheet will be applied that transport rule?<br />
<br />
Just to clarify, all external outgoing email communication for the provided users &nbsp;on the spreadsheet will be BCC to the centralized mailbox
</div>


Just to clarify,

instead of adding each user individually, can we do this by selecting a spreadsheet, and everyone who is member of that spreadsheet will be applied that transport rule?

Just to clarify, all external outgoing email communication for the provided users  on the spreadsheet will be BCC to the centralized mailbox

<div>
Sorry, I will get back to this question tomorrow tied up at the moment.<br />
<br />
Will.
</div>


Sorry, I will get back to this question tomorrow tied up at the moment.

Will.

<div>
<div class="content wysiwyg-content">
Hi Team,<br />
<br />
I have a client who has the following request:<br />
<br />
<br />
Need to BCC all emails from specific email accounts to a centralized email account. &nbsp;This is for QA purposes.<br />
<br />
About 300 user accounts.<br />
<br />
<br />
Can this be achieved by using transport rules?<br />
<br />
If so, can you please provide instruction step by step with tons of screenshots?<br />
<br />
Any service impact?<br />
<br />
What are the best practices for requests like this?<br />
<br />
Our exchange version is 2013<br />
<br />
multiple MBX servers in a DAG <br />
<br />
Multiple CAS servers behind a F5 HLB
</div>
</div>


Hi Team,

I have a client who has the following request:


Need to BCC all emails from specific email accounts to a centralized email account.  This is for QA purposes.

About 300 user accounts.


Can this be achieved by using transport rules?

If so, can you please provide instruction step by step with tons of screenshots?

Any service impact?

What are the best practices for requests like this?

Our exchange version is 2013

multiple MBX servers in a DAG 

Multiple CAS servers behind a F5 HLB

transport rule

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.