> By the way, RTFM rblsmtpd, or look at the way it was called in the examples.
> You should be able to figure out how to call it from inetd if you are really
> so against using tcpserver.
I sense a wee bit of hostility on this list! sheesh!
Whether you think their witnesses are credible or non-credible...
they've admitted monopoly power, they've admitted the absence of
competitive constraints, they've admitted raising prices to hurt
consumers, they've admitted depriving consumers of choice and they've
admitted that the reason was because they were afraid that consumers
would in their view make the wrong choice, which is the non-Microsoft
choice. -- DAVID BOIES, US Department of Justice
I'm mostly interested in the last part. I sure would be nice if the
docs didn't assume that the consumer/installer hasn't made the non-qmail
or non-djb choice. You know, sometimes it is nice to use standards. If
qmail offers a sufficient reason to change, people will -- but forcing
part of qmail on people isn't well accepted by me and I'm sure there
are others that feel the same way.
I use tcpd/inetd and I fail to see why I need to start splitting up my
system to run tcpserver, xinetd, etc., just to get an smtp to run!
I once tried to install ppp under sunos... way back in like 93 or 94 or
something. You see, this one package required another package to be
pre-installed before it would work. Of course, that package was not
distributed as part of the original, since they were separate
packages... and you had to find the package -- since there might be
upgrades and fixes to it. Fine, found that package. Now that package
required two more other packages to be previously installed before *it*
would go it. Repeat this a few times and add a package or two that no
longer is used (superceded?) and you have a royal mess.
I just wish the qmail system would be friendly to non-djb software
and/or have instructions that were laid out with some vision. It's
really nice to see a context diff patch -- but it doesn't do any good if
the file being patched is hard referenced through someone's personal src
tree (ie: not just ./file) and/or the patch doesn't tell you when or
how to apply it (ie; before make config check or after?).
Anyway, enough rant.
Yes, I'll rtfm *again* and see the same old examples which won't help
any more now than it did the first time that I read them. Yes, I'll
figure it out. I'm just doing what I've always done on this list and
suggested that if, perhaps, qmail really wants more people to use it --
perhaps the install could be a little more organized and/or straight
forward and documented!
Right now I consider qmail (source) as organized as an egg after an m80
has gone off inside it. I've seen many people give up trying to install
qmail because it was just too convoluted. I also think that
documentation that assumes or requires other system design capitulations
that may or may not be neccessary -- will be viewed as distractful at the very least.
Scott
