aliasgroup + lmtp + Connection timed out

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

aliasgroup + lmtp + Connection timed out

natan
Hi
For test I create aliasgroup ~100 user. For test i try send like:

for i in {1..10}; do echo "asdasdasdasda" |mail
[hidden email];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=<[hidden email]>, orig_to=<[hidden email]>, 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)



I have other question
How I tune conf if in aliasgroup user set 1000 address in aliasgroup and send 1 e-mail ?

 

--

Reply | Threaded
Open this post in threaded view
|

Re: aliasgroup + lmtp + Connection timed out

Matus UHLAR - fantomas
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
>[hidden email];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=<[hidden email]>, orig_to=<[hidden email]>, 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.

--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"One World. One Web. One Program." - Microsoft promotional advertisement
"Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
Reply | Threaded
Open this post in threaded view
|

Re: aliasgroup + lmtp + Connection timed out

natan
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
>> [hidden email];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=<[hidden email]>, orig_to=<[hidden email]>, 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
  }

}

--