Hello,
I have a somewhat busy mail relay running postfix 2.7, which has
problems with a slow destination.
The symptom: the incoming queue grows large, the active queue is always
at qmgr_message_active_limit and only (well, mostly) contains messages
for the slow domain.
What I have already
What about setting a second instance up to use for your
slow destinations. Then you can route to that instance from
your production instance and keep those messages from
impacting the faster sites.
Cheers,
Ken
On Fri, Mar 19, 2010 at 03:58:42PM +0100, Attila Nagy wrote:
Hello,
I have a
On Fri, Mar 19, 2010 at 03:58:42PM +0100, Attila Nagy wrote:
I have a somewhat busy mail relay running postfix 2.7, which has problems
with a slow destination.
I can't limit the number (or rate) of incoming e-mails for that domain, and
I can't increase the throughput of the destination,
Attila Nagy:
So:
- is there any way to let other domains get into the active queue in a
No.
Just like ordinary programs read large files sequentially using a
limited amount of intermediate buffer space, the Postfix queue
manager reads a large queue sequentially using a limited amount
of
On 03/19/10 16:13, Victor Duchovni wrote:
Forward mail for this domain to a separate queue (Postfix instance)
that handles mail for this---and perhaps some other similar---domains.
The slow domain will no longer clog your primary queue.
You are right that this will solve the problem, but
Attila Nagy:
I've only written this, because I was sure that somebody would miss it.
This destination is not slow because of slow delivery times on the
already open connections, but because of connection timeouts (I can
observe this on other, mostly silent systems, which send only few
On Fri, Mar 19, 2010 at 05:28:07PM +0100, Attila Nagy wrote:
On 03/19/10 16:13, Victor Duchovni wrote:
Forward mail for this domain to a separate queue (Postfix instance)
that handles mail for this---and perhaps some other similar---domains.
The slow domain will no longer clog your primary
