similar to: Segfault in imap

I've attached two backtraces, one from a segfault and another from an assertion error in imap. I've seen a couple of the same assertion and this is the only segfault. It looks like they could be related. They both have to do with indexing anyway... The code is from CVS as of May 30. The segfault happened while imap was doing searches for my pine filters. I've also noticed that in

I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs -------------- next part -------------- dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=

This is from the CVS version as of Aug. 28. It's the first time I've seen this assertion failure. Prior to this, I was using the CVS version from Aug. 15. dovecot: Aug 30 16:07:52 Error: 24929 IMAP(support): UIDVALIDITY changed (1125327213 -> 1125430510) in mbox file /mailhome/new/s/b/support/mbox dovecot: Aug 30 16:08:13 Error: 24929 IMAP(support): UIDVALIDITY changed

I'm running the CVS version from May 9. I've seen these errors in the log file before (every time I open my mailbox), but this is the first time it crashed. Todd dovecot: May 11 15:00:18 Error: 8438 IMAP(todd.bluegenesis.com): Corrupted index cache file /mailhome/new/t/b/todd.bluegenesis.com/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: May 11

This is from the June 16 CVS, it also happens with June 15 but not with June 8. Basically, imap segfaults when opening my mbox. Some details are below: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x08094e5c in message_parse_header_next (ctx=0x80c8e10, hdr_r=0xbffff64c) at message-parser.c:755 755 if (msg[0] ==

There seems to be a bug in updating uid/uidvalidity when copying mail to an empty or newly created mailbox: <new connection> . OK Logged in. . CREATE testfolder4 . OK Create completed. . SUBSCRIBE testfolder4 . OK Subscribe completed. . SELECT otherfolder * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags

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:

Setting mbox_min_index_size above zero and accessing a small mbox triggers the panic in index_storage_mailbox_init() at dovecot-1.0.rc25/src/lib-storage/index/index-storage.c:368 dovecot: Mar 03 01:28:03 Error: IMAP(user): in-memory index creation failed. dovecot: Mar 03 01:28:03 Error: IMAP(user): Raw backtrace: imap [0x80b52c4] -> imap [0x80b4d59] ->

Part of our migration plan takes our users from one endianness to another (big to little). Will the index and mail cache files survive? I'm seeing some new core dumps as the first test user is migrated, which makes me think... not. What about if we want to build dovecot 64 bit in the future? Will that cause problems too? Stack trace is below the log messages. I've edited the

Hi, I have a lot of problems to compile or to run the dovecot on my OpenSUSE 10.3 x86_64. Sometimes the compiled binary cannot read the existing and running config, the dovecot -n results in: ian:/opt/src/build/dovecot-1.1.rc7 # /opt/dovecot/sbin/dovecot -n # 1.1.rc7: /etc/dovecot/dovecot.conf Error: Missing auth section for server default Fatal: Invalid configuration in

This is the trace (gdb) run Starting program: /root/tmp/dovecot-1.0.rc7/src/imap/imap x select inbox Program received signal SIGSEGV, Segmentation fault. mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at mail-index.c:1313 1313 memcpy(index->map->mmap_base, hdr, hdr_size); (gdb) bt #0 mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at

We've been testing dovecot for a while and I noticed yesterday that imap crashes quite often. It seems to be about even with SIGABRT and SIGSEGV. This one was SIGSEGV. Our system is SuSE Linux 9.2, 2.6.11.5 kernel (also happened with an older 2.6 kernel). Dovecot version is 1.0-test64 and was compiled with: "./configure --prefix=/services/dovecot --disable-ipv6" It's using

We are just trying to bring up a new server and chose to use Dovecot rather than the uw-imap from our previous servers. At this point I am just testing with some throw away accounts using squirrelmail. I can load my inbox, but then the imap connection is lost. I presume you need some real information to get your teeth into, so this is going to get a little long. I'll give you three things