Target Skills:
Ability to configure Routing Table entries.
Ability to Specify an Address Completion Domain.
Ability to Specify Local Domains. |
|
Important SMTP Settings
There are three important SMTP service settings that we will discuss
in more detail.
This is one of the most useful configurations you can set, and we will
do it in the exercise on the following pages. You can use the SMTP
routing table to determine how the Messaging Server will route non-local
messages. This is useful for forcing certain addresses to take unique
routes through your network. The server processes the table entries
in sequential order.
The format for an entry is:
recipient_address_domain:server_to_route_to
The following example routes all internal mail through a hub server:
*.airius.com:hub.airius.com
The next example forces the use of IP addresses for frequently called servers
(bypassing DNS):
hub.airius.com:[205.117.238.276]
The next example shows the use of a firewall server for all outside mail:
*airius.com:*
*:firewall.airius.com
If the Messaging Server receives a message that does not contain a domain
name in the recipient address, it will add the domain name to the address
to complete the address. You can specify the domain name to be used for
address completion. If you do not specify a domain, the domain name of
the machine on which the Messaging Server resides (the default domain)
is used to complete the address.
It is very important, especially if you use virtual domains, to specify
the local domains your messaging server should recognize. A domain
is local to your server if the Messaging Server knows the recipient addresses
in the domain. If a message is sent to a local domain, but the recipient
cannot be found in the directory, the Messaging Server will bounce the
message. Otherwise, the server will either deliver the message to a local
mailbox or route the message to another server. A common configuration
mistake is not setting local domains properly. |