similar to: replication issues between to nodes

Hi, Anyone has suggestions? The situation also happends when I ?delete? a message from my Phone. It seems to get replicated instantly and the just deleted email is back in the mailbox again. I did remove HA Proxy support in the meantime to rule that out and I have enabled the default replication_max_conns. thanks Remko > On 13 Oct 2017, at 11:56, Remko Lodder <remko at FreeBSD.org>

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

Maybe you could not delete the message instantly, but keep track of last seen UID. UIDs increase monotonically, so you can rest assured that next arriving email has larger UID. Then you can bulk delete mails that are older than one day. Aki > On October 20, 2017 at 8:01 PM Remko Lodder <remko at FreeBSD.org> wrote: > > > Hi, > > Anyone has suggestions? The situation

Dear Dovecot and community, We run a small email service for our customers, based on two machines that are made ?redundant or clustered? by using the replication feature of Dovecot. This works well, for most emails. Sometimes the following happends: Email to our support database arrives at the inbox. Every period a cronjob looks into that mailbox and parses the information and makes a support

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these

Dear Dovecot community, As discussing on IRC with Aki, I have the following thing happening: I got an alert from my mailservice last night that I was running over quota. My quota reached almost 91% (coming from 30%) in one day. I do not recall receiving so much email (we talk about multiple gb?s additional space usage), so something was acting up. When I logged into my mailservers (I?ll

Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root at dovecot01:~# dovecot --version//

Em Sat, 18 Mar 2017 16:24:25 +0100, Christian Kivalo escreveu > Am 18. M?rz 2017 18:55:58 MEZ schrieb Nilton Jose Rizzo <rizzo at i805.com.br>: > >Em Sat, 18 Mar 2017 11:36:34 +0100, Christian Kivalo escreveu > >> On 2017-03-18 07:19, Nilton Jose Rizzo wrote: > >> > Em Fri, 17 Mar 2017 22:35:40 -0300, Nilton Jose Rizzo escreveu > >> >> Em Thu, 16

5 Gennaio 2017 01:21, "John Fawcett" <john at voipsupport.it> wrote: > On 01/04/2017 08:40 PM, Juri wrote: > >> Hi, >> I'm trying to configure a Dovecot dsync service between two servers, using a tcp+ssl connection and >> a valid Let's Encrypt certificate. >> I followed the guide on the wiki (http://wiki.dovecot.org/Replication) using the

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

Am 18. M?rz 2017 18:55:58 MEZ schrieb Nilton Jose Rizzo <rizzo at i805.com.br>: >Em Sat, 18 Mar 2017 11:36:34 +0100, Christian Kivalo escreveu >> On 2017-03-18 07:19, Nilton Jose Rizzo wrote: >> > Em Fri, 17 Mar 2017 22:35:40 -0300, Nilton Jose Rizzo escreveu >> >> Em Thu, 16 Mar 2017 23:06:08 -0700, Doug Barton escreveu >> >> > On 03/17/2017

Hi, I'm trying to configure a Dovecot dsync service between two servers, using a tcp+ssl connection and a valid Let's Encrypt certificate. I followed the guide on the wiki (http://wiki.dovecot.org/Replication) using the tcps method, but when I launch the replication it fails writing on the log (/var/log/mail.err): (Server 1 - sync "client" )| Error: sync: Disconnected from

Hello, I have two mail servers and am also experiencing sporadic replication errors over tcps, similar to Reuben. Each server is running Dovecot 2.3.11.3 (502c39af9) on Debian 10.6. *Log entries from MX1* Nov 18 00:39:26 mx1 dovecot: dsync-local(user at example.com)<Ow3zAjWxtF+TDgAAPHKnuQ>: Error: dsync(mx2.example.com): I/O has stalled, no activity for 600 seconds (last sent=mailbox,

Em Sat, 18 Mar 2017 11:36:34 +0100, Christian Kivalo escreveu > On 2017-03-18 07:19, Nilton Jose Rizzo wrote: > > Em Fri, 17 Mar 2017 22:35:40 -0300, Nilton Jose Rizzo escreveu > >> Em Thu, 16 Mar 2017 23:06:08 -0700, Doug Barton escreveu > >> > On 03/17/2017 01:21 AM, Nilton Jose Rizzo wrote: > >> > > > >> > > > >> > >

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 "mail2" host, by creating symlink ".dovecot.sieve ->

Have you specified the path to ca-certificates? On Debian it's normally something like that #10-ssl.conf ssl_client_ca_dir = /etc/ssl/certs see http://wiki.dovecot.org/Replication#SSL Am 10.11.2016 um 16:09 schrieb nerbrume at free.fr: > Hello, > > I'm using dovecot 2.2.13 on Debian stable. > My users are authenticated through PAM, and stored in an LDAP backend >

Hi, I've been seeing errors logged for some time with replication processes, whereby replication sessions seem to be timing out periodically. This is with dovecot version 2.3.10.1 (a3d0e1171) and both are Gentoo x86_64. After some investigation I've determined that these timeouts are only ever occurring with tcps as the replication connection type. These errors never occur if

Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal:

Hi all! I've decided to rotate the dovecot logs automatically on my freebsd 10.4 server using the system's newsyslog feature. I started with logfile.info putting the line /var/log/dovecot/logfile.info 600 31 * @T16 ZCU /var/run/dovecot/master.pid 30 which should send a SIGUSER to the master process, which it seems to do for I see in the log file: master:

The 'noreplicate' user database field described in the wiki appears to make no difference as to whether an account gets replicated or not. My sql user query returns a 'noreplicate' field and I can confirm that this is getting set using 'doveadm user', however when I add a new account with noreplicate=true it gets replicated regardless. User query: user_query = SELECT