similar to: 1.2.13 QRESYNC crash.

Hi guys, Anyone know what this error with deliver is (v1.1.1)? 2008-07-03T09:45:19+01:00 mail4 deliver(alexander): Panic: file mail-index-transaction.c: line 642 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) Seen a few of these this morning. Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development *

Hi, I'm trying to use dsync to convert sdbox + sis mailboxes to mbox (mbox is chosen here to "re-attach" the attachments to their original place) # dsync -Dv -u $LOGIN -o "mail_location=sdbox:/zfspool/clone_srv_mail/$LOGIN" -o "mail_attachment_dir=/zfspool/clone_srv_attachments" backup

http://dovecot.org/test/ Well, remember when I said: > Here you go, maildir syncing problems finally fixed (I hope). Well, > except there's this "new-dir-only syncing" optimization which I'm not > really sure if it works as it should. Just before I found the expunge bug in index, I was trying to fix the new-dir-only syncing because the code looked wrong. Then I

Heya, We are occasionally seeing core dumps with dovecot 2.2.10, which are mostly like this: Jan 11 18:31:08 hostname dovecot: imap(username): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) Jan 11 18:31:08 hostname dovecot: imap(username): Error: Raw backtrace:

Hi, we have started to switch our users mails from mbox to maildir and see for some users panics. May be someone has a hint on whats causing that and how to fix it? It's dovecot 2.2.10 on Redhat. dsync(s109487): Error: Corrupted index cache file /srv/vmail/s109487/mail/.imap/GS Drehbuch 1/dovecot.index.cache: Broken physical size for mail UID 42 dsync(s109487): Error: mail parser:

I've got this in my logfile, should I worry? May 19 14:45:04 imap(liscia_mcs): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) May 19 14:45:04 imap(liscia_mcs): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9cd16) [0xb7568d16] ->

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul

Just installed the latest (Dec. 12) CVS version and one user keeps getting this assertion failure. Todd dovecot: Dec 13 15:53:01 Error: 29718 imap(username): mbox sync: UID inserted in the middle of mailbox /mailhome/new/o/h/username/mbox (4863 > 3417, seq=780, idx_msgs=1913) dovecot: Dec 13 15:53:06 Error: 29718 imap(username): file mail-index-transaction.c: line 129

The actual alpha4 release this time. With a few changes since the pre-release. The important changes again: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could

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

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

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

> 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

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, I have run Dovecot via Debian for some years but in the last few weeks something has broken....I have been upgrading Debian but today rebooted it to try and sort out a failed DLT....now I find dovecot is non-functional.... So, Where to look for faults please? ie logs? can I make dovecot verbose? Thunderbird if telling me Dovecot is not imap4 compliant........and I cannot connect to it... I

Been seeing these occasionally for the last few weeks. Only way to fix is to remove cache files in the affected mailbox. Reproduced with both 1.2.5 and 1.2.6. IMAP transaction: ----------------- * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1

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

Hi Everyone, I am trying to setup xen3.4.1 FC12(xendom0) on top of FC12 freshly installed. I am using DQ965GF intel mother board having intel VT-x enabled. I have installed everything properly, but xen boot gets stuck at this point, xenbus_probe_init ok ACPI: bus type pci registered PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 PCI: Not using MMCONFIG. I did few googlings