similar to: NOTIFY broken in 2.2.31?

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

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

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/"

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):

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

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

your work on NOTIFY was brought to my attention, and I see it hasn't been changed in two months, a week after you announced it. a few users and some mail admins have been wanting something like this for k9 mail, which I help develop. what is the current status? is it worth installing and starting work in getting k9 to support it yet? I'd offer help on your end, but I just know java and

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

I've been working on Evolution's 'imapx' back end to support QRESYNC, and was going to look at NOTIFY next. Then I realised I may have to look at implementing it on the server side first. Before I can even contemplate that, though, I had to mirror it into git. I've always resisted the one-version-control-system-per-child craze, and these days if I'm even contemplating a

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $

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

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

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

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misconfiguration on my side, or a know / desired limitation or just a bug? I use LMTP to deliver

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

Timo Sirainen wrote: > On 21 Jun 2017, at 16.03, Mart Pirita <sysadmin at e-positive.ee> wrote: >>>> ltest_lib-test-bits.o: In function `bits_required64': >>>> /usr/src/redhat/BUILD/dovecot-2.2.30/src/lib/bits.h:33: undefined >>>> reference to `__builtin_clzll' > This can be fixed with the attached patch. Thanks, got this time new error, do

Hi Aki, first thanks for the quick fix. Unfortunately, it only resolves the issue partially. For the ?To: undisclosed-recipients:;?, it works now. For ?To: ? it still crashes (i. e. what I did with my manual lmtp dialog). Michael > On 13. Dec 2019, at 11:54, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > Hi! > > We have released v2.3.9.1 fixing this issue. >

Hi Timo, >> * LIST (\HasNoChildren) "/" "folder1" >> * LIST (\HasNoChildren) "/" "folder2" >> * LIST (\HasNoChildren) "/" {9} >> six"wafer >> . OK List completed. >> >> Note the {9} length of the following real folder name. Is this normal >> handling of special folder names ? >Yes. Well,

Hello, since the upgrade from 2.3.8 to 2.3.9 (using the Ubuntu 18.04 packages from dovecot.org), lmtp crashes for me for some mails. Currently I have three pending mails in my postfix deferred queue since the upgrade a couple of days ago. I did not observe these issues with 2.3.8. The backtrace from one of the coredumps: Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from

Can you provide p *addr? Aki On 13.12.2019 13.15, Michael Stilkerich wrote: > HI, > > and the backtrace (essentially same as before except for the line numbers moved by the code changes): > > Core was generated by `dovecot/lmtp'. [50/749] > Program terminated