search for: recent_messages_count

Hi, Got the following today with test62 and mbox: IMAP(juergen): Fixed index file /home/juergen/Mail/.imap/INBOX/dovecot.index: recent_messages_count 19 -> 0 imap-login: Login: juergen [192.168.0.1] file mail-index-sync-ext.c: line 118 (mail_index_sync_deinit_handlers): assertion failed: (size <= synch_size) child 31196 (imap) killed with signal 6 after that I had to delete dovecot.index to be able to select the folder. And another one...

...map_refs = 0xa21a0, hdr = { major_version = 7 '\a', minor_version = 0 '\0', base_header_size = 120, header_size = 200, record_size = 40, compat_data = "\000\b\004", indexid = 1124149513, flags = 2, uid_validity = 1122257472, next_uid = 271, messages_count = 31, recent_messages_count = 0, seen_messages_count = 9, deleted_messages_count = 0, first_recent_uid_lowwater = 0, first_unseen_uid_lowwater = 0, first_deleted_uid_lowwater = 240, log_file_seq = 1, log_file_int_offset = 24240, log_file_ext_offset = 24240, sync_size = 13022941, sync_stamp = 1126108845, day_st...

Hi, We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10) a few days ago and have been seeing many errors and one corrupted mailbox so far. Almost everyone uses mbox format, and most users primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well as accessing the mailboxes locally with Mutt, and have not noted any visible problems. There have been several of

...c_log_file_seq == (index)->hdr->log_file_seq && \ (index)->sync_log_file_offset == (index)->hdr->log_file_ext_offset) index->hdr is NULL dovecot: Apr 09 20:52:07 Error: 27413 IMAP(support): Fixed index file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index: recent_messages_count 12 -> 0 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: Extension introduction for unknown id 1 dovecot: Apr 09 20:52:11 Error: 27413 IMAP(support): Corrupted index file /mailhome/new/m/2/support/.imap...

...dr = {major_version = 0 '\0', minor_version = 12 '\f', base_header_size = 15224, header_size = 801664, record_size = 753608, compat_flags = 68 'D', unused = "o??", indexid = 1, flags = 0, uid_validity = 0, next_uid = 771168, messages_count = 582656, recent_messages_count = 582656, seen_messages_count = 0, deleted_messages_count = 771220, first_recent_uid_lowwater = 4290769872, first_unseen_uid_lowwater = 366928, first_deleted_uid_lowwater = 771168, log_file_seq = 0, log_file_int_offset = 0, log_file_ext_offset = 0, sync_size = 4, sync_stamp = 1, day...

...fs = 0x0, hdr = {major_version = 7 '\a', minor_version = 0 '\0', base_header_size = 120, header_size = 200, record_size = 40, compat_data = "\001\b\004", indexid = 1122493952, flags = 0, uid_validity = 1130429256, next_uid = 5142, messages_count = 1913, recent_messages_count = 0, seen_messages_count = 1452, deleted_messages_count = 0, first_recent_uid_lowwater = 0, first_unseen_uid_lowwater = 1149, first_deleted_uid_lowwater = 0, log_file_seq = 16, log_file_int_offset = 22028, log_file_ext_offset = 22028, sync_size = 101978714, sync_stamp = 113...

When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong? Here's where a SIGABRT happens: 280 return array->buffer->used / array->element_size; This is the stack trace: (gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0,

...count = 3, hdr = {major_version = 7 '\a', minor_version = 0 '\0', base_header_size = 120, header_size = 200, record_size = 36, compat_data = "\001\b\004", indexid = 1113829460, flags = 0, uid_validity = 1113827022, next_uid = 2872, messages_count = 929, recent_messages_count = 0, seen_messages_count = 810, deleted_messages_count = 0, first_recent_uid_lowwater = 0, first_unseen_uid_lowwater = 1149, first_deleted_uid_lowwater = 2846, log_file_seq = 8, log_file_int_offset = 27912, log_file_ext_offset = 27912, sync_size = 9241460, sync_stamp = 111386365...

http://dovecot.org/test/ I've still lots of mails in my INBOX and in this list that I should be looking into.. But here's a release that fixes at least some things. Maybe I'll make another one tomorrow.. Most importantly keyword code was changed a lot. It's now faster and less buggy. The keywords are also finally written into mbox, and keyword changes in the mbox are picked up.