Text written by Dave Sill at 09:14 AM 3/25/99 -0500:
>
>I agree, but I think all of the patches included should be optional
>and turned off by default. A single config file with a short
>description of each patch and a mechanism for enabling it would be
>nice.
I think this is an excellent suggestion. So the "official patch" would
essentially be like one of those "software samplers" that come with every
Boot magazine (for example), plus maybe an interactive shell script or
something that gives the info you mention.
>>So, what goes in the official patch?
>
>I don't use any of the patches, but the most popular ones seem to be
>those that do spam control and improved logging.
I'd add Russ' Open-SMTP to that list, and I'd suggest that the official
patch include daemontools, since it is not included in the standard Qmail
download. Other patches that I hear about a lot on this list (this is just
off the top of my head, and totally non-scientific) are: rblsmtpd,
qmail-uce, qmail-popbull and quite a few that I'm accidentally forgetting. :)
-----------------------------------------------------------------
Kai MacTane
System Administrator
Online Partners.com, Inc.
-----------------------------------------------------------------
>From the Jargon File: (v4.0.0, 25 Jul 1996)
can't happen
The traditional program comment for code executed under a condition
that should never be true, for example a file size computed as
negative ... Although "can't happen" events are genuinely infrequent
in production code, programmers wise enough to check for them habitu-
ally are often surprised at how frequently they are triggered during
development and how many headaches checking for them turns out to
head off.
