onf:54:
imap_client_workarounds=outlook-idle is no longer necessary
-Original Message-
From: dovecot On Behalf Of Jorge Bastos via
dovecot
Sent: Thursday, June 20, 2019 11:32
To: dovecot@dovecot.org
Subject: RE: IMAP IDLE
Hum guys,
For this, i was comparing configuration from my old dbm
Message-
From: dovecot On Behalf Of Jorge Bastos via
dovecot
Sent: Thursday, June 20, 2019 11:04
To: dovecot@dovecot.org
Subject: RE: IMAP IDLE
Hi,
2.2.33.2
Well your confs are almost mine except for
director_ping_idle_timeout = 30 secs
submission_relay_max_idle_time = 29 mins
but i think
in the
inbox, no matter if it was selected for 15m or the last 4 hours
Any ideia please let me know,
-Original Message-
From: dovecot On Behalf Of @lbutlr via dovecot
Sent: Thursday, June 20, 2019 0:20
To: dovecot@dovecot.org
Subject: Re: IMAP IDLE
On 19 Jun 2019, at 16:11, Jorge Bastos
On 19 Jun 2019, at 16:11, Jorge Bastos via dovecot wrote:
> root@fastmail:/etc/dovecot# doveconf |grep -i idle
> default_idle_kill = 1 mins
> imap_idle_notify_interval = 2 mins
> imapc_max_idle_time = 29 mins
> mailbox_idle_check_interval = 30 secs
I have:
default_idle_kill = 1 mins
The IDLE disconnection timeout is hardwired in the Dovecot code
http://wiki.dovecot.org/Timeouts
It's set to the RFC minimum of 30min.
I am ok if connection is closed automatically after 30 min if client is not
responding but connection is not being closed even after 2 days.
Hmm.
I am ok if connection is closed automatically after 30 min if client is not
responding but connection is not being closed even after 2 days.
On Sat, Mar 26, 2016 at 2:52 AM, Joseph Tam wrote:
> Joy wrote:
>
> We have implement imap idle
Joy wrote:
We have implement imap idle in web mail built by us to have
push mail feature. IMAP idle working perfectly with browser notification
and we are happy with it but having one issue with users who close the
browser directly and never logout in that