similar to: How to recover a mail box from an assertion failure

I'm seeing this periodically in my logs for a specific user (followed by a backtrace which I've deleted from this post): Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could

Hello there! I've migrated our courier-imap production imap/pop server to dovecot 1.0-beta few days ago. In general dovecot performs excellent, but i've encountered several "bugs" in dovecot log: --- snip --- dovecot.log.1.gz:Feb 24 16:05:21 elfstone dovecot: imap(user3 at domain.tld): Maildir /export/mail/domain.tld/user3 sync: UID inserted in the middle of mailbox (47681

Hello Timo, I can reproduce this issue even with mmap_disable and mmap_no_write set to yes, please see the following back trace: $ gdb /usr/local/libexec/dovecot/imap /tmp/imap.core GNU gdb 6.3 Copyright 2004 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 conditions.

i recently helped a friend of mine migrate from imap-uw using mboxes to dovecot on top of Maildirs and came up against two issues. this is quite embarrassing as ive been claiming dovecot is Solid As A Rock(tm) and hasn't ever given me any issues. 1. if dovecot runs out of file descriptors it will loop forever trying to open new logging pipes. the code in question is at line 624 of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, After having moved to using Apple mail.app for offline imap reading (served by a dovecot 1.0-test59 server), I noticed the following in the logs: Feb 14 13:52:48 top dovecot: 3102(schmitta): file mail-transaction-log-view.c: line 86 (mail_transaction_log_view_set): assertion failed: (min_file_seq <= max_file_seq) Is this bad? Would

I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108

Hello all. I've just recently (this last weekend) migrated to Dovecot on my FreeBSD 4.x box. So far, so good, I like it a lot, and plan on moving mboxes to Maildirs sometime this next weekend. BUT....I've currently run into a problem. I'm seeing an error when one user account tries to access the INBOX from Squirrelmail: Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file

I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes was used with dovecot 1.1.6). OS: FreeBSD 8.3-STABLE, amd64. All index files from dovecot 1.1.6 has been deleted. Some times dovecot processes aborted. E. g. Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dovecot: Jan 18 10:48:39 Error: IMAP(bfg at noviforum.si): file mail-transaction-log-view.c: line 138 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq ~ || min_file_offset <= max_file_offset) dovecot: Jan 18 10:48:39 Error: child 18837 (imap) killed with signal 6 dovecot: Jan 18 10:48:52 Info: imap-login: Login:

We recently upgraded from Dovecot 1.2.4 to 1.2.6 (with the sieve patches of course). Everything has been running quite well since the upgrade. The occasional issue with assert-crashing when expunging has gone away. However, one of our users seems to have triggered a new issue. She's been the only one to see it, but whenever she logs in, her imap process segfaults immediately. It appears that

GNU gdb 6.7.1-debian Copyright (C) 2007 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

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200

Hi. I don't know if the problem is related with squirrelmail or not, but I started to have index corruption when I started to try squirrelmail. Some informaton about my instalation: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package Some log information: dovecot: 2008-02-27 08:39:39 Warning: IMAP(<please don't send spam to me>): fscking index file

My mail server consumed all of its configured file table slots and started returning ENFILE ("Too many open files in system") for many operations. This wreaked havoc with dovecot-1.1.13. Here are some areas where dovecot should detect and more gracefully handle ENFILE error returns: 1. Deliver should report an error more helpful than "Unknown internal error" when

Hello List, We just migrated from a PPC Xserve to an Intel Xserve. I used "rsync" to bring everyone's home directories over, and in the back of my mind wondered about how it would handle the binary index files... only one way to find out! :) Once I tried to login to IMAP, I got the following results: May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index file

Hi all. Looking at previous weeks logs I discovered strange errors: "file mail-transaction-log-view.c: assertion failed" dovecot v 1.0.12 Server is hosting more than 500 virtual users. It is compleate dovecot error log; only my own mailbox is affected ...and imap folder affected is "dovecots mailing list" :) While "Corrupted transaction log file" as far as I know

I'm looking at the possibility of using shared folders to solve a particular problem for my employer and I have a few questions: 1) Can shared folders be in mbox format while allowing the user's mail to be in maildir format? (I think the answer is yes, but wanted to check). 2) What version of dovecot should I be running in order to support shared folders? 3) Is

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

Hello, I'm running an Debian etch box with unstable and ever since the last upgrade to dovecot, I've seen odd things. At times, I would see emails would go missing from the Inbox or other folders, and I couldn't move emails that were moved from the Inbox to another folder back into the Inbox. These have seen gone away since I removed all dovecot.* files and .index* files from my