similar to: asserts and cores in beta3

Timo, My first assert in beta2. Syslog said: Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): Cached message offset 94625 is invalid for mbox file /var/mail/m/user Jan 24 09:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file mbox-sync.c: line 1471 (mbox_sync_do): assertion failed: (!sync_ctx->mbox->mbox_sync_dirty || (flags & MBOX_SYNC_UNDIRTY) == 0) Gdb

Hello, I use mbox compressed by gzip as read-only folder (using zlib plugin). This setup worked for a while, but doesn't work with latest dovecot version (2.2.27). I have error in logs: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) I can see list of messages in MUA but can't ready body of any message. I've tried to delete indexes, but it

... Version from April 26, gives me the following errors in the imap log file : dovecot: May 04 09:56:58 Error: IMAP(m6933192-4): file mbox-sync.c: line 1262 (mbox_sync_do): assertion failed: (sync_ctx->ibox->mbox_sync_dirty) dovecot: May 04 09:56:58 Error: child 10721 (imap) killed with signal 6 This occurs sporadically and vanishes after some time. Is this something to worry about or

Hello List, I am in the process of building a new mail system here. I am hoping to eventually migrate my users from mbox storage to maildir. They have been using mbox forever and would rather get used to maildir slowly. So I have come upon the idea of using namespaces to provide the different mailstores. Since this isn't available in the current stable, or at least I could not figure

One of my users is causing dovecot to exit with signal 6 and generate a core file. Seems to be in the mbox code. Dovecot configuration: # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-STABLE amd64 protocols: imap imaps pop3s listen(default): localhost:143 listen(imap): localhost:143 listen(pop3): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995

Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980

Timo, Attached is gdb information from core dumps related to the following assert in test-80: IMAP(username): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) My setup: Solaris 9, mbox format. test-80 compiled with gcc 4.0.1 using the following configure options: CC=gcc

Dovecot 1.1.7 is running so smoothly that I gave up checking its log files daily. :) I've just had a look, and among the usual "IMAP(username): FETCH for mailbox Sent UID xx got too little data: xx vs xx" messages (that means that unfortunately sometimes some messages are still written truncated) I saw this assertion failure: file mbox-sync.c: line 1305

Hi, I've been running 1.0alpha1 in production since August 18, and got my first assert and core yesterday. Otherwise it has been running flawlessly. My setup: Sun E220R, Solaris 9, compiled dovecot with gcc 4.0.1, configured dovecot like so: #!/usr/bin/sh VERSION=1.0-alpha1 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure

Same as reported before: Assert: IMAP(user): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) Setup: 1.0alpha1 on Solaris 9, built with gcc 4.0.1 Debug output of the core is attached. Jeff Earickson Colby College -------------- next part -------------- Script started on

It might not be a fault in dovecot, as the user is accessing the folder locally with alpine while also running imap-sessions. However it would have been nice with a more graceful action than panic? The panic is preceeded by Error: Next message unexpectedly corrupted in mbox file PATH Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed:

Hallo, I have the following problem with doveadm: # gdb --args /opt/local/bin/doveadm -v mailbox status -u userxy/g029 'messages' "Software-alle/AK-Software-Tagung" GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain

Hi, An assertion that I haven't seen before: Apr 20 11:15:32 emerald dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos < data_size) gdb output from the core file of imap is attached. My setup: Solaris 9, mbox format, INBOX is NFS mounted from a Solaris 10 system, imap and imaps only. Jeff Earickson

Hello, We're having a problem in Dovecot 1.1.8 with a failed assertion on certain mbox format mailboxes. It happens both with deliver when it attempts to delier to the mailbox, and with IMAP connections for the affected box (though I'm not sure what they're doing at the time). Mar 3 12:55:26 <snip> dovecot: Panic: IMAP(<snip>): file istream.c: line 81 (i_stream_read):

Timo, I upgraded from alpha3 to alpha4 yesterday, and I am seeing a few of the following asserts: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) Gdb info on a couple of the cores is attached. It looks like the arg lock_type for mbox_lock_fcntl() is not getting passed in correctly, like the enum "enum mbox_lock_type type" in

Timo, I see where at least one other person reported this, but here goes. I went from rc24 to rc25 this morning, and I got an assert and core from my own mailbox withing five minutes: Mar 2 06:52:26 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): file mbox-sync-rewrite.c: line 408: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 2 06:52:26 karst dovecot: [ID 107833

I'm running Dovecot dovecot-1.0.r13 on FreeBSD (FreeBSD 6.1-RELEASE- p10). Mail is stored in mbox format (dovecot.conf after the msg). Procmail delivers mail to subfolders under ~/.mail, locking using dotfiles. One folder in particular for one user has an mbox file ~/.mail/Cron. Quite often, I'll see that procmail processes are stacking up because ~/.mail/Cron.lock exists, and

Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

I've been getting a few of these errors on a couple different mboxes. This is using the CVS version as of May 14. So far, these are the only errors and it looks like most/all of the older ones are gone. (maybe I shouldn't say that ;-) dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed: