Tony Gale writes:
>
> There's always an exception. For example, legacy systems with strange
> (but conformant) IP stacks - some VMS systems for example. I would
> love to be able to do set per-host concurrency for such systems where
> I know *exactly* what the upper limit on concurrent connections it
> can handle is, cause it's defined in it's IP / MTA implementation.
>
> There's no point in going above this figure cause it just ties up my
> remote connections due to the way it handles connections above this
> number - i.e. it becomes a black hole.
If you know that you have an ongoing need to talk to hosts like this,
install another instance of qmail with the desired concurrencyremote,
and use a virtualdomain on your main qmail to redirect the mail
through that qmail. Sounds complicated, but it isn't.
echo 'dumb.host:dumbhost' >>/var/qmail/control/virtualdomains
rm /var/qmail2/control/*
ln -s /var/qmail/control/me /var/qmail2/control/me
echo '4' >/var/qmail2/control/concurrencyremote
echo '|/var/qmail2/bin/forward "$EXT2"' >~alias/.qmail-dumbhost-default
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
