Sendmail Installation and Operation Guide
SMM:08-9
of the complexity. See cf/README for details.
Our configuration files are processed by m4 to facilitate local customization; the directory cf
of the sendmail distribution directory contains the source files. This directory contains several sub-
directories:
cf
Both site-dependent and site-independent descriptions of hosts. These can be lit-
eral host names (e.g., "ucbvax.mc") when the hosts are gateways or more general
descriptions (such as "generic-solaris2.mc" as a general description of an SMTP-
connected host running Solaris 2.x. Files ending .mc (``M4 Configuration'') are
the input descriptions; the output is in the corresponding .cf file. The general
structure of these files is described below.
domain
Site-dependent subdomain descriptions. These are tied to the way your organiza-
tion wants to do addressing. For example, domain/CS.Berkeley.EDU.m4 is our
description for hosts in the CS.Berkeley.EDU subdomain. These are referenced
using the
DOMAIN
m4
macro in the .mc file.
feature
Definitions of specific features that some particular host in your site might want.
These are referenced using the
FEATURE
m4
macro. An example feature is
use_cw_file (which tells sendmail to read an /etc/mail/local-host-names file on
startup to find the set of local names).
hack
Local hacks, referenced using the
HACK
m4
macro. Try to avoid these. The
point of having them here is to make it clear that they smell.
m4 Site-independent m4(1) include files that have information common to all configu-
ration files. This can be thought of as a "#include" directory.
mailer
Definitions of mailers, referenced using the
MAILER
m4
macro. The mailer types
that are known in this distribution are fax, local, smtp, uucp, and usenet. For
example, to include support for the UUCP-based mailers, use "MAILER(uucp)".
ostype
Definitions describing various operating system environments (such as the loca-
tion of support files). These are referenced using the
OSTYPE
m4
macro.
sh
Shell files used by the m4 build process. You shouldn't hav e to mess with these.
siteconfig
Local UUCP connectivity information. This directory has been supplanted by the
mailertable feature; any new configurations should use that feature to do UUCP
(and other) routing. The use of this directory is deprecated.
If you are in a new domain (e.g., a company), you will probably want to create a cf/domain
file for your domain. This consists primarily of relay definitions and features you want enabled site-
wide: for example, Berkeley's domain definition defines relays for BitNET and UUCP. These are
specific to Berkeley, and should be fully-qualified internet-style domain names. Please check to
make certain they are reasonable for your domain.
Subdomains at Berkeley are also represented in the cf/domain directory. For example, the
domain CS.Berkeley.EDU is the Computer Science subdomain, EECS.Berkeley.EDU is the Electri-
cal Engineering and Computer Sciences subdomain, and S2K.Berkeley.EDU is the Sequoia 2000
subdomain. You will probably have to add an entry to this directory to be appropriate for your
domain.
You will have to use or create .mc files in the cf/cf subdirectory for your hosts. This is
detailed in the cf/README file.
1.3. Details of Installation Files
This subsection describes the files that comprise the sendmail installation.