similar to: assertion failed in 1.1.7 file mbox-sync.c: line 1305 (mbox_sync_handle_eof_updates)

First of all apologies for using such an old version - I am trying to upgrade slowly and have had to go through this version first. As you can see I am getting an error in the log file as : file mbox-sync.c: line 1371 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2) Raw backtrace: imap [0x80acdc1] -> imap [0x80accdc] -> imap(mbox_sync+0x14e9) [0x8079a29]

We've just cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system

Hallo, I have the following problem with doveadm: # gdb --args /opt/local/bin/doveadm -v mailbox status -u userxy/g029 'messages' "Software-alle/AK-Software-Tagung" GNU gdb 5.3 Copyright 2002 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

The actual alpha4 release this time. With a few changes since the pre-release. The important changes again: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could

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

Hello, list, I'm new here and also new to Dovecot. On Friday evening (perhaps not the best moment...) I sent the following question but it seems to have been lost somehow: Yesterday I had to reboot my server machine and I think there was an email client connected from the LAN during the reboot which I did not notice then. Now that mailbox is no longer accessible: as soon as I try to

Hi, i am the new one;) - and my first post is about a problem i ran into. I installed a mailserver on a RaspberryPi. It works mostly well, using dovecot 2.1.7. (exim4 4.8 (not in use, smtp direct to Provider), fetchmail 6.3.21, RasPi 3.12.28+, Roundcube (no version known) - the whole system went through an apg-get update/uppgrade this night to look if a known problem already been fixed. When

I'm getting this in my logfile, should I worry?: Jun 06 12:28:47 imap(paco_mcs): Error: Next message unexpectedly corrupted in mbox file /var/spool/mail/paco_mcs at 639279728 Jun 06 12:28:47 imap(paco_mcs): Error: Unexpectedly lost From-line from mbox file /var/spool/mail/paco_mcs at 639279728 Jun 06 12:28:47 imap(paco_mcs): Panic: file mbox-sync.c: line 1338 (mbox_sync_handle_eof_updates):

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

BehrensM <EDV2 at BehrensM.de> writes: > Beside the lokal mailserver-account(s) there is/are pulled Mails via > imap direct from the mailprovider, the "old" solution which shall be > replaced by the new mailserver. imap direct from provider shows the > mails/Attachments in corrects size an opening works. > Only using the local mailserver fails. > ... > Mar 26

This looks like a coprrupted mbox file Aki On 06.06.2017 15:54, Luciano Mannucci wrote: > I'm getting this in my logfile, should I worry?: > > Jun 06 12:28:47 imap(paco_mcs): Error: Next message unexpectedly corrupted in mbox file /var/spool/mail/paco_mcs at 639279728 > Jun 06 12:28:47 imap(paco_mcs): Error: Unexpectedly lost From-line from mbox file /var/spool/mail/paco_mcs at

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

Here is another crash we've been seeing recently in rc15 on Solaris 10. (gdb) bt full #0 0xff1c12a4 in ?? () No symbol table info available. #1 0xff140040 in ?? () No symbol table info available. #2 0x000786a8 in t_buffer_alloc (size=688976) at data-stack.c:346 __PRETTY_FUNCTION__ = "file %s: line %" #3 0x00078190 in t_pop () at data-stack.c:149 frame_block = (struct

Hi, on a clustered Dovecot server installation that was recently moved from a shared GPFS filesystem to GFS2, occasional corruptions in the users' INBOXes started appearing, where a new incoming message would be appended directly after a block of NUL bytes, and be scanned by dovecot as being glued to the preceding message. I traced this to the file extension operation performed in

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

I've been getting a few of these errors on a couple different mboxes. This is using the CVS version as of May 14. So far, these are the only errors and it looks like most/all of the older ones are gone. (maybe I shouldn't say that ;-) dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:

Hi Benjamin: I think that the following link will give you an idea for what you need to know: http://www.cisco.com/warp/customer/620/roadmap_b.shtml This is for the naming: http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not you worry you will not loose anything with the new

Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real

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

I'm running Dovecot dovecot-1.0.r13 on FreeBSD (FreeBSD 6.1-RELEASE- p10). Mail is stored in mbox format (dovecot.conf after the msg). Procmail delivers mail to subfolders under ~/.mail, locking using dotfiles. One folder in particular for one user has an mbox file ~/.mail/Cron. Quite often, I'll see that procmail processes are stacking up because ~/.mail/Cron.lock exists, and