Exxhange SQL And IIS- P70 ppsx

Figure 6.4 Message Format OptionsCreating a New Remote Domains Entry To create a new Remote Domains entry, click New Remote Domain in the Action pane.. Accepted Domains Under the Accepte

Figure 6.4 Message Format Options

Creating a New Remote Domains Entry

To create a new Remote Domains entry, click New Remote Domain in the Action pane This will

launch the New Remote Domain wizard shown in Figure 6.5 Here, you simply need to enter a name for the new entry, as well as specify the external SMTP domain to which you want to apply the settings

If the domain contains subdomains, you may also want to check Include all subdomains When you have entered the necessary information, click New and then Finish on the completion page.

Notice that you don’t specify the different settings during the creation of the Remote

Domains entry Instead, this is done by opening the Property page of the remote domain entry

after the fact

To create a Remote Domains entry via the Exchange Management Shell, you need to

use the New-RemoteDomain cmdlet For example, to create a remote domain entry

similar to the one we created in Figure 6.5, you would need to run the following command:

New-RemoteDomain –Name “Syngress” –DomainName “*.syngress.com”

Accepted Domains

Under the Accepted Domains tab, we specify the SMTP domains for which our Exchange

2007 organization should either be authoritative, relay to an e-mail server in another Active Directory Forest within the organization, or relay to an e-mail server outside the respective Exchange organization 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 fi rst be delivered to the Edge Transport server in the perimeter network, and from there will be routed to the respective external e-mail server on the Internet

When the fi rst Hub Transport server is deployed in the Exchange 2007 organization, the

domain name of the Active Directory Forest root domain is confi gured as an authoritative domain

by default Since the Hub Transport server 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 6.6) Since we use a split-DNS setup, where the internal and external domain names match, we don’t need to do any confi guration changes after the Hub Transport server has been deployed Many organizations use an internal domain name that differs from the external domain name, which among other things is used for inbound mail For example, it’s common to use a domain.local domain internally If this is the case in your organization, you must manually create an accepted domain matching your external domain name

Creating a New Accepted Domain

Creating a new accepted domain is a straightforward task You simply click New Accepted Domain

in the Action pane In the New Accepted Domain wizard, enter a name for the accepted domain

entry and the domain for which you want to receive e-mail

As we already talked about, the Hub Transport server can handle messages for a particular domain in several different ways, as shown in Figure 6.7 Choose the desired option and click New and then Finish on the next page

NOTE

Any accepted domain that is added under the Accepted Domains tab can be linked

to an E-mail Address Policy (EAP), such that it will generate recipient e-mail addresses for the accepted domain As a matter of fact, every EAP must link to an accepted domain, such that e-mail messages sent to e-mail addresses specifi ed in an EAP are allowed to be routed by the Hub Transport servers in the organization You’ll see what I mean when we cover e-mail address policies next

Figure 6.7 The New Accepted Domain Wizard