)
Figure 2-3 One domain, two networks, a router, and multiple uucp connections.
| Previous | Table of Contents | Next |
The mail configuration shown in Figure 2-3 has one domain, two networks, and a router. In this configuration, the mail server, the mailhost, and the relay host (or hosts) are likely to be different systems. To make administering and distributing mail easier, a naming service is used.
Figure 2-3 One domain, two networks, a router, and multiple uucp connections.
To set up this kind of mail configuration (assuming that the mail clients may have local or remote /var/mail files), you need everything that is specified in Table 2-1.
| Category | Requirements |
|---|---|
| Relay host | The main.cf file on the relay hosts--the systems with uucp connections. You must edit the file to select a major relay connector. You may want to define a mail relay host that knows about all of the connections. Special rules added to the sendmail.cf file are a good idea but are not mandatory. |
| Mailhost | One system that is designated as the mailhost. (Add mailhost to the Hosts database on the mailhost system.) |
| Mail server | Adequate spooling space for client mailboxes. |
| Mail client | The subsidiary.cf file on each mail client system (no editing required). Entries in each mail client's /etc/vfstab file to mount the /var/mail directory. |
| NIS+ tables | mail_aliases.org_dir tables for NIS+ with a mail alias entry for all of the users to point to where their mail is stored. |
The mail configuration shown in Figure 2-4 has two domains and a gateway. In this configuration, the mail server, the mailhost, and the relay host (or hosts) for each domain are likely to be different systems. To make administering and distributing mail easier, a naming service is used.
)
Figure 2-4 Two domains with a gateway.
Table 2-2 lists the requirements for this mail configuration.
| Category | Requirements |
|---|---|
| Gateway | Complex gateway systems usually need a customized sendmail.cf file with special rules added. |
| Relay host | The main.cf file on the relay hosts--the systems with uucp connections. (You must edit the file to select a major relay mailer.) It might be useful to define a mail relay host that knows about all of the connections. (Special rules added to the sendmail.cf file are a good idea but are not mandatory.) |
| Mailhost | One system designated as the mailhost. (Add mailhost to the Hosts database on the mailhost system.) |
| Mail server | Adequate spooling space for client mailboxes. |
| Mail client | The sendmail.cf file on each mail client system (no editing required). Entries in each mail client's /etc/vfstab file to mount the /var/mail directory. |
| NIS+ tables | mail_aliases.org_dir tables for NIS+ with a mail alias entry for each user to point to the NIS+ tables. |
NOTE: The subsidiary.cf file has an entry (the CV class) that you can use to define “local” uucp connections (such as the system at the left of Domain 1 in Figure 2-4). If you define such a local uucp connection, users must address mail using the format uucphost!remote-system!address.
| Previous | Table of Contents | Next |
){kind=link}
){kind=link}