>From my phone, so excuse brevity and top-posting, but Fastmail running murder
>would be a huge bonus. I not-so-fondly recall the intimate relationship I
>developed with gdb debugging murder issues when we upgraded from 2.3 to 2.4 :)
Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
For sure :)
Just having testing infrastructure that tests murder would go a long way
to avoiding that mess again.
The more I think about it, the more having the SAME mailboxes.db for
both local and remote data doesn't make sense. We should have a separate
central database that the mupdate_activa
14.03.2015 01:50, Bron Gondwana wrote:
So I've been doing a lot of thinking about Cyrus clustering, with the
underlying question being "what would it take to make FastMail run a
murder". We've written a fair bit about our infrastructure - we use
nginx as a frontend proxy to direct traffic to bac
On Sat, Mar 14, 2015, at 11:22 PM, Vladislav Bogdanov wrote:
> 14.03.2015 01:50, Bron Gondwana wrote:
> > So I've been doing a lot of thinking about Cyrus clustering, with the
> > underlying question being "what would it take to make FastMail run a
> > murder". We've written a fair bit about our i
On 2015-03-13 23:54, Dave McMurtrie wrote:
From my phone, so excuse brevity and top-posting, but Fastmail running
murder would be a huge bonus. I not-so-fondly recall the intimate
relationship I developed with gdb debugging murder issues when we
upgraded from 2.3 to 2.4 :)
You won't have t
On 2015-03-13 23:50, Bron Gondwana wrote:
So I've been doing a lot of thinking about Cyrus clustering, with the
underlying question being "what would it take to make FastMail run a
murder". We've written a fair bit about our infrastructure - we use
nginx as a frontend proxy to direct traffic to
On Sun, Mar 15, 2015, at 07:18 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2015-03-13 23:50, Bron Gondwana wrote:
> > So I've been doing a lot of thinking about Cyrus clustering, with the
> > underlying question being "what would it take to make FastMail run a
> > murder". We've written a f
On 2015-03-14 22:48, Bron Gondwana wrote:
On Sun, Mar 15, 2015, at 07:18 AM, Jeroen van Meeuwen (Kolab Systems)
wrote:
How, though, do you "ensure" that a mailbox for a new user in such
business is created on the same backend as all the other users of said
business?
If the business already exi
On Wed, Mar 18, 2015, at 09:00 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2015-03-14 22:48, Bron Gondwana wrote:
> > On Sun, Mar 15, 2015, at 07:18 AM, Jeroen van Meeuwen (Kolab Systems)
> > wrote:
> >> How, though, do you "ensure" that a mailbox for a new user in such
> >> business is cre
On 2015-03-18 01:51, Bron Gondwana wrote:
On Wed, Mar 18, 2015, at 09:00 AM, Jeroen van Meeuwen (Kolab Systems)
wrote:
We promote a standby frontend not otherwise used, to become the new
mupdate server. The interruption is a matter of seconds this way,
unless of course you're in the typical stal
On Wed, Mar 18, 2015, at 09:49 PM, Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2015-03-18 01:51, Bron Gondwana wrote:
> > On Wed, Mar 18, 2015, at 09:00 AM, Jeroen van Meeuwen (Kolab Systems)
> > wrote:
> >> We promote a standby frontend not otherwise used, to become the new
> >> mupdate server
11 matches
Mail list logo
