Hi all,
New to the mailing lists but have joined up because of above */2.3.1
Replication is throwing scary errors
/*Brief system configuration
MX1 - Main
Freebsd 11.1-Release-p9
Hosted on a Vultr VM in Sydney AU
MTA = Postfix 3.4-20180401
Dovecot = 2.3.1
s to
investigate) or just let us know if the root cause has been found. This
bug is a showstopper and has stopped me tracking master-2.3 for over 3
months now, as I can't test later builds or even upgrade to the 2.3.1
release while replication is so broken.
Reuben
Message: 1
Date: Sun, 6 May
On 1/06/2018 2:47 AM, Michael Grimm wrote:
On 31. May 2018, at 18:09, Remko Lodder wrote:
On 31 May 2018, at 17:52, Michael Grimm wrote:
I would love to get some feedback from the developers regarding:
#) are commercial customers of yours running 2.3 master-master replication
without thos