similar to: Race condition in IMAP NOTIFY for events received NOTIFY_DELAY_MSECS apart

Quoting RFC 5465 (NOTIFY): ?If the NOTIFY command enables MessageNew, MessageExpunge, AnnotationChange, or FlagChange notifications for a mailbox other than the currently selected mailbox, and the client has specified the STATUS indicator parameter, then the server MUST send a STATUS response for that mailbox before NOTIFY's tagged OK. [?] If either AnnotationChange or

On Sun, 19 Jul 2015 at 19:21:16 +0200, Guilhem Moulin wrote: > The "subtree" mailbox filter has the same problem, but the > non-parameterized ones ("inboxes", "personal" and "subscribed") work > fine. Actually there are further problem with the INBOX namespace, to which I'm subscribed: $ /usr/lib/dovecot/imap S1: * PREAUTH [CAPABILITY

Hi list, The NOTIFY extension (RFC 5465) works fine for mailboxes in the "virtual/" namespace, but it crashes the IMAP client when used with a mailbox in the empty "" namespace: ~$ /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 ? NOTIFY SPECIAL-USE] Logged in as guilhem a NAMESPACE * NAMESPACE (("" "/")("virtual/"

Hi, I just updated my Dovecot to the new build in Fedora 26, which is based on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving notifications about new mail in folders other than inbox (the same version of Evo that worked fine against Dovecot 2.2.30.2). The only folder that still gets notifications is inbox. I see there have been changes to NOTIFY code in this release. What

http://hg.dovecot.org/dovecot-2.2-notify/ contains the initial implementation of IMAP NOTIFY extension. It's less than half-working, but the difficult part of it is done I think. If I give it a command like: x notify set (personal (messagenew messageexpunge flagchange)) and then in another session I copy a message to another mailbox, it sends: * STATUS "foobar" (MESSAGES 77

Here is an example with APPEND $ /usr/lib/dovecot/imap S1: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem C1: a1 NOTIFY SET (INBOXES (MessageNew MessageExpunge FlagChange)) S1: a1 OK NOTIFY completed (0.000 secs) $ /usr/lib/dovecot/imap S2: * PREAUTH [CAPABILITY IMAP4rev1 ? MOVE NOTIFY SPECIAL-USE] Logged in as guilhem C2: a2 APPEND

On 29 Jun 2017, at 13.27, Bojan Smojver <bojan at rexursive.com> wrote: > > Hi, > > I just updated my Dovecot to the new build in Fedora 26, which is based > on 2.2.31. After I did that, Evolution (3.24.3) is no longer receiving > notifications about new mail in folders other than inbox (the same > version of Evo that worked fine against Dovecot 2.2.30.2). The only

hi, i'm not sure if i've discovered a bug or if i'm not following the IMAP specs correctly. observations: { echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993 produces the following output (aside from the openssl s_client cert-inspection

Hi, For a few weeks I've been running a custom notification script[1] that uses IMAP NOTIFY. The script uses a single connection, sets up a NOTIFY watch on a couple of mailboxes + automatic FETCH for the selected mailbox. If a status update arrives for a different mailbox, it selects that box and fetches the mail. Today I got the following error in the log: > Aug 5 14:56:12 karif

On 27.04.2016 11:00, Heiko Schlittermann wrote: > Hi, > >> ? login ? >> C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL) >> >> Apr 27 09:29:16 backend1 dovecot: imap-login: Login: user=<heiko>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6651, secured >> Apr 27 09:29:16 backend1 dovecot: imap(heiko):

On 9.5.2019 9.01, Christian Balzer via dovecot wrote: > Hello, > > Both the examples on the Push Notification wiki page and the XAPS plugin > docs seem to suggest or state that LMTP/LDA is required. It is required. > However IMAP IDLE notifications work without either of these (please no > religious discussion of why Dovecot LMTP is the best thing since sliced > bread and

Hello, On Thu, 9 May 2019 09:14:13 +0300 Aki Tuomi via dovecot wrote: > On 9.5.2019 9.01, Christian Balzer via dovecot wrote: > > Hello, > > > > Both the examples on the Push Notification wiki page and the XAPS plugin > > docs seem to suggest or state that LMTP/LDA is required. > > It is required. > Thanks for the quick, but unwelcome reply. There's a

I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server Notice that some status responses are missing (For folders INBOX.Archive, INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected In rfc5819 there is this: If the server runs into unexpected problems while trying to look up the STATUS information, it MAY drop the corresponding STATUS reply. In

Hello, Both the examples on the Push Notification wiki page and the XAPS plugin docs seem to suggest or state that LMTP/LDA is required. However IMAP IDLE notifications work without either of these (please no religious discussion of why Dovecot LMTP is the best thing since sliced bread and that everybody should use it). The LUA part of the push notification docs however states that events other

Greetings, I'm new to the list. I have encountered what I believe to be a bug in the return of HIGHESTMODSEQ when talking to a IMAP client. HIGHESTMODSEQ does not appear to be incrementing when a new message arrives. The exact steps I took are: 1) Create a new mail account 2) Send a mail to the account, check that you can receive the email. Send a second mail to the account. 3) perform a

On 09/10/2020 21:17, Gustavo Ajeitos [Office365] wrote: > Hello, > > I'm using dovecot 2.3.10 in OpenSUSE and I have configured a > master/master replication between two backends, it works well but I > have found an issue with the replication of the HIGHESTMODSEQ. > When I move a set of message from a mailbox to other, e.g. move 3 > messages from INBOX to Junk, the

Hello, I'd like to follow up on someone else's old thread: http://dovecot.org/list/dovecot/2012-April/082624.html I understand that Dovecot (that 2012 discussion was about version 2.0.18) can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was never enabled for a mailbox. I'd like to get a clarification on how to enable proper persistent modseq

Hi John, ??? Thank you for your answer! I agree with you, I think you recommendation should solve the problem, it seems the only possible workaround. I have to investigate if it possible and how to accomplish that with the load balancer. Gustavo El 3/11/20 a las 15:27, John Fawcett escribi?: > On 09/10/2020 21:17, Gustavo Ajeitos [Office365] wrote: >> Hello, >> >>

Hello, I'm using dovecot 2.3.10 in OpenSUSE and I have configured a master/master replication between two backends, it works well but I have found an issue with the replication of the HIGHESTMODSEQ. When I move a set of message from a mailbox to other, e.g. move 3 messages from INBOX to Junk, the HIGHESTMODSEQ get different on each server, with no errors in the log: [Borrador] 34:34

Hello, after dealing with shared folder within version 2.0 rc* I started using it with a group of users. user1 shares a folder to user2. user2 has access to messages of this shared folder. After a "random" time (minutes up to several days) user2 doesn't see those messages anymore. user1 (the owner) hasn't changed anything inside this folder. All messages are still in place