Decoding Accepted Domains in Exchange Server & Exchange Online

In the world of Exchange Server and Exchange Online, managing email flow effectively hinges on understanding accepted domains. These domains define how your Exchange organization handles email for specific SMTP namespaces. Getting this right is crucial for proper mail routing, preventing NDRs (Non-Delivery Reports), and ensuring a seamless user experience.

There are three primary types of 𝗮𝗰𝗰𝗲𝗽𝘁𝗲𝗱 𝗱𝗼𝗺𝗮𝗶𝗻𝘀, each serving a distinct purpose:

1️⃣𝗪𝗲 𝗛𝗮𝗻𝗱𝗹𝗲 𝗔𝗹𝗹 𝗼𝗳 𝗜𝘁 (𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗗𝗼𝗺𝗮𝗶𝗻):

✅𝗜𝗻 𝗦𝗶𝗺𝗽𝗹𝗲 𝗧𝗲𝗿𝗺𝘀: This is your organization's primary email domain (or domains). Think of it as the official address for all your users' mailboxes within your Exchange environment.

✅𝗛𝗼𝘄 𝗶𝘁 𝗪𝗼𝗿𝗸𝘀: Exchange assumes responsibility for every email address within an authoritative domain. If a message arrives for a recipient in this domain, Exchange expects to find a corresponding mailbox. If no such mailbox exists, the sender typically receives an NDR.

✅𝗞𝗲𝘆 𝗖𝗵𝗮𝗿𝗮𝗰𝘁𝗲𝗿𝗶𝘀𝘁𝗶𝗰: Recipient Lookup (AddressBookEnabled) is usually enabled by default. Why? Because all recipients are internal, it makes it easy for users to find each other in the Global Address List (GAL).

✅𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Imagine "Global Innovations" uses globalinnovations.com as their primary email domain. All employees have email addresses ending in @globalinnovations.com, and their mailboxes reside within Global Innovations' Exchange Online tenant. When someone emails sales@globalinnovations.com, Exchange looks within its organization for that mailbox. If support@globalinnovations.com doesn't exist as a mailbox, the sender will get a bounce-back.

✅𝗨𝘀𝗲 𝗖𝗮𝘀𝗲: This is the most common configuration for an organization's main email domain(s).

2️⃣𝗪𝗲 𝗛𝗮𝗻𝗱𝗹𝗲 𝗦𝗼𝗺𝗲 𝗼𝗳 𝗜𝘁 (𝗜𝗻𝘁𝗲𝗿𝗻𝗮𝗹 𝗥𝗲𝗹𝗮𝘆 𝗗𝗼𝗺𝗮𝗶𝗻):

✅𝗜𝗻 𝗦𝗶𝗺𝗽𝗹𝗲 𝗧𝗲𝗿𝗺𝘀: This type of domain is used when your Exchange organization hosts some, but not all, of the mailboxes for a particular SMTP namespace. Some recipients are internal, while others reside in a separate email system (often still within your control).

✅𝗛𝗼𝘄 𝗶𝘁 𝗪𝗼𝗿𝗸𝘀: Exchange accepts emails for recipients in an internal relay domain. It first attempts to deliver the message to a local mailbox. If the recipient isn't found internally, Exchange will then relay the message to another email server that you've specified (via a Send Connector).

✅𝗞𝗲𝘆 𝗖𝗵𝗮𝗿𝗮𝗰����𝗲𝗿𝗶𝘀𝘁𝗶𝗰: Recipient Lookup (AddressBookEnabled) is typically disabled by default. However, you can enable it if you've created Mail Contacts or Mail Users within your Exchange environment to represent all the external recipients in this domain. This allows internal users to see these external addresses in the GAL.

✅𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Consider "Tech Solutions Inc." acquiring "Creative Marketing Ltd." Creative Marketing still uses creativemarketing.net for some of its employees who haven't been fully migrated to Tech Solutions' techsolutions.com Exchange Online environment. Tech Solutions configures creativemarketing.net as an Internal Relay Domain. If a Tech Solutions employee emails info@creativemarketing.net, Exchange first checks for a local mailbox. If it doesn't find one, it forwards the email to the mail servers still handling creativemarketing.net mailboxes.

✅𝗨𝘀𝗲 𝗖𝗮𝘀𝗲𝘀: Common during mergers, acquisitions, or when an organization shares an SMTP namespace with another internal email system.

3️⃣𝗪𝗲 𝗝𝘂𝘀𝘁 𝗦𝗲𝗻𝗱 𝗜𝘁 𝗢𝗻 (𝗘𝘅𝘁𝗲𝗿𝗻𝗮𝗹 𝗥𝗲𝗹𝗮𝘆 𝗗𝗼𝗺𝗮𝗶𝗻):

✅𝗜𝗻 𝗦𝗶𝗺𝗽𝗹𝗲 𝗧𝗲𝗿𝗺𝘀: Your Exchange organization accepts email for this domain but doesn't host any mailboxes for it. All recipients for this domain exist entirely outside your Exchange environment.

✅𝗛𝗼𝘄 𝗶𝘁 𝗪𝗼𝗿𝗸𝘀: Exchange accepts the incoming mail and immediately relays all messages for this domain to an external email server that you've configured through a Send Connector.

✅𝗞𝗲𝘆 𝗖𝗵𝗮𝗿𝗮𝗰𝘁𝗲𝗿𝗶𝘀𝘁𝗶𝗰: Recipient Lookup (AddressBookEnabled) should never be enabled for an external relay domain, as there are no local recipients.

✅𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 (𝗛𝘆𝗽𝗼𝘁𝗵𝗲𝘁𝗶𝗰𝗮𝗹 𝗳𝗼𝗿 𝗢𝗻-𝗣𝗿𝗲𝗺𝗶𝘀𝗲𝘀 𝗘𝘅𝗰𝗵𝗮𝗻𝗴𝗲): Imagine an ISP, "ConnectNow," hosts email for a small business, "LocalBakes," which uses the domain localbakes.org. ConnectNow might configure localbakes.org as an External Relay Domain on their Exchange server. When someone emails orders@localbakes.org, ConnectNow's Exchange accepts it and immediately forwards it to LocalBakes' actual mail server.

✅𝗨𝘀𝗲 𝗖𝗮𝘀𝗲𝘀: Less common for typical organizations. Might be used by ISPs hosting email for clients or when an organization needs to route specific domain traffic through their infrastructure for filtering before final delivery by another system.

📢𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗡𝗼𝘁𝗲 𝗳𝗼𝗿 𝗘𝘅𝗰𝗵𝗮𝗻𝗴𝗲 𝗢𝗻𝗹𝗶𝗻𝗲: External Relay Domains are not supported in 𝗘𝘅𝗰𝗵𝗮𝗻𝗴𝗲 𝗢𝗻𝗹𝗶𝗻𝗲. If you need to relay email to an external domain where you have no mailboxes, you'll configure an Outbound Connector to route the mail directly to the recipient domain's MX records or a smart host. The accepted domain in your Microsoft 365 tenant would then be configured as either Authoritative or Internal Relay, depending on whether you have any mailboxes within your tenant for that domain.

#ExchangeServer #ExchangeOnline #Microsoft365 #EmailManagement #AcceptedDomains #MailFlow #ITAdmin #TechTips