Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!wasp.eng.ufl.edu!esj
From: esj@wasp.eng.ufl.edu (Eric S. Johnson)
Newsgroups: comp.mail.sendmail
Subject: Re: How do you maintain your .cf?
Message-ID: <23955@uflorida.cis.ufl.EDU>
Date: 25 Jul 90 04:29:49 GMT
References: <KARL.90Jul20104100@giza.cis.ohio-state.edu>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: esj@eng.ufl.edu (Eric S. Johnson)
Distribution: na
Organization: U of Florida  Engineering Computer Support Facility
Lines: 29

In article <KARL.90Jul20104100@giza.cis.ohio-state.edu> karl_kleinpaste@cis.ohio-state.edu writes:
>For the sake of my curiosity, mostly, I'd be interested in hearing how
>others maintain sendmail.cf.
>

I maintain sendmail.cf's on a large number of various machines/os's. 
What do is use a shell script which I put together which has as flags
a bunch of options. Key options are the domain under ufl.edu, the 
hostname, if the host is the "domain head" I.E. should accept and send 
mail for domain.ufl.edu as well as hostname.domainname.ufl.edu., if the 
host runs a MX sendmail version (ill get em all running 5.6X later ;-),
if the host is a ultrix decnet gateway, etc.

This shell script simply runs a bunch of sed's on a generic.cf which 
has various options commented out untill the sed removes the comment
headers on the lines. Example: The no-nameserver hosts hosts forward 
their mail to be final delivered by a host which digs nameservers.


#NONSR$*<@$+>$*		$#tcp$@$I$:$1<@$2>$3		user@host
#NSR$*<@$+>$*		$#tcp$@$2$:$1<@$2>$3		user@host

$I is a nameserver groking host and one of these two lines gets 
un-commented in ruleset 0.

This works with 90% of the machines. Real strangeness (and UUCP stuff ;-( )
gets hand edited.

Ej