op.me

来自「<B>Digital的Unix操作系统VAX 4.2源码</B>」· ME 代码 · 共 2,890 行 · 第 1/5 页

.if n .ls 2
.he 'Sendmail Installation and Operation Guide''%'
.fo 'Version 4.2''Last Mod 7/28/83'
.nr si 3n
.de $0
.(x
.in \\$3u*3n
.ti -3n
\\$2.  \\$1
.)x
..
.de $C
.(x
.in 0
\\$1 \\$2.  \\$3
.)x
..
.+c
.(l C
.sz 16
.b SENDMAIL
.sz 12
.sp
.b "INSTALLATION AND OPERATION GUIDE"
.sz 10
.sp
.r
Eric Allman
Britton-Lee, Inc.
.sp
Version 4.2
.)l
.sp 2
.pp
.i Sendmail
implements a general purpose internetwork mail routing facility
under the UNIX*
.(f
*UNIX is a trademark of Bell Laboratories.
.)f
operating system.
It is not tied to any one transport protocol \*-
its function may be likened to a crossbar switch,
relaying messages from one domain into another.
In the process,
it can do a limited amount of message header editing
to put the message into a format that is appropriate
for the receiving domain.
All of this is done under the control of a configuration file.
.pp
Due to the requirements of flexibility
for
.i sendmail ,
the configuration file can seem somewhat unapproachable.
However, there are only a few basic configurations
for most sites,
for which standard configuration files have been supplied.
Most other configurations
can be built by adjusting an existing configuration files
incrementally.
.pp
Although
.i sendmail
is intended to run
without the need for monitoring,
it has a number of features
that may be used to monitor or adjust the operation
under unusual circumstances.
These features are described.
.pp
Section one describes how to do a basic
.i sendmail
installation.
Section two
explains the day-to-day information you should know
to maintain your mail system.
If you have a relatively normal site,
these two sections should contain sufficient information
for you to install
.i sendmail
and keep it happy.
Section three
describes some parameters that may be safely tweaked.
Section four
has information regarding the command line arguments.
Section five
contains the nitty-gritty information about the configuration
file.
This section is for masochists
and people who must write their own configuration file.
The appendixes give a brief
but detailed explanation of a number of features
not described in the rest of the paper.
.pp
The references in this paper are actually found
in the companion paper
.ul
Sendmail \- An Internetwork Mail Router.
This other paper should be read before this manual
to gain a basic understanding
of how the pieces fit together.
.sh 1 "BASIC INSTALLATION"
.pp
There are two basic steps to installing sendmail.
The hard part is to build the configuration table.
This is a file that sendmail reads when it starts up
that describes the mailers it knows about,
how to parse addresses,
how to rewrite the message header,
and the settings of various options.
Although the configuration table is quite complex,
a configuration can usually be built
by adjusting an existing off-the-shelf configuration.
The second part is actually doing the installation,
i.e., creating the necessary files, etc.
.pp
The remainder of this section will describe the installation of sendmail
assuming you can use one of the existing configurations
and that the standard installation parameters are acceptable.
All pathnames and examples
are given from the root of the
.i sendmail
subtree.
.sh 2 "Off-The-Shelf Configurations"
.pp
The configuration files
are all in the subdirectory
.i cf
of the sendmail directory.
The ones used at Berkeley are in
.i m4 \|(1)
format;
files with names ending
.q .m4
are
.i m4
include files,
while files with names ending
.q .mc
are the master files.
Files with names ending
.q .cf
are the
.i m4
processed versions of the corresponding
.q .mc
file.
.pp
Two off the shelf configuration files are supplied
to handle the basic cases:
.i cf/arpaproto.cf
for Arpanet (TCP) sites
and
.i cf/uucpproto.cf
for UUCP sites.
These are
.i not
in
.i m4
format.
The file you need should be copied to a file with the same name
as your system,
e.g.,
.(b
cp uucpproto.cf ucsfcgl.cf
.)b
This file
is now ready for installation as
.i /usr/lib/sendmail.cf .
.sh 2 "Installation Using the Makefile"
.pp
A makefile exists in the root of the
.i sendmail
directory that will do all of these steps
for a 4.2bsd system.
It may have to be slightly tailored
for use on other systems.
.pp
Before using this makefile,
you should already have created your configuration file
and left it in the file
.q cf/\fIsystem\fP.cf
where
.i system
is the name of your system
(i.e., what is returned by
.i hostname \|(1)).
If you do not have
.i hostname
you can use the declaration
.q HOST=\fIsystem\fP
on the
.i make \|(1)
command line.
You should also examine the file
.i md/config.m4
and change the
.i m4
macros there to reflect any libraries and compilation flags
you may need.
.pp
The basic installation procedure is to type:
.(b
make
make install
.)b
in the root directory of the
.i sendmail
distribution.
This will make all binaries
and install them in the standard places.
The second
.i make
command must be executed as the superuser (root).
.sh 2 "Installation by Hand"
.pp
Along with building a configuration file,
you will have to install the
.i sendmail
startup into your UNIX system.
If you are doing this installation
in conjunction with a regular Berkeley UNIX install,
these steps will already be complete.
Many of these steps will have to be executed as the superuser (root).
.sh 3 "lib/libsys.a"
.pp
The library in lib/libsys.a
contains some routines that should in some sense
be part of the system library.
These are the system logging routines
and the new directory access routines
(if required).
If you are not running the new 4.2bsd directory code
and do not have the compatibility routines installed in your system library,
you should execute the commands:
.(b
cd lib
make ndir
.)b
This will compile and install the 4.2 compatibility routines
in the library.
You should then type:
.(b
cd lib      # if required
make
.)b
This will recompile and fill the library.
.sh 3 "/usr/lib/sendmail"
.pp
The binary for sendmail is located in /usr/lib.
There is a version available in the source directory
that is probably inadequate for your system.
You should plan on recompiling and installing the entire system:
.(b
cd src
rm \-f *.o
make
cp sendmail /usr/lib
.)b
.sh 3 "/usr/lib/sendmail.cf"
.pp
The configuration file
that you created earlier
should be installed in /usr/lib/sendmail.cf:
.(b
cp cf/\fIsystem\fP.cf /usr/lib/sendmail.cf
.)b
.sh 3 "/usr/ucb/newaliases"
.pp
If you are running delivermail,
it is critical that the
.i newaliases
command be replaced.
This can just be a link to
.i sendmail :
.(b
rm \-f /usr/ucb/newaliases
ln /usr/lib/sendmail /usr/ucb/newaliases
.)b
.sh 3 "/usr/lib/sendmail.cf"
.pp
The configuration file must be installed in /usr/lib.
This is described above.
.sh 3 "/usr/spool/mqueue"
.pp
The directory
.i /usr/spool/mqueue
should be created to hold the mail queue.
This directory should be mode 777
unless
.i sendmail
is run setuid,
when
.i mqueue
should be owned by the sendmail owner
and mode 755.
.sh 3 "/usr/lib/aliases*"
.pp
The system aliases are held in three files.
The file
.q /usr/lib/aliases
is the master copy.
A sample is given in
.q lib/aliases
which includes some aliases which
.i must
be defined:
.(b
cp lib/aliases /usr/lib/aliases
.)b
You should extend this file with any aliases that are apropos to your system.
.pp
Normally
.i sendmail
looks at a version of these files maintained by the
.i dbm \|(3)
routines.
These are stored in
.q /usr/lib/aliases.dir
and
.q /usr/lib/aliases.pag.
These can initially be created as empty files,
but they will have to be initialized promptly.
These should be mode 666 if you are running a reasonably relaxed system:
.(b
cp /dev/null /usr/lib/aliases.dir
cp /dev/null /usr/lib/aliases.pag
chmod 666 /usr/lib/aliases.*
newaliases
.)b
.sh 3 "/usr/lib/sendmail.fc"
.pp
If you intend to install the frozen version of the configuration file
(for quick startup)
you should create the file /usr/lib/sendmail.fc
and initialize it.
This step may be safely skipped.
.(b
cp /dev/null /usr/lib/sendmail.fc
/usr/lib/sendmail \-bz
.)b
.sh 3 "/etc/rc"
.pp
It will be necessary to start up the sendmail daemon when your system reboots.
This daemon performs two functions:
it listens on the SMTP socket for connections
(to receive mail from a remote system)
and it processes the queue periodically
to insure that mail gets delivered when hosts come up.
.pp
Add the following lines to
.q /etc/rc
(or
.q /etc/rc.local
as appropriate)
in the area where it is starting up the daemons:
.(b
if [ \-f /usr/lib/sendmail ]; then
	(cd /usr/spool/mqueue; rm \-f [lnx]f*)
	/usr/lib/sendmail \-bd \-q30m &
	echo \-n ' sendmail' >/dev/console
fi
.)b
The
.q cd
and
.q rm
commands insure that all lock files have been removed;
extraneous lock files may be left around
if the system goes down in the middle of processing a message.
The line that actually invokes
.i sendmail
has two flags:
.q \-bd
causes it to listen on the SMTP port,
and
.q \-q30m
causes it to run the queue every half hour.
.pp
If you are not running a version of UNIX
that supports Berkeley TCP/IP,
do not include the
.b \-bd
flag.
.sh 3 "/usr/lib/sendmail.hf"
.pp
This is the help file used by the SMTP
.b HELP
command.
It should be copied from
.q lib/sendmail.hf :
.(b
cp lib/sendmail.hf /usr/lib
.)b
.sh 3 "/usr/lib/sendmail.st"
.pp
If you wish to collect statistics
about your mail traffic,
you should create the file
.q /usr/lib/sendmail.st :
.(b
cp /dev/null /usr/lib/sendmail.st
chmod 666 /usr/lib/sendmail.st
.)b
This file does not grow.
It is printed with the program
.q aux/mailstats.
.sh 3 "/etc/syslog"
.pp
You may want to run the
.i syslog
program
(to collect log information about sendmail).
This program normally resides in
.i /etc/syslog,
with support files
.i /etc/syslog.conf
and
.i /etc/syslog.pid .
The program is located in the
.i aux
subdirectory of the
.i sendmail
distribution.
The file
.i /etc/syslog.conf
describes the file(s) that sendmail will log in.
For a complete description of syslog,
see the manual page for
.i syslog \|(8)
(located in
.i sendmail/doc
on the distribution).
.sh 3 "/usr/ucb/newaliases"
.pp
If
.i sendmail
is invoked as
.q newaliases,
it will simulate the
.b \-bi
flag
(i.e., will rebuild the alias database;
see below).
This should be a link to /usr/lib/sendmail.
.sh 3 "/usr/ucb/mailq"
.pp
If
.i sendmail
is invoked as
.q mailq,
it will simulate the
.b \-bp
flag
(i.e.,
.i sendmail
will print the contents of the mail queue;
see below).
This should be a link to /usr/lib/sendmail.
.sh 1 "NORMAL OPERATIONS"
.sh 2 "Quick Configuration Startup"
.pp
A fast version of the configuration file
may be set up by using the
.b \-bz
flag:
.(b
/usr/lib/sendmail \-bz
.)b
This creates the file
.i /usr/lib/sendmail.fc
(\c
.q "frozen configuration" ).
This file is an image of
.i sendmail 's
data space after reading in the configuration file.
If this file exists,
it is used instead of
.i /usr/lib/sendmail.cf
.i sendmail.fc
must be rebuilt manually every time
.i sendmail.cf
is changed.
.pp
The frozen configuration file will be ignored
if a
.b \-C
flag is specified
or if sendmail detects that it is out of date.
However, the heuristics are not strong
so this should not be trusted.
.sh 2 "The System Log"
.pp
The system log is supported by the
.i syslog \|(8)
program.
.sh 3 "Format"
.pp
Each line in the system log
consists of a timestamp,
the name of the machine that generated it
(for logging from several machines
over the ethernet),
the word
.q sendmail: ,
and a message.
.sh 3 "Levels"
.pp
If you have
.i syslog \|(8)
or an equivalent installed,
you will be able to do logging.
There is a large amount of information that can be logged.
The log is arranged as a succession of levels.
At the lowest level
only extremely strange situations are logged.
At the highest level,
even the most mundane and uninteresting events
are recorded for posterity.
As a convention,
log levels under ten
are considered
.q useful;
log levels above ten
are usually for debugging purposes.
.pp
A complete description of the log levels
is given in section 4.3.
.sh 2 "The Mail Queue"
.pp
The mail queue should be processed transparently.
However, you may find that manual intervention is sometimes necessary.
For example,
if a major host is down for a period of time
the queue may become clogged.
Although sendmail ought to recover gracefully when the host comes up,
you may find performance unacceptably bad in the meantime.
.sh 3 "Printing the queue"
.pp
The contents of the queue can be printed
using the
.i mailq
command
(or by specifying the
.b \-bp
flag to sendmail):
.(b
mailq
.)b
This will produce a listing of the queue id's,
the size of the message,
the date the message entered the queue,
and the sender and recipients.
.sh 3 "Format of queue files"
.pp
All queue files have the form
\fIx\fP\|\fBf\fP\fIAA99999\fP
where
.i AA99999
is the
.i id
for this file
and the
.i x
is a type.
The types are:
.ip d
The data file.
The message body (excluding the header) is kept in this file.
.ip l
The lock file.
If this file exists,
the job is currently being processed,
and a queue run will not process the file.
For that reason,
an extraneous
.b lf
file can cause a job to apparently disappear