Yes, you no longer have to wait for several minutes to see email addresses on your objects as was often the case with the antiquated RUS.Note: For a detailed explanation about the removal of RUS, read the following post on the MS Exchange Team blog.
As we already talked about, the Hub Transport server can handle messages for a particular domain in several different ways (shown in Figure 2).Choose the desired option and click New and then Finish.First, if a domain was specified for an e-mail address recipient policy, but wasn’t configured as the authoritative domain, the e-mail sent to the recipients with e-mail addresses defined by the policy would not be routed within the Exchange organization for this domain.Even though this is an invalid scenario, the Exchange 20 System Manager allowed this type of configuration.Figure 2: New Accepted Domain Wizard If you'd rather create an Accepted Domain entry using the Exchange Management Shell, you can do so using the New-Accepted Domain cmdlet.
For example, to create an accepted domain entry similar to the one we created in Figure 2, you would need to run the following command: New-Accepted Domain –Name “Exchange-faq” –Domain Name “exchange-faq.dk” –Domain Type “Authoritative”As you can see in Figure 3, we have several E-mail Address Policies in our Exchange 2007 organization, listed in prioritized order (the lower the number, the higher the priority) as was also the case in Exchange 20.
The difference between internal and external relayed domains is that internal relaying simply sends the e-mail messages directly to the e-mail server in the organization.
Messages sent to an external relayed domain will first be delivered to the Edge Transport server in the perimeter network, and from there be routed to the respective external e-mail server on the Internet.
When the first Hub Transport server is deployed in the Exchange 2007 organization, the domain name of the Active Directory Forest root domain is configured as an authoritative domain by default.
Since the Hub Transport server used as an example throughout this article has been installed into an Active Directory Forest named exchangedogfood.dk, this domain name is the authoritative domain for this Exchange 2007 organization by default (Figure 1).
Secondly, the authoritative domain concept was hidden under the e-mail address recipient policy GUI, which wasn’t very intuitive for administrators.