similar to: Director and backend on the same server

I'm trying to setup our first director server. Trying to keep the initial config simple really as just maybe a proof of concept and its got me pulling my hair out today. Initially I just tried to convert one of my already running IMAP servers to be a director just to see if I could do it. I modified the configs as it appeared they needed based on: https://wiki2.dovecot.org/Director

Hi all, I am interested in running a Dovecot Proxy(with Director) on the same server as the main Dovecot IMAP/POP3 service. I have a basic Proxy/Director configuration working, however I am struggling with getting the Proxy and IMAP/POP3 service to coexist on the same server. I plan to use three IMAP/POP3 servers with a NFS/maildir backend, and I am playing with Dovecot 2.1.5 at the moment. I

I'm experiencing some problems similar to those described in http://dovecot.org/list/dovecot/2012-July/137250.html except with 2.0.9. Adding http://dovecot.org/list/dovecot/2012-July/084906.html to the main config didn't seem to help, nor did setting the list of director and backend servers to just the system itself. I get a banner connecting to port 143: [root at retr01 log]# telnet

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

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, I'm trying to use dovecot as a proxy as described on http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy but without much success. The problem is that when I send a IMAP login command dovecot is responding with "BYE Internal login failure. Refer to server log for more information." Can anyone help me shed light on this problem? Here's the log (Username,

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with

Dave McGuire writes: >> http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets >> >> then setup fail2ban to manage extrafields > > Now that's a very interesting idea, thank you! I will investigate this. If you don't expect yor firewall to handle 45K+ IPs, I'm not how you expect dovecot will handle a comma separated string with 45K+ entries any

Hi, I'm setting up an IMAP/POP cluster using dovecot director for some NFS reasons and I'm getting some troubles with director_servers directive. Configuration is shared on both nodes : director_servers = 10.0.50.50 10.0.50.51 director_mail_servers = 192.168.0.150 192.168.0.151 director_user_expire = 15 min service director { unix_listener login/director { mode = 0666 }

Hello, I've been running dovecot for over 3 years now and it works with no problems. I have it setup so that it authenticates users against Active Directory via LDAP and so far no problems. What I would like to know is if there is any way that I could deny access for users trying to access email via cellphones or email clients outside the company. I can

Hi I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is configured to act as director and delivers to my two backend servers. I enabled lmtp proxy on director to listen on port 24. Now I see in msg headers that the connection to the lmtp proxy uses STARTTLS but the connection from proxy to backend seems to be unencrypted. Is it possible to enforce the use of STARTTLS in the

Hi All, Does anyone know how to disable the Director service. In our current running Dovecot 2.2.4, if the director configuration is commented out and Dovecot has no errors nor warnings. But the version 2.2.12 I'm testing with gives out fatal errors. We have dedicated Dovecot Director servers that serve the public frontend and separate dedicated imap/pop3 servers on the backend

Hi, I thought I read that anything from dovecot.conf can be overridden in a userdb lookup. Or a passdb lookup with "userdb_" prefix. But I tried for fun change log_path but it never worked. Is that because logging is special, already started logging before it comes to the passdb/userdb lookups? So are there some dovecot.conf settings that cannot be overridden? Thanks!

Hi Timo Heiko Schlittermann <hs at schlittermann.de> (Mi 14 Okt 2015 01:10:20 CEST): ? > Ah, the information comes from the other director running. The other one > is using an unpatched version of dovecot. Your patch for backend-certificate verification works. Thank you for the good and fast work. Is there any chance that this will make it into Dovecot's next release? BTW: The

Abstract from http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy > > host=s: The destination server's *IP address*. This field is required. > Note that currently it's required to use an IP address since no DNS > resolving is done. > Hello Timo, Here goes one more item for the v2.0 wishlist: Will it become possible to do dovecot imap proxying based on a

Hello, I like to enable the allow_nets Feature (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets) for my customers. To help them knowing there own IP I imagine a special mailbox/loginuser at the pop3 server. That user could give a valid pop3 answer from a dummy pop3 server or simply throw a login error with customised answer containing the IP information. Has anybody done

We are looking at deploying several pop/imap servers to house the mail for 15,000 or more mailbox accounts. We are contemplating on the design and are looking at using MySQL auth (we already have a MySQL environment in place for our user auth to live) and proxy_maybe so each server can proxy for all the others and we just have a network load balancer distribute the incoming connections to all of

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

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

The wiki <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy> page says this: "The connections created to the destination server can't be TLS/SSL encrypted.". Hrmm. Right now, with perdition, I'm forcing the use of STARTTLS on the internal connections. I'd just as soon get rid of perdition (to have one less moving part in my architecture), but I need the