similar to: dovecot.map.index corrupted: missing map extension

Hi, we had the same problem after a system failure. Our problem could be solved by rm /PATH/USER/mdbox/storage/dovecot.map.index* doveadm -D -v force-resync -u USER INBOX Best regards, Gordon On 05.06.2017 18:34, micah wrote: > > 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 >

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

After a (power)crash two accounts have been corrupted. I tried to rescue things by running force-resync multiple times, but that didn't work out. Searching the archives, I found a recent suggestion (by Timo) to delete the index files, but I'm not sure which files to delete and what the consequences will be. When I deleted ``storage/dovecot.map.index'' in an unimportant account

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning:

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

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

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: >>>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>>>

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

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.

?I managed to figure this out. Just wanted to follow up if anyone in the future encounters the same issue. I am using HAProxy along with dovecot replication. When an email comes in... it is round robin'd to each of the 2 dovecot/postfix servers. I have postfix running on each server and it uses the local dovecot LMTP service for storing the mails. We sometimes get surges of emails(hundreds

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:

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)

On 18.08.2017 14:55, Webert de Souza Lima wrote: > 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

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

Having an empty m-File, doveadm force-resync isn't able to detect and repair this: -rw------- 1 vmail vmail 4948043 8. Jan 20:32 m.634 -rw------- 1 vmail vmail 5237411 8. Jan 20:32 m.635 -rw------- 1 vmail vmail 0 9. Jan 16:23 m.636 mail1:~ # doveadm force-resync -u user mailbox INBOX doveadm(user): Warning: fscking index file

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:

But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:

Hello, I current using dovecot with mdbox and on one account i get this error: doveadm(user at domain): Panic: file mail-index-sync-ext.c: line 209 (sync_ext_reorder): assertion failed: (offset < (uint16_t)-1) doveadm(user at domain): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3fd8a) [0x7fae684fdd8a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)

Hi all, We have recently had some power failures have led to corrupt mdbox instances. Dovecot?s fsck appears to get caught in a loop when the recipient has a large amount of mail. In the example log output below, each ?rebuilding indexes? seems to be interrupted by a new IMAP connection. Later, when our folks realized the issue and blocked access to the mailbox, the index rebuild finished in

Hi, I am seeing constant "Log synchronization error"s in my logs. See later for an example. This is dovecot 2.2.4, pigeonhole 0.4.1, and postfix 2.10.1 (with mailbox_command = /usr/libexec/dovecot/deliver) on a Fedora 19 system. I am using packages from Atrpms so there are some patches applied - ask for details. The mailboxes have resently been moved from a i386 system. I have