similar to: Fatal: -N parameter requires syncing with remote host

I have been fighting, for 2 days, with a Dovecot setup and I now officially need help :) Basically, I am trying to setup replication between 2 identical Dovecot servers, on different physical servers (different hostnames/etc, of course), and although I've managed to solve many problems I can't overcome the final hurdle. When a mail comes in to one of the servers, replication over TCP

Hi, Some time ago I posted the below but never got a reponse that I could work with. So i am retrying now in the hope that there might be a better idea/suggestion on how to approach this. Situation; I have two nodes, which should replicate to eachother. My main machine receives most mail and the other one receives mostly system messages and should get replicated. (This used to be delivered on

We started using Dovecot replication between two nodes and noticed that our configured private flags (INDEXPVT) in public/shared mailboxes are not replicated. We are only replicating INBOX namespace, as we dont want to replicate content of shared mailboxes for every user again. Is there a way to replicate the INDEXPVT or is that not (yet) implemented? Dovecot versions: # 2.2.31 (65cde28):

Dovecot 2.2.27 (c0f36b0) I'm trying to configure dovecot to backup all my email to a secondary server using "dsync". I got it working in "sync" mode or two-way synchonization, that means whatever happens in one server gets replicated in the other. However, documentation also says that a one way synchronization is posible, yet, after spending a good amount of hours

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

This has been fixed in a later version of Dovecot, so your best course of action is to upgrade to some more recent version. I'd recommend 2.2.36. Aki > On 10 December 2018 at 18:28 admin via dovecot <dovecot at dovecot.org> wrote: > > > Dear suscribers. > > I just dont understand this error. Don't know where to look first. If > someone have already meet

Hi, I'm dealing for few days with replication issues between two dovecot containerized instances in Kubernetes environment. After some search, I found this thread that reports exactly the same symptoms I encountered : https://dovecot.org/pipermail/dovecot/2019-October/117353.html I can confirm that downgrade of dovecot to 2.3.7.2 fixes the issue. Testing usage of -T parameter with a very low

I'm trying to set up replication between two servers and I've hit a snag. I have two users and am using mbox files. If anybody has a sample config file for a simple system like mine I would really be grateful to see it. Thanks, The error I'm getting is: Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: user nobody: Initialization failed: Namespace

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, *Our setup:* Two Debian 10 machines that are setup to replicate mail between them, we have round robin DNS setup so a user can connect to either server. *What should happen:* Mail is delivered to either server and replicated across straight away to their mailbox on the other server so it does not matter which one they are connected to they will receive it fairly soon after delivery.

Hi, I'm trying to get dovecot working with postgres, I'm on Debian 10 and have installed dovecot-pgsql from the Dovecot repo (https://repo.dovecot.org/ce-2.3-latest/debian/....). I have the following in my local.conf : passdb sql { ? args = /etc/dovecot/local_sql_users.conf } And the following in the referenced file: driver = pgsql connect = host=localhost dbname=foobar user=bar

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 05:58 PM, Thierry wrote: > 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

Hi list, I get these warnings quite frequently. Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync Is this something to worry about? Otherwise the replication works perfectly. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum ---------------------------------------- Auf dem Huegel 69, D-53121 Bonn

Hi, I am trying to setup Sieve replication, it is almost working: 1/ Create a script - sync'd across 2/ Activate/de-activate a script - change sync'd 3/ Delete a script - change sync'd But if I make a change to a script it is not replicated, unless I de-activate and activate again. I am seeing in the logs the below during this process (de-activating/activating): Oct? 9

Hi, Jan 26 17:21:40 doveadm(user7 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:23:59 doveadm(user3 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user5 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user4 at domain.ltd): Fatal:

Dear list, I have setup a master-master replication setup. My primairy MX's send email over on a DNS loadbalanced way, so DNS is doing some kind of round-robin way of sending mail to both master servers. I found out, that on one of the two machines, the email synchronisation is heavily delayed. Lets assume server A receives a mail from the MX; it synchronises almost instantly with the other

Hi, I have two servers replicating mail as required, the directory structure (per user), however they will not replicate the sieve scripts directory: server 1 Maildir sieve server 2 Maildir Output of doveconf -n on server 1: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn >

We use a pair of replicating Dovecot servers. If a user subscribes to a folder, shared by an other user, in one replica, that does not get replicated to the other node. Subscription of regular folders below INBOX seem to replicate correctly. Is that a general bug, a known problem or do we need to enable that somehow. Here's our configuration for the concerned namespace: namespace users { ?