similar to: mdbox corruption

Trying to clean up the last of the corruption caused by my own stupidity. I now have two mailboxes for one user that give errors such as: doveadm(fax at amfes.com): Error: zlib.read(/var/mail/amfes.com/fax/mdbox/storage/m.9): gz trailer has wrong CRC value at 20065618 doveadm(fax at amfes.com): Error: read(/var/mail/amfes.com/fax/mdbox/storage/m.9) failed: Invalid argument (uid=238)

Hi, I have a "ubuntu10.04 + ext4-filesystem + dovecot-2.0.13 +mdbox" configuration in my server. It works fine with ~50k accounts. Recently happened a filesystem corruption in a device of StMailLocation and I fix with fsck.ext4. After this crash, one account began to show access timeout and errors like this on force-resync: # doveadm force-resync -u account INBOX doveadm(account):

With an error like this: doveadm(dmiller at amfes.com): Error: Corrupted dbox file /var/mail/amfes.com/dmiller/mdbox/storage/m.20 (around offset=74408): Unexpected EOF while reading metadata header What can be done? -- Daniel

Hi Timo, hi all! Today i noticed imap throws segmentation faults and dumps cores. I looked into logs I can see: 2013-03-07T12:12:52.257986+01:00 meteor dovecot: imap(marcinxxx at kolekcja.mejor.pl) <7sRXtFPXYAA+eX93>: Error: Corrupted dbox file /dane/domeny/mejor.pl/mail/marcin//.mdbox/mailinglists/storage/m.75 (around offset=2779212): EOF reading msg header (got 0/30 bytes)

Having a problem with a mailbox. I've been trying to rebuild - but doveadm force-resync crashes. This is mdbox with sis. doveadm purge -u dmiller at amfes.com doveadm(dmiller at amfes.com): Panic: file istream.c: line 466 (i_stream_grow_buffer): assertion failed: (stream->max_buffer_size > 0) doveadm(dmiller at amfes.com): Error: Raw backtrace:

Hi, I have recently migrated (under emergency conditions) a dovecot imap/pop based server to a new instance. The mailboxes used mdbox format and due to various screwups I had corrupt indexes. I thought I'd cleaned this up but then I found that this new instance hadn't been set up correctly for nfs. Long story short, I still get users with new cases of corrupt indexes. The symptom is imap

I could use some help with a corrupt mdbox. doveadm force-resync is crashing (see below), but I really need just to get this account functioning. What's my next step, as far as deleting index files? These were the earliest errors I could find: Nov 28 09:40:21 macy dovecot[6615]: imap(cory at metro-email.com): Error: Corrupted index cache file

Hi! When I force-resync a mailbox of mine, I see following output: # doveadm force-resync -u $USER $PATH doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y2 != $X,$Y2) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: rebuilding indexes doveadm($USER): Error: mdbox .../storage: Duplicate GUID $G in

Reviewing some mailing list archives and the wiki, I still don't have a real clear picture of why I'd want to use mdbox. What I've taken from the info I've reviewed says mdbox is more complicated (than sdbox), has greater potential for breakage (simply because it's more complex), and has a theoretical performance impact depending on the exact filesystem/hardware used.

Hello. We are using mdbox 2.013 + zlib, without SIS. When I try doveadm force-resync on a user's mailbox I get the following: doveadm(jmraya): Error: Corrupted dbox file /buzones/mydomain/0b/59/jmraya/storage/m.27 (around offset=22805024): Unexpected EOF while reading metadata header doveadm(jmraya): Warning: dbox: Copy of the broken file saved to

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

It's apparent I have some level of corruption in my mailboxes - something to do with the combination of mdbox, sis, and zlib. I should note that I know I have a mix of compressed and raw messages - if that makes any difference in identifying the problems. I think I need to somehow regenerate the mailboxes with issues. Is there a suggestion for how to accomplish this? Should I perhaps use

2017-01-30 11:43 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > Hi! > > Please send these to dovecot at dovecot.org instead of us directly. Thank you. Ok, added to cc. > Also, did you try force-resync? Not help. # doveadm force-resync -u altek at altek.info \* doveadm(altek at altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index

Getting some errors like: Feb 26 12:19:43 bubba dovecot: imap(dmiller at amfes.com): Error: read(attachments-connector(/var/mail/amfes.com/dmiller/mdbox/storage/m.7089)) failed: read(/var/mail/attachments/f6/f4/f6f4f3b882bf3488af632389d4aaba8adc332b12-60ab750a1aa4b554da1600009db5accb[base64:18 b/l]) failed:

2017-01-31 13:03 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > >> On January 30, 2017 at 10:53 AM Andrey Melnikov <temnota.am at gmail.com> wrote: >> >> >> 2017-01-30 11:43 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: >> > Hi! >> > >> > Please send these to dovecot at dovecot.org instead of us directly. Thank you.

Hello, The following errors are constantly popping up for 2 accounts. I can't get it fixed, I did doveadm backup to another account, the same happens in the new account. I did doveadm force-resync, the problem persists. I'm using dovecot 2.2. 2017-08-18T11:46:12.472821881Z Aug 18 11:46:12 lmtp(ramon.lacerda at alliar.com): Warning: mdbox

Hi Aki, Am 18.09.17 um 11:13 schrieb Aki Tuomi: > On 18.09.2017 12:10, Ralf Becker wrote: >> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>> >>>> Since a couple of days some mailboxes have the problem, that sieve

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:

Hi Aki, Am 18.09.17 um 11:22 schrieb Aki Tuomi: > On 18.09.2017 12:20, Ralf Becker wrote: >> Hi Aki, >> >> Am 18.09.17 um 11:13 schrieb Aki Tuomi: >>> On 18.09.2017 12:10, Ralf Becker wrote: >>>> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>>>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: