The set of email domains for an organization are the authoritative domains. You can use authoritative domains in email address policies, and Exchange is responsible for generating NDRs for non-existent recipients in authoritative domains.
You configure an accepted domain as a relay domain also known as non-authoritative domain when some or none of the recipients in that domain exist in your Exchange organization for example, partners or subsidiaries.
Exchange isn't responsible for generating NDRs for non-existent recipients in a relay domain. Instead, you configure a Send connector with the address space of the relay domain, and you configure this Send connector to use smart host routing to relay messages to their destination directly or to the next hop.
For more information about creating Send connectors that use smart host routing, see Create a Send connector to route outbound mail through a smart host. You configure a relay domain as an internal relay domain or as an external relay domain. The differences are described in the following list:.
Some of the recipients in the internal relay domain don't exist in the Exchange organization. For example:. Recipients in the internal relay domain can be represented as mail contacts or mail users in the Exchange organization manually created or automatically created by using directory synchronization.
The Send connector that you configure for the internal relay domain is sourced on an internal Mailbox server. Note : By default, you can't configure a Send connector for an internal relay domain on a subscribed Edge Transport server. This Send connector is automatically configured to route mail for all authoritative domains and internal relay domains the address space value is For more information, see Send connectors created automatically by the Edge Subscription.
None of the recipients in the external relay domain exist in the Exchange organization including mail contacts or mail users. For example, your Exchange organization is the central location for accepting Internet email for a group of separate organizations. The Send connector that you configure for the external relay domain is sourced on an Edge Transport server or Internet-facing Mailbox server.
Email address policies assign email addresses to recipients. You need to add an authoritative domain or an internal relay domain before you can use that domain in an email address policy. For more information about email address policies, see Email address policies in Exchange Server.
Recipient filtering on a subscribed Edge Transport server can block messages that are addressed to non-existent recipients in your Exchange organization.
This feature is known as Recipient Lookup. Nathaniel Mon Microsoft Agent. Hi, We suggest that you check the article below to fix this stopped working error in Outlook Microsoft Exchange Add-In is required for various Exchange account features to work.
Keep us posted. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Riptack McCoy. In reply to Nathaniel Mon's post on February 8, You didn't answer the question. What does "Microsoft Exchange Add-In" actually do? Palcouk Volunteer Moderator. In reply to Riptack McCoy's post on May 20, In reply to Palcouk's post on May 20, Nope, not helpful at all Obviously you have no idea what the 'Microsoft Exchange Add-In' does and obviously can't answer a question without being patronizing.
Bump - I have exactly the same question as well. To Palcouk - I use a hotmail account exchange - Outlook seems to work fine without the add-in - The add-in only works when I run Outlook as administrator mode, which is troublesome to do - Hence to reiterate RipTack's question - Do I really need to have Exchange add-in running? This question has not been answered in this thread yet - If so, which functions, so that I can once in a while run it as administrator mode.
To Riptack McCoy - From the description the add-in appears to provide the following: unified messaging i think backward compatability , email permissions calendar availability. In reply to jasonlim's post on August 25, By default the Ex Add-in is enabled. This is pathetic. You can also use it if some recipients exist on your own email servers. However, if recipients exist on your own email servers, you must add your recipients to this Microsoft or Office domain in order to make sure that mail is delivered as expected.
For more information about how to manage your recipients, see these topics:. Internal relay also known as non-authoritative : Recipients for this domain can be in Microsoft or Office or your own email servers. Email is delivered to known recipients in Office or is relayed to your own email server if the recipients aren't known to Microsoft or Office You should not select this option if all of the recipients for this domain are in Microsoft or Office If you select this option, you must create a connector for mail flow from Microsoft or Office to your on-premises email server; otherwise recipients on the domain who are not hosted in Microsoft or Office won't be able to receive mail on your own email servers.
For more information about setting up connectors, see Set up connectors to route mail between Microsoft or Office and your own email servers. This option is required if you enable the subdomain routing option on a domain in order to let email pass through the service and be delivered to any subdomains of your accepted domains.
For more information, see Enable mail flow for subdomains in Exchange Online. You need permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Domains" entry in the Feature permissions in Exchange Online topic. For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts for the Exchange admin center. Having problems?
Ask for help in the Exchange forums. The Accepted domains screen appears.
0コメント