From: neal@neal.ctd.comsat.com (Neal Becker)
Newsgroups: comp.sys.hp
Subject: Re: prob w/ smail HP-UX 8.02 (837)
Date: 3 Sep 92 14:14:20 GMT
Organization: COMSAT Labs
NNTP-Posting-Host: neal.ctd.comsat.com
In-reply-to: tmike@cmptrc.lonestar.org's message of 2 Sep 92 17:06:31 GMT

I have smail-3.1.26 on hpux 8.07 (720).  It works fine.  Here is my
EDITME and os/hpux-8.0.  I think you need ANSI compiler.  Hope this helps.


#! /bin/sh
# This is a shell archive.  Remove anything before this line, then unpack
# it by saving it into a file and typing "sh file".  To overwrite existing
# files, type "sh file -c".  You can also feed this as standard input via
# unshar, or by typing "sh <file", e.g..  If this archive is complete, you
# will see the following message at the end:
#		"End of archive 1 (of 1)."
# Contents:  smail-3.1.26/conf/EDITME smail-3.1.26/conf/os/hp-ux8.0
# Wrapped by neal@neal on Thu Sep  3 10:12:31 1992
PATH=/bin:/usr/bin:/usr/ucb ; export PATH
if test -f 'smail-3.1.26/conf/EDITME' -a "${1}" != "-c" ; then 
  echo shar: Will not clobber existing file \"'smail-3.1.26/conf/EDITME'\"
else
echo shar: Extracting \"'smail-3.1.26/conf/EDITME'\" \(47337 characters\)
sed "s/^X//" >'smail-3.1.26/conf/EDITME' <<'END_OF_FILE'
X# @(#)conf/EDITME-dist	1.46 8/15/92 15:52:50
X#
X# EDITME - edit me to perform high level configuration of smail
X#
X# The EDITME file is used by makefiles to build individual defs.h,
X# defs.sh and defs.sed files, which in turn control the build/install
X# process of smail.
X#
X# The EDITME-dist file servers as a reference copy only.  Patches to
X# smail will refer to EDITME-dist rather than EDITME.  Only the EDITME
X# file is used in the build/install process.  Any editing should be done
X# to the file EDITME, which should be located in the same directory as
X# EDITME-dist.
X#
X# The EDITME is a /bin/sh shell script.  That is, comments begin with
X# the first non-quoted/non-escaped '#' character.  Values are set
X# using NAME=VALUE or NAME=, with no spaces around the equal sign.
X# Values that have spaces or special shell characters should be
X# qouted and/or escaped.  Consult the sh(1) man page for further details.
X#
X# Values that are indicated as optional may, in some cases, not be set.
X# All other values MUST be set to some value.  The NAME= form is
X# equivalent to not setting the value, with the exception of TEST_BASE.
X#
X# An alternate path to the EDITME file can be specified through setting
X# the environment variable SMAIL_EDITME.  This can either be a full
X# pathname or a relateive pathname, which will be referenced relative
X# to the smail conf directory.  Care must be taken with dependencies in
X# makefiles when the path to the EDITME file has changed.  If this is
X# a permanent change, then type "make depend" at the top of the smail
X# source tree.  Otherwise the conf/lib/mkdefs.sh shell script can be
X# run in affected directories to create new defs files.
X
X
X# CFLAGS - the base set of flags for the cc command
X#
X# optional
X#
X# When debugging smail, it is useful to set this to "-g".  Otherwise
X# "-O" is normally used to optimize the code produced.
X#
X# NOTE:  I get core dumps on SCO MPX 2.0 when using the bind router (I
X#   haven't tried other SCO releases).  Whatever the problem is, it
X#   goes away when I compile without -O.  If anybody finds the cause,
X#   please let me know.  For now, if you get core dumps when using the
X#   bind router on SCO, try compiling without -O.
X
XCFLAGS=-O				# common
X#CFLAGS=				# don't use optimizer
X#CFLAGS=-g				# use when debugging
X#CFLAGS="-O -C"				# UTS/580
X#CFLAGS="-g -C"				# UTS/580 for debugging
X
X
X# CC - the C compiler to use for compiling smail
X#
X# optional (defaults to cc)
X#
X# CAUTION: gcc does not work with smail on all architecures.  In
X# particular, problems have been reported on the SunOS platform.  The
X# typical problem is that gcc uses different structure-passing
X# conventions for function calls.  This is a problem for a few
X# networking calls which pass around in_addr structures.
X#
X# Some conf/os files set an alternate default value for CC.  In
X# particular, the SunOS CC defaults to /bin/cc, to ensure that
X# /usr/sys5/cc is not used.
X
X#CC=gcc					# use the GNU C Compiler
X
X
X# LDFLAGS - flags to pass to the loader
X#
X# optional
X#
X# These flags are passed to the cc command before any object
X# modules or libraries.
X
X#LDFLAGS=-L/usr/ucblib			# use an alternate directory for libs
X#LDFLAGS="-L/usr/ucblib -Bstatic"	# and don't use shared libraries
X
X
X# LIBS - libraries to include in binaries
X#
X# optional
X#
X# These libraries are passed to the cc command before any libraries
X# mentioned in the conf/os file.  It can be used to link in additional
X# libraries before the system libraries.
X#
X# If you wish to use the GNU dbm library, then add -lgdbm to LIBS
X# (perhaps with a -L to indicate the directory containing gdbm),
X# and then add NDBM to the HAVE variable.
X
X#LIBS=-lgdbm				# use the GNU dbm library
X#LIBS="-L/usr/local/lib -lgdbm"		# if gdbm is in /usr/local/lib
X#LIBS="-L/usr/local/lib -lgdbm -lalloca" # load alloca function from somewhere
X
X
X# OSLIBS - ending libraries to include in binaries
X#
X# optional
X#
X# These libraries are passed to the cc command after all other
X# libraries from any other source.  For example, this can be used
X# to force the use of an alternate C library, or a shared version
X# of the C library.
X#
X# Some conf/os files already specify use of the shared C library, and
X# some necessary system libraries.
X
X#OSLIBS=-lc_s				# SVR3 shared C library
X#OSLIBS="-lc_s -lcposix"		# POSIX and shared C libs
X
X
X# STRIP - define this if you wish to strip binaries when installing
X#
X# optional
X#
X# The smail binaries will only be striped on installation if STRIP=yes.
X# This may save some disk space at the expence of the ability to do
X# symbolic debugging.
X
X#STRIP=yes
X
X
X# USE_SYMLINKS - define this if you wish to use symlinks when installing
X#
X# optional
X#
X# The smail binaries are normally installed using hardlinks between
X# the various copies of the smail binary.  Where hardlinks cannot be
X# made, real copies are made.  To use symbolic links instead of
X# hard links and copies, set USE_SYMLINKS=yes.  This will cause only
X# one copy of the smail binary to be installed.  Do not define this
X# if your system does not have symbolic links.
X
X#USE_SYMLINKS=yes
X
X
X# OS_TYPE - define the operating system type for your machine
X#
X# required
X#
X# Consult the conf/os directory for a complete list of recognized
X# operating system types.  The names given below may not represent
X# all of the operating systems for which an OS description file
X# is available.
X
XOS_TYPE=hp-ux8.0
X#OS_TYPE=aix3.1				# IBM AIX 3.1
X#OS_TYPE=aix3.2				# IBM AIX 3.2
X#OS_TYPE=bsd4.2				# 4.2 BSD systems
X#OS_TYPE=bsd4.3				# 4.3 BSD systems
X#OS_TYPE=cpc3.0				# Counterpoint C-XIX Release 3.0
X#OS_TYPE=forpro				# fortune FOR:Pro 2.1 to 3.1
X#OS_TYPE=sco3.2				# SCO UNIX 3.2
X#OS_TYPE=sco3.2+tcp			# SCO UNIX 3.2 with SCO TCP/IP
X#OS_TYPE=sun_os3			# Sun/OS version 3.x
X#OS_TYPE=sun_os4			# Sun/OS version 4.x
X#OS_TYPE=sys5.2				# System V release 2
X#OS_TYPE=sys5.3				# System V release 3
X#OS_TYPE=sys5.4				# System V release 4
X#OS_TYPE=ultrix1.2			# DEC Ultrix release 1.2
X#OS_TYPE=unixpc3.0			# AT&T Unix PC (3b1) release 3.0
X#OS_TYPE=unixpc3.5			# AT&T Unix PC (3b1) release 3.5
X#OS_TYPE=uts1.2				# UTS/580 release 1.2
X#OS_TYPE=uts2.0				# UTS/580 release 2.0
X#OS_TYPE=xenix5				# SCO Xenix System V
X#OS_TYPE=posix				# Generic P1003.1 system
X#OS_TYPE=isc2.2.1			# Interactive release 2.2.1
X#OS_TYPE=delta				# Motorola delta
X
X
X# ARCH_TYPE - architecture type
X#
X# required
X#
X# The ARCH_TYPE of 16bit refers to machines with 16 bit words.  This
X# mode is untested.  It is assumed that 16bit machines have extended
X# address spaces as smail is more than 64k bytes long.
X
XARCH_TYPE=32bit					# common
X#ARCH_TYPE=small32bit				# 32 bit without reasonable VM
X#ARCH_TYPE=16bit				# untested
X
X
X# DRIVER_CONFIGURATION - configuration file describing smail drivers
X#
X# optional
X#
X# By default, the os configuration file (conf/os/OS_TYPE) refers to
X# the file that describes the available director, router and transport
X# drivers.
X#
X# For example on BSD-based OS_TYPEs, the os configuration file refers to
X# a driver configuration that uses BSD networking.  A BSD based system
X# could not set DRIVER_CONFIGURATION and get the BSD netwokring based
X# drivers; or a system could set DRIVER_CONFIGURATION=unix-generic and
X# disable BSD networking drivers.
X#
X# Currently few conf/os files specify the arpa-network driver
X# configuration (which includes support for the BIND server).
X# If you want to use this, you must usually set DRIVER_CONFIGURATION
X# explicitly.  You may also have to add BIND to the HAVE list (later
X# in this file) to use the arpa-network driver configuration.
X#
X# IMPORTANT NOTE FOR INTERNET HOSTS
X#
X# NOTE: The bind router driver is not configured into the compiled-in
X# routers, so you will need to install a routers file to use it.  Get
X# a routers file from samples/generic/routers and copy it to
X# /usr/lib/smail.  Comment out the first version of inet_hosts from
X# that file, and uncomment the second (the bind version) of the
X# router.  You may also want to uncomment the forcepaths router, if
X# you forward for any hosts in the UUCP zone.
X
X#DRIVER_CONFIGURATION=unix-generic		# no BSD networking
X#DRIVER_CONFIGURATION=$ROOT/mydriver.cf		# customized configuration
XDRIVER_CONFIGURATION=arpa-network		# include bind router
X
X
X# LMAIL - where the real /bin/mail resides
X#
X# optional
X#
X# On many System V machines, the /bin/mail program will deliver what 
X# it thinks is local mail directly into user mailboxes, and may also
X# call uucp, or some other remote delivery mechanism.  The /bin/mail
X# program will therefore can bypass smail.
X#
X# A solution to this program is to move the /bin/mail supplied with
X# your system to another name, LMAIL, and to then install the binmail
X# program, in pd/binmail as /bin/mail.  If binmail is invoked to read
X# mail, the LMAIL (old /bin/mail) is called, otherwise SMAIL is called
X# to deliver mail.
X#
X# If LMAIL is defined below and the specified file does not exist,
X# then the binmail makefile install rule will attempt to move
X# /bin/mail to LMAIL and then copy binmail into /bin/mail.  If LMAIL
X# is defined and the file LMAIL does exist, then the binmail
X# makefile will refuse to install binmail.
X#
X# If LMAIL is not defined then /bin/mail is not touched.
X#
X# NOTE: due to potential problems or confusion with binmail
X#	installation, binmail is not automatically built and installed
X#	from higher level makefiles.  One must go to the pd/binmail
X#	directory and "make install" explicitly.
X
X#LMAIL=/bin/lmail				# standard System V
X
X
X# MISC_DEFINES - miscellaneous definitions
X#
X# optional
X#
X# A colon-separated list that names miscellaneous macros to define
X# for C programs and shell scripts.  Each entry in the list can be
X# a simple name, or the name can be followed by an equal sign to
X# provide a value.  For example:
X#
X#	MISC_DEFINES="void=int:DECLARE_UTIMBUF:NO_FORWARDTO_FILE"
X#
X# Defines void to be int for compilers that do not correctly support
X# the void type, and declares the macro DECLARE_UTIMBUF, so that smail
X# will not try to get the utimbuf structure from a header file.
X#
X#
X# IMPORTANT FOR INTERACTIVE UNIX USERS:
X#
X# Some versions of Interactive UNIX have a <sys/socket.h> header
X# file that directly includes the <time.h> header file, which is
X# not protected against multiple inclusion.  If your system has
X# this problem, you will encounter a multiple declaration problem
X# when compiling src/modes.o.  To repair the situation, use:
X#
X#	MISC_DEFINES=ISC_SOCKET_TIME_BUG
X#
X#
X# IMPORTANT FOR BSD AND SUNOS USERS:
X#
X# Some mail readers compare access and modify times to determine
X# whether mail has been delivered which has not been read.  The local
X# mail transport (using the appendfile driver) preserves access time
X# for files so that this will work.  However, if smail is configured
X# to use the System V convention of reading forwarding information
X# from user mailbox files, then this will be defeated (the forwardto
X# director does not preserve access times).
X#
X# Since BSD systems (and System V systems running Smail) have little
X# reason to use the System V forwarding convention, it is sufficient
X# to disable it.  To disable the System V forwarding convention, add
X# NO_FORWARDTO_FILE to MISC_DEFINES.
X#
X#
X# IMPORTANT FOR USERS OF OLD BIND RELEASES
X#
X# The bind resolver can make use of features in newer releases of
X# BIND (named).  In particular, it will use the res_search function,
X# rather than older res_mkquery function.  If you do not have the
X# new BIND release (e.g., res_search is listed as an undefined
X# variable when you link smail), then add OBSOLETE_RESOLVER to
X# MISC_DEFINES.  Also, the res_search function does not appear to
X# interract correctly with the 'defnames' attribute to the bind
X# driver, on some versions of the resolv library, so beware.  If bind
X# doesn't work for you, try defining OBSOLETE_RESOLVER.
X#
X#
X# IMPORTANT FOR USERS OF SOME SEQUENT OS RELEASES
X#
X# Some releases of the Sequent C compiler recognize private as a keyword.
X# However, smail uses this as a variable or structure name in several
X# places.  To get around this problem use:
X#
X#	MISC_DEFINES=private=smail_private_tag
X#
X#
X# IMPORTANT FOR NON-POSIX OPERATING SYSTEMS
X#
X# Smail uses the utime() system call to set file times in a few places.
X# All U*IX releases appear to support this call, although not all
X# systems define the structure (utimbuf) used as an argument to the
X# call.  In particular, true 4.2 and 4.3BSD do not declare this
X# structure (at least not the original, non-POSIX, 4.3BSD release).
X#
X# The bsd4.2 and bsd4.3 conf/os files define DECLARE_UTIMBUF to cause
X# smail itself to define this structure.  However, this may fail if
X# your system is extended to define the utimbuf structure in an
X# incompatible fashion.  This can be disabled by defining
X# NO_DECLARE_UTIMBUF in MISC_DEFINES.
X#
X# For other operating systems, you may need to add DECLARE_UTIMBUF
X# in MISC_DEFINES.  Some releases of Interactive U*IX require this.
X# Other releases don't (I don't have a list).
X#
X#
X# IMPORTANT FOR USERS OF GCC ON NON-ANSI C SYSTEMS
X#
X# If you are using a C compiler that defines __STDC__ (such as gcc) but
X# you are running into problems due to non-ANSI #include files or missing
X# ANSI definitions, then you can define NO_ANSI_C.
X
X#MISC_DEFINES=ISC_SOCKET_TIME_BUG
XMISC_DEFINES=NO_FORWARDTO_FILE		# recommended for BSD systems
X#MISC_DEFINES=ISC_SOCKET_TIME_BUG:NO_FORWARDTO_FILE
X#MISC_DEFINES=OBSOLETE_RESOLVER
X#MISC_DEFINES=DECLARE_UTIMBUF		# if smail must define utimbuf struct
X#MISC_DEFINES=NO_DECLARE_UTIMBUF	# if smail must _not_ define utimbuf
X#MISC_DEFINES=private=smail_private_tag	# for sequent
X#MISC_DEFINES=NO_ANSI_C			# don't believe __STDC__
X
X
X# HAVE - miscellaneous supported features
X#
X# optional
X#
X# A colon-separated list of features that the local system supports
X# in addition to those defined in the OS configuration file.  Some
X# interesting features you might want to list are:
X#
X#	NDBM	      - this system supports the new DBM library
X#			functions introduced in 4.3BSD.
X#	DBM	      - this system supports the old DBM library
X#			distributed with older BSD systems and
X#			many System V systems.  This *requires* the
X#			dbmclose() function, which does not exist
X#			in most historic dbm implementations.
X#	HDB_UUCP      - this system uses HoneyDanBer UUCP, rather
X#			than a traditional version of UUCP.
X#	NIALIAS	      - aliases with NeXT NetInfo databases.
X#	BIND	      - the system supports the bind resolver library
X#
X# Defining NDBM or DBM may require the specification of additional
X# libraries, in LIBS or in OSLIBS.  See conf/os/template for a more
X# complete list of recognized features, and for more detailed
X# descriptions.  If neither NDBM or DBM is specified, Ozan Yigit's
X# sdbm (an ndbm workalike) will be used.
X#
X# CAUTION: The HoneyDanBer UUCP in System V Release 4.0 uses multi-
X#	letter message grade values, rather than the traditional
X#	single-letter message grades in earlier versions.  Smail
X#	presumes that message grades are single letters, so Smail and
X#	the default grades for SVR4.0 are incompatible.
X#
X#	As a result of this incompatiblity, either HDB_UUCP must not
X#	be defined with SVR4.0, or the message grades that smail
X#	uses will have to be added to the file /etc/uucp/Grades.
X#	The list of grades that smail will use is specified in the
X#	grades variable (whose default value can be specified by
X#	setting GRADES in this file).  Grades are specified by
X#	providing a longer string in the Precedence: field.  The
X#	grade letters for the default value of GRADES are:
X#
X#		9	- special-delivery
X#		A	- air-mail
X#		C	- first-class	(also the default message grade)
X#		a	- bulk
X#		n	- junk
X#
X#	To add the default letters, you might add the following lines
X#	to /etc/uucp/Grades:
X#
X#		9	9	Any	User	Any
X#		A	A	Any	User	Any
X#		C	C	Any	User	Any
X#		a	a	Any	User	Any
X#		n	n	Any	User	Any
X
X#HAVE=HDB_UUCP				# have HoneyDanBer UUCP
X#HAVE=NDBM				# have the new DBM functions
X#HAVE=DBM				# have the old DBM functions
X#HAVE=HDB_UUCP:NDBM			# new DBM and HoneyDanBer UUCP
XHAVE=BIND
X
X# UUCP_ZONE - this host is within the UUCP zone
X#
X# optional (defaults to undefined)
X#
X# Smail supports both strictly compliant SMTP transfers, and a
X# modification the the SMTP protocol for use within the UUCP zone.
X# The modified protocol transmits sender and recipient addresses in
X# accordance with the RFC976 specification, and provides behavior that
X# is more likely to work with other mailers in the UUCP zone.
X# Transferring mail using SMTP over private IP networks can work well
X# within the UUCP zone, except for the fact that the SMTP
X# specification doesn't work as well in the presence of generated
X# UUCP-zone routes form path files.
X#
X# The built-in smail transport definitions include transport
X# definitions that provide either behavior: inet_zone_smtp and
X# uucp_zone_smtp.  The first provides conformant behavior and should
X# be used when transferring mail to sites on the Internet.  The
X# second, uucp_zone_smtp, provides the modified protocol.
X#
X# An additional builtin transport protocol, smtp, is defined as having
X# the same behavior as inet_zone_smtp or uucp_zone_smtp, depending
X# upon whether UUCP_ZONE is set.  To make the the basic smtp transport
X# use the modified behavior for the UUCP zone, set UUCP_ZONE to true.
X#
X# In the presence of generated routes from paths files, the
X# Internet-zone version of the SMTP transport will generate route-addr
X# addresses.  The introduction of RFC1123 removes the requirement that
X# route-addrs work as routes, preferring instead the use of the %
X# operator for routing.  Intermixed % and ! operators, particularly in
X# the presence of an @ operator (e.g., veritas!mitsu%tron@apple.com),
X# are sufficiently ambiguous that it is undesirable to use with ! or %
X# operators for routing when strict SMTP compliance is needed.  This
X# is one of the motivations for introducing the modified UUCP-zone
X# protocol.  However, generating route-addr addresses works well for
X# transferring mail between nodes running Smail 3.1.
X#
X# NOTE: the UUCP_ZONE flag does not affect the batched SMTP transports
X# that operate through UUCP.  The uusmtp and demand_uusmtp transports
X# always operate with the modified UUCP-zone protocol.  Two additional
X# transports, inet_uusmtp and inet_demand_uusmtp use compliant
X# protocols.
X
X#UUCP_ZONE=true					# this site is in the UUCP zone
X#UUCP_ZONE=					# this site is on the Internet
X
X
X# HOSTNAMES - names for the local host
X#
X# optional
X#
X# The HOSTNAMES value is a colon-separated list of names your system.
X# This does not need to include the name given by UUCP_NAME.  If
X# HOSTNAMES is set, then the first name in the list will be used as the
X# canonical name of your system.  That is, the name by which your
X# machine can be uniquely named across all networks.
X#
X# Normally HOSTNAMES is not set.  In this case the HOSTNAMES value will
X# be computed at run-time from the DOMAINS value and the system-dependently
X# computed name of your system.
X#
X# If you are registered in a domain, you might consider seting HOSTNAMES
X# to a list such as:   sitename.subdom.dom:sitename.dom:sitename.uucp
X
X#HOSTNAMES=kgbvax.ussr.comm:kgbvax.uucp		# example only
X
X
X# DOMAINS - domains under which the local host resides
X#
X# optional   (except when HOSTNAMES is not set)
X#
X# If HOSTNAMES is not defined, then HOSTNAMES is computed by concatenating
X# local host's actual name with each name in this colon-separated list of
X# domain names.  This computation is done at run-time.
X#
X# Example: if DOMAINS="uts.amdahl.com:uucp", then the HOSTNAMES value
X# for the site "amdahl" would become "amdahl.uts.amdahl.com:amdahl.uucp".
X#
X# NOTE: The uucp domain is not meaningful in any standard way, though
X#	many sites treat this as implying any site that is registered
X#	in the UUCP zone through the USENET maps.  Sites that really
X#	wish to be able to receive mail from anywhere in the world
X#	should get a registered domain.
X
XDOMAINS=ctd.comsat.com				# common
X#DOMAINS=ussr.comm:uucp				# example only
X
X
X# UUCP_NAME - name for the local host on the UUCP network
X#
X# optional
X#
X# This should be set to the name of the local host as known by the
X# UUCP software.
X#
X# Normally, no value is given for this variable, in which case the
X# value will be computed by smail at run-time from the actual name for
X# local host, as computed in a system-dependent fashion.
X
X#UUCP_NAME=kgbvax				# example only
X
X
X# VISIBLE_NAME - local host name used in outgoing addresses
X#
X# optional
X#
X# Some installations may wish to hide a group of machines under a common
X# name.  For example, at Amdahl, we may wish to hide the machines on our
X# ethernet under the domain "uts.amdahl.com".  If we set the value
X# VISIBLE_NAME="uts.amdahl.com" on the machine "futatsu", then mail
X# from "futatsu" sent as if it came from "user@uts.amdahl.com" rather than
X# "user@futatsu.uts.amdahl.com".  Of course, the "uts.amdahl.com" gateways
X# will need to forward mail to "user", however the fact that a user
X# does not have check for mail on all machines on the network is useful.
X#
X# The VISIBLE_NAME value will not be recognized as a name for the local
X# host unless it is also included in one of the other lists of names for
X# the local host.
X
X#VISIBLE_NAME=kgbvax.uucp			# example only
XVISIBLE_NAME=ctd.comsat.com
X
X# GATEWAY_NAMES - more names for the local host
X#
X# optional
X#
X# It is often important that hosts which are domain gateways recognize
X# the domain names as alternate names for the local host.  These names
X# should be defined in addition to those computed automatically from
X# the actual name for the local host by putting them in GATEWAY_NAMES.
X#
X# This variable is a colon-separated list of names for the local host
X# which is not computed from the actual name for the local host.
X
X#GATEWAY_NAMES=moscow.ussr.comm:ussr.comm:comm	# example only
X
X
X# POSTMASTER - the default address for the mail administrator
X#
X# optional	(defaults to root)
X#
X# This address is used by smail as a last resort in trying to deliver
X# to the address "postmaster".  Normally, "postmaster" is aliased to a
X# responsible person, or persons through the alias file.  In the event
X# that no alias file exists, or that "postmaster" was not found in
X# that file or by any other directors, the default address will be
X# used.
X
X#POSTMASTER=neal
X
X
X# NOBODY - a user with few access capabilities
X#
X# optional
X#
X# The user named here will be used by smail whenever a user ID is
X# desired that cannot do any more damange than any unpriveledged user
X# on the system.  Under 4.3BSD and SunOS, this would be the user named
X# "nobody".  Under other operating systems, it may be reasonable to
X# create a "nobody" entry in the passwd file.  Some systems have a
X# user such as "unknown" which will suffice.
X#
X# If this is not defined, then a default will be chosen.  This default
X# is os-type dependent, and is commonly nobody for BSD- and sun-derived
X# systems.
X
X#NOBODY=nobody
X#NOBODY=unknown		# some sites have this in their passwd file
X
X
X# TEST_BASE - directory where smail test files are kept
X#
X# optional  (special when defined to an empty string)
X#
X# When testing smail, it is convenient to put binaries and configuration
X# files in an area separated from the actual installation areas.  The
X# TEST_BASE directory defines this alternate area.  Smail will assume
X# assume a fixed hierarchy below this directory, with a "bin" subdirectory
X# containing the smail binary and utilities, a "lib" directory containing
X# smail configuration files, and a "spool" directory containing smail
X# spool files.
X#
X# If no TEST_BASE is defined, then this facility is turned off.  If a
X# TEST_BASE is defined to be an empty string, then all programs will be
X# used in the area where they are compiled, LIB_DIR will be set to the
X# "lib" directory under the root of the smail source tree, and SPOOL_DIRS
X# will be set to the "spool" directory under the root of the smail source
X# tree.  In this case, a "make install" is not required.
X#
X# If a TEST_BASE is defined as a relative path (e.g. "."), then it is
X# defined relative to the root of the smail source directory.
X
X#TEST_BASE=/usr/project/smail
X#TEST_BASE=test
X#TEST_BASE=					# use progs in source area
X
X
X# SMAIL_BIN_DIR - directory where copies of the smail binary are kept
X#
X# optional
X#
X# The Smail program comes in user callable names: smail, uupath,
X# pathto, optto, and so on.  A copy of smail will be linked to files
X# under SMAIL_BIN_DIR.  The SMAIL_BIN_DIR should be a directory
X# that is commonly in users search path (i.e., $PATH).
X
XSMAIL_BIN_DIR=/usr/local/bin			# BSD local convention
X#SMAIL_BIN_DIR=/usr/amdahl/bin			# convention for UTS/580
X#SMAIL_BIN_DIR=/usr/local/bin			# yet another convention
X#SMAIL_BIN_DIR=/usr/smail/bin			# I use this right now
X
X
X# SMAIL_NAME - file where the primary working copy of smail is located
X#
X# optional
X#
X# Any program that needs to call smail, including smail itself will
X# attempt to execute the program named by SMAIL_NAME.
X#
X# Often the primary working copy of smail is /usr/lib/sendmail.  This
X# should be used for systems that used to run sendmail.  Programs such
X# as Berkeley Mail, System V mailx or /bin/mail can be made to, or do
X# call /usr/lib/sendmail for mailer activity.  It is common for public
X# domain programs to expect a mailer to exist under this name, also.
X#
X# If SMAIL_NAME is not defined here, or is set to a null string, then
X# $SMAIL_BIN_DIR/smail is used instead.  If this is the name that you
X# want to use as the primary binary pathname, then do set SMAIL_NAME
X# to the null string.  This will prevent the smail src/Makefile from
X# installing it as $SMAIL_BIN_DIR/smail twice.
X
XSMAIL_NAME=/usr/lib/sendmail			# common convention
X#SMAIL_NAME=					# use smail in bin directory
X
X
X# OTHER_SMAIL_NAMES - other names under which to install smail
X#
X# optional
X#
X# Many systems will wish to install smail as /bin/rmail to catch mail
X# coming in over UUCP directly with smail.  To install under this
X# name set OTHER_SMAIL_NAMES to /bin/rmail.  As implied by the name,
X# other pathnames can be specified as well, if a system has other
X# potential rendezvous points for mail.  This should be a colon or
X# white-space separated list of full pathnames.
X#
X# Users of XENIX may wish to use smail as their execmail interface.
X# To do this, add /usr/lib/mail/execmail to this list.
X#
X# This is assumed to be empty when TEST_DIR is defined.
X#
X# NOTE: A pathname CANNOT be in both SMAIL_NAME and OTHER_SMAIL_NAMES.
X
XOTHER_SMAIL_NAMES=/bin/rmail			# common
X#OTHER_SMAIL_NAMES=/usr/lib/sendmail		# could use this rather
X						# than putting it into
X						# SMAIL_NAME
X#OTHER_SMAIL_NAMES=/bin/rmail:/usr/lib/mail/execmail # for XENIX
X
X
X# LIB_DIR - directory where various smail files are found
X#
X# required
X#
X# The LIB_DIR is where various static smail files reside, by default.
X# Files which may reside under this directory are: the primary config
X# file, the directors, routers and transports files, an aliases file,
X# pathalias database, uuwho database, and the COPYING file.
X#
X# The common subdirectories under LIB_DIR are: "methods", where method
X# files are by default found; "maps", where local pathalias files,
X# mkmap configuration files and the getmap batch file are located;
X# and "lists" where mailing lists are commonly located.
X#
X# It should be noted that none of these files, except for COPYING,
X# is required by the smail binary as it is released.  See smail(5)
X# and smail(8) for more details on this and related topics.
X
XLIB_DIR=/usr/local/lib/smail				# common convention
X#LIB_DIR=/usr/local/lib/smail
X#LIB_DIR=/usr/smail/lib				# I use this right now
X
X
X# UTIL_BIN_DIR - directory where smail utilities are located
X#
X# required
X#
X# The smail system has a number of programs such as pathalias, mkline,
X# mksort, mkdbm that users normally need not execute directly.  Such
X# utilities will be placed under the UTIL_BIN_DIR directory.
X#
X# UTIL_BIN_DIR is often the same as LIB_DIR.
X
XUTIL_BIN_DIR=$LIB_DIR				# common, same as LIB_DIR
X#UTIL_BIN_DIR=/usr/smail/util			# I use this right now
X
X
X# NEWALIASES - alternate pathname for mkaliases program
X#
X# optional
X#
X# For compatibility with sendmail, mkaliases can be installed under
X# a name such as /usr/ucb/newaliases, or /usr/lib/newaliases.  To setup
X# smail to perform this installation, set NEWALIASES to the desired full
X# pathname.  When testing, this is set to the empty string, signifying
X# that mkaliases will be installed only under the name mkaliases.
X
X#NEWALIASES=$UTIL_BIN_DIR/newaliases
X#NEWALIASES=/usr/local/bin/newaliases
X#NEWALIASES=/usr/ucb/newaliases			# BSD location
X#NEWALIASES=/usr/lib/newaliases			# UTS/580 location
XNEWALIASES=/usr/bin/newaliases			# HPUX
X
X# SECOND_CONFIG_FILE - pathname of an alternate config file
X#
X# optional
X#
X# Smail allows one to have a second set of configuration files that can
X# override both the compiled in and the optional primary config file.
X# Normally, the path to this secondary configuration file is defined
X# in the primary smail configuration file.  However the value
X# SECOND_CONFIG_FILE can be the filename of the secondary (alternate)
X# config file.  In the case where both this value, and where the
X# LIB_DIR/config file specifies a "second_config_file" value, the
X# LIB_DIR/config file takes presidence.
X#
X# A secondary configuration file is useful in an environment with
X# distributed filesystems.  In such an environment, the regular config
X# directory can be maintained centrally on a remotely mounted
X# filesystem.  Individual machines, can then setup a secondary
X# configuration file which overrides these centrally maintained files
X# for specific purposes.
X
X# For example, in a network with one gateway to the outside world,
X# all could share the same smail binaries and standard configuration.
X# However the the gateway machine could have a secondary configuration
X# file which so that the gateway's the smail setup has greater intelligence
X# and thus act as a smart_user and smart_path host.
X
XSECOND_CONFIG_FILE=/local/smail/config			# common for non-NFS systems
X#SECOND_CONFIG_FILE=/private/usr/lib/smail	# convention for NFS systems
X
X
X# PATHS_FILE, PATHS_TYPE - location and type of the paths database
X#
X# optional
X#
X# If PATH_FILE begins with a '/', then it is the name of the optional
X# pathalias database, otherwise it is assumed that PATH_FILE refers to
X# a file under the LIB_DIR directory.
X#
X# For use with YP, it may be more convenient to use the "yp" type,
X# rather than "aliasyp", because this way a paths file can be maintained
X# in a format compatible with other YP maps.
X#
X# If PATHS_FILE is left undefined, no paths file is defined in the
X# preloaded smail configuration.
X
XPATHS_FILE=paths				# for file under LIB_DIR
X#PATHS_FILE=mail.paths				# YP (NIS)
X
X#PATHS_TYPE=dbm					# indexed
X#PATHS_TYPE=bsearch				# shorted
XPATHS_TYPE=lsearch				# linear search
X#PATHS_TYPE=yp					# YP (NIS)
X
X# ALIASES_FILE, ALIASES_TYPE - location and type of the aliases database
X#
X# optional
X#
X# If ALIASES_FILE begins with a '/', then it is the full pathname of the
X# optional aliases database, otherwise it is assumed that ALIASES_FILE
X# refers to a file under the LIB_DIR directory.
X#
X# For use with YP, it may be more convenient to use the "yp" type,
X# rather than "aliasyp", because this way an alias file can be maintained
X# in a format compatible with other YP maps.
X#
X# NOTE:	 If ALIASES_TYPE is specified as bsearch, then the suffix .sort
X#	 will be appended to the filename given in ALIASES_FILE.  The
X#	 mkaliases command will then treat a file without that suffix
X#	 as the unsorted source file for the database.
X#
X# If ALIASES_FILE is left undefined, no aliases file is defined in the
X# preloaded smail configuration.
X#
X# NOTE FOR AIX SYSTEMS:
X#	I have received reports that AIX3.1 requires use of "yp",
X#	rather than "aliasyp".  If this is true, I don't quite see
X#	how Suns and RS/6000s running sendmail can share the same
X#	YP maps.  In any case, use whatever works in your
X#	environment.
X
XALIASES_FILE=/usr/lib/aliases			# compatible with sendmail
X#ALIASES_FILE=aliases				# for file under LIB_DIR
X#ALIASES_FILE=mail.aliases			# YP (NIS)
X#ALIASES_FILE=NetInfo				# for NeXT NetInfo aliases
X
XALIASES_TYPE=dbm				# compatible with sendmail
X#ALIASES_TYPE=lsearch				# for sites without dbm(3x)
X#ALIASES_TYPE=bsearch				# for sorted files, faster
X#ALIASES_TYPE=aliasyp				# YP (NIS)
X#ALIASES_TYPE=nialias				# for NeXT NetInfo aliases
X
X
X# ALIASES_REMOVE_SENDER - remove the sender (by default) from alias expansions
X# LISTS_REMOVE_SENDER - remove the sender (by default) from list expansions
X#
X# optional
X#
X# For compatibility with sendmail, smail can be configured to remove the
X# sender of a message (if the sender is a local user) from alias
X# expansions.  Users can disable this feature by invoking smail with
X# the -m flag, typically by setting "metoo" in their .mailrc file.
X#
X# However, many people find this behavior confusing and some administrators
X# would prefer to disable this "sender removal" feature altogether.
X# Also, it has recently been noticed that smail's sender removal
X# behavior is not quite sendmail-compatible with regards to nested
X# aliases and have been surprised by the results of aliasing.
X#
X# Smail supports two forms of aliasing to which sender removal can be
X# applied: the regular aliases file (defined by ALIASES_FILE above), and
X# a directory of mailing lists (typically /usr/lib/smail/lists) where
X# all files in that directory define a list.  A site that has converted
X# entirely over to smail3 can use alias files strictly for username
X# aliasing, while using the lists directory for real mailing lists.  With
X# such a usage model, sender removal should be disabled for the alias
X# file, but can be enabled (depending upon preference) for the lists
X# directory.
X#
X# To enable sender removal, set ALIASES_REMOVE_SENDER or LISTS_REMOVE_SENDER
X# (depending upon preference) to "yes".  If these values are empty, or are
X# note defined, then sender removal is disabled.
X#
X# This behavior can be configured using the run-time directors configuration
X# file by setting the "sender_okay" flag, to indicate that sender removal
X# should NOT be done.
X
X#ALIASES_REMOVE_SENDER=yes
XLISTS_REMOVE_SENDER=yes
X
X
X# RETRY_INTERVAL - minimum per-host retry interval for TCP/IP delivery
X# RETRY_DURATION - maximum time to keep messages in the input queue
X#
X# optional (RETRY_INTERVAL defaults to 10 minutes, RETRY_DURATION to 5 days)
X#
X# Messages to hosts on TCP/IP networks may block for quite some time, if
X# the recipient host is down, or some intervening network is inoperative.
X# Connections to such unreachable or downed hosts can block for quite
X# some time until a timeout indicates indicates that the condition
X# exists.
X#
X# To prevent the mail queue from blocking repeatedly on the same set of
X# unreachable hosts, smail keeps a directory of files that store the
X# last connection failure encountered for each host.  Message deliveries
X# to a host that has failed recently will be deferred until a certain
X# period of time (the retry interval) has elapsed, preventing queue runs
X# from hanging again immediately.
X#
X# If a host is down for an extended period of time (such as forever),
X# then sending a message to the message sender is preferable to keeping
X# the message in our mail queue.  If message deliveries to a particular
X# host have not succeeded within a particular length of time (the retry
X# duration), smail considers delivery to have failed, and sends a bounce
X# notification to the sender or address owner.
X#
X# Retry durations and intervals for specific hosts or domains can be
X# defined by creating a retry file in $LIB_DIR and adding lines of
X# the form:
X#
X#	hostname	duration/interval
X#	*.domain	duration/interval
X#
X# A default can be added at the end of this file with:
X#
X#	*		duration/interval
X#
X# Alternately, a default can be specified by setting RETRY_INTERVAL
X# and RETRY_DURATION in this file.  Both values are in seconds.  To
X# help in calculating, 1 day is 86400 seconds.  You can actually
X# use C constant expressions here, if you want to use addition or
X# multiplication.
X#
X# These values can also be set using the retry_interval and
X# retry_duration variables in $LIB_DIR/config.  In the config file
X# and in the retry file, times can be specified with suffixes, such
X# as 'm', 'h', or 'd' to indicate minutes, hours, or days.  For
X# example:
X#
X#	*.uu.net	3d/10m
X
XRETRY_INTERVAL=600		# 10 minutes
X#RETRY_INTERVAL='20*60'		# 20 minutes
XRETRY_DURATION='86400*5'	# 5 days
X#RETRY_DURATION='86400*14'	# 2 weeks
X
X
X# UUCP_SYSTEM_FILE - path to UUCP file containing remote systems
X#
X# optional
X#
X# The normal smail configuration defines a router that scans the
X# output of the /usr/bin/uuname command for neighboring UUCP sites.
X# When smail is running as a daemon, it can cache the output of uuname
X# so that the uuname command need not be executed for each mail
X# message.  In order to be able to detect when the output of uuname
X# will change, smail daemons will stat the UUCP configuration file
X# which contains the names of neighboring hosts.  This EDITME variable
X# defines the full pathname to this file.  If this variable is not
X# defined, then the output of the uuname will not be cached.
X#
X# NOTE:	Many OS files specify the correct file for this, though some
X#	don't.  Also, if you add HoneyDanBer UUCP to a system that
X#	does not normally have it, then you will need to set this.
X
X#UUCP_SYSTEM_FILE=/usr/lib/uucp/L.sys		# use this for normal UUCP
X#UUCP_SYSTEM_FILE=/usr/lib/uucp/Systems		# use this for HoneyDanBer UUCP
X
X
X# SPOOL_DIRS - smail spooling directories
X#
X# required
X#
X# Smail can use one or more spooling directories, where spool directories
X# other than the first are used if earlier spool directories were
X# inaccessible or were on file systems which filled up.  The list of spool
X# directories should be colon-separated and may contain only one spool
X# directory if desired.
X
XSPOOL_DIRS=/usr/spool/smail			# common
X#SPOOL_DIRS=/usr/spool/smail:/usr2/spool/smail	# use of alternate filesystem
X#SPOOL_DIRS=/usr/smail/spool			# I use this right now
X
X
X# LOG_DIR - smail logging directory
X#
X# optional (defaults to $SPOOL_DIR/log)
X#
X# Smail creates two log files in this directory: logfile and paniclog.
X# The first is a file that logs all incoming messages and deliveries,
X# plus many errors.  The second file (paniclog) logs important system
X# errors that smail can manage to write into the log file.
X
X#LOG_DIR=/usr/spool/smail/log			# common
X#LOG_DIR=/usr/smail/log				# I use this right now
X
X
X# UNSHAR_MAP_DIR - where unshared USENET map files are to be placed
X#
X# optional
X#
X# The getmap utility will read a list of files on the file
X# LIB_DIR/map/batch, and using unsharmap unshar these maps into the
X# UNSHAR_MAP_DIR directory.
X#
X# A common way that maps are distributed is through the USENET news group
X# "comp.mail.maps".  A sys file line of:
X#
X#	usenet-maps:comp.mail.maps,world:F:<UNSHAR_MAP_DIR>/work/batch
X#
X# will add names into the UNSHAR_MAP_DIR/work/batch file for getmap to
X# process.
X#
X# If UNSHAR_MAP_DIR is not defined, then the getmap and uuwho utilities
X# will not function.
X
XUNSHAR_MAP_DIR=/usr/spool/uumaps
X
X
X# NEWS_SPOOL_DIR - where news articles are stored
X#
X# optional (defaults to /usr/spool/news)
X#
X# C News stores pathnames in the batch file that are relative to
X# the top-level of the news article directory hierarchy.  Smail needs
X# to know the name of this directory in order to be able to extract
X# the news articles from comp.mail.maps.
X
X#NEWS_SPOOL_DIR=/usr/spool/news
X#NEWS_SPOOL_DIR=/var/spool/news
X
X
X# UUWHO_FILE - file used to store the uuwho file
X#
X# optional (defaults to $LIB_DIR/uuwho)
X#
X# This specified the file used to store the host database generated by
X# and used by the uuwho command.  If the uuwho database is stored in a
X# DBM file, then UUWHO_FILE is the file prefix before adding the .pag
X# and .dir suffixes to form the actual files.
X#
X# If UUWHO_FILE does not begin with /, then the name is relative to
X# the $LIB_DIR directory.
X
X#UUWHO_FILE=$UNSHAR_MAP_DIR/uuwho	# to store database with the map files
X
X
X# UUWHO_USE_DBM - configure the uuwho command to use the DBM library
X#
X# optional
X#
X# If you would like the uuwho utility to use the DBM library, set
X# UUWHO_USE_DBM to true.  If this is not set, then the uuwho utility
X# will use a sorted database.  Earlier versions of the uuwho utility
X# worked only with the DBM library.
X#
X# Not using DBM does not result in any real measurable speed-up, since
X# binary searches of even large databases happen fast enough to
X# prevent users from noticing.  However, generation of the DBM uuwho
X# database can take significantly longer.  The uuwho utility creates
X# sorted databases by calling the sort utility, which is usually quite
X# fast.
X
X#UUWHO_USE_DBM=true				# use DBM
X#UUWHO_USE_DBM=					# default, don't use DBM
X
X
X# TMP_DIR - secure temp directory used by smail utilities
X#
X# optional (defaults to /tmp)
X#
X# Some smail utilities use TMP_DIR to define a directory in which
X# their temporary files can be created.  Utilities that use this
X# directory are those that wish to use a secure temporary area.
X#
X# The only smail utilities that need to use TMP_DIR are utilities that
X# should be run as root, or as some other user with appropriate privledges.  
X# It is therefore recommended that TMP_DIR not be globally writable.  
X
X#TMP_DIR=$UNSHAR_MAP_DIR/tmp			# common for unsecure /tmp
X#TMP_DIR=/usr/tmp				# if /usr/tmp is sticky
X#TMP_DIR=$LIB_DIR/tmp
X
X
X# SECURE_PATH - path for smail utilities
X#
X# optional (defaults to system-specific path or /bin:/usr/bin)
X#
X# The smail utilities often set their PATH to begin with the SECURE_PATH.
X# The SECURE_PATH should be a path of directories where standard commands
X# are located.  These directories and commands should not be writeable by
X# normal users.  A common directory for smail utilities to append to
X# SECURE_PATH is UTIL_BIN_DIR.
X
X#SECURE_PATH=/bin:/usr/bin:/usr/ucb		# common for BSD systems
X#SECURE_PATH=/bin:/usr/bin:/usr/amdahl/bin	# common for UTS/580 systems
X#SECURE_PATH=/bin:/usr/bin			# common for System V system
X
X
X# MAN1 - where smail user command man pages are to be installed
X# MAN5 - where smail file format man pages are to be installed
X# MAN8 - where smail administrator man pages should be installed
X# MAN1_EXT - file extension for user command man pages
X# MAN5_EXT - file extension for file format man pages
X# MAN8_EXT - file extension for adminstrator man pages
X#
X# optional
X#
X# The man page for "foo.an" in the smail man/man5 source directory
X# will be installed in MAN5/foo.MAN5_EXT, if MAN5 is defined.
X#
X# For some reason, BSD and System V differ on where file format man
X# pages are kept, hence the unusual values of MAN5 for System V.
X
X#MAN1=/usr/man/man1				# common for BSD systems
X#MAN1=/usr/man/u_man/man1			# common for System V systems
XMAN1=/usr/local/man/man1			# common for local man pages
XMAN1_EXT=1					# common
X
X#MAN5=/usr/man/man5				# common for BSD systems
X#MAN5=/usr/man/a_man/man4			# common for System V systems
XMAN5=/usr/local/man/man5			# common for local man pages
X#MAN5=/usr/local/man/man4			# common for local man pages
XMAN5_EXT=5					# common for BSD systems
X#MAN5_EXT=4					# common for System V systems
X
X#MAN8=/usr/man/man8				# common for BSD systems
X#MAN8=/usr/man/a_man/man1			# common for System V systems
XMAN8=/usr/local/man/man8			# common for local man pages
X#MAN8=/usr/local/man/man1			# for Sys V local man pages
XMAN8_EXT=8					# common
X#MAN8_EXT=1m					# system V suffix
X
X
X# COMPRESS - file compression
X#
X# optional (default is system dependent or uses cat)
X#
X# The savelog utility can save space by compressing old log files.
X# Normally when a file is compressed, the suffix is added to the
X# filename.
X#
X# The COMPRESS symbol is the name of a program such that:
X#
X#		$COMPRESS $COMP_FLAG filename ...
X#
X# the file: filename is replaced by: filename$DOT_Z
X# regardless of the size of filename.  The command:
X#
X#		$UNCOMPRESS filename$DOT_Z
X#
X# will replace filename$DOT_Z with the original filename.
X# The command:
X#		$ZCAT filename$DOT_Z
X#
X# will read the compressed file: filename$DOT_Z and write the
X# plain text to standard output while leaving the file compressed.
X
XCOMPRESS=compress				# common
XCOMP_FLAG="-f"
XUNCOMPRESS=uncompress
XZCAT=zcat
XDOT_Z=".Z"
X
X#COMPRESS=pack					# System V standard
X#COMP_FLAG="-f"
X#UNCOMPRESS=unpack
X#ZCAT=pcat
X#DOT_Z=".z"
X
X#COMPRESS=true					# if no compress is used
X#COMP_FLAG=""
X#UNCOMPRESS=true
X#ZCAT=cat
X#DOT_Z=""
X
X
X# MISC_C_DEFINES - miscellaneous #defines for C programs
X#
X# optional
X#
X# The value of MISC_C_DEFINES is included directly into the file defs.h
X# in each source directory.  It is useful as a central place for
X# miscellaneous #defines not otherwise setable above.  In particular,
X# it is useful for overriding other more values given in the file
X# src/config.h.  It was felt that it was appropriate to keep the
X# EDITME file fairly small, with only a reasonable subset of the
X# configurable aspects of smail being explicitly described.  As a
X# result, there may be some other things in config.h that you may
X# wish to change.  Use #define's here to accomplish this.
X#
X# A suitable collection of #undef's and #define's here can also
X# change the behavior defined in the file under conf/os or conf/arch
X# for your operating system and architecture.  However, use of
X# MISC_C_DEFINES for this is discouraged.
X#
X# As with /bin/sh scripts, a logical line beginning with a : causes
X# that line to be parsed but ignored.  If it were simply commented out
X# then the second line would be processed.
X
X: MISC_C_DEFINES='			/* example only */
X#undef ALIASES_FILE
X#define NO_ALIASES_FILE			/* disable aliases file */
X#define REQUIRE_CONFIGS TRUE		/* dont allow optional config files */
X#define DIRECTOR_FILE NULL		/* no director file */
X#define TRANSPORT_FILE NULL		/* no transport file */
X#undef LOCAL_MAIL_FILE			/* see src/config.h */
X#define LOCAL_MAIL_FILE "/usr/mail/${lc:user}"
X'
X
XMISC_C_DEFINES='
X#define HAVE_SETEUID
X#define seteuid(uid) setresuid(-1, (uid), -1)
X#define setegid(uid) setresgid(-1, (uid), -1)
X'
X
X# MISC_SH_DEFINES - miscellaneous script to include in defs.sh
X#
X# optional
X#
X# The value of MISC_SH_DEFINES is included directly into the file
X# defs.sh, in each source directory.  It is a useful place to store
X# script lines to override values set by the mkdefs.sh shell script
X# or in a conf/os or conf/arch file.
X#
X# As with /bin/sh scripts, a logical line beginning with a : causes
X# that line to be parsed but ignored.  If it were simply commented out
X# then the second line would be processed.
X
X: MISC_SH_DEFINES='			# example only
XLIST_FILENAME="~operator/mail/lists/${lc:user}"	# somewhat silly example
X'
X
X
X# MISC_SED_DEFINES - miscellaneous lines to include in defs.sed
X#
X# optional
X#
X# The value of MISC_SED_DEFINES is included directly into the file
X# defs.sed, in each source directory.  It is a useful place to store
X# sed lines to override lines set by the mkdefs.sh shell script from
X# information in a conf/os or conf/arch file.
X#
X# As with /bin/sh scripts, a logical line beginning with a : causes
X# that line to be parsed but ignored.  If it were simply commented out
X# then the second line would be processed.
X
X# We can't readily think of good examples for this one.
X: MISC_SED_DEFINES=''
END_OF_FILE
if test 47337 -ne `wc -c <'smail-3.1.26/conf/EDITME'`; then
    echo shar: \"'smail-3.1.26/conf/EDITME'\" unpacked with wrong size!
fi
# end of 'smail-3.1.26/conf/EDITME'
fi
if test -f 'smail-3.1.26/conf/os/hp-ux8.0' -a "${1}" != "-c" ; then 
  echo shar: Will not clobber existing file \"'smail-3.1.26/conf/os/hp-ux8.0'\"
else
echo shar: Extracting \"'smail-3.1.26/conf/os/hp-ux8.0'\" \(1405 characters\)
sed "s/^X//" >'smail-3.1.26/conf/os/hp-ux8.0' <<'END_OF_FILE'
X# @(#)conf/os/hp-ux8.0	1.4 8/8/92 18:42:30
X#
X# hp-ux8.0 - define characteristics of Hewlet Packard's HP-UX version 8.0
X#
X# contributed by Chip Salzenberg <chip@tct.com>
X
X. $ROOT/conf/os/sys5.3		# this is on an System V release 3 base
X
X# OSNAMES - Names defining this operating system
XOSNAMES="UNIX_HPUX8_0:UNIX_HPUX8:UNIX_HPUX:$OSNAMES:POSIX_OS"
X
X# CC - the C compiler to use for compiling smail
XCC=cc
X
X# CFLAGS - flags that should be passed to the C compiler
XCFLAGS="-Aa -D_HPUX_SOURCE"
X
X# OSLIBS - name any object libraries containing routines we will need
XOSLIBS="-lndbm $OSLIBS"		# use this to get ndbm
X
X# HAVE - what features should be used with this operating system
XHAVE=BSTRING:SYS5_STRLIB:READDIR:VFPRINTF:GETOPT:DUP2:ULIMIT
XHAVE=$HAVE:MKDIR:SETGROUPS:NDBM:YP:GETHOSTNAME:BSD_NETWORKING
X
X# MISC_DEFINES - miscellaneous definitions
XMISC_DEFINES=INET_NTOA_USE_STRUCT
X
XLOCKING_PROTOCOL="\
X#include <unistd.h>
X#define LOCK_REQUIRES_WRITE
X#define lock_fd(fd)		(lockf((fd), F_TLOCK, 0L) < 0? FAIL: SUCCEED)
X#define lock_fd_wait(fd)	(lockf((fd), F_LOCK, 0L) < 0? FAIL: SUCCEED)
X#define unlock_fd(fd)		((void) lockf((fd), F_ULOCK, 0L))
X#define unlock_fd_wait(fd)	((void) lockf((fd), F_ULOCK, 0L))
X#define USE_FCNTL_RD_LOCK
X#define lock_fd_rd_wait(fd)	(fcntl_rd_lock(fd))
Xextern int fcntl_rd_lock();
X"
X
X# DRIVER_CONFIGURATION - configuration file describing smail drivers
XDRIVER_CONFIGURATION=bsd-network
END_OF_FILE
if test 1405 -ne `wc -c <'smail-3.1.26/conf/os/hp-ux8.0'`; then
    echo shar: \"'smail-3.1.26/conf/os/hp-ux8.0'\" unpacked with wrong size!
fi
# end of 'smail-3.1.26/conf/os/hp-ux8.0'
fi
echo shar: End of archive 1 \(of 1\).
cp /dev/null ark1isdone
MISSING=""
for I in 1 ; do
    if test ! -f ark${I}isdone ; then
	MISSING="${MISSING} ${I}"
    fi
done
if test "${MISSING}" = "" ; then
    echo You have the archive.
    rm -f ark[1-9]isdone
else
    echo You still need to unpack the following archives:
    echo "        " ${MISSING}
fi
##  End of shell archive.
exit 0