search for: mboxcrypt

...ox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)". Reverting to beta1, it also failed with the same error! I've deleted indexes, restored the mbox from a backup made in October (no changes) and I still get the error. It *does* open OK in 1.0-stable. I've put it through mboxcrypt.pl, deleted the UW-IMAP pseudo-message (which wasn't converted properly by mboxcrypt) and it still fails to open with a similar error, so I've sent it to Timo (gzipped, of course!) I've e-mailed this to the list minus the attachment as sending unsolicited 1MB attachments is unfriendly!...

Hi list, Today i tried upgrading my dovecot server from 0.99.14 to 1.0alpha3. Unfortunately the new version does not work. The log file says: Oct 2 20:40:02 knut dovecot: imap-login: Login: user=<arved>, method=PLAIN, rip=213.225.30.218, lip=213.9.70.XXX, TLS Oct 2 20:40:02 knut dovecot: imap(arved): file istream-raw-mbox.c: line 450 (istream_raw_mbox_get_body_size): assertion failed:

Hello everybody, I get the following assertion error with dovecot 1.0-stable when accessing a large folder: file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) There is no error when using dovecot 0.99.14. Any ideas ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet

Hi, I've installed dovecot on my server (pop3 service on dovecot 1.0 stable plus patch for more logging, postfix as mta) and it's ok (not all, need more fine-tuning) but on one account i've a problem.. the account is read by oe 6, message on server mode. dovecot: Jun 09 15:00:18 Info: pop3-login: Login: info-xxx, auth: PLAIN, lip: [151.8.36.12], rip: [xx.xx.xx.xx] dovecot: Jun 09

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

...occasional assert messages in the syslog: 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) How do I give you useful debug info? Run the offending mailbox thru mboxcrypt.pl, try to reproduce with the mailbox, send the mailbox in? Otherwise test-80 is working great... Jeff Earickson Colby College

...nc_headers_add_space): assertion > failed: (start_pos < data_size) > Jan 8 18:53:13 saigo dovecot: child 88663 (imap) killed with signal 6 This happens all the time with one specific mbox? Could you send it and the index files to me? You could put the mbox though http://dovecot.org/tools/mboxcrypt.pl -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20060108/7ef56d0d/attachment.bin>

Hallo! I installed dovecot at a customers and it is not working. Neither the 1.0.alpha4 (Debian testing) nor the 1.0.beta2 (Debian unstable) do. in /var/log/mail.err I get following error message over and over again: Feb 7 07:12:02 harmserv dovecot: imap(duerkop): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos < data_size) Feb 7 07:12:02

We're in a bit of a panic here as we're getting a lot of errors along the lines of: May 2 12:39:00 lenny dovecot: IMAP(XXXXX): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos < data_size) We didn't see this until our mail servers went under a full load and now we've trashed the ability of nearly all our users to read email.

We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using mboxes, mostly without issues. However I had to trash the index/cache files (too many folders were showing corruption issues which is especially bad for Prayer Webmail ".prayer" folders that store preferences; Prayer sees a disconnection as the folder being missing!). I've had one imap process panic in mailbox