Re: Replication going away?

Marc wrote: >> That simply isn't true, and I am baffled that you don't know that >> replication works with a two server active/active setup for years now! >> Two separate instances (active/active) on two different continents are a >> completely reliable failover scenario for years now. > >

Re: Replication going away?

Michael Slusarz via dovecot wrote: >> On 07/18/2023 9:00 AM MDT Gerald Galster wrote: >> While I understand it takes effort to maintain the replication plugin, this >> is especially problematic for small active/active high-availability >> deployments. > > To clarify: replication absolutely

Re: Replication going away?

Emmanuel Fusté wrote: > Le dim. 16 juil. 2023, 18:55, Aki Tuomi via dovecot a > écrit : > >> Yes, director and replicator are removed, and won't be available for pro >> users either. Why in hell would one remove replicator? It's working for years now. Yes, I recall issues in the beginning,

Re: Blacklistd

Marc wrote: >> Blacklistd places a very short set of code to send a small packet to a >> socket when >> the decision is made to deny access. > And how does blacklistd get fed? Actually, one needs to add a small amount of code to dovecot which writes to a socket. This code needs to be

Re: [whishlist] new option for 'doveadm purge'

Aki Tuomi via dovecot wrote: > On 8.12.2019 22.10, Michael Grimm via dovecot wrote: >> I do store mail in mdbox format of 150m in size (dovecot 2.3.9). >> >> Once in a while I do experience mdbox files of smaller size, even after >> applying 'doveadm purge' and pre

[whishlist] new option for 'doveadm purge'

Hi, I do store mail in mdbox format of 150m in size (dovecot 2.3.9). Once in a while I do experience mdbox files of smaller size, even after applying 'doveadm purge' and previous expunges by the users. like: -rw--- 1 vmail dovecot 104854595 Feb 9 2019

Re: Dovecot release v2.3.7

Timo Sirainen via dovecot wrote: > On 13 Jul 2019, at 18.39, Michael Grimm via dovecot > wrote: >> Now replication is working from my point of view, besides occational error >> messages like: >> >> | imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE

Re: Dovecot release v2.3.7

Michael Grimm wrote: But, replication still doesn't works as known from previous versions. I will give it a try over night, but I am seeing … | Queued 'full resync' requests 1 … after 1 minute, already. The following modifications regarding my setup made replication work again (at least

Re: Dovecot release v2.3.7

Michael Grimm via dovecot wrote: > > Timo Sirainen via dovecot wrote: >> This likely fixes it anyway: >> >> diff --git a/src/lib/ostream-file.c b/src/lib/ostream-file.c > I do not compile from source, I'm using FreeBSD's ports. Thus I tried to put > this

Re: Dovecot release v2.3.7

Timo Sirainen via dovecot wrote: > > On 12 Jul 2019, at 21.05, Michael Grimm via dovecot > wrote: >> My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE >> r349799): > > I don't think these cause any actual breakage? It doesn't break completely

Re: Dovecot release v2.3.7

Aki Tuomi via dovecot wrote: > We are pleased to release Dovecot release v2.3.7. My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for imap, lmtp, sieve | dovecot[76035]: replicator: Error: