Managing the Hub Transport Server Role • Chapter 6 327 E-mail Address Policies E-mail address policies were known as recipient policies back in Exchange 2000 and 2003. Exchange address policies defi ne the proxy addresses stamped onto recipient objects in the Exchange organization. With Exchange 2007, the recipient policies have been separated into two types: accepted domains (which we just covered) and e-mail address policies. Those of you with Exchange 2000 and/or 2003 experience know that recipient policies also controlled which SMTP namespaces were accepted by the Exchange organization. Some of you probably are wondering why these two features were separated in Exchange 2007. The Exchange Product group made this separation for three chief reasons. First, if a domain was specifi ed for an e-mail address recipient policy but wasn’t confi gured as the authoritative domain, the e-mail sent to the recipients with e-mail addresses defi ned by the policy would not be routed within the Exchange organization for this domain. Even though this is an invalid scenario, the Exchange 2000 and 2003 System Manager allowed this type of confi guration. Secondly, the authoritative domain concept was hidden under the e-mail address recipient policy GUI, which wasn’t very intuitive for administrators. Lastly, relay domains were controlled via the SMTP connectors GUI, allocated in a completely different location from where the authoritative domains (recipient policies) were controlled. TIP To create an accepted domain entry via the Exchange Management Shell, you need to use the New-AcceptedDomain cmdlet. For example, to create an accepted domain entry similar to the one we created in Figure 6.7, you would need to run the following command: New-AcceptedDomain –Name “Exchange-faq” –DomainName “exchange-faq.dk” –DomainType “Authoritative” SOME INDEPENDENT ADVICE This separation of accepted domain and e-mail address policies is not the only change in regards to e-mail address policies. The infamous Recipient Update Service (RUS), which most of us know from Exchange 2000 and 2003, is also no longer part of the Exchange 2007 product. RUS was responsible for stamping e-mail addresses on AD objects, in addition to address list membership, and a few other things. However, it didn’t always work as expected and was very diffi cult to troubleshoot when it acted up. With Exchange 2007, the RUS (and thereby the asynchronous behavior used to provision objects) has been replaced by a new synchronous process (the EmailAddressPolicy cmdlet), which is used to stamp e-mail address onto objects immediately! Yes, you no longer have to wait for several minutes to see e-mail addresses on your objects, as was often the case with the antiquated RUS. 328 Chapter 6 • Managing the Hub Transport Server Role Okay, so to carve it in stone, before you begin creating a new e-mail address policy, you must fi rst add the respective domain name under the Accepted Domains tab. As you can see in Figure 6.8, 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 2000 and 2003. If you want to move a particular policy up the list, highlight the policy and click Change Priority in the Action pane. You must have at least two EAPs aside from the default in order to see the Change Priority Action pane option. Figure 6.8 A Prioritized List of the E-mail Address Policies in the Organization For a detailed explanation about the removal of RUS, see the following blog on the MS Exchange Team blog: http://msexchangeteam.com/archive/2006/10/02/ 429053.aspx Managing the Hub Transport Server Role • Chapter 6 329 Figure 6.9 The New E-Mail Address Policy Window Creating a New E-mail Address Policy Creating a new e-mail address policy is a straightforward task, although much different from Exchange 2000 and 2003. In order to do so, perform the following steps: 1. Click New E-mail Address Policy in the Action pane. 2. On the Introduction page of the New E-Mail Address Policy wizard, enter a name for the new policy, and then specify what type of recipients should be included (Figure 6.9). Afterward, click Next. 330 Chapter 6 • Managing the Hub Transport Server Role Figure 6.10 The New E-Mail Address Wizard Conditions Page 3. You can now be a bit more selective when defi ning your target group by using the fi lter and selecting one or more conditions, as shown in Figure 6.10. When you have confi gured any conditions you want applied to the policy, click Next. Managing the Hub Transport Server Role • Chapter 6 331 Figure 6.11 Specifying the Local Part of the E-mail Addresses and the E-mail Address Domain 4. Click Add and select the E-mail address local part to be used to create the username portion of the e-mail address. Then, choose an e-mail domain from the E-mail address domain in the drop-down box, as shown in Figure 6.11. When ready, click OK and Next. . separated into two types: accepted domains (which we just covered) and e-mail address policies. Those of you with Exchange 2000 and/ or 2003 experience know that recipient policies also controlled. following command: New-AcceptedDomain –Name “Exchange-faq” –DomainName “exchange-faq.dk” –DomainType “Authoritative” SOME INDEPENDENT ADVICE This separation of accepted domain and e-mail address. Exchange 2000 and 2003, is also no longer part of the Exchange 2007 product. RUS was responsible for stamping e-mail addresses on AD objects, in addition to address list membership, and a few other