You need to ensure that all of the email messages sent from the Internet to adatum.com are routed through the contoso.com organization. What should you create in contoso.com? (Each corrects answer presents part of the solution. Choose all that apply.)
A. a contact object for each adatum.com recipient
B. an internal relay accepted domain for adatum.com
C. a Send connector that is configured to point to the contoso.com transport servers
D. a Send connector that is configured to point to the adatum.com transport servers
E. an authoritative accepted domain for adatum.com
Internal Relay Domain
You can configure a relay domain as an internal relay domain or as an external relay domain. These two relay domain types are described in the following sections. When you configure an internal relay domain, some or all of the recipients in this domain don’t have mailboxes in this Exchange organization. Mail from the Internet is relayed for this domain through Transport servers in this Exchange organization. This configuration is used in the scenarios that are described in this section.
An organization may have to share the same SMTP address space between two or more different messaging systems. For example, you may have to share the SMTP address space between Exchange and a third-party messaging system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each email system have the same domain suffix as part of their email addresses.
To support these scenarios, you need to create an accepted domain that’s configured as an internal relay domain. You also need to add a Send connector that’s sourced on a Mailbox server and configured to send email to the shared address space. If an accepted domain is configured as authoritative and a recipient isn’t found in Active Directory, a nondelivery report (NDR) is returned to the sender. The accepted domain that’s configured as an internal relay domain first tries to deliver to a recipient in the Exchange organization. If the recipient isn’t found, the message is routed to the Send connector that has the closest address space match.
If an organization contains more than one forest and has configured global address list (GAL) synchronization, the SMTP domain for one forest may be configured as an internal relay domain in a second forest. Messages from the Internet that are addressed to recipients in internal relay domains are relayed to the Mailbox servers in the same organization. The receiving Mailbox servers then route the messages to the Mailbox servers in the recipient forest. You configure the SMTP domain as an internal relay domain to make sure that email that’s addressed to that domain is accepted by the Exchange organization. The connector configuration of your organization determines how messages are routed.
An accepted domain is any SMTP namespace for which a Microsoft Exchange Server 2013 organization sends or receives email. Accepted domains include those domains for which the Exchange organization is authoritative. An Exchange organization is authoritative when it handles mail delivery for recipients in the accepted domain. Accepted domains also include domains for which the Exchange organization receives mail and then relays it to an email server that’s outside the organization for delivery to the recipient.
2nd part of establishing an internal relay domain is to establish a Send Connector that is configured to point to the other organization’s mail servers (a datum)
Better to establish an internal relay domain. A mail-enabled Active Directory contact that contains information about people or organizations that exist outside the Exchange organization. Each mail contact has an external email address. All messages sent to the mail contact are routed to this external email address.
Need to establish a Send connector to adatum.com not contoso.com
Need to establish an internal relay domain not an authorative accepted domain for adatum.com
Accepted Domains: Exchange 2013 Help
Send Connectors: Exchange 2013 Help