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
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
On Thu, Oct 21, 1999 at 09:30:41AM -0400, Russell Nelson wrote:
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.
On Thu, Oct 21, 1999 at 04:52:56PM +0200, Mirko Zeibig wrote:
I guess you have to recompile qmail, then and have two sets of binaries etc?
So this would only be an approach for a handful of hosts.
Yes, but Do you have a lot of hosts, then dedicate some of them to have high
concurrency and
Mirko Zeibig writes:
I guess you have to recompile qmail, then and have two sets of binaries etc?
I would recommend that you have a whole separate source tree.
So this would only be an approach for a handful of hosts.
Right, those specific hosts which are consistently giving you trouble.
On Thu, Oct 21, 1999 at 01:34:42PM -0400, Russell Nelson wrote:
Right, those specific hosts which are consistently giving you trouble.
Hopefully you told the sysadmin that his system is broken, because if
it's giving you trouble, it's probably giving everyone else trouble as
well.
Well, not
On Tue, Oct 19, 1999 at 11:44:10PM -0400, Russell Nelson wrote:
Or to put it a different way, you want qmail to recognize and remember
those hosts and when one of that host's connections closes, adjust the
retry schedule for the next message bound for that host. However, the
next message
On Tue, Oct 19, 1999 at 04:57:08PM -0400, John R. Levine wrote:
Or use serialmail. This limits the concurrency to one and you'll have
to trigger serialmail from time to time, but it is easier I think to
install serialmail for a few band-aided sites than to have qmail
installations
Hello fellow qmail users:
In the qmail documentation, there's information about that says I can use
the concurrencyremote control file to set the maximum number of concurrent
remote mail deliveries can occur. I am wondering if this can be set on a
per system basis. Specifically, I want to set
It can only be set on a per physical queue basis. If each "system"
uses the same physical queue, then the answer to your question is no.
If the "systems" use different physical queues, then you can do it.
Ken Jones
Stan Horwitz wrote:
Hello fellow qmail users:
In the qmail documentation,
On Tue, Oct 19, 1999 at 03:00:50PM -0400, Stan Horwitz wrote:
particular qmail server. Is this possible? If so, how?
Take a look at
http://www.illuin.demon.co.uk/qmail/
there is a domain concurrency patch.
However this is from Aug 1997 so it is probably for qmail-1.01 and needs
adaption to
Stan Horwitz [EMAIL PROTECTED] wrote:
In the qmail documentation, there's information about that says I can use
the concurrencyremote control file to set the maximum number of concurrent
remote mail deliveries can occur. I am wondering if this can be set on a
per system basis. Specifically, I
Stan Horwitz [EMAIL PROTECTED] wrote:
Specifically, I want to set the concurrencyremote level
down to a value of 5 for one specific system (because its being overloaded
with mail processing) and while allowing concurrencyremote to be set to a
value of 50 for all other systems that might receive
On Tue, Oct 19, 1999 at 01:23:18PM -0600, Charles Cazabon wrote:
It's not really a qmail issue. If a particular mailhost is bogging down
because it is accepting more SMTP connections than it can actually handle,
it's due to:
-poor configuration. Solution: tell the sysadmin.
On Tue, 19 Oct 1999 15:39:28 -0400 (EDT) Dave Sill wrote:
However, should you chose to attempt a band-aid for a key remote site,
the approach would be to install a second qmail with a lower
concurrencyremote and redirect messages for the swamped site from the
primary qmail to the
However, should you chose to attempt a band-aid for a key remote site,
the approach would be to install a second qmail with a lower
concurrencyremote and redirect messages for the swamped site from the
primary qmail to the secondary.
Or use serialmail. This limits the concurrency to one
Markus Stumpf writes:
1) There are mailservers that don't accept more than n concurrent
connections from the same IP (while they still have the capability for
open slots for other IPs).
However this causes them to first "see" the connection and then
dropping them. I wouldn't
17 matches
Mail list logo
