Hi --
On 28.02.2012, at 15:03, Timo Sirainen wrote:
> This document describes a design for a dsync-replicated Dovecot cluster.
Whow! That's more than interesting, that's a real bummer ;-) At least for
my setup of redundant mail servers.
Looking forward to test it,
Michael
On 28.2.2012, at 22.10, Charles Marcus wrote:
> But a question out of curiosity: can the Director be configured to redirect
> userA to private IP #.#.#.# when connecting from a local subnet, but connect
> them to Public IP ##.##.##.##.## when accessing remotely? I don't know enough
> about rout
On 2012-02-28 9:43 AM, Timo Sirainen wrote:
On Tue, 2012-02-28 at 09:27 -0500, Charles Marcus wrote:
On 2012-02-28 9:03 AM, Timo Sirainen wrote:
This document describes a design for a dsync-replicated Dovecot cluster.
Wow, talk about timing... this looks like a perfect answer to my
previo
On Tue, 2012-02-28 at 09:27 -0500, Charles Marcus wrote:
> On 2012-02-28 9:03 AM, Timo Sirainen wrote:
> > This document describes a design for a dsync-replicated Dovecot cluster.
>
>
>
> Wow, talk about timing... this looks like a perfect answer to my
> previous question about setting up two
On 2012-02-28 9:03 AM, Timo Sirainen wrote:
This document describes a design for a dsync-replicated Dovecot cluster.
Wow, talk about timing... this looks like a perfect answer to my
previous question about setting up two servers in two different
locations to serve two different sets of use
This document describes a design for a dsync-replicated Dovecot cluster.
This design can be used to build at least two different types of dsync
clusters, which are both described here. Ville has also drawn overview
pictures of these two setups, see
http://www.dovecot.org/img/dsync-director-replicat
