similar to: Error: broken sync positions in index file

Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser at maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot:

Hello, I have been seeing an issue with Dovecot 2.2.5 (which is the current version packaged by cPanel). This is happening with any action that tries to access the mailbox index via IMAP. This log and debug information comes from a force-resync attempt, however, the same errors are logged when the user tries to open the mailbox or move a message to it. (User, domain, and IPs in log have been

Hi All, I upgrade my mail server from doveot 1.1.7 to 2.2.13 and encounter problems with file locking issues. The server has around 400 clients using IMAP and I get tons of "Warning: fscking index file .. dovecot.index" and "Error: Corrupted transaction log". Sometimes the transaction log problem is followed by "Panic: file mail-transaction-log.c: line 350

El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: > Hello, > > Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot: >> Hello, >> Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: >>> Hello List, >>> >>> i have a problem with index-files which is separated in 2 >>> subproblems. May be these problems are connected.

Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves. Am 15.02.2019 um 11:35 schrieb Hajo Locke via dovecot: > Hello, > > Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot: >> El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: >>> Hello, >>> >>> Am 11.02.2019 um 09:12 schrieb Hajo

Hi, I recently upgraded from a dovecot 2.1 version to 2.2.6. I now have a single user who occasionally triggers a crash (just this one user it seems?). The user connects via LiveMail (v14.0.8117.) and IMAP. Oct 29 08:05:26 mail1 dovecot: imap(customer at example.org): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6575a) [0xd94cc75a] ->

Hello, Are there any chances that I could fix this issue by running a "doveadm force-rsync" (https://wiki2.dovecot.org/Tools/Doveadm/ForceResync) on this problematic mailbox? Best regards, Mabi ??????? Original Message ??????? On Tuesday, January 21, 2020 9:53 AM, mabi <mabi at protonmail.ch> wrote: > Hello, > > I just migrated a few dovecot IMAP mailbox (Maildir

We have often found the below error in VPS servers using OpenVZ, and some cases using OpenStack, in neither case is used for storage or sharing ISCSI or NFS Client can not receive messages via POP3 or IMAP In /var/log/maillog the message below is seen Oct 31 15:28:26 vps dovecot: pop3(user at domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07400] ->

You could try force-resync, it is safe to run. Anyways, without backtrace from core file it's hard to say. Aki On 27.1.2020 9.05, mabi wrote: > Hello, > > Does anyone one have any idea? Aki maybe? > > Regards, > Mabi > > ??????? Original Message ??????? > On Wednesday, January 22, 2020 11:37 AM, mabi <mabi at protonmail.ch> wrote: > >> Hello,

Hello, I just migrated a few dovecot IMAP mailbox (Maildir format) from a Dovecot 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox server and one particular mailbox does not work properly and generates the following error log entries: Jan 21 09:39:21 Panic: imap(EMAIL_ADDRESS)<7741><UTsrWKKcasoAAAAAAAAAAAAAAAAAAAAB>: file array.c: line 10

Hello, Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot: > El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribi?: >> Hello, >> >> Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot: >>> Hello, >>> Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: >>>> Hello List, >>>> >>>> i have a problem

Hi, I have two servers that share nothing, running dovecot version 2.2.9. The first server hosts the original mail base, which I want to sync using dovecot to the second server. With some trial and error I managed to get synchronisation running using tcp sockets. Now for some accounts I see dsync-local crashing on the server that has the original mail base (which is still the only of the two

Hi I'm running into regular problems with dovecot choking on "corrupted" index files. The main problem is that it doesn't sort itself out and recover. This message below is repeated regularly in the log files (until I delete the index files) I *think* the trigger to get into this situation might be a files being delivered with incorrect S= values in the filename? Which

Hello, Does anyone one have any idea? Aki maybe? Regards, Mabi ??????? Original Message ??????? On Wednesday, January 22, 2020 11:37 AM, mabi <mabi at protonmail.ch> wrote: > Hello, > > Are there any chances that I could fix this issue by running a "doveadm force-rsync" (https://wiki2.dovecot.org/Tools/Doveadm/ForceResync) on this problematic mailbox? > > Best

Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: > Hello List, > > i have a problem with index-files which is separated in 2 subproblems. > May be these problems are connected. > Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 > These servers are fresh installed machines and users are added to the > system after, there was no upgrade.

Hello List, i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just

Hi! I've now seen this assertion failure from lmtp (most frequent), pop3 (next frequent), and imap (rarely). It didn't start happening until the number of accounts on the server was increased into the 10k-25k range. It happens when index->file_lock is a read lock and mail_index_lock is called asking for a write lock. Dovecot 2.x dies at the assertion on line 62 of mail-index-lock.c

Hello, Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot: > Hello, > Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot: >> Hello List, >> >> i have a problem with index-files which is separated in 2 >> subproblems. May be these problems are connected. >> Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 >> These servers are

I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE_NAME="cpe:/o:fedoraproject:fedora:32" Solr FTS plugin is enabled/configured, mail_plugins = virtual acl fts fts_solr plugin { fts = solr fts_autoindex = yes

> On 19/10/2020 02:49 PGNet Dev <pgnet.dev at gmail.com> wrote: > > > I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. > > Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... > > Except for this accented-character search mystery. I've got a