similar to: test80: in production, occasional assert

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

Same as reported before: Assert: IMAP(user): 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) Setup: 1.0alpha1 on Solaris 9, built with gcc 4.0.1 Debug output of the core is attached. Jeff Earickson Colby College -------------- next part -------------- Script started on

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

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

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

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

Timo, I see where at least one other person reported this, but here goes. I went from rc24 to rc25 this morning, and I got an assert and core from my own mailbox withing five minutes: Mar 2 06:52:26 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): file mbox-sync-rewrite.c: line 408: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 2 06:52:26 karst dovecot: [ID 107833

Hi, I was brave enough to upgrade from UW-imap to stable 1.0 20050725 today for our IMAP service. I have seen a few of the following in my syslog: Jul 26 15:37:18 emerald dovecot: [ID 107833 mail.error] IMAP(bjkupke): file mbox -sync-update.c: line 372: assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid == mail->uid) Jul 26 15:37:18 emerald dovecot: [ID 684838 mail.error] child

Help! I just noticed this error this morning, we have been getting a lot of these in rc28 and rc29, not in rc27 or before: Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings Pine coughed up an internal error, no core dump, and dovecot basically doubled the size of my mailbox by

If its too hard for them to setup the pop3 catch all, we can probably put some mapping in place to smtp froward mail to their server. This is more complex on our part so would prefer not to do it that way, but its an option and will require not setup on their part other than make sure their server does not accept mail for anyone other than our server. dovecot-request@dovecot.org wrote: >

Hi, Has a patch against 3.2.2p1 been posted for bug 245, the bug that gives the following syslog complaint? open /dev/tty failed - could not set controlling tty: No such device or address I hit this when upgrading from 3.1p1, solaris 8, using Sun Forte 6 C compiler. I would get authenticated at login, but my shell would never get going. I had to roll back to 3.1p1. ** Jeff A. Earickson,

Hi, After searching gmane.mail.imap.dovecot on the topic, and wiki.dovecot.org, I'm still clueless on how to use RFC 2087 quotas in dovecot with the quota plugin. How come no wiki doc? My setup: Solaris 9, mbox format. Both the filesystem for INBOXes (/var/mail) and the user's home directories have filesystem-based quotas imposed. For example: % quota -v joeblow Disk quotas for

Gang, For those who asked about making a Solaris system a Kerberos client to Active Directory, the magic document to have is: http://www.connectathon.org/seam1.0/files/c0101.htm See the section "How to Configure a SEAM Client Using a Windows 2000 KDC". SEAM was Sun's Kerberos client stuff in Solaris 8; it is just there as part of Solaris 9 and 10. These instructions apply if

Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \

Timo, After several days of flawless work, rc27 gave an assert/core yesterday: Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-rewrite.c: line 423: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): Raw backtrace: 0x8a51c -> 0x473f4 -> 0x479b0 -> 0x41c50 -> 0x42430 ->

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

hi all, i've built dovecot: Sep 09 18:04:24 Info: Dovecot v1.0-test80 starting up on OSX 10.4.2. in addition to pgsql auth, which is working 4 me, i'd like to step-by-step verify simple passwd-file authentication/testing. unfortunately, i'm having a problem with the login process NOT FINDING the ".../cur" dir. here are the details .... my config includes: ...

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, In the "for what it is worth" category... The following assert popped up in beta1 on Solaris 9 this morning: imap(user): file mail-index-view-sync.c: line 155 (view_sync_get_expunges): assertion failed: (ret == 0) The user had hit a hard disk quota on their home directory, ie where the indexes go. Dovecot cored with a zero-byte core file in the user's home directory,

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing,