similar to: doveadm + dsync merging

Having dsync to make backups from existing mail-spaces, it would be nice to make dsync syncing the sieve-dirs too. -Otherweise backups aren't complete... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht

Hi I understand the crash below is caused by filesystem quota. I just report it because perhaps it could have a more graceful failure. Apr 29 09:39:17 danceny dovecot: dsync-local(jdoe): Error: Mailbox Sent: Saving failed: Not enough disk space Apr 29 09:39:17 danceny syslogd[165]: last message repeated 4 times Apr 29 09:39:17 danceny dovecot: doveadm: Error: dsync-remote(jdoe): Error: Cached

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:

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with

Dear all I have a few public folders setup and working fine, and one such public folder is 'Public/General'. I'm trying to sort dsync replication out to another server and notice that the system log is full of error messages similar to: dovecot: doveadm: Error: dsync-remote(username: Error: Can't update subscription Pu blic/General: Invalid mailbox name The replication setup

Hi! I test dsync through tcp. In a log error: dsync-remote (): Error: doveadm client: No command given All are synchronized. The error is shown by rand for the user and on that server where it is synchronized # 2.2.rc2 (976bf9e69367): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.6 ext3 auth_mechanisms = plain login digest-md5 auth_username_format = %Ln@%Ld

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot:

We're using doveadm/dsync/imapc to migrate accounts from Courier to Dovecot 2.2.20. On the source-server some user have folder names including a "%" in their name. Looks like doveadm isn't able to handle that folder names. I always stops with: dsync(testtest): Error: Failed to access mailbox INBOX.Test%TEST: Mailbox does not exist, or must be subscribed to. Peer --

Running 2.2.15 on FreeBSD 10.0. Forcing replication with: doveadm replicator replicate -f user at host.com on one user that I've seen some syslogs show up to see what's going on. Other users are fine. When I run the above command on the one user it produces a core dump. See below for syslog output and full backtrace: syslog output: Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc2.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc2.tar.gz.sig Lots of fixes since rc1. Some of the changes were larger than I wanted at RC stage, but they had to be done now.. Hopefully it's all over now, and we can have v2.1.0 soon. :) Some of the more important changes: * dsync was merged into doveadm. There is still

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc2.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc2.tar.gz.sig Lots of fixes since rc1. Some of the changes were larger than I wanted at RC stage, but they had to be done now.. Hopefully it's all over now, and we can have v2.1.0 soon. :) Some of the more important changes: * dsync was merged into doveadm. There is still

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

Hi, I'm trying to use doveadm backup but I'm having a few issues. When trying locally: `doveadm backup -D -A maildir:/usr/local/backup` It results that no mailbox is separated by user - all seems to sync on the same folder, messing up with the folder structure of the original maildir. When trying remotely: `doveadm backup -D -A -N ssh -i mykey root at myremotebackup.com:/backup

Hi list, I'm trying to do a domain migration using the imapc feature, but i'm having some problems and I really don't know what is happening. So if you guys could help me with a path to solve this, I will be glad. I'm using Dovecot 2.1.7 in a Debian Wheezy machine. The command I'm using is: dsync -Dv -o imapc_features=rfc822.size -o imapc_host=IP -o imapc_port=143 -o

Hi, It seems that dsync 2.1.10 does not correctly handle renames of mailbox subtrees. The scenario is as follows. There are two servers, A and B, both running dovecot 2.1.10 and configured to use mdbox. Automatic replication between them is disabled, ie. replication plugin is not active and replicator service has process_min_avail = 0. I perform the following actions: 1. On A: doveadm mailbox

Hi, I'm trying to configure replication with dsync on Dovecot 2.2.5 (and latest nightly). I did followed the guide at http://wiki2.dovecot.org/Replication But I can get dsync-server working only if my users do not have access to shared mailboxes and / or public mailboxes which is problematic for our setup. dsync-server is trying to create folders in public/ namespace :

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

Using strchr() was splitting login and host at the first occurrence of '@' which leads to troublesome behaviour. When calling strace one would notice the misbehaviour: execve("/usr/sbin/ssh", ["ssh", "-lthomas", "domain.org at 10.8.13.2" using strrch() however splits login and host at the last occurrence of '@'. Signed-off-by: Thomas

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)

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