similar to: dsync problems

I've been moving users from one system to another by doing a dsync mirror operation. The first dsync mirror takes some time, because of the number of users involved, so I am doing an initial sync, and then I direct the users to the new location and do a final 'freshening' sync to get any changes that happened during the longer sync. The problem seems to be with this freshening sync,

Dear all, I am using VMWare and I have cloned my emails server. Now I do have two identicals servers, both running the same version of dovecot (2.2.13) and imap. Let's call them: server1.domain.ltd and server2.domain.ltd. I would like to sync both server using dsync. Dovecot is working well except concerning the sync. dsync config server1.domain.ltd # Enable the replication plugin

Hi Mike, Is the value of the 'doveadm_port' if I am choosing: mail_replica = tcp:server1.domain.ltd no ? I might be wrong too ;) Thx Le mardi 24 janvier 2017 ? 11:41:28, vous ?criviez : > Hello, > I might be wrong, but the port which will be used for the replicator > port is the value of 'doveadm_port' which in your case is 4711. > Mike; > On 01/23/2017

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 \

Gents, I'm relocating mailboxes to a new server. Before switching over to a new server I ran syncing a few times without any issues first I sync files with rsync from the old server to have a local copy, then I sync mailboxes with dsync /usr/bin/doveadm -Dv sync -u $MBOX -R "sdbox:/srv/vmail/temp/srv/srv.bgoperator.ru/${MBOX}:DIRNAME=DbOx-mAiLs" After switching over smtp

I ran across what I think may be a bug in dsync when trying to convert from mbox to Maildir format. My first attempt failed with a runaway dsync process spewing out thousands of identical lines of the form: dsync(buus): Error: Duplicate mailbox GUID 00fe691ff60da85b090d0000c8119523 for mailboxes Archive/Personal and Work/VendorInfo - giving a new GUID 00fe691ff60da85b090d0000c8119523 to

We are currently in the process of replacing one of our customer mail systems with a dovecot solution. However, one of the sticking points right now is how to get the old mail to the new system. On the dovecot side, we are using mdbox storage. On the old system we are using qpopper/mbox mailboxes in the following setup. All user inboxes are in /mnt/mail/mail_spool. Only select, privileged,

In case anyone is interested in reading (and maybe helping!) with a dsync redesign that's intended to fix all of its current problems, here are some possibly incoherent ramblings about it: http://dovecot.org/tmp/dsync-redesign.txt and even if you don't understand that, here's another document disguising as an algorithm class problem :) If anyone has thoughts on how to solve it, would

I would like to set up an active-active fault tolerance couple of mail servers. Is the following procedure correct? Let's suppose I want to set up two servers for acme.com, mail1.acme.com and mail2.acme.com I declare both servers as MX in DNS configuration. Mailbox are stored in maildir with a single UID/GID owner for all the maildir files Userbase is MySQL, user tables are replicated

Hi, I want to set-up two dovecot imap servers, with active-active replicated maildirs. The goal is to have a hosted public server on Internet, and a private server on my LAN to speed-up local connections. So I compiled dovecot 2.0 beta 1 in order to use dsync utility... Actually my config is pretty simple as I just want to setup a proof of concept before going ahead in this way : (Both servers

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

Hello, dovecot version: 2.3.9.2 When I use dsync: /usr/bin/dsync -v -D -o plugin/quota= -f -u my at email.dom backup maildir:/tmp/mailbackup/Maildir it always stops when it comes to a folder with an "@" in its name. Error Message: Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID (maybe it was just deleted?) I dont know if it makes a

Hi, I'm trying to migrate from Cyrus (remote side) to Dovecot 2.2.24 (local). On the local side the destinations folders, and indexes are empty. The command I'm using is doveadm \ -o mail_plugins= \ -o imapc_master_user=<cyrus-user> \ -o imapc_password=<cyrus-password> \ -o imapc_host=<cyrus-ip> \ \ -o imapc_ssl_verify=no

Hi again, after replacing CRLF in 4 mboxes dsync was able to sync all of the 30+GB mailstore to mdbox. Now the (repeated) calling of dsync yields info messages of the kind dsync(athimm): Info: old/speicher: highest_modseq changed: 1 != 10 dsync(athimm): Info: root/root-heretic: highest_modseq changed: 1 != 10 dsync(athimm): Info: lists/ccrma.stanford.edu/planetccrma: highest_modseq changed: 11

I'm using dsync for a regular backup. The backup system flocks so that two cannot run at the same time, which is generally a good thing. The problem is that it seems like dsync sometimes goes off into the weeds and never comes back, leaving a process running and doing nothing forever, hogging the lock and causing my backups never to run again. I just finally figured out that was what was

I have been working on converting people from courier maildir -> dovecot mdbox and during some of the dsync runs I'm seeing the quota_exceeded_message be printed as an Error: dsync(<user>): Error: Can't save message to mailbox INBOX: You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and \ delete emails with large attachments.

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

Thanks. I've had the user clear out that mailbox, and replication is working fine for them again. Is there a better way to catch this than watch for crashes and read the backtrace to find what mailbox needs to be shrunk? Where is the threshold for "too big"? -- Ian On 2/23/18 11:33 AM, Aki Tuomi wrote: > The mailbox is too big. > > > > --- > Aki Tuomi >

Im trying to sync 2 mailserver with dsync mirror functionality. Problem occurs when mails arrive in the same folder on both sides then dsync sometimes runs into problems and duplicates that entrys on both side(2mails then with same content). After running again the same happens again(now 4 mails with same content on every side). And then duplicates this mails on both sides on every run :(

Hello, I'm aware of these two threads http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox