Hello Wietse,
Thx a lot for your quick reply.
I thought that the client side concurrency was defined by:
1) lmtp_destination_concurrency_limit
2) the number of lmtp processes
I have set them both to 1 now and still get the same error message. So I
am starting to believe that there must be yet another configuration that
I am unaware of. I have read many pages on the topic but haven't yet
seen anything different from what I have done.
What I am missing?
regards,
Luciana
Wietse Venema wrote:
Luciana Moreira Signed by - PrivaSphere AG:
Hello guys,
I am trying to tunne our postfix installation. In our setup we receive
mails, pass them after an anti-virus milter to a internal mail
processing system that uses lmtp using a content filter, and then
forward the mail to the final destination.
Since I have full control over the internal mail processing system,
ideally I should be able to define the number of processes in such a way
that all requests would get through without getting deferred between the
internal hops. Unfortunately this is not the case. Several messages are
going to the deferred queue with the mesage bellow:
0EEF34A925 1247 Thu Jun 24 16:38:19 f...@foo.com
(lost connection with 171.20.1.10[171.20.1.10] while sending MAIL FROM)
jm-tes...@mydomain.com
You need to reduce the CLIENT SIDE concurrency: fewer processes
in master.cf, for example.
Wietse
