Interactions of `sendmail` With Name Services

This section describes domain names as they apply to sendmail and name services, as well as the rules for effective use of name services, and the specific interactions of sendmail with name services. For details, refer to the following topics.

If you are looking for related task information, refer to "How to Use DNS With sendmail" or "Administering Mail Alias Files (Task Map)" in Chapter 25, Mail Services (Tasks).

`sendmail.cf` and Mail Domains

The standard sendmail.cf file uses mail domains to determine whether mail is delivered directly or through a mail host. Intradomain mail is delivered through a direct SMTP connection, while interdomain mail is forwarded to a mail host.

In a secure network, only a few selected hosts are authorized to generate packets that are targeted to external destinations. Even if a host has the IP address of the remote host that is external to the mail domain, the establishment of an SMTP connection is not guaranteed. The standard sendmail.cf assumes the following.

The current host is not authorized to send packets directly to a host outside the mail domain.
The mail host is capable of forwarding the mail to an authorized host that can transmit packets directly to an external host. Actually, the mail host can itself be an authorized host.

With these assumptions, the mail host is responsible for delivering or forwarding interdomain mail.

`sendmail` and Name Services

sendmail imposes various requirements on name services. To improve your understanding of these requirements, this section first describes the relationship of mail domains to name service domains. Then the section describes the various requirements. Refer to the following.

"Mail Domains and Name Service Domains"
"Host Name Service Data"
Man pages for in.named(1M), nis+(1), nisaddent(1M), and nsswitch.conf(4)

Mail Domains and Name Service Domains

The mail domain name must be a suffix of the name service domain. For example, if the domain name of the name service is A.B.C.D, the mail domain name could be one of the following.

A.B.C.D
B.C.D
C.D
D

When first established, the mail domain name is often identical to the name service domain. As the network grows, the name service domain can be divided into smaller pieces to make the name service more manageable. However, the mail domain often remains undivided to provide consistent aliasing.

Host Name Service Data

This section describes the requirements that sendmail imposes on name services.

A host table or map in a name service must be set up to support three types of gethostbyname() queries.

mailhost - Some name service configurations satisfy this requirement automatically.
Full host name (for example, smith.admin.acme.com) - Many name service configurations satisfy this requirement.
Short host name (for example, smith) - sendmail must connect to the mail host in order to forward external mail. To determine if a mail address is within the current mail domain, gethostbyname() is invoked with the full host name. If the entry is found, the address is considered internal.

NIS, NIS+, and DNS support gethostbyname() with a short host name as an argument, so this requirement is automatically satisfied.

Two additional rules about the host-name service need to be followed to establish efficient sendmail services within a name service.

gethostbyname() with full host-name argument and short host-name argument should yield consistent results. For example, gethostbyname(smith.admin.acme.com) should return the same result as gethostbyname(smith), as long as both functions are called from the mail domain admin.acme.com.
For all name service domains under a common mail domain, gethostbyname() with a short host name should yield the same result. For example, if the mail domain smith.admin.acme.com is given, gethostbyname(smith) should return the same result when the call originates from either the ebb.admin.acme.com domain or the esg.admin.acme.com domain. The mail domain name is usually shorter than the name service domain, which gives this requirement special implications for various name services.

For more information about the gethostbyname() function, refer to the gethostbyname(3NSL) man page.

Interactions of NIS and `sendmail`

The following list describes the interactions of sendmail and NIS and provides some guidance.

Mail domain name - If you are setting up NIS as the primary name service, sendmail automatically strips the first component of the NIS domain name and uses the result as the mail domain name. For example, ebs.admin.acme.com becomes admin.acme.com.
Mail host name - You must have a mailhost entry in the NIS host map.
Full host names - The normal NIS setup does not "understand" the full host name. Rather than trying to make NIS understand the full host name, turn off this requirement from the sendmail side by editing the sendmail.cf file and replacing all occurrences of %l with %y. This change turns off sendmail's interdomain mail detection. If the target host can be resolved to an IP address, a direct SMTP delivery is attempted. Ensure that your NIS host map does not contain any host entry that is external to the current mail domain. Otherwise, you need to further customize the sendmail.cf file.
Matching full and short host names - Follow the previous instructions on how to turn off gethostbyname() for a full host name.
Multiple NIS domains in one mail domain - All NIS host maps under a common mail domain should have the same set of host entries. For example, the host map in the ebs.admin.acme.com domain should be the same as the host map in the esg.admin.acme.com. Otherwise, one address might work in one NIS domain, but fail in the other NIS domain.

For task information, refer to "Administering Mail Alias Files (Task Map)" in Chapter 25, Mail Services (Tasks).


26. Mail Services (Reference) Mail Addresses and Mail Routing


	Interactions of `sendmail` With Name Services This section describes domain names as they apply to `sendmail` and name services, as well as the rules for effective use of name services, and the specific interactions of `sendmail` with name services. For details, refer to the following topics. "`sendmail.cf` and Mail Domains" "`sendmail` and Name Services" "Interactions of NIS and `sendmail`" "Interactions of `sendmail` With NIS and DNS" "Interactions of NIS+ and `sendmail`" "Interactions of `sendmail` With NIS+ and DNS" If you are looking for related task information, refer to "How to Use DNS With `sendmail`" or "Administering Mail Alias Files (Task Map)" in Chapter 25, Mail Services (Tasks). `sendmail.cf` and Mail Domains The standard `sendmail.cf` file uses mail domains to determine whether mail is delivered directly or through a mail host. Intradomain mail is delivered through a direct SMTP connection, while interdomain mail is forwarded to a mail host. In a secure network, only a few selected hosts are authorized to generate packets that are targeted to external destinations. Even if a host has the IP address of the remote host that is external to the mail domain, the establishment of an SMTP connection is not guaranteed. The standard `sendmail.cf` assumes the following. The current host is not authorized to send packets directly to a host outside the mail domain. The mail host is capable of forwarding the mail to an authorized host that can transmit packets directly to an external host. Actually, the mail host can itself be an authorized host. With these assumptions, the mail host is responsible for delivering or forwarding interdomain mail. `sendmail` and Name Services `sendmail` imposes various requirements on name services. To improve your understanding of these requirements, this section first describes the relationship of mail domains to name service domains. Then the section describes the various requirements. Refer to the following. "Mail Domains and Name Service Domains" "Host Name Service Data" Man pages for `in.named`(1M), `nis+`(1), `nisaddent`(1M), and `nsswitch.conf`(4) Mail Domains and Name Service Domains The mail domain name must be a suffix of the name service domain. For example, if the domain name of the name service is `A.B.C.D`, the mail domain name could be one of the following. `A.B.C.D` `B.C.D` `C.D` `D` When first established, the mail domain name is often identical to the name service domain. As the network grows, the name service domain can be divided into smaller pieces to make the name service more manageable. However, the mail domain often remains undivided to provide consistent aliasing. Host Name Service Data This section describes the requirements that `sendmail` imposes on name services. A host table or map in a name service must be set up to support three types of `gethostbyname()` queries. `mailhost` - Some name service configurations satisfy this requirement automatically. Full host name (for example, `smith.admin.acme.com`) - Many name service configurations satisfy this requirement. Short host name (for example, `smith`) - `sendmail` must connect to the mail host in order to forward external mail. To determine if a mail address is within the current mail domain, `gethostbyname()` is invoked with the full host name. If the entry is found, the address is considered internal. NIS, NIS+, and DNS support `gethostbyname()` with a short host name as an argument, so this requirement is automatically satisfied. Two additional rules about the host-name service need to be followed to establish efficient `sendmail` services within a name service. `gethostbyname()` with full host-name argument and short host-name argument should yield consistent results. For example, `gethostbyname(smith.admin.acme.com)` should return the same result as `gethostbyname(smith)`, as long as both functions are called from the mail domain `admin.acme.com`. For all name service domains under a common mail domain, `gethostbyname()` with a short host name should yield the same result. For example, if the mail domain `smith.admin.acme.com` is given, `gethostbyname(smith)` should return the same result when the call originates from either the `ebb.admin.acme.com` domain or the `esg.admin.acme.com` domain. The mail domain name is usually shorter than the name service domain, which gives this requirement special implications for various name services. For more information about the `gethostbyname()` function, refer to the `gethostbyname`(3NSL) man page. Interactions of NIS and `sendmail` The following list describes the interactions of `sendmail` and NIS and provides some guidance. Mail domain name - If you are setting up NIS as the primary name service, `sendmail` automatically strips the first component of the NIS domain name and uses the result as the mail domain name. For example, `ebs.admin.acme.com` becomes `admin.acme.com`. Mail host name - You must have a `mailhost` entry in the NIS host map. Full host names - The normal NIS setup does not "understand" the full host name. Rather than trying to make NIS understand the full host name, turn off this requirement from the `sendmail` side by editing the `sendmail.cf` file and replacing all occurrences of `%l` with `%y`. This change turns off `sendmail`'s interdomain mail detection. If the target host can be resolved to an IP address, a direct SMTP delivery is attempted. Ensure that your NIS host map does not contain any host entry that is external to the current mail domain. Otherwise, you need to further customize the `sendmail.cf` file. Matching full and short host names - Follow the previous instructions on how to turn off `gethostbyname()` for a full host name. Multiple NIS domains in one mail domain - All NIS host maps under a common mail domain should have the same set of host entries. For example, the host map in the `ebs.admin.acme.com` domain should be the same as the host map in the `esg.admin.acme.com`. Otherwise, one address might work in one NIS domain, but fail in the other NIS domain. For task information, refer to "Administering Mail Alias Files (Task Map)" in Chapter 25, Mail Services (Tasks).

Interactions of sendmail With Name Services

sendmail.cf and Mail Domains