zimbra server delivering email to pop3 clients timeout

[rllanes2004]

thanks a lot Raunaq it look like its working ... remember that this is not a permanent anomaly ... just an occasional one ... right now i passed the solution to other coworker of my company to see if they have similar positive results ... one other thing ... in my last reply i said that my zimbra build does not have the proxy module installed ... therefore i cant use the proxyconfgen ... do you think i should activate this module in order to have more control over the timeout variables ... best regards

[Rajib Askory]

I think there is no need

[sergio_sd]

Hello Zimbra Community.
I'm sorry to resume this old topic.
But I have a similar problem and it is not possible to solve it with the proposed methods. Help me underdstand this.

There are pop3 email clients with weak channels (VSAT). Different clients are used, Thunderbird, Outlook.
Everyone has the same problem when receiving a large message.
If you immediately upload a message when checking mail, then it begins to multiply indefinitely if you do not delete it to the server via the web interface.
If only the headers are loaded during the check, then when you try to load the rest of the message, it does not load to the end, although data is being transmitted for some time.

Server: Release 8.8.15.GA.3869.UBUNTU18.64 UBUNTU18_64 FOSS edition, Patch 8.8.15_P7.

Enabled the trace log for zimbra.pop and have this:

Code: Select all

2021-10-14 15:09:21,889 INFO  [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - user testov@some.domain authenticated, mechanism=PLAIN
2021-10-14 15:09:21,891 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: +OK authentication successful
2021-10-14 15:09:24,197 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - C: STAT
2021-10-14 15:09:24,198 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: +OK 1 2068280
2021-10-14 15:09:24,198 INFO  [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - STAT elapsed=1
2021-10-14 15:09:26,675 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - C: LIST
2021-10-14 15:09:26,675 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: +OK 1 messages
2021-10-14 15:09:26,675 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: 1 2068280
2021-10-14 15:09:26,675 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: .
2021-10-14 15:09:26,676 INFO  [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - LIST elapsed=1
2021-10-14 15:09:29,532 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - C: UIDL
2021-10-14 15:09:29,533 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: +OK 1 messages
2021-10-14 15:09:29,533 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: 1 282.337A++ZxAz4I7glPoyDHoOhO2ySkTt6CHZwYVzNxI34=
2021-10-14 15:09:29,533 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: .
2021-10-14 15:09:29,533 INFO  [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - UIDL elapsed=1
2021-10-14 15:09:31,541 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - C: RETR 1
2021-10-14 15:09:31,545 TRACE [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - S: +OK message follows
2021-10-14 15:09:31,571 INFO  [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - RETR elapsed=30
2021-10-14 15:11:31,665 DEBUG [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - Idle timeout
2021-10-14 15:11:31,670 DEBUG [Pop3Server-3] [name=testov@some.domain;ip=10.168.0.12;oip=198.44.196.246;] pop - idle connection

2 minute - idle timeout. Where is set it is parameter?

[sergio_sd]

I get it )
While I was writing the previous post.

I`m find:

Code: Select all

~$ zmlocalconfig | grep 120
ldap_connect_pool_timeout = 120000
octopus_incoming_patch_max_age = 120
pop3_max_idle_time = 120
pop3_thread_keep_alive_time = 120
xmpp_server_session_idle = 1200000
zimbra_configrewrite_timeout = 120
zimbra_noop_max_timeout = 1200
zimbra_servlet_output_stream_buffer_size = 5120
zimbra_waitset_max_request_timeout = 1200

And make:

Code: Select all

~$ zmlocalconfig -e pop3_max_idle_time=1800
~$ zmlocalconfig -e pop3_thread_keep_alive_time=1800
~$ zmcontrol restart

Thanks for your attention!