On 03.11.2020 11:39, Matus UHLAR - fantomas wrote:
> On 03.11.20 11:26, natan wrote:
>> For test I create aliasgroup ~100 user. For test i try send like:
>>
>> for i in {1..10}; do echo "asdasdasdasda" |mail
>> aliasgr...@domain.ltd;done & (for test x 4) - I known this is stupid
>>
>> In log i found "Connection timed out" and I dont known what value
>> exceeds
>>
>> 10.0.100.5 - this is dovecot with lmtp to deliver
>>
>> main.cf:
>> ....
>> virtual_transport = lmtp:inet:10.0.100.5:24
>>
>> lmtp_destination_concurrency_limit = 100 - > probably this is value -
>> but I may be wrong - maby check this value to 600 ?
>> default_destination_concurrency_limit = 100
>> lmtp_destination_recipient_limit = 1
>> .....
>>
>> master.cf:
>> ....
>> smtp inet n - y - 100 smtpd
>> -o receive_override_options=no_address_mappings
>> ....
>>
>> In log I found:
>>
>> Nov 3 10:42:07 thebe4 postfix/lmtp[29734]: 4CQPvC3gPyz20nRG:
>> to=<user....@domain.ltd>, orig_to=<aliasgr...@domain.ltd>, relay=none,
>> delay=7.7, delays=0.25/0.28/7.1/0, dsn=4.4.1, status=deferred (connect
>> to 10.0.100.5[10.0.100.5]:24: Connection timed out)
>
> "connection timed out " means that postfix wasn't able to connect to
> destination. That could be caused by firewall, nothing listening on
> destination
> port, or the destination server has reached limit and does not accept
> connections.
>
> increasing concurrency limit on the postfix side does not help here.
> Increasing maximum number of servers on port 24 could help in the last
> case.
>
I dont have firewall in this case - I thinking abount
lmtp_destination_concurrency_limit. If lmtp_destination_concurrency_limit.
In dovecot via 24 I dont have more limit or timeout - this is proxy to
klaster dovecot (director+node) like:
20-lmtp.conf:
lmtp_proxy = yes
protocol lmtp {
syslog_facility = local3
mail_plugins = $mail_plugins
passdb {
args = proxy=y nopassword=y port=24
driver = static
}
}
--
