similar to: Some issues in Dovecot 1.2.5 after upgrade from 1.0.15

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. NFS may have been used. Panic: IMAP(user): file mail-index-sync-update.c: line 843 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- >indexid || map->hdr.indexid == 0) Two different backtraces to this error are: 0 libSystem.B.dylib 0x00007fff87b775ea __kill + 10 1

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) It was

I've tried this on both Solaris 8 and SuSE Enterprise 9 (64-bit). I get a assert-crash when using a gzipped mbox folder . OK Logged in. . SELECT test.gz * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Label4 $Label2 $Label1 $Label3 $Label5) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 167 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1096038620] UIDs valid * OK

Hi, I've got a core dump during initialisation when I use 1.0.rc12 and LDAP with authenticated binds in Solaris. It worked OK in 1.0.rc10. Here's the non-commented entries in dovecot-ldap.conf - some of which are probably redundant :) :- hosts = xxx.yyy.rdg.ac.uk auth_bind = yes auth_bind_userdn = "cn=%n,cn=users,dc=xxx,dc=yyy,dc=rdg,dc=ac,dc=uk" ldap_version = 3 base =

I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes was used with dovecot 1.1.6). OS: FreeBSD 8.3-STABLE, amd64. All index files from dovecot 1.1.6 has been deleted. Some times dovecot processes aborted. E. g. Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed

Hi - We tried to access a dovecot-0.99.10.7 IMAPS server with a Blackberry 7230. The Blackberry was on loan so we don't have much access to it for testing. We got the following in our logs: Jul 27 12:30:27 xserv imap-login: Login: testuser [xxx.xxx.xxx.xxx] Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree file /home/testuser/mail//.imap/INBOX/.imap.index.tree Jul 27

Should I be concerned about these errors? imap(msun): Jun 13 13:21:38 Error: Error indexing mbox file /home/msun/mail/Deleted Messages: LF not found where expected imap(msun): Jun 13 13:39:08 Error: Corrupted binary tree for index /home/msun/mail/.imap/INBOX/.imap.index: lookup returned index outside range (1 >= 0) imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file

http://dovecot.org/test/ - Added pop3_mails_keep_recent setting. Currently this only means that mails won't be moved from new/ to cur/ in maildir. More I/O friendly. - Fixed \Recent-flag handling and counters to work correctly with maildir. I think it's finally working right :) - mbox syncing fixes (but expunging still not implemented) - some other fixes.. Please try and report what

Hi Timo and All, after upgrading to 2.1.2 i'm getting a lot of these messages: Error: Corrupted squat uidlist file XXXXXX wrong indexid I did not have them before. Ideas? Luca

We've had another random imap process crash. This is with the original 1.2.5 imap (I haven't applied the patch for two processes creating an index simultaneously): > Oct 03 13:24:56 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.1.46, lip=134.225.16.6 > Oct 03 13:25:59 IMAP 6067 xxxxxxxx 134.225.1.46 : Info: delete: uid=483, msgid=<xxxxxxxx> > Oct

I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with Maildir storage. This has worked well for most of the accounts for several months. However in the last couple of weeks we are seeing increasing errors regarding corrupted index files. Some of the accounts affected are unable to retrieve messages due to timeouts. It appeared the problems were due to the accounts being accessed

See below: ----- Forwarded message from root <root at postamt.charite.de> ----- From: root <root at postamt.charite.de> Date: Sun, 24 Aug 2008 12:10:26 +0200 (CEST) To: ralf.hildebrandt at charite.de Subject: Backtrace:/usr/local/libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

2 backtraces: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes

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

I get a few messages of this ilk each day: Dec 16 01:56:31 aurora dovecot: IMAP(doug): Corrupted index cache file /home/doug/Maildir/.users.joe/dovecot.index.cache: indexid changed I usually address this by deleting dovecot.* in the directory of issue. I was thinking that I could instead just have the server delete these files and attempt to recreate them, and skipping that error message

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

Hi. I don't know if the problem is related with squirrelmail or not, but I started to have index corruption when I started to try squirrelmail. Some informaton about my instalation: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package Some log information: dovecot: 2008-02-27 08:39:39 Warning: IMAP(<please don't send spam to me>): fscking index file

Running 2.3.0~alpha0-1~auto+1045, basically as a proxy between MUA and Exchange (IMAP): Sep 7 16:10:32 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61031, TLS, session=<fp3JBZpYop+sEIAI> Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: imapc(exchange-imap.charite.de:993): Connected to