🚀 go-pugleaf

	     Tell me, why does SendMail need such complex configuration files?
	Wouldn't a preferable scheme be to look at ones environment at runtime
	and do the right thing by default?

This is a little like claiming your computer should "do the right thing
by default" when presented with a null program.  "The right thing" is
highly subjective, and probably depends on reading someones mind.  For
example, how should "a!b@c" be interpreted?  "(a!b)@c" as required by
the ARPANET?  "a!(b@c)" as required by existing UUCP software?  Someone
has to make a decision, and this decision must be implemented in the
sendmail config file.  In fact, "looking in ones environment" is done on
UNIX largely by reading a file.  Wouldn't such a file be called a config file?

Sure, sendmail configuration files are complex.  So is machine language.
It doesn't mean that you shouldn't have any machine language on your
machine.  It means you write a compiler from a high level language.

Sendmail's config files are very complex because they do so much.  What
should be done is for someone to write a simple compiler or interactive
front end that asks a few questions and generates the appropriate file.