Three services that are used on many networks are file servers, print servers, and mail servers. The purpose of these services and the protocols they are built on is discussed in Chapter 3 . In this section we investigate what information must be passed to the users so that the client systems can be successfully configured, and how the network administrator determines that information.
At a minimum the user needs to know the hostnames of the network file servers. Using the names and the showmount command, the user can determine what filesystems are being offer by the servers and who is permitted to use those filesystems.  Without at least the hostname, the user would have to guess which system offered file service.
A better approach is to give users information that also includes what filesystems are being offered and who should use those filesystems. For example, if the UNIX man pages are made available from a central server, the users should be informed not to install the man pages on their local disk drives and they should be told exactly how to access the centrally supported files.
Whether printers are shared using lp , lpd , or NFS, the basic information needed to configure the print server's clients is the same: the hostname and IP address of the print server, and the name of the printer. Printer security may also require that the user be given a username and password to access the printer.
This is the only information needed to configure the client. However, you probably will want to provide your users with additional information about the features, location and administration of shared printers.
TCP/IP provides the tools you need to create a reliable, flexible electronic mail system. Servers are one of the tools that improve reliability. It is possible to create a peer-to-peer email network in which every end system directly sends and receives its own mail. However, relying on every system to deliver and collect the mail requires that every system be properly administered and consistently up and running. This isn't practical, because many small systems are offline for large portions of the day. Most networks use servers so that only a few systems need to be properly configured and operational for the mail to go through.
The terminology that describes email servers is confusing because all of the server functions usually occur in one computer, and all of the terms are used interchangeably to refer to that system. In this text we differentiate between these functions, but we expect you will do all of these tasks on one UNIX system running sendmail . We use these terms in the following manner:
The mail server is the most important component of a reliable system because it eliminates reliance on the user's system. A centrally controlled, professionally operated server collects the mail regardless of whether or not the end system is operational.
The relay host also contributes to the reliability of the email system. If mail cannot be immediately delivered by the relay host, it is queued and processed later. An end system also queues mail, but if it is shut down no attempts can be made to deliver queued mail until the system is back online. The mail server and the mail relay are operated 24 hours a day.
The design of most TCP/IP email networks is based on the following guidelines:
For their client configurations, provide the users with the hostname and IP address of the mail server and the mail relay. The mail server will also require a username and password for each person.