>The difference between sendmail (any version) and smail is more
>a religious one. It has to do with relative ease of getting
>some jobs done and readability of configuration files:
>- sendmail configuration is said to be a secret science
> including donors of young living cats to a dark godess at
> midnight. sendmails configuration files have similarity to
> line noise or the winning entry into a regular expression
> abuse contest.
This is true of the sendmail.cf file, which no longer needs tweaking
with the advent of 8.6.4. I have appended my
Quote:>In my personal opinion smail is much better for UNIX
>beginners, because it does throw that many special characters
>at you ("How shall I learn to write a sendmail configuration? I
>can even type it if it were given on a sheet of paper to me!").
No no no no no. :-) Read below.
Read the docs which come with sendmail on how to transform this into a
.cf file. It is a one-liner ("mf < bugs.mc > sendmail.cf" or
something in the appropriate directory), but IMHO basic mail
configuration is something which should be thoroughly understood by
the admin of any box hung off of the Internet.
P.S. My machine name is bugs, thus the file name and RCS Id
-------- Begin bugs.mc
# Copyright (c) 1983 Eric P. Allman
# Copyright (c) 1988, 1993
# The Regents of the University of California. All rights reserved.
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
# 3. All advertising materials mentioning features or use of this software
# must display the following acknowledgement:
# This product includes software developed by the University of
# California, Berkeley and its contributors.
# 4. Neither the name of the University nor the names of its contributors
# may be used to endorse or promote products derived from this software
# without specific prior written permission.
# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
# This is the prototype file for a configuration that supports nothing
# but basic SMTP connections via TCP.
# You may want to add an OSTYPE macro to get the location of various
# support files for your operating system environment.
VERSIONID(`$Id: bugs.mc,v 0.1 1993/11/23 21:32:02 sorcerer Exp sorcerer $')
-------- End of bugs.mc