[Dovecot] imap idle and concurrent connections
Hi,
in my testing dovecot (1.2 in that case) seems to not notify all idling clients about new "recent" mails but only one of them. The others get usually a message about the new number of mails after some time but never recent ones. Only one client gets notified about a new mail. Is that a known issue or something which might be configuration specific?
Wolfgang
On 04/07/2011 09:04, Wolfgang Rosenauer wrote:
Hi,
in my testing dovecot (1.2 in that case) seems to not notify all idling clients about new "recent" mails but only one of them. The others get usually a message about the new number of mails after some time but never recent ones. Only one client gets notified about a new mail. Is that a known issue or something which might be configuration specific?
Interesting if you have a reproducible test case?
I have seen a peculiar issue for a while with Thunderbird, where in a shared inbox, my Thunderbird is set to enable it's basic "lemonade" support and very occasionally someone else using the shared mailbox marks a message read but I don't see it read on my machine (it's even tricky to get TB to resync and notice...). Also sometimes two emails arriving very close together my Thunderbird only shows one of them
There are plenty of non Dovecot things which could cause these symptoms: Thunderbird bugs (probably!), NAT timeouts on the client side (I'm behind a NAT). However, I haven't been able to repro this in a consistent way...
Do please consider if NAT is involved in your scenario. I have a sneaking suspicion that NAT timeouts might be at least part of the reason?
Good luck
Ed W
Hi,
On Mon, Jul 4, 2011 at 11:25 AM, Ed W lists@wildgooses.com wrote:
On 04/07/2011 09:04, Wolfgang Rosenauer wrote:
Hi,
in my testing dovecot (1.2 in that case) seems to not notify all idling clients about new "recent" mails but only one of them. The others get usually a message about the new number of mails after some time but never recent ones. Only one client gets notified about a new mail. Is that a known issue or something which might be configuration specific?
Interesting if you have a reproducible test case?
this is reproduced with IMAP connections idling in a telnet session. Two telnet imap connections open and both idling on the inbox and only one of them gets the "1 recent" notification. I've reproduced on a system where I have access which is a Dovecot 1.0 as delivered in Debian Lenny but also on another system which is apparently Dovecot 1.2 (but I have no direct access to that one so cannot be sure which version runs exactly.
Wolfgang
On 4.7.2011, at 13.07, Wolfgang Rosenauer wrote:
Two telnet imap connections open and both idling on the inbox and only one of them gets the "1 recent" notification.
This is how it's supposed to work according to IMAP RFC. Only one session ever sees a message as \Recent. Both of them gets an updated EXISTS though.
Hi,
On Mon, Jul 4, 2011 at 3:40 PM, Timo Sirainen tss@iki.fi wrote:
On 4.7.2011, at 13.07, Wolfgang Rosenauer wrote:
Two telnet imap connections open and both idling on the inbox and only one of them gets the "1 recent" notification.
This is how it's supposed to work according to IMAP RFC. Only one session ever sees a message as \Recent. Both of them gets an updated EXISTS though.
Is this: RFC 3501 Section 7.3.2?
Examples of situations in which this is not the case are: multiple clients having the same mailbox open (the first session to be notified will see it as recent, others will probably see it as non-recent)
So the implementation seems to be fine according to the RFC but it came somehow unexpected to me. It's not that this is required by the RFC though.
Thanks for the information, Wolfgang
participants (3)
-
Ed W
-
Timo Sirainen
-
Wolfgang Rosenauer