similar to: Can we retrieve Dovecot Proxys 'hostName' from Director instead of LDAP?

Hi everyone, short version: Is there no built in failover mechanism for the director service to handle a backend failure? Long version: I have a frontend server running the director service and two backends. Due to maintenance I had to shut down one of the backends which caused connection errors for the users being directed to this backend. I was very surprised as I expected the director to

I'm working the kinks of a new director based setup for the eventual migration away from courier. At this point, with everything basically working I'm trying to ensure that things are properly monitored and I've run into an issue. There doesn't appear to be a way to get dovecot to tell if it is (or is not) connected and properly synced with the other director servers in the ring

I have Poolmon (https://github.com/brandond/poolmon) set up. When it does all the checks concurrently, obviously there are locking issues on each mailserver it tests: "Warning: Locking transaction log file xxxx/indexes/dovecot.list.index.log took 60 seconds (syncing)" It's just an empty mailbox. Is there any way to do a login test, without locking the index files? Hence

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at interactive.eu> > > wrote: > > > > > > The only suspect thing is this: > > > > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host > > 192.168.1.142 > > vhost count changed from 100 to 0 >

In data venerd? 7 settembre 2018 11:20:49 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.25, Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > > Actually, I have a poolmon script running that should drop vhost count for > > unresponsive backends; the strage thing is, the backends are NOT > > unresponsive, they are working as ususal. > If it's this

Hi I have two server directors in ring and 5 dovecot servers (2.2.36) IP for IMAP and POP3 is a VIP (keepalived) What is the best solutions to get realy HA for 5 dovecot servers ? Maby corosync+pacemeker ? But this solution is too problematic and hardcore Why I need HA ? Doveadmin is too lazy and doveadm director does not know that one machine broke down and still sends traffic

Hello, I have recently setup mailserver solution using 2-node master-master setup (mainly based on MySQL M-M replication and GlusterFS with 2 replica volume) on Ubuntu 14.04 (Dovecot 2.2.9). Unfortunately even with shared-storage-aware setting: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mmap_disable = yes ..I have hit strange issues pretty soon especially when user was

In data marted? 11 settembre 2018 10:46:30 CEST, Timo Sirainen ha scritto: > On 11 Sep 2018, at 10.57, Simone Lazzaris <s.lazzaris at interactive.eu> wrote: > > Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file > > doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion > > failed: (conn->to_ring_sync_abort == NULL) Sep 11 03:25:55 imap-front4

Hi, First, my version: [root at centos1 conf.d]# dovecot --version 2.2.15 [root at centos1 conf.d]# I have already configured dovecot that way (on one single VM, so everythinh is stored on the same machine) - A post fix server sending out to LMTP - LMTP is the dovecot LMTP server, configured with "lmtp-proxy= no", - LMTP checks the users receiving

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but there does not seem to be a similar breakdown of user connections per director. The output of

As someone who is about to begin the process of moving from maildir to mdbox on NFS (and therefore just about to start the 'director-ization' of everything) for ~6.5m mailboxes, I'm curious if anyone can share any experiences with it. The list is surprisingly quiet about this subject, and articles on google are mainly just about setting director up. I've yet to stumble across an

On Thu, Feb 23, 2017 at 3:45 PM, Zhang Huangbin <zhb at iredmail.org> wrote: > > > On Feb 24, 2017, at 6:08 AM, Mark Moseley <moseleymark at gmail.com> wrote: > > > > * Do you use the perl poolmon script or something else? The perl script > was > > being weird for me, so I rewrote it in python but it basically does the > > exact same things. >

I have this[0] config, yet the /var/run/dovecot/login/director is not created, what to check in the config? dovecot: imap-login: Error: auth: connect(director) failed: No such file or directory [0] service director { unix_listener login/director { #mode = 0666 } fifo_listener login/proxy-notify { #mode = 0666 } unix_listener director-userdb { #mode = 0600 }

Halo, Please can you explain why this is advantage over a hardware load balancer. I fail to see advantage if anything it add in more point of failure, with several hundred thousand user, we can ill afford to mess around or add to complexity, sometime keeping it simple is simply way to be, when use qmail/vpopmail, we never had one failure or problem, ever, we very proud of this record so our users.

But if in the configuration of the director is stated login/director. Than I assume this socket should be in the login dir not? You have also the director activate with executable = imap-login director? -----Original Message----- Subject: Re: Login/director not created On my install the login/ dir is: drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/ srw-rw-rw- 1 root

Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:

Hello, I have discovered a strange behaviour with director proxying... I have a user, its assigned server is 155.54.211.164. The problem is that I don't know why director sent him yesterday to a different server, because my server was up all the time. Moreover, I'm using poolmon in director servers to check availability of final servers and it didn't report any problem with the

I plan on putting two dovecot directors in front of our backend dovecot pop/imap servers, instead of our current haproxy loadbalancing of the connections -- but how do we handle SSL in such a setup. Will all SSL be terminated on the directors automatically, and then proxyed plain text, or is there any configuration needed to achieve this ? Does it matter that the directors are v2.0 while the