similar to: director with same director / backend servers

Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I?ve got some problems to get my director scenario running as needed/expected :( My scenario: I?d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As

Hi Folks, I spent quite some time yesterday understanding how proxy works along with the director. I came to the conclusion that proxy_maybe and director cannot be used together, but this isn?t a true incompatibility so much as caused by the way things are handled and the order they are processed in. The way proxy_maybe works is that it is processed by the auth provider once it gets the

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically

Hi help is preciated, PROBLEM The dovecot-ldap.conf of "proxy server A" is working when the "host" attribute is the FQDN of other server: pass_attrs = uid=user,userPassword={SSHA}password,\ =proxy_maybe=,maildrop=host,=port=143,=destuser=%u,=starttls=any-cert pass_filter = (&(objectClass=posixAccount)(uid=%u)) CASES When the "host" attribute is the

Hi folks, i am trying to get dovecot to work in my qmail-ldap instalation but no success so far. I respectfuly request your help. Here is my /etc/dovecot/dovecot.conf : auth_debug = yes auth_verbose = yes base_dir=/var/dovecot default_process_limit=100 disable_plaintext_auth=no listen=200.235.128.97 log_path=/var/log/dovecot.log login_greeting = Etosha Messaging Suite IMAP ready mail_uid=vmail

Hi, I'm using dovecot 2.1.7 on debian Squeeze with ldap integration. Almost everything is working fine and I would link to thank all developers for this amazing piece of software. But after changing my qmail-ldap to do LDA integration get all the benefits from LDA and sieve, some emails return with failure like this: <sar at mondialline.com.br>: lda(sar): Fatal: Unknown argument: sar

Hello everybody and Timo. I have the next problem. With LDAP tree like ou=mail | - dc=example1.com,ou=Mail | - mail=box1 at example1.com,dc=example1.com,ou=Mail | - mail=box2 at example1.com,dc=example1.com,ou=Mail ? | - dc=example2.com,ou=Mail | - mail=box1 at example2.com,dc=example2.com,ou=Mail | - mail=box2 at example2.com,dc=example2.com,ou=Mail ? and settings in dovecot

Hello, After going crazy building a dovecot cluster, I finally see the light ;-)) But some things are "strange" and could probably be fixed/enhanced. First : I follow the wiki doc, setting global doveadm_port. Things did not work, I've got: dovecot: doveadm(X1234567): Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don't support crentials lookups (to see if user

Le 07/05/2014 17:38, Emmanuel Fust? a ?crit : > Hello, > > After going crazy building a dovecot cluster, I finally see the light ;-)) > But some things are "strange" and could probably be fixed/enhanced. > > First : > I follow the wiki doc, setting global doveadm_port. > Things did not work, I've got: > > dovecot: doveadm(X1234567): Error: sync:

heya-- Been playing with dovecot today as I was learning about the features I haven't used yet like the director/proxy stuff. I setup a basic dovecot stack today which is 1 director and 1 IMAP dovecot server behind it. I have one user setup in MySQL and when I first changed from proxy mode to director mode I left the host column populated with the IMAP server. Once I confirmed this was

Hi, We recently shutdown our old LDAP server and repointed our mail server (dovecot + postfix) to our new LDAP server and ever since we've been unable to fetch mail. Mail is getting delivered, but we just can't pop it. We're using Ubuntu 16.04, btw. We keep on getting the following error messages in /var/log/dovecote: 2019-05-15 16:27:43 auth: Error: LDAP

On 13 Oct 2015, at 21:44, Heiko Schlittermann <hs at schlittermann.de> wrote: > > 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

When using proxy_maybe CRAM-MD5 authentication fails when the connection is proxied. Is this expected behavior? Is proxy_maybe too simplified for this case? We're using SQL so I could rewrite the query with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS

Hello Timo, The last time I checked my understanding about director was that : 1. backend/"real" imap servers should not be on the same host (or the same dovecot instance) to avoid proxying loops. Is it still the case with the latest 2.1 stable release ? Is there a plan to be able to run director and real server on the same host, thus requiring only 2 hosts instead of 4 to have

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

Hello, ???I am trying to setup dovecot director and am receiving a lot of "Aborted login (proxy dest auth failed)" and "error proxying loops to itself" messages in the dovecot log. I don't fully understand the dovecot-ldap.conf file config? could someone please let me know if the following is correct. If so what could be causing the errors mentioned above, if not what

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64

Hello. 1. I have two identically hosts 2. I have set up replication between two hosts 3. I have 'Y' AS proxy_maybe in password_query. 4. password_query returns one of this one hosts 5. I set this parameters in dovecot config: disable_plaintext_auth = yes ssl = yes auth_mechanisms = plain login for enforce use encrypted connections by client programs.

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

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi