similar to: Dovecot 1.1.1 killed with SIGABRT

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

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

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

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:

I recently upgraded dovecot from 1.0.15 to 1.1.2 and since then I am getting the following types of things in the logs: Aug 21 17:23:13 mail1 dovecot: imap-login: Login: user=<myuser>, method=PLAIN, rip=172.16.78.20, lip=172.16.78.22 Aug 21 17:24:01 mail1 dovecot: Panic: IMAP(myuser): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed:

-----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, 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 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 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

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:

Hi Timo and all others! The current Dovecot 2.0.rc4 did really well with Mutt 1.5.20 and Thunderbird 3.1.2, but a user with Alpine 2.00 crashed it immediately. I'm running Fedora 13 (Linux) and compiled Dovecot 2.0.rc4 manually like I did before with Dovecot 1.2.13. When switching from 1.2 to 2.0 I removed all those ".imap" folders with internal cache data (didn't know for sure

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

Environment: Dovecot 1.0beta8 Host: 64 bit Red Hat AS4 Linux (2.6.9-34.0.1) Disks: NFS netapp In the case below, the two connections were going through two separate servers sharing disks via an NFS NetApp. Here is the sequence of operations: 1. Open a connection to a folder (say mail/Trash) 2. Open a connection to another folder (say Inbox) 3. Move messages from Inbox to Trash using this

Hello, I still cannot fetch my mails, relying on my smartphone (which makes it a burden to read my mails ...) - could probably somebody help me? Kind regards, Peter

> On 27 May 2019 20:20 Peter Nabbefeld via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I still cannot fetch my mails, relying on my smartphone (which makes it > a burden to read my mails ...) - could probably somebody help me? > > Kind regards, > Peter Hi! I read your previous email, can you provide gdb bt full from the core file? Also,

Hello, I've never used gdb, so I don't know why I'm running into problems using "gdb bt". Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't seem to work with backtrace. :-/ Output from "dovecot -n" attached. Kind regards, Peter -------------- next part -------------- # 2.3.6 (7eab80676): /etc/dovecot/dovecot.conf #