similar to: adding servers to director_mail_servers

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

director_mail_servers setting uses IP Adresses as values https://doc.dovecot.org/settings/core/#core_setting-director_mail_servers As described in the documentation, hostnames are converted to addresses when the configuration is read https://doc.dovecot.org/settings/types/#ip-addresses This is acceptable in host or virtual machine environment, but becomes a problem in a containerized environment.

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

Hi Maby stupid question :) It possible to have 3 directors (frontend) but without rings ? All directors connect to this same dovecot (backend) - all backad have this same login_trusted_networks -- Maciej Mi?aszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy

Hello All, Have anyone met the problem I am struggling with at the moment ? The problem is when I run two instances of dovecot 2.1.8 which are one for proxy-director and another one is a regular one on the same server then I have big amount of strange entries in the /var/log/mail.err: Jul 26 11:51:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:51:20 dovecot-test-1

Hi Timo, Upgraded to 2.0.14 last night for the director-related features and I noticed an oddity in the logs: Sep 28 09:53:21 director2 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:53:56 director1 dovecot: master: Warning: service(ipc): client_limit reached, client connections are being dropped Sep 28 09:54:23 director2 dovecot:

Hello, I have a question about director_mail_servers setting for director, I am aware that I can define a list of dovecot backend hostname there but I am not sure if the hashing apply to the hostname or underlying IP address of each hostname given? What if the IP of a specify hostname is changed? Will director pickup the new IP automatically? Will the same user hashed into the original IP still

I have a Dovecot server set up as a proxy and getting a ton of these errors, but I'm not sure where to begin troubleshooting it. I'm hearing frequently that Outlook users who use IMAP with SSL are getting disconnected often as a result. Any suggestions?... Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure

Hello, i have a setup with two director servers pointing to two backends. I don't care that much for load balancing, my main goal is high availability. CRAM-MD5 auth is working fine if I connect directly to the backends, but the director only supports AUTH=PLAIN because of the static passdb. director config: > passdb { > driver = static > args = nopassword=y proxy=y > } >

Timo, Just this morning I upgraded from 2.0.6 to 2.0.7 (hg changeset 66a523135836). A few hours later we had some power problems that caused the networking to drop out at one site. The directors on the surviving site all had a few imap-login processes crash with the following error: Nov 23 09:15:30 cc-director1 dovecot: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd

Hello, using Dovecot 2.2.9 and a setup with directors and backends. The communication between directors and backends needs to be TLS secured. The director config contains a list of hostnames for the backends. (implicit list because of multiple A/AAAA records for a single hostname or explicit list of several host names) On connection setup from a client the director connects to the selected

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

The sample Director configuration (10-director.conf) says that director_servers and director_mail_servers can be lists of either IPs or hostnames: # List of IPs or hostnames to all director servers, including ourself. # Ports can be specified as ip:port. The default port is the same as # what director service's inet_listener is using. #director_servers = # List of IPs or hostnames to all

I am running dovecot 1.0 beta3 as a front-end proxy, and getting the following error when using epoll. The error goes away if I switch to poll. On the backend IMAP server I see that the login was successful. The error occurs when I try to retrieve an email or get a folder listing via IMAP after logging in successfully... Feb 9 15:35:57 director4 dovecot: imap-login: proxy(bboebel at

On 14 Oct 2015, at 00:34, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi Timo, > > Heiko Schlittermann <hs at schlittermann.de> (Di 13 Okt 2015 22:33:23 CEST): >>> Does the attached patch work? Compiles, but untested. >> I'm about to test it. > > It seems to update the struct mail_host, but it looks as if the data > in mail_host

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

Hi, I've just tried to add managesieve to our director server, and when I try to connect they fail with Jun 26 12:28:13 director2 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=sieve#011secured#011session=5LNQjl3DjQAKAAsR#011lip=10.0.100.75#011rip=10.0.11.17#011lport=4190#011rport=39309#011resp=<hidden> Jun 26 12:28:13 director2 dovecot: managesieve-login: Error:

Hi @all, on Saturday I upgraded two dovecot servers from squeeze to wheezy and dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade everything worked fine at first. On Sunday Morning I recognized these errors (they occured after a reload for logging purpose on midnight) on one server: director: Error: Ring SYNC appears to have got lost, resending After reloading/restarting

Hey all, im experimenting with dovecot stats service, and graphing the result. My initial results are kind of interesting. Check out this graph showing connected sessions and users: http://grab.by/dReu At first I thought maybe one of our 35 imap servers was having issues sending data, but all individual servers show this patters. Here is a bunch of individual servers: http://grab.by/dReC