similar to: One way dsync replication with dsync -R

Ugh, sorry for the formatting. Not sure what happened when it sent through the list. Trying again Blessings, Rob Archibald CTO, EndFirst LLC rob at robarchibald.com -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Rob Archibald Sent: Wednesday, March 22, 2017 3:55 PM To: 'Wolfgang Hennerbichler'; dovecot at dovecot.org Subject: RE: One way

So, even with a particular user only connecting to one node in the pair, you still see the issue? I'm not seeing that in my setup. I only see it when concurrently connecting the same user to two different nodes in the pair. Blessings, Rob Archibald CTO, EndFirst LLC rob at robarchibald.com > On Mar 24, 2017, at 12:50 AM, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > >

Rob, Unfortunately I don?t think the director will solve this problem. I have a director in front of my setup and it is configured to point every client to one server. It didn?t change anything in its behavior. I also have a setup without a director where the clients are only allowed to talk to one host (DNS entries control this) - same thing. Wolfgang > On Mar 22, 2017, at 23:58, Rob

I'm using dsync successfully to keep two nodes synchronized, but I have the same problems as you. When I first set it up, I purposely had my phone connected to one node and my desktop connected to the other node. This allowed me to watch for the very issues you're referring to. I ran into them enough that I quit using it that way. But, what I also found was that it was just a timing issue.

It turns out that if I enable this option: pop3_deleted_flag = "$POP3Deleted? The issue no longer persists. I have to manually expunge the kept mails that have been deleted via pop3 though: doveadm expunge mailbox INBOX KEYWORD '$POP3Deleted' -A Wolfgang > On 21 Jun 2015, at 21:05, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > FWIW I just tried the sdbox

Hi, When I enable (and it only happens when it is actually running) replication over TCP my users get duplicate mails via pop3. Here?s what happens: * User gets mail * Mail appears in (Maildir) new/ folder on both replicas * user retrieves mail (retr), calls dele. Mail still exists in new/ folder on both replicas. * user runs retr (and gets the duplicate) and dele a second time, the mail is

Hi Dovecot Users, I?ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can?t explain. I found similar threads on this mailinglist, but I couldn?t find a solution anywhere. Does anybody have dsync running without problems on a high volume mailserver? I see the following logs, examples given: Feb 17 18:16:49 dovecot dovecot: imap(zoechi):

On 20 Feb 2017, at 11:09, Timo Sirainen <tss at iki.fi> wrote: > > On 17 Feb 2017, at 21.37, Wolfgang Hennerbichler <wogri at wogri.com> wrote: >> >> Hi Dovecot Users, >> >> I?ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can?t explain. I found similar threads on this mailinglist, but I couldn?t

FWIW I just tried the sdbox mailbox format for a singe user (not the whole installation) by overriding the mail-userattr via ldap and the problem persists, so I don?t think it?s an issue with maildir per se, but rather a pop3 / replication issue or a misconfiguration on my side. Wolfgang > On 20 Jun 2015, at 22:29, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > Hi, >

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

Hi, I know this may be very basic question but I need some help . Actually I installed VM using the Xen Administrative console. Now I need to change the configuration file as I need to passthrough (using the pci-hide) a SCSI contoller from Dom0 to DomU. But I couldnot find the configuration file. Where can I find the Configuration file for this DomU? Actually I added the

Is it stable for dovecot 2.2.27 to implement DRBD (or HAST) on block level for maildir data replication instead of using dsync plugin? Regards, George

Hi, I have a failover cluster for mail server with: Ubuntu12.04 + DRBD (for block replication) + Ext4 filesystem + Dovecot-2.0.19-2 with Mdbox It works fine with ~50k accounts. My cluster design: http://adminlinux.com.br/cluster_design.txt I plan to test Dovecot Replication with dsync to build an active/active cluster with load balancing. Can anyone direct me to some literature? A tutorial

dsync in Dovecot v2.0 tree is a new utility for syncing a mailbox in two locations. Some things it can be used for: - Initially transfer a mailbox to another server via SSH - A faster sync done to an existing mailbox, sending only changes - A superfast sync based on modification sequences. - Source and destination mailboxes can use different formats (convert-tool will be history) dsync can

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

Hello Everyone, I use dovecot2-2.2.10, FreeBSD 9.2-RELEASE. Replication was set up according to: http://wiki2.dovecot.org/Replication, dsync wrapper script is used. It seems that all is worked as desired, but i see the following into log file: doveadm: Error: dsync-remote(XXX at YYY): Info: save: box=INBOX, ... There were no such log records when i tried replication without wrapper script.

Hi, I have two servers that share nothing, running dovecot version 2.2.9. The first server hosts the original mail base, which I want to sync using dovecot to the second server. With some trial and error I managed to get synchronisation running using tcp sockets. Now for some accounts I see dsync-local crashing on the server that has the original mail base (which is still the only of the two

I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other

In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't finished yet, but it appears to work and I've enabled it for my @dovecot.fi mails. Some issues: - public namespace isn't replicated at all - shared namespace is replicated, but not private mail flags - I've only tested SSH replication setup now, not director replication setup (and director setup

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the