Apologies for the offtopic inquiry, but I'm pretty sure there are a
bunch of qmail experts here and I need dollop of reassurance: We're
contemplating swtiching from sendmail to qmail. This is already a
bit of an operational problem [worrying about how many things will
break when we do the conversion [e.g., we have various system tools
we've written for messing with mailboxes that will probably break;
other tools for collecting stats, processing logs, etc] we'll have to
also change to a different POP server so more changes will have to be
dealt with] and trying to bound how much of a disturbance it'll be to
operations to 'drop in' qmail...
So I visit DJB's qmail page and discovered, rather to my dismay, that
qmail seems to require also replacing inetd.. Now while this might
be a prudent and sensible thing to do, it also will potentially
'rock' a *LOT* of other programs and applications.. But undaunted, I
go and check the links for tcpserver and discover that it is
apparently not just an inetd replacement, but it, itself, a whole
collection of apps [ucspi-tcp]... Again, the problem isn't that this
that isn't isn't a prudent/recommended changover, but it has very
much changed the size of the 'try qmail' project ---
Surely switching to qmail can't take THIS much much mucking around
down in the bowels of the TCP machinery???? Thanks!
/Bernie\
--
Bernie Cosell Fantasy Farm Fibers
mailto:[EMAIL PROTECTED] Pearisburg, VA
--> Too many people, too few sheep <--
