similar to: Panic when using QRESYNC

Aug 18 22:07:31 twosheds IMAP(dwmw2): : Panic: file mail-index-transaction.c: line 637 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS

We recently upgraded from Dovecot 1.2.4 to 1.2.6 (with the sieve patches of course). Everything has been running quite well since the upgrade. The occasional issue with assert-crashing when expunging has gone away. However, one of our users seems to have triggered a new issue. She's been the only one to see it, but whenever she logs in, her imap process segfaults immediately. It appears that

Good Afternoon I?m really new at this and i don?t know if i?m posting at the right place. My problem is that our Dovecot IMAP is stopping from time to time with no info in the log, i just realize about this when our support person call me saying that the whatsup monitor is showing the IMAP4 process down. I can figure about this too by trying to get in our webmail Horde and i cannot login.

Hi! I'm thinking around an try to debug the problem a lot. And i think it's a problem of horde AND dovecot. Horde handles the reconnect wrong (not reenabling QRESYNC), but why is this disconnect? So i found out, it must be the thing with imap(jakob): Panic: file index-mail-binary.c: line 586 (index_mail_get_binary_stream): assertion failed: (mail->data.stream != NULL The

Hi there! This is the horde-imap. Hope this helps more to find out, what's the problem with QRESYNC and dovecots virtual-plugin ------------------------------ >> Wed, 15 Nov 2017 08:45:21 +0000 >> Connection to: imap://aldebaran.local/ Server connection took 0,0031 >> seconds. S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE XDOVECOT

RFC 5162 [3.1] states that a QRESYNC should return all changes in a SELECT/EXAMINE since the given modseq. In the following case, it looks like there is an off-by-1 error somewhere: C: A64 SELECT "TestMailboxTest" (QRESYNC (1224531494 6 1,3:5)) [MMS: MODSEQ given is 6] S: * OK [CLOSED] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S: * OK [PERMANENTFLAGS (\Answered \Flagged

> On 17 Nov 2017, at 21.36, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > >> On November 16, 2017 at 9:59 AM wertstoffe at nurfuerspam.de wrote: >> >> >> > > Hi! > > Thanks for the sample, we were able to identify the problem! Fixed: https://github.com/dovecot/core/commit/489af46c6c1ee32fe6a6ff96a8281f2ef5870c8d

I wrote a mostly-working CONDSTORE support for Dovecot today. You can try it with: hg clone http://hg.dovecot.org/dovecot-condstore/ There are a few problems left: - STORE FLAGS.SILENT should be sending FETCH MODSEQ updates - When SELECTing a mailbox while CONDSTORE hasn't yet been enabled in the session, Dovecot returns a higher HIGHESTMODSEQ than what's used after CONDSTORE is

Don't see any reason why X-REFERENCES2 should not be advertised in the CAPABILITY string - the wiki indicates this is a new addition for 1.2, and RFC 5256 explicitly states that the THREAD= is to be used for upwards-compatible extensions. # HG changeset patch # User root at bigworm.curecanti.org # Date 1225057043 21600 # Branch HEAD # Node ID 1f082281f8d4e3d364b85c08ec329cf1be7ba61f #

Hi there! I'm new on this list, so hello to all! First i want say, that dovecot is a really great mailserver. I use it since many years for my private usecase. I'm planning to setup a new Mailserver, so i'm fiddeling around to understand dovecot better and get a "perfect" Mailserver. (Linux and Win10) Outlook, k9mail and the gmail-app on android. I want to leave google

It seems that horde forgots to re-enable QRESYNC after connection timeout. Regarding the connection timeout, do you see anything in dovecot logs? Aki On 15.11.2017 12:51, Jakob Sch?rz wrote: > Hi there! > > This is the horde-imap. Hope this helps more to find out, what's the > problem with QRESYNC and dovecots virtual-plugin > > ------------------------------ > >>

Hi there, I'm currently working on adding QRESYNC support for james.apache.org/imap (which is a JAVA - based imapserver). For testing I'm currently using ImapTest but I'm currently not really sure it really reflect the RFC. Here are the "problems" I see: * It expect to have the UID param in the FETCH Response if QRESYNC was enabled (I was not able to spot the section were

Hi Timo, How long is the MODSEQ NUMBER kept for each UID ever exists in the mailbox? - Joe

So! I found another, similar report for my problem. https://lists.horde.org/archives/horde/Week-of-Mon-20170102/056304.html The problem was the same. The fix was in dovecot 2.2.26. Maybe it is not fixed in virtual-plugin... Bye Jakob

> On November 16, 2017 at 9:59 AM wertstoffe at nurfuerspam.de wrote: > > > Hi! Thanks for the sample, we were able to identify the problem! Aki

Probably better to get the full protocol debug log from the Horde/IMP side. Instructions on how to enable that can be found in imp/config/backends.php. See: https://github.com/horde/imp/blob/master/config/backends.php#L288 rawlog output below only shows what Dovecot is returning - would be more useful to see the entire client round-trip transactions however. > On November 14, 2017 at 4:15

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 Timo - hope things are well :) Playing around with the CONDSTORE (RFC 4551) stuff while testing the IMAP lib I am writing and I think I have found a bug in Dovecot 1.2. RFC 4551 [4] identifies the FETCH response to a MODSEQ request as follows: fetch-mod-resp = "MODSEQ" SP "(" permsg-modsequence ")" with 'permsg-modsequence' defined as:

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

I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ubuntu/ ) My configuration has worked nicely since 2009, but failed after a recent upgrade of dovecot (during basic upgrade from Ubuntu 18.04 to 18.10). The version of Alpine did not change.