similar to: dsync changing source permission to "root" in backup mode

Hi there, I'm currently evaluating the idea of a multi-master setup where each node shall hold a full copy of the mailboxes. Basically the idea is to use NFS and dsync to keep those copies in sync. So I did some tests with dsync and ran into a problem. Consider the following scenario: 1) Location1 and Location2 are in sync 2) A mail gets deleted on Location1 (via IMAP) 3) dsync mirror run to

On 9/2/19 3:03 PM, Sami Ketola wrote: >> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: ... >> Is there anyway for dsync to avoid moving Gigabytes of data for could >> just be "moved" by moving the mount? > > > Not tested but you can probably do something like this in the target server: > > doveadm backup -u

Hi, I was wondering... If one had mdbox ALT path set to a shared storage mount (say, on NFS) and one wanted to move a mailbox to a different host... I guess it in principle wouldn't be necessary to copy all the ALT storage through dsync, when the volume could just be mounted on the new host. Is there anyway for dsync to avoid moving Gigabytes of data for could just be "moved" by

Hi, It seems we are still able to reproduce this: http://www.dovecot.org/list/dovecot/2014-May/096367.html However... there's no longer any error-messages. It just silently changes permissions on some dovecot files in the source maildir. (most often dovecot-uidlist) We're running dsync as root, with hardwired userdb values for other reasons. So it has the OS permissions to change

So... I've done some testing. One method which seemed to work - at least for primitive cases - was to: * Mount the ALT storage on the destination. * Run "doveadm force-resync \*" on the destination. (putting all the mails in ALT storage into the dovecot.map.index) * Run dsync from source to destination. Of course... if there was some way to avoid step 2... /Peter

All umlauts in mailbox names are lost after converting mbox/Maildir mailboxes to mdbox. [location2 scp-ed from the old server] # ls -d /srv/import/Maildir/.Gel\&APY-schte\ Elemente/ /srv/import/Maildir/.Gel&APY-schte Elemente/ # dsync -u jane at example.com -v mirror maildir:/srv/import/Maildir/ ? dsync(jane at example.com): Info: Gel?schte Elemente: only in dest ? ? # doveadm mailbox

I think I have a working dovecot installation, and the time has come to migrate my users. There are only 4 of us, so it can be done manually per user. I looked at this page in the wiki http://wiki2.dovecot.org/Migration/Dsync but I am totally confused. 1st off, it uses doveadm, but with commands parameters that dont match my doveadm's man page. In fact they look more like dsync

I have: mail_home = /srv/mailstore/%256RHu/%d/%n mail_location = maildir:~/:INDEX=/indexes/%1u/%1.1u/%u userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } and the dovecot-ldap.conf.ext specifies: user_attrs = mailMessageStore=home, mailLocation=mail, mailQuota=quota_rule=*:storage=%$ Now I want to convert individual users to mdbox using dsync, but how to I tell

Hi all, Another question regarding migration. While migrating a mailbox with dsync is it safe to deliver mail via LMTP to the new (target) mailbox or is it wiser to deactivate LMTP delivery to this mailbox until it's fully migrated? And what methods could I use to stop delivery to a mailbox during migration? Our user data is stored on an LDAP server. Cheers, -- j.hofm?ller

Hi. Mostly annoying: I migrated from one machine to another, made sure the target host worked as expected, updated mx records and - after a couple of days - signed it off as good. This is just my private machine, no big deal if something goes wrong.. Everything's fine? Good, let's migrate my inbox from the old machine. There's no direct connectivity between those servers, so what

Hi! While performing a dsync from cyrus imap to dovecot 2.2.12, dsync seems to stop for perhaps a minute without disk / cpu / memory activity (that I can see). This happens several times per sync per user so it takes an enormous amount of time to sync just a couple of gigs of mail. dsync -D -v -o mail_fsync=never mirror -f -R -u user at example.com imapc: What could possibly be the cause of

I am running two servers with Dovecot v2.2.12 on CentOS x86_64 (5.10 and 6.5 respectively) and users are virtual over ldap. I have setup our main internal server (vmail.example.com) with dsync replication according to the first part of http://wiki2.dovecot.org/Replication. The second one (vmail1.example.com) will be the failover server which we want to be a real-time mirror (but can be

> On 3 Sep 2019, at 15.34, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: > > > > On 9/2/19 3:03 PM, Sami Ketola wrote: >>> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: > ... >>> Is there anyway for dsync to avoid moving Gigabytes of data for could >>> just be "moved" by moving

doveadm already supports some nice things, such as being able to remotely launch a doveadm command via TCP socket. It also supports executing a command for all users or to some specific users using a wildcard. dsync could use these features, so I merged dsync and doveadm into same binary for v2.1. I'll still install "dsync" symlink pointing to "doveadm", and running that

On 03/04/2016 08:52 AM, Timo Sirainen wrote: > On 04 Mar 2016, at 07:47, Richard Laager <rlaager at wiktel.com> wrote: >> Is there any way to disable the header hashing in dsync? ... > Does the attached patch happen to work? Compiles, but untested for now. It works with one more change on top of your patch: diff --git a/src/doveadm/dsync/dsync-mailbox-export.c

Hello, Some code that I didn?t write but am maintaining passes a local script?s path as dsync?s ?destination? argument, like so: dsync -D -u john -v backup -R -1 "/code/dsync_client.pl" 127.0.0.1 john at mydomain.org dsync_client.pl establishes a TCP connection with a remote dsync process then acts as a proxy between the two dsync processes. ?127.0.0.1? and ?john at mydomain.org?

Hi list! I have a problem with transfering mails from mbox to maildir format. On dovecot wiki I found a dsync tool, which looks good, but returns me an error: # dsync -u mail at example.com mirror mbox:~/mail:INBOX=/var/mail/virtuser_808 dsync(root): Fatal: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) I found a solution with

I think I get pretty much the same issue: dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a]

Hi, while syncing dsync crashed: dsync-local(matthias): Panic: dsync brain state=10 dsync-local(matthias): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0xf7eed541] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x4e) [0xf7eed66e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0xf7eed878] -> dsync [0x804e106] -> dsync [0x80539b7] ->

Hello, I'm trying to migrate from maildir++ to mdbox. The maildir++ is a leftover of our previous setup (was using courier) We have 3 virtuals servers for our +70000 accounts. Now, I'd like to use mdbox, so I'm trying using dsync for that. I setup a new virtual server, configured for mdbox. 1st, I tried a basic setup: I established a file with all my accounts (taken from LDAP)