similar to: dsync with namespaces

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, I'm having some issues with replicating public namespaces. Everything seems to work fine for private namespaces, but while importing some huge mailboxes (many small mails) into a public namespace via imapsync, something goes wrong. The expected mail flow is: old-server (imapsync)> new-server1 (replication)> new-server2 But then, dovecot seems to run into race conditions when the

Hi, I am in the middle of setting up a dovecot imap server to replace an aging cyrus imapd. The new server is using mdbox storage for better filesystem performance and is running dovecot-2.2.32. To migrate email over and keep UIDs etc. intact I used the backup feature of doveadm. During testing this generally worked fine. So thanks for that functionality, it really makes migration much

On 23/01/16 15:33, Robert Schetterer wrote: > for multiple advanced imap settings at migration you might use > imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen. Sami

Hi -- I used to run two mailservers with identical MX priorities (poor man's fail-over approach) with Maildir mail folders accessed by Dovecot. Synchronization has been achieved using unison, mirroring all files except dovecot index files. Once in a while some oddities could be observed, like reappearing of deleted mails, duplicates and such alike. But the all-over performance was quite

> On 26 Jan 2016, at 15:56, Marc Schiffbauer <m at sys4.de> wrote: > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >> >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve

v2.2.19 has many fixes related to dsync+imapc, which were found while migrating several million users from GMail. I'm not aware of any problems with it now. Also even before v2.2.19 dsync+imapc has been used to successfully do many large migrations. > On 26 Nov 2015, at 17:49, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote: > > Hi, > > No, I tried fetching

Hi, I'm still trying to migrate from Dovecot 1.2.16 to 2.0.7 on FreeBSD. Previous attempts have failed with mails not being visible after the upgrade. Version 1.2.16 was migrated from maildir to dbox about a year ago via the convert-plugin. After previous attempts to "clean" the hybrid maildir-dbox situation I used imapsync to copy all mails from the old account to a new

Hi! I am playing with dsync and trying to fix an issue I have mentioned in another thread (subject: "Re: [Dovecot] Dsync error: Couldn't drop privileges: getgrnam") and feel that dsync could use some additional informational output. It would be particularly helpful while experimenting with a migration if it could output a transfer summary and / or log separately. A summary

Gentlemen, I've setup 2 servers with dsync replication and hit a serious issue - some messages got duplicated thousands times in some shared mailboxes(~5). There is actually no reason to replicate anything from shared name space and I've tried to limit replication scope with just 'inbox' name space but it didn't help. dovecot version ||2.2.18 (2de3c7248922) errors in the

I'm working on migrating IMAP users from Mirapoint Message Servers to Dovecot servers. The Mirapoint IMAP server uses INBOX as a namespace for private mailboxes. I created the same namespace in Dovecot, but when I migrate mailboxes dsync seems to ignore/miss the namespace on Mirapoint and I end up with all mailboxes under a INBOX.INBOX hierarchy. Mirapoint Source Server

I'm not certain of the correct syntax for this - and I'm reluctant to risk my live data by experimenting. I've setup a 2.0.2 server on a virtual machine, and I want to copy a live account over to it for testing. Not that it should matter, but the 1.2 machine is using maildir and I want to give sdbox a try on 2.0.2. I'm assuming (dangerous, I know) I should run dsync on the

> On 04 September 2018 at 23:20 Robert Schetterer <rs at sys4.de> wrote: > > > Am 04.09.2018 um 18:27 schrieb Sami Ketola: > > > > > >> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: > >> > >> Sorry i migrated terrabytes of mail with imapsync and never had a > >> problem, it works as designed, also with

Hi, No, I tried fetching over imapc too exactly as you suggested. In my case it was not from cyrus, but from CriticalPath. isync was finally able to do the job, preserving flags and doing UIDs mapping. The most boring part was generating proper config file for thousands of accounts. A working imapc/dsync would have been better. Emmanuel. Le 26/11/2015 15:24, Sami Ketola a ?crit : > Hi,

Am 05.09.2018 um 07:37 schrieb Aki Tuomi: > >> On 04 September 2018 at 23:20 Robert Schetterer <rs at sys4.de> wrote: >> >> >> Am 04.09.2018 um 18:27 schrieb Sami Ketola: >>> >>> >>>> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >>>> >>>> Sorry i migrated terrabytes of mail with

Hi! We have 2 servers replicating each other and after upgrade to 2.2.26.0 we are seeing this in the logs: Primary server: Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user at domain.ee): Panic: file dsync-brain-mailbox.c: line 814 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0)

Trying to get my new storage server synced up using dsync replication with SSH. Followed the wiki and everything works great for the initial sync, for about 4 hours, then I get some errors and it stops replicating: dsync-local(user at host.com): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync dsync-local(user at host.com): Error: Remote command returned error 75:

17.11.2016 11:01 Sander Lepik kirjutas: > Hi! > > We have 2 servers replicating each other and after upgrade to 2.2.26.0 > we are seeing this in the logs: > > Primary server: > > Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user at domain.ee): Panic: > file dsync-brain-mailbox.c: line 814 (dsync_brain_slave_recv_mailbox): > assertion failed:

Hello, Here is a Panic that happened while doing some testing with two servers both running Dovecot v2.2.26 on CentOS 7. These are test servers owning 32 accounts whose data were copied from our production server. What I've done is: server01# doveadm force-resync -A '*' server01# doveadm replicator replicate -f '*' For 5 accounts I obtained the following crash:

Am 04.09.2018 um 18:27 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >> >> Sorry i migrated terrabytes of mail with imapsync and never had a >> problem, it works as designed, also with maildir rsync did a good job, >> what never worked as it should was dsync ,cause of bugs ,that may >> changed now