Re: High availability of Dovecot

2019-04-11 Thread luckydog xf via dovecot
It seems that we got 2 solutions. 1. use DNS MX record and dsync plugin of dovecot. No shared storage. 2. use VIP and shared storage. I'll try both of them, thank you guys. On Thu, Apr 11, 2019 at 8:45 PM Gerald Galster via dovecot < dovecot@dovecot.org> wrote: > > > > Am 11.04.2019 um 13:45 s

Re: High availability of Dovecot

2019-04-11 Thread Gerald Galster via dovecot
> Am 11.04.2019 um 13:45 schrieb Patrick Westenberg via dovecot > : > > Gerald Galster via dovecot schrieb: > >> mail1.yourdomain.com IN A 192.168.10.1 >> mail2.yourdomain.com IN A 192.168.20.1 >> >> mail.yourdomain.com

Re: High availability of Dovecot

2019-04-11 Thread Stephan von Krawczynski via dovecot
On Thu, 11 Apr 2019 16:44:40 +0800 luckydog xf via dovecot wrote: > Hi, list, > [...] >Thanks for any suggestions and ideas. > Hm, it seems most of the people answering have no real experience in production with suchs setups. Basically do this: - setup keepalived as a cluster director on bo

Re: High availability of Dovecot

2019-04-11 Thread Stephan von Krawczynski via dovecot
On Thu, 11 Apr 2019 16:44:40 +0800 luckydog xf via dovecot wrote: > Hi, list, > [...] >Thanks for any suggestions and ideas. > Hm, it seems most of the people answering have no real experience in production with suchs setups. Basically do this: - setup keepalived as a cluster director on bo

Re: High availability of Dovecot

2019-04-11 Thread Patrick Westenberg via dovecot
Gerald Galster via dovecot schrieb: > mail1.yourdomain.com IN A 192.168.10.1 > mail2.yourdomain.com  IN A 192.168.20.1 > > mail.yourdomain.com  IN A 192.168.10.1 > mail.yourdomain.com

Re: High availability of Dovecot

2019-04-11 Thread Gerald Galster via dovecot
> Am 11.04.2019 um 11:48 schrieb luckydog xf : > > As your statement, nothing speical is needed to do except setting up DNS MX > records, right? MX records are for incoming MAIL: yourdomain.com IN MX 100 mail1.yourdomain.com yourdomai

Re: High availability of Dovecot

2019-04-11 Thread Jan Bramkamp via dovecot
While possible it probably overkill. A simple failover proxy is enough unless he requires a active-active setup. On 11.04.19 11:54, Aki Tuomi via dovecot wrote: > > On 11.4.2019 11.44, luckydog xf via dovecot wrote: >> Hi, list, >> >>      I'm going to deploy postfix + dovecot + CephFS( as Mail S

Re: High availability of Dovecot

2019-04-11 Thread Aki Tuomi via dovecot
On 11.4.2019 11.44, luckydog xf via dovecot wrote: > Hi, list, > >      I'm going to deploy postfix + dovecot + CephFS( as Mail Storage). > Basically I want to use two servers for them, which  is kind of HA. >   >     My idea is that using keepalived or Pacemaker to host a VIP, which > could fail

Re: High availability of Dovecot

2019-04-11 Thread Gerald Galster via dovecot
> I'm going to deploy postfix + dovecot + CephFS( as Mail Storage). > Basically I want to use two servers for them, which is kind of HA. you may consider dovecot's builtin dsync replication which works great with two servers (while there still is one little bug that may duplicate mails u

Re: High availability of Dovecot

2019-04-11 Thread Jean-Daniel Dupas via dovecot
> Le 11 avr. 2019 à 10:44, luckydog xf via dovecot a > écrit : > > Hi, list, > > I'm going to deploy postfix + dovecot + CephFS( as Mail Storage). > Basically I want to use two servers for them, which is kind of HA. > > My idea is that using keepalived or Pacemaker to host a VIP

High availability of Dovecot

2019-04-11 Thread luckydog xf via dovecot
Hi, list, I'm going to deploy postfix + dovecot + CephFS( as Mail Storage). Basically I want to use two servers for them, which is kind of HA. My idea is that using keepalived or Pacemaker to host a VIP, which could fail over the other server once one is down. And I'll use Haproxy or Ng