110 lines
5.2 KiB
HTML
110 lines
5.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<!-- updated Sun Jul 14 20:10:00 MET DST 1996 by:
|
|
Tony den Haan (tony@iaehv.nl) ftp://ftp.IAEhv.nl/pub/users/tony-->
|
|
|
|
<HEAD>
|
|
<TITLE>Getting smail Up and Running</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node199.html">UUCP Setup</A>
|
|
<B>Up:</B> <A HREF="nag.html">The Network Administrators' Guide</A>
|
|
<B> Previous:</B> <A HREF="node197.html">National Character Sets</A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION0016000000">Getting smail Up and Running</A></H1>
|
|
<A NAME="smail"></A>
|
|
This chapter will give you a quick introduction to setting up smail,
|
|
and an overview of the functionality it provides. Although smail
|
|
is largely compatible with sendmail in its behavior, their
|
|
configuration files are completely different.
|
|
<P>
|
|
The main configuration file is the /usr/lib/smail/config. You always
|
|
have to edit this file to reflect values specific to your site. If you
|
|
are only a UUCP leaf site, you will have relatively little else to do,
|
|
ever. Other files that configure routing and transport options may also
|
|
be used; they will be dealt with briefly, too.
|
|
<P>
|
|
By default, smail processes and delivers all incoming mail
|
|
immediately. If you have relatively high traffic, you may instead have
|
|
smail collect all messages in the so-called <em>queue</em>, and
|
|
process it at regular intervals only.
|
|
<P>
|
|
When handling mail within a TCP/IP network, smail is frequently
|
|
run in daemon mode: at system boot time, it is invoked from
|
|
rc.inet2, and puts itself in the background where it waits for
|
|
incoming TCP connections on the SMTP port (usually port-25). This is
|
|
very beneficial whenever you expect to have a significant amount of
|
|
traffic, because smail isn't started up separately for every
|
|
incoming connection. The alternative would be to have inetd
|
|
manage the SMTP port, and have it spawn smail whenever there is a
|
|
connection on this port.
|
|
<P>
|
|
smail has a lot a flags that control it behavior; describing
|
|
them in detail here wouldn't make help you much. Fortunately,
|
|
smail supports a number of standard modes of operation that are
|
|
enabled when you invoke it by a special command name, like rmail,
|
|
or smtpd. Usually, these aliases are symbolic links to the
|
|
smail binary itself. We will encounter most of them when
|
|
discussing the various features of smail.
|
|
<P>
|
|
There are two links to smail you should have under all
|
|
circumstances; namely /usr/bin/rmail and
|
|
/usr/sbin/sendmail.<A HREF="footnode.html#7779"><IMG ALIGN=BOTTOM ALT="gif" SRC="foot_motif.gif"></A> When you compose and send a mail message with a user agent like
|
|
elm, the message will be piped into rmail for delivery,
|
|
with the recipient list given to it on the command line. The same
|
|
happens with mail coming in via UUCP. Some versions of elm,
|
|
however, invoke /usr/sbin/sendmail instead of rmail, so you
|
|
need both of them. For example, if you keep smail in
|
|
/usr/local/bin, type the following at the shell prompt:
|
|
<PRE>
|
|
# ln -s /usr/local/bin/smail /usr/bin/rmail
|
|
# ln -s /usr/local/bin/smail /usr/sbin/sendmail
|
|
</PRE>
|
|
If you want to dig further into the details of configuring smail,
|
|
please refer to the manual pages smail(1) and smail(5).
|
|
If it isn't included in your favorite distribution, you can get
|
|
it from the source to smail.
|
|
<P>
|
|
<BR> <HR>
|
|
<UL>
|
|
<LI> <A HREF="node199.html#SECTION0016100000">UUCP Setup</A>
|
|
<LI> <A HREF="node200.html#SECTION0016200000">Setup for a LAN</A>
|
|
<UL>
|
|
<LI> <A HREF="node201.html#SECTION0016210000">Writing the Configuration Files</A>
|
|
<LI> <A HREF="node202.html#SECTION0016220000">Running smail</A>
|
|
</UL>
|
|
<LI> <A HREF="node203.html#SECTION0016300000">If You Don't Get Through...</A>
|
|
<UL>
|
|
<LI> <A HREF="node204.html#SECTION0016310000">Compiling smail</A>
|
|
</UL>
|
|
<LI> <A HREF="node205.html#SECTION0016400000">Mail Delivery Modes</A>
|
|
<LI> <A HREF="node206.html#SECTION0016500000">Miscellaneous config Options</A>
|
|
<LI> <A HREF="node207.html#SECTION0016600000">Message Routing and Delivery</A>
|
|
<LI> <A HREF="node208.html#SECTION0016700000">Routing Messages</A>
|
|
<UL>
|
|
<LI> <A HREF="node209.html#SECTION0016710000">The paths database</A>
|
|
</UL>
|
|
<LI> <A HREF="node210.html#SECTION0016800000">Delivering Messages to Local Addresses</A>
|
|
<UL>
|
|
<LI> <A HREF="node211.html#SECTION0016810000">Local Users</A>
|
|
<LI> <A HREF="node212.html#SECTION0016820000">Forwarding</A>
|
|
<LI> <A HREF="node213.html#SECTION0016830000">Alias Files</A>
|
|
<LI> <A HREF="node214.html#SECTION0016840000">Mailing Lists</A>
|
|
</UL>
|
|
<LI> <A HREF="node215.html#SECTION0016900000">UUCP-based Transports</A>
|
|
<LI> <A HREF="node216.html#SECTION00161000000">SMTP-based Transports</A>
|
|
<LI> <A HREF="node217.html#SECTION00161100000">Hostname Qualification</A>
|
|
</UL>
|
|
<HR><A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node199.html">UUCP Setup</A>
|
|
<B>Up:</B> <A HREF="nag.html">The Network Administrators' Guide</A>
|
|
<B> Previous:</B> <A HREF="node197.html">National Character Sets</A>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|