Much of the sendmail samples directory is dedicated to the automated
creation of the configuration file. The /usr/lpp/tcpip/samples/sendmail/cf
directory contains a sample.mc file and the subsequent sample.cf configuration
file that was created by running the m4 macro preprocessor on the
sample.mc file. If the /usr/lpp/tcpip/samples/sendmail directory is
examined, the following directory structure can be found:
cd /usr/lpp/tcpip/samples/sendmail
README.m4 TRACEFLAGS feature mailer sh
README.milter TUNING hack milter siteconfig
RELEASE_NOTES cf inetd.conf.pop ostype
SECURITY domain m4 sendmail.ps
- README.m4
- Contains all the latest information regarding this latest version
of sendmail from the www.sendmail.org site.
- README.milter
- This README file describes the steps needed to compile and run
a filter, through reference to a sample filter that is attached at
the end of this file.
- RELEASE_NOTES
- The sendmail release notes.
- SECURITY
- Gives some security-related hints on how to configure and run
sendmail.
- TRACEFLAGS
- Describes the different trace flags used with the -d option.
- TUNING
- If the default configuration of sendmail does not achieve the
required performance, several configuration options can be changed
to increase performance. However, before those options are changed,
it is necessary to understand why performance is not as good as wanted.
This file describes the performance implications of sendmail.
- cf
- Both site-dependent and site-independent descriptions of hosts.
Files ending in .mc (Master Configuration) are
the input descriptions. The output is in the corresponding .cf file.
The general structure of these files is described Creating the configuration file.
- domain
- Site-dependent subdomain descriptions. These are tied to the way
your organization wants to do addressing. These descriptions 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 z/OS® UNIX 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.
This code should be used only during the transition from Berkeley.EDU
names to .CS.Berkeley.EDU names.
- inetd.conf.pop
- The inetd changes needed to run popper.
- m4
- Site-independent m4(1) include files that
have information common to all configuration files. Think of this
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).
- milter
- A directory containing a sample mail filter.
- ostype
- Definitions describing various operating system environments (such
as the location of support files). These are referenced using the
OSTYPE m4 macro.
- sendmail.ps
- This is a postscript file of the Sendmail Installation and
Operation Guide provided by www.sendmail.org in
this version of sendmail.
- sh
- Shell files used by the m4 build process.
- siteconfig
- Local UUCP connectivity information. These normally contain lists
of site information, for example:
- SITE(contessa)
- SITE(hoptoad)
- SITE(nkainc)
- SITE(well)
These are referenced using the SITECONFIG macro: SITECONFIG(site.config.file, name_of_site,X)
where X is
the macro or class name to use. It can be U (indicating locally connected
hosts) or one of W, X, or Y for up to three remote UUCP hubs. This
directory has been supplanted by the mailer table feature. Any new
configurations should use that feature to do UUCP (and other) routing.