similar to: [2.3.8] possible replication issue

I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > upgrading to 2.3.9

Hello, upgrading to 2.3.9 unfortunately does *not* solve this issue: I upgraded one of my replicators from 2.3.7.2 to 2.3.9 and after some seconds replication stopped. The other replicator remained with 2.3.7.2. After downgrading to 2.3.7.2 replication is again working fine. I did not try to upgrade both replicators up to now, as this is a live production system. Is there a chance, that

Hello Timo, upgrading both replicators did the job! Both replicators now run v2.3.9 and replication works fine, all sync-jobs which queued up during the upgrading have been processed successfully. Thanks for the reassurement and all your great work with dovecot, Andreas Am 05.12.19 um 13:15 schrieb Timo Sirainen via dovecot: > I think there's a good chance that upgrading both will

Hello, after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords, which in my case are set by thunderbird, are not preserved any more when moving a mail between folders. Are there any ideas, what may be the reason. Thanks for any hints on that, Andreas 'doveconf -n' gives: # 2.3.4 (0ecbaf23d): /etc/opt/csw/dovecot/dovecot.conf # Pigeonhole version 0.5.4 (60b0f48d) # OS:

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the

Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of 'doveconf -n' with the newly build package is # 2.2.25 (68082dc):

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

Hello, Dovecot 2.2.25 OS: Solaris 11 (SunOS 5.11 11.3 i86pc i386 i86pc) Virtualization: VMware Filesystem: ZFS active users: ~4000 About once a day Dovecot crashes with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)" The log shows in each case: Aug 29 12:59:00 surz113 dovecot: [ID 583609 mail.crit] imap(username): Panic:

On 01.09.2016 14:20, Piper Andreas wrote: > Hello Timo, > > with the newly build CSW-package the crashes still occur, today already > twice within two hours. The log shows always the same: > > Sep 1 11:50:13 surz113 dovecot: [ID 583609 mail.crit] imap(user): > Panic: file imap-client.c: line 837 (client_check_command_hangs): > assertion failed: (client->io != NULL) >

Hi Jake, thanks for fixing this. I have installed now the newly built package on my production system and will report, if any more core dumps occur. Regards, Andreas Am 31.08.2016 um 20:19 schrieb Jake Goerzen: > Hi Andreas & Timo, > > > I've found out what is causing the incorrect hash in the built > packages. Our build system use here at OpenCSW has internal git

Hi, i tried to setup replication since some days but I'am stuck now. My conf: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.3.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) dsync_remote_cmd = ssh -l%{login} %{host} /usr/bin/doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} log_path = /var/log/dovecot mail_gid = 5000 mail_home = /var/vmail/%d/%n mail_location =

Hi, I am attempting to setup replication between two hosts running Centos 6.4 and Dovecot 2.2.5. My users are real unix users, so I am trying to run the replication as root user, so that it has the appropriate permissions to run. I have two users at present syd1 and syd2, and the two hosts are called syd1 and syd2 as well. When I start Dovecot with the settings below, nothing happens, and the

I am migrating an old dovecot 2.2.30 (macOS High SIerra, macO S Server) to a new server with dovecot 2.3.7 (macOS Mojave, macports). To get the data over, I?m trying to do a reverse backup with doveadm between an old and a new mail server, but failing to do so. I?m trying (from the new server, the old server is 192.168.2.67): doveadm -Dv \ -o imapc_host=192.168.2.67 \ -o imapc_user=gerben \

with dovecot --version 2.3.10.1 (a3d0e1171) exec of doveadm -v -o mail_fsync=never backup -R -f -u testuser at example.com imapc: currently fails, here, with Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted checking lists, this has been seen before @ https://dovecot.org/pipermail/dovecot/2016-January/102988.html On 24 Jan 2016, at 18:47, Timo Sirainen

hi all when I use dsync migrate users from dovecot2.0.14(maildir Solaris10) to dovecot2.2.15(mdbox debian7) , most of the users migrated well, only one user has a error. migrate cmd: "$dovecotHome"bin/doveadm -Dv -o mail_fsync=never -o imapc_host=$ip backup -R -u $user imapc: dovecot2.2.15 log: doveadm(root): Debug: Loading modules from directory: /home/mail/dovecot/lib/dovecot

Hi everyone, I'm hoping I am just missing something obvious - but I cannot seem to get a one-way migration dsync working between two Dovecot servers because the Prefix configuration is different. I am doing a migration from our old Dovecot servers to some new cPanel based ones. Source: 2.2.15 Dest: 2.2.21 Here is the debug output for the sync: doveadm(root): Debug: Loading modules from

Hi, Using dsync to backup my users' mailboxes (dovecot 2.2.10 on both sides), I sometimes encounter the following issue. Below is the output of: dsync -Dvf -u "user" -R backup ssh root at server.domain.tld dsync -u "user" doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin,

Hi all, I've run into an issue with in-place mailbox format conversions between mdbox and maildir and wondered if someone could assist. When using dsync to convert a mailbox, the conversion loses a mailbox GUID and produces a warning. This behavior seems to have been introduced between version 2.2.31 and 2.2.32. See below for the full debug output from both versions followed by the dovecot

Hi All! I'm also hitted by this problem. I'm trying to migrate emails from very old dbmail to dovecot (maildir). I read old threads with similar problem but I found only such solutions: - upgrade to 2.2.13 - workarround : use imapsync - no solution I'd like to not use imapsync, have you got an idea what should I do to do migration successfully? dsync throws: doveadm(root): Debug:

>> As per my post: checkpassword. You can then use one password on Mondays, >> Wednesdays, and Fridays, alternate passwords on Tuesdays and Thursday >> fetched from a rot-13 database, and only from prime numbered IP addresses >> on weekends, if that's what you want. > > Having read the wiki page on checkpassword, I am unsure how this would > work with an ldap