Hello,
Thx again for the replies, I am starting to see the light at the end of
the tunnel :-)
I have tried to disable the lmtp connection caching by setting the
following variable on main.cf:
lmtp_cache_connection=no
but the same errors are happening.
Victor Duchovni wrote:
On Thu, Jun 24, 2010 at 06:55:47PM +0200, Luciana Moreira wrote:
Per nexthop, provided the transport is called "lmtp", and not something
else. Do you route multiple destination domains to the LMTP transport?
If so, use a consistent nexthot destination "lmtp:[lmtp.example.com]"
Right now we are using the lmtp as a content filter as defined in the
main.cf:
content_filter = lmtpd:171.20.1.10:7026
But I am starting to believe that this is where the problem may be
comming from even though it works perfectly besides the fact that some
messages take too long to be processed due to the deferred queueing.
Could it be that we need to set it as a transport rather than a content
filter to have the client side concurrency use my settings?
However, if LMTP delivery is indirect, via mailbox_transport, then the
LMTP concurrency ceiling is actually determined by the process limit of
the local(8) delivery agent, since it is local(8) and not the queue
manager that hands off mail to lmtp(8) via mailbox_transport.
As I mention above we deliver it via content filter.
Regards,
Luciana
