similar to: Replication between servers with different mail_home path

Just had my first (non-Dovecot) server failure due to dried out caps on the motherboard. Got me to thinking about my single-point-of-failure mail server. Currently running Dovecot and Postfix with no issues, but want to start taking steps just to be safe. I currently run a filesystem backup every 24 hours to a tar file over NFS to another server in our rack. I am backing up: /home/vmail

I'm getting the following error when using dovecot replication: dovecot: imap(foo at bar.com): Error: open(/var/dovecot/replication-notify-fifo) failed: No such file or directory I guess this has something to do with the fact that every user is chrooted in it's own homedir. Does dsync support dsync notification when all users are chrooted? lmtp does not seem to have this problem so new

I'm running dovecots replicator successfully on 33 mailboxes. There is only one mailbox (the biggest one, 167000 mails) that is not replicating successfully. After 10 minutes the "source" starts logging these messages: dovecot: dsync-local(foo at example.com): Error: dsync(imap.netsend.nl): I/O has stalled, no activity for 600 seconds dovecot: dsync-local(foo at example.com):

Greetings, Working on setting up replication and ran into some errors I have questions about and wondering if there's something I need to change. This one is fairly common: Sep 3 12:58:25 molecular dovecot: dsync-server(user at domain.org): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 100298 no longer in transaction log) These two I ran into

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 =

I'm getting an error backing up mailboxes. I'm using the mirror command: dsync -fvo mail_home=/home/users/bob mirror ssh vmail at 10.1.4.1 dsync -o mail_home=/home/.incoming_mail_migrations/users/bob dsync-remote(vmail): Error: Mailboxes don't have unique GUIDs: 1ef6ee37c694894d783100000581a675 is shared by INBOX and INBOX dsync-remote(vmail): Error: command BOX-LIST failed

On 24.06.2019 16:25, Reio Remma wrote: > On 24.06.2019 8:21, Aki Tuomi wrote: >> On 22.6.2019 22.00, Reio Remma via dovecot wrote: >>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l >>> vmail backup.host.ee doveadm dsync-server -D -uuser at host.ee >>>

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

Hi everyone, I'm running a test environment with a proxy in front of working replication between two backends but redirecting in case of a backend failure is not working. Nov 09 21:03:59 imap-login: Error: proxy(mail at example.net): connect(10.5.29.211, 143) failed: Connection refused (after 0 secs, local=10.5.29.201:38333) I appreciate any advice. Regards Patrick Proxy: # 2.2.7:

Hi! This is a issue that has been fixed in master, thank you for reporting. See https://github.com/dovecot/core/commit/187fbf157d5c42f9f06ce52884fefbb4f66c070d.patch Aki On 17.10.2017 21:12, Dmitry Nezhevenko wrote: > Hi, > > Can't find any notes about this in documentation. Is replication supposed > to work between different versions of dovecot? > > I've just found

Hi, We have dsync failing once in a while when running in "backup" mode. What's strange is that the result is that the file permissions on the *source* machine ends up with the wrong permissions (set to uid 0). Even though the dsync manual clearly says: "Backup mails from default mail location to location2 (or vice versa, if -R parameter is given). No changes are ever done

hi, I had a long (upgraded today from 2.0.17 to 2.1.9) time mail_location and mail_home at the same path, which I recognize know, that it wasn't a good idea, idea. On my testsystem I've set: mail_home = /imap/spool/%d/%1u/%u mail_location = maildir:~/:INDEX=~/ otherwise I don't have access to the mails anymore. Is that ok? cu denny

Hello In my setup I have the following in dovecot.conf (dovecot 2.0.12) mail_home = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/ mail_location = mdbox:/buzones/my_domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n My problem is with the autocreation of mail_home. We are using roundcube+sieve plugin and the first time a user tries to use sieve fails with

2.2.13/0.4.2, both from source-tarball, no fancy options. tcp-replication between two nodes and following plugin parameters (same on both sides, except the ip-addr) plugin { sieve_before = /home/ssfn/etc/dovecot/sieve.default sieve_global_dir = /home/ssfn/etc/dovecot sieve = ~/.dovecot.sieve sieve_dir = ~/.sieve sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 6h

Hi, Can't find any notes about this in documentation. Is replication supposed to work between different versions of dovecot? I've just found that dovecot 2.2.33.1 was uploaded to debian unstable and it crashes on every replication with older dovecot 2.2.27. (version 2.2.32.1 was probably ok) Summary: - 2.2.33.1 crashes when replicating from/to 2.2.27 - 2.2.32.1 probably ok when

Hi all, I'm using dsync for backups. I recently upgraded to 2.1.7 due to issues with dsync mirror/backups. 2.1.7 fixed the issue with the guid conflict, but now I'm seeing this error on a couple of mailboxes: Error: proxy client timed out (waiting for output stream to flush, 0 bytes left) If there are 0 bytes left, why is it trying to flush? I'm using this command to backup the

At a customer we run dovecot-2.3.10 along with postfix and mariadb, using postfixadmin as GUI. Now I plan to migrate to a new hardware (bigger machine) and in the same step to migrate from Gentoo Linux to Debian Linux. So I think about how to get the mailboxes from A to B. We use one UID afaik: mail_home = /home/vmail/%d/%u mail_location = maildir:~ I read about dsync and wonder: * does it

Hello! dovecot version 2.1.7 I set up vacation with sieve. We have mboxes and maildirs and in dovecot.conf mail_location = mbox:/var/spool/vhosts/%d/dovecotprivate/%n:INBOX=/var/spool/vhosts/%d/%n Error: User archiv at xyz.de doesn't have home dir set, disabling duplicate database Dec 19 20:37:03 lda(archiv at xyz.de): Error: sieve: sieve script file path ~/.dovecot.sieve is relative to

Hello, Although this issue has been raised in another thread: https://www.mail-archive.com/dovecot at dovecot.org/msg57281.html I decided I should create a new one dedicated on it because that thread includes other issues as well, and the issue in question still remains unresolved although it is an important one (and I am hoping to attract Timo's attention on it, too ;-) ). The

This document describes a design for a dsync-replicated Dovecot cluster. This design can be used to build at least two different types of dsync clusters, which are both described here. Ville has also drawn overview pictures of these two setups, see http://www.dovecot.org/img/dsync-director-replication.png and http://www.dovecot.org/img/dsync-director-replication-ssh.png First of all, why dsync