similar to: another assert/core with 1.0alpha1

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

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

If the first message in an mbox is deleted by an external program, therefore removing the X-IMAPbase header, an error such as the following occurs. Apr 9 20:10:51 sm1 dovecot: imap(306812): file mbox-sync-update.c: line 460 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) This prevents the user from logging

Timo, Test-80, running on our production IMAP server. Setup: Solaris 9, compiled with gcc 4.0.1, mbox format, configured like so: VERSION=test80 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out Still seeing

We are currently running dovecot 2.2.rc3. I am trying to 'dsync mirror' old Qpopper/mbox inboxes to our new Dovecot/mdbox servers. For most of the several thousand accounts, it works without issue. But there are a handful of accounts that are generating the following errors. dsync(joe): Error: Sync failed for mbox file /var/opt/migrate/users/joe/inbox: seq=981 uid=981 uid_broken=0

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

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

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:

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

I don't know if this is significant or not, but it is at least unusual here. First we see this: > Oct 9 10:10:03 sbh16 dovecot: imap(mark): Error: Sync failed for mbox file /var/spool/mail/mark: seq=393 uid=201517 uid_broken=0 originally needed 0 bytes, now needs 66 bytes which has apparently added 66 bytes to UID 201517 Then, later we see: > Oct 9 11:26:19 sbh16 dovecot:

Hi, My compiler AIX 5.2, complained about the following: cc -qlanglvl=ansi -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/index -I/usr/local/include -O2 -c mbox-file.c "mbox-sync-private.h", line 50.17: 1506-009 (S) Bit-field

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, amd64. I've long been getting the following kind of messages in my logs, on random occasions when I access or move mail into mboxes: Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 18446744073709551615 bytes Whatever

Hi folks. We're moving users from rc24 and 27 to 1.0.0. On four mailboxes so far we've seen these errors after the move (quick and dirty anonymizing follows): Apr 23 13:22:41 server.umn.edu dovecot: [ID 107833 local6.info] imap-login: Login: user=<USER>, pid=<9046>, method=PLAIN, rip=***.***.***.***, lip=***.***.***.***, TLS Apr 23 13:22:41 server.umn.edu dovecot: [ID

Hi, I'm running dovecot-1.0.7-7.el5 on a CentOS 5.5x64 server, accessed through Thunderbird clients. Thunderbird is reporting constant disconnections from the server; the maillog shows constant repeats of Apr 4 16:39:21 holly dovecot: imap-login: Login: user=<?user?>, method=PLAIN, rip=::ffff:172.31.255.193, lip=::ffff:172.31.255.1 Apr 4 16:39:21 holly dovecot: IMAP(?user?): mbox

Debug output: May 6 11:23:42 qemu-sid dovecot: master: Dovecot v2.2.16 starting up for imap (core dumps disabled) May 6 11:24:06 qemu-sid dovecot: imap-login: Login: user=<bluser>, method=PLAIN, rip=192.168.122.8, lip=192.168.122.8, mpid=441, secured, session=<HtpSW2YVaQDAqHoI> May 6 11:24:06 qemu-sid dovecot: imap(bluser): Debug: Loading modules from directory:

Help... Dovecot 1.0alpha1 hung up today with nothing working and the following spewing to my syslog: pipe() failed: Too many open files My setup: Solaris 9, just using imap, mbox format. The various "max" settings in dovecot.conf use the defaults. Suggestions on what to change in fovecot.conf to keep this from happening? Jeff Earickson Colby College

Hi, I have seen the following in my syslogs for 1.0alpha1: Corrupted index cache file [filename]: record points outside file and : indexid changed : record list is circular : Cache record offset 9772 points outside file : invalid record size Are these errors minor? Major? Self-healing? Should the cache files be blown away to fix these errors? Jeff Earickson Colby College

Hi, I just upgraded from test80 to 1.0alpha1. I wanted to try something new on the lock_method, so I set: lock_method = fcntl, dotlock I got syslog complaints like: IMAP(username): Unknown lock_method: fcntl, dotlock Can one specify multiple file locking mechanisms? If so, what is the syntax (and can the syntax be shown in the comments of the .conf file)? Jeff Earickson Colby College

Timo, The dovecot.conf file comments talk about login_process_per_user but this variable does not appear in the file. Do you mean login_process_per_connection instead? Jeff Earickson Colby College