similar to: dovecot panic after upgrade 1.0.15 to 1.1.2

I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs: dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Aug 29 09:34:32 Error: IMAP(user): Raw backtrace: imap [0x483888] -> imap [0x484293] -> imap

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. Pretty sure NFS was not used. Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: seq_range_exists(&ibox->recent_flags, uid) The backtrace is: 0 libSystem.B.dylib 0x00007fff85025166 __kill + 10 1 libSystem.B.dylib 0x00007fff850a80e0

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig There's always time for one more release candidate. :) I was planning on releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC according to Wikipedia). Maybe it'll bring luck to the release. :) - mbox: Fixed a crash when adding a new X-IMAPbase:

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig There's always time for one more release candidate. :) I was planning on releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC according to Wikipedia). Maybe it'll bring luck to the release. :) - mbox: Fixed a crash when adding a new X-IMAPbase:

We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic:

Hi, with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error after doing a system upgrade. May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) May 7 22:04:27 mail kernel: pid 79989 (deliver), uid 4873: exited on signal 6 (core dumped) this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sent an e-mail off as was detailed here: http://wiki.dovecot.org/MboxProblems for crashes but I also wanted to see if any of you folks had insight into the issue. Dovecot is crashing on a certain user inbox which is in mbox format as well as one of the users other mbox files. The crash doesn't exactly match what is listed in the aforementioned

Hi folks, with Dovecot 1.1.1, I've had two "crashes" (SIGABRT) recently. Dovecot 1.1.1 has been compiled from source and is running on Fedora 8 Linux 32 Bit (all patches) with custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.1: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just switched over to dovecot 1.1.2 on our live system last night. I'm seeing the following errors in the logs: Aug 19 10:01:03 goku dovecot: [ID 107833 mail.crit] Panic: IMAP(elevin): file in dex-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range _exists(&ibox->recent_flags, uid)) I did apply the assertion fix

Hi, another imap crash with latest dovecot. segmentation fault in fetch_bodystructure src/imap/imap-fetch.c static int fetch_bodystructure(struct imap_fetch_context *ctx, struct mail *mail, void *context ATTR_UNUSED) { const char *bodystructure; if (mail_get_special(mail, MAIL_FETCH_IMAP_BODYSTRUCTURE,

Hello, I upgraded dovecot to 1.1.2 this weekend and i get those errors: grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100| sort | uniq -c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) 89 file index-mail.c: line 1091: assertion failed: (! mail->data.destroying_stream) 18 file

I just installed a limited test of RC10 last night. So far, all is great except for errors being logged for one user (out of about 150 users total). This one user has not yet complained or anything, but the log file has repeated entries of the following format for him (host and username changed to protect the guilty/innocent): Oct 24 06:13:02 mail dovecot: IMAP(username): file

Hi folks, because I accidently missed a syslog entry from previous reports, here's a new one with both syslog lines. Same problem as always when saving mail from one folder to another with Pine 4.64. Does nobody else get this when copying/moving mail between folders? The assertion refers to src/lib-storage/index/index-sync.c, line 39 (function index_mailbox_set_recent_uid). Aug 19 23:01:15

Hi, This small mail to share my observation about a recent move of mailboxes between two servers and ask about explanation and/or improvement about UIDL in dovecot. SV1 : Dovecot 0.99.14 / Red Hat Fedore Core 4 SV2 : Dovecot 1.07 / CentOS 5.2 Mailboxes in /var/spool/mail on the twoo servers. Test will be done with outlook express with option "leave message on server" checked. Goal is

Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25

Log: Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): /home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216 -> 2) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap [0x80efdb1]

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, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831

Hi all, I plan to run a dovecot IMAPS and POPS service on our network. We handle about 3 000 mailboxes. I thought first buying a topnotch server (8 cores and 16 Go RAM) with equalogic iSCSI SAN SAS 15K for storage backend. On second though (and after a comprhensive read of dovecot features), I saw in http://wiki.dovecot.org/MailLocation that index files can be created on a separete local