similar to: Assertion Failure

Just installed the latest (Dec. 12) CVS version and one user keeps getting this assertion failure. Todd dovecot: Dec 13 15:53:01 Error: 29718 imap(username): mbox sync: UID inserted in the middle of mailbox /mailhome/new/o/h/username/mbox (4863 > 3417, seq=780, idx_msgs=1913) dovecot: Dec 13 15:53:06 Error: 29718 imap(username): file mail-index-transaction.c: line 129

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul

This is in the CVS version as of Dec. 12. A user got a few of these: dovecot: Dec 14 15:10:29 Error: 23648 imap(username): mbox sync: UID inserted in the middle of mailbox /mailhome/new/s/h/username/DONE (1591 > 19, seq=19, idx_msgs=1593) dovecot: Dec 14 15:10:33 Error: 23648 imap(username): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos

Starting at 05:32 this morning, one user on my dovecot server is receiving hundreds of copies of old email. This is a short excerpt from my dovecot.log showing the problem: > dovecot: Nov 03 05:27:02 Info: pop3-login: Login: > user=<howard at obfusca.ted>, method=PLAIN, rip=::ffff:81.44.31.210, > lip=::ffff:zz.zz.zz.zz, TLS > dovecot: Nov 03 05:27:02 Info: POP3(howard at

dovecot: POP3(knute): mbox sync: Expunged message reappeared in mailbox /var/mail/knute (UID 585 < 379664, seq=2, idx_msgs=0): 1 Time(s) dovecot: POP3(knute): mbox sync: UID inserted in the middle of mailbox /var/mail/knute (379664 > 585, seq=2, idx_msgs=1): 1 Time(s) I've been getting these lately. Any idea what causes them? Should I worry about it? Thanks, --

Mar 29 10:57:02 k8ux dovecot: POP3(stf): mbox sync: Expunged message reappeared in mailbox /var/mail/stf (UID 123 < 60016, seq=2, idx_msgs=0) Mar 29 10:57:02 k8ux dovecot: pop3-login: Login: user=<stf>, method=... Mar 29 10:57:03 k8ux dovecot: POP3(stf): mbox sync: UID inserted in the middle of mailbox /var/mail/stf (60016 > 123, seq=2, idx_msgs=1) Mar 29 10:57:03 k8ux dovecot:

I have a problem since a couple of hours: I manage several mboxes on a virtual server using Dovecot (over POP3). Until a few hours ago, it worked well, but since 11:50, the e-mail clients which access Dovecot's mailboxes, receive all e-mails new each time the mailbox is queried. For example: 15:40 fetches 22 new mails 15:41 fetches the same 22 mails again as new 15:42 fetches the same 22

Our support team seems to have caused another crash. They treat this mailbox like a shared one, so there may be a few people accessing it at once. They are mostly using dovecot, but some could be using uw-imap. These are the only two ways that this box is accessed. I know that this doesn't really work with mbox, but it doesn't appear to corrupt the mailbox. It seems to be a good stress

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 doing some stress testing in the last few days and fixing all the errors I saw. I'm hoping that I've finally really fixed all the index/mbox problems. So, again I think the only thing left for v1.0 is the documentation. Please test this nightly snapshot before I'll release rc27 tomorrow: http://dovecot.org/nightly/dovecot-latest.tar.gz If you've seen any of the

Hi. I'm a dovecot newbie. I've set my pop client to leave messages on the server for 7 days. I'm downloading the same messages over and over as dovecot appears to be overwriting X-UID's in the mbox's. I can't think of any other program on the system that might write to the mbox other than postfix (and that program doesn't appear to be writing X-UID). My setup has one

Hi, I have had some problem with duplicate emails using dovecot1.0alpha5using the prebuilt testing binaries on a debian stable/testing 3.1system. I am running both pop3d and imap, but all users are just usingpop3d. I am using mbox format. Users are using Thunderbird 1.5 to access emails. Dotlocks are used,postfix is the email agent. Note that dovecot/[postfix are running in avserver. In

Found an imap crash. I'm using the CVS copy from March 23. This is running under Linux, kernel 2.6.11.something. We use mbox over NFS, everything is on the NFS server. There is currently only one dovecot server accessing the mailbox. Here's the log messages: dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file

The segfault problem that was happening seems to be fixed. I'm still getting some "(imap) killed with signal 6" errors. I just noticed that it did get one segfault. Unfortunately, I don't have a core file. I'll try to get one if this happens again. Here's the error messages, not sure if it will help. I'm using the CVS copy from March 24. dovecot: Mar 26

Hi, I'm using dovecot-2.2.18 on fedora22 and receiving the following messages: Sep 26 11:07:52 orion dovecot: imap(dave): Error: Sync failed for mbox file /var/spool/mail/alex: Expunged message reappeared to mailbox (UID 267101 < 267175, seq=2, idx_msgs=0) How do I troubleshoot this? Any idea what could be causing it? I've included my doveconf below. # 2.2.18:

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

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

Just saw in my logfile this line appeared: imap(xxxxxx)<56614><CMMJw9i0aoBSsH9H>: Error: Mailbox INBOX: Sync failed for mbox: Expunged message reappeared to mailbox (UID 174550 < 174552, seq=11, idx_msgs=9) Looks like messages' UIDs are mixed up? I thought that if Dovecot sees broken X-UID headers for "new" messages, they're silently fixed? Can you tell how I

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