By default, the IMTA is expected to be able to resolve an address of the form user@xzy.com, where xzy.com is the mail domain name. To resolve addresses, the IMTA constructs an alias cache containing all users in the domain xzy.com via alias synchronization.
It may be useful to change the routability scope of the alias cache in the following cases:
|
|
When the directory is not populated with the entire domain. |
|
|
To limit the size of the alias cache |
|
|
To enforce routing policies. For example, if all mail going outside of the domain must be forwarded by a specific set of IMTAs. |
The routability scope is the group of addresses to which the IMTA can route directly (send directly to the user's delivery mail store) or to which it can deliver locally.
This section explains how to set the routability scope to one of following:
|
|
Nobody - Indicates that the mail server does not support a user community. This setup is typical if your mail server is a backbone IMTA that routes messages between domains. It does not know of each mail user, but uses the host or domain specifications to forward the message to the appropriate mail server for delivery. For example, if a message is sent to user@eng.alpha.com, the IMTA knows to forward this message to mailhost.eng.alpha.com. Similarly, it can forward a message addressed to user@qa.eng.alpha.com to mailhost.qa.eng.alpha.com. |
|
|
Local system users only - The IMTA can deliver messages to local users only. The IMTA cannot deliver to non-local users. If a message arrives that is not addressed to a local user and the To: envelope address is not canonical and fully qualified (that is, it does not specify the address's information as user@host.domain), the IMTA forwards it to a specified smart host. The smart host is more likely to be able to forward the message to the recipient's mail server. |
|
|
Mail server domains - The IMTA can route messages within its internet domain or to a specified set of domains. The mail server can forward a message to the recipient's mail server if the recipient belongs to one of the specified domains. The advantage of specifying this routability scope is that it reduces network hops by sending messages directly to the appropriate mailserver, rather than sending them to a smart host. A disadvantage may be the requirement for the directory to contain one entry for each valid mail user in the domains. |
|
|
Entire mail network - The IMTA can route messages to local users and to users that it knows about through replicated directory information that exists on this particular mail server. |
Modifying the routability scope modifies the way the IMTA persistent alias cache is created and modifies the IMTA rewrite rules. If the routability scope is set to domains, you must specify which domain(s) in "To Configure Mail Server Domains" on page 116. Generally, it is recommended that you list all domains shared by users within the routability scope.
 |
To Configure Routability Scope
|
|
AdminConsole>IMTA>Routability Scope
|
| |
1. |
From the Sections list of the IMTA property book, click Routability Scope. |
FIGURE 4-8 Routability Scope Section
| |
2. |
Select the portion of the mail network to which the IMTA can route using the pull-down menu. |
| |
3. |
If you selected the Mail Server Domains option, then make certain that mail server domains are configured, add domains to the Mail Server Domain list, or modify the existing list. |
| |
4. |
Click the Apply button. |
| |
To Configure Mail Server Domains
|
If you specified the Mail Server Domain option in the Routability Scope section of the IMTA property book as described in "Routability Scope" on page 114, you must configure a list of mail server domains to which your IMTA can route messages. Your list can include as many Internet domains as desired.
|
AdminConsole>IMTA>Mail Server Domains
|
| |
1. |
From the Sections list of the IMTA property book, click Mail Server Domains. |
| |
|
The Mail Server Domains section appears in FIGURE 4-9. |
FIGURE 4-9 Mail Server Domain Section
| |
2. |
To add a mail server domain to the list, enter the name in the Mail Server Domains field. |
| |
|
For example, if you want your IMTA to route messages to the sales.bravo.com domain, then enter the following: |
| |
|
The mail server domain name appears in the list. |
| |
4. |
To delete a mail server domain from the list, you can either click on the domain name in the list to highlight it then click the delete button, or enter the domain in the Mail Server Domains field and click the delete button. |
| |
5. |
Click the Apply button. |
Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.