You have an Exchange organization named Contoso, Ltd. All servers in the organization
have Exchange Server 2010 SP1 installed. The organization contains an Edge Transport
Server.
Users from a company named Fabrikam, Inc., send email messages over the Internet by
using the @fabrikam.com email address suffix.
Contoso acquires Fabrikam.
You need to ensure that messages sent from Fabrikam users to Contoso users have the
contoso.com email address suffix in their source address.
What should you create?
A.
an accepted domain
B.
an address rewrite entry
C.
an e-mail address policy
D.
a Receive connector
Explanation:
You use address rewriting to present a consistent appearance to external recipients of
messages from your Exchange 2010 organization. Address rewriting can be valuable to
organizations that use third-party vendors to provide e-mail support and services. Customers
and partners expect e-mail messages to come from the organization, not a third-party
vendor. Similarly, after a merger or acquisition, an organization might want all email
messages to appear to come from the single new organization. The address rewriting
feature frees organizations to structure their businesses by business requirements instead of
by technical requirements or limitations.
You can also use address rewriting to enable appropriate routing of inbound messages from
outside your Exchange 2010 organization to internal recipients. Address rewriting enables
replies to messages that were rewritten to be correctly routed to the original sender of the
rewritten message.
You configure Address Rewriting agents on the Receive connector and Send connector on a
computer that has the Edge Transport server role installed.
EMS:
Enable-TransportAgent -Identity “Address Rewriting Inbound agent”
New-AddressRewriteEntry -name “[email protected] to [email protected]” –
InternalAddress
[email protected] -ExternalAddress [email protected]
http://technet.microsoft.com/en-us/library/aa996806
http://technet.microsoft.com/en-us/library/bb123966.aspx