similar to: Dovecot 2.2.13+ Assertion failed in sync_expunge_range

Hi I got this error when configured imapc proxy (http://wiki2.dovecot.org/HowTo/ImapcProxy) and moved indexes to memory (mail_location = imapc:~/imapc:INDEX=MEMORY), with indexes on disk this error does not occurred. Jul 16 17:06:31 imap-login: Info: Login: user=<user87>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=21703, secured, session=<iwFgMU/+lwB/AAAB> Jul 16 17:06:31

We're seeing this: % doveadm force-resync -u USERNAME INBOX doveadm(USERNAME): Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) doveadm(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x817ad) [0x33ab08317ad] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x3a) [0x33ab08318ba] ->

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8

Hello, I'm seeing a segfault in the imap process with the current mercurial tip (including changeset 17382 e99cd21e1f92) when selecting a particular virtual mail folder (but no other virtual mailboxes) and then selecting a different mail folder as in the IMAP transcript below. The same segfaults are triggered with IMAP clients. The situation is worse with the 2.2.13 which segfaults when

Hello, I'm upgrading one of our servers to the last HG 2.2.13 versi?n and I've found some problems with our configuration which has been working fine with previous versions. We have a LDAP userdb for the users and a master userdb for user assistance, Until now the definition of usersdb in 10-auth.conf was: !include auth-master.conf.ext !include auth-system.conf.ext !include