similar to: dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server

Greetings - I', continuing to build a test system that, at present, only I have access to. It is running Dovecot 1.0rc24. Here's the output of a "dovecot-n"... # /usr/local/etc/dovecot.conf log_path: /logfiles/mail/live/dovecot protocols: imap ssl_cert_file: /usr/local/etc/ssl/certs/imapservice-bundle.crt ssl_key_file: /usr/local/etc/ssl/private/imapservice-private.key

Hi, I have configured dovecot for auth_bind against an LDAP server on the localhost and I'm seeing the following error in my dovecot logs: dovecot: Apr 30 09:03:18 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Apr 30 09:03:27 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server ... and so on ... When I turned on LDAP

I can't get my domain users presented to my local machine with getent passwd and the wiki https://wiki.samba.org/index.php/Local_user_management_and_authentication/nslcd doesn't give me any steps troubleshoot this issue. My best guess it that I configured the user account incorrectly or I configured nslcd incorrectly. I can't exactly see what is the problem. I get these messages from

Dear list members, I am having some problems with a LDAP passdb authentication on Dovecot. Before I forget, the specs: it's a Ubuntu 7.10 server running Dovecot 1.0.5 connecting to 2 different machines running LDAP servers: gold with OpenLDAP 2.4.19 and extra with OpenLDAP 2.4.9 (extra is a replication slave of gold). The initial setup of dovecot was with a MySQL passdb, which is still the

Hi, i have this in /var/log/messages May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Timed out May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Can't contact LDAP server but i defined log_path and info_log_path in dovecot.conf "dovecot -n not show different values for "protocol lda"? Regards # dovecot -n # 1.0.10: /etc/dovecot.conf log_path:

Hi list I currently having troubles to "connect" dovecot (for proxy) to an existing LDAP. If I got the dovecot wiki right only userdb is needed for a proxy setup where the proxy does not authenticate but just forward to the backend for authentication. So I setup the following in dovecot-ldap.conf.ext user_attrs = =password,=y=nopasswd,=y=proxy,mailHost=host user_filter =

Hello All, We have interesting issue. When application connect to PDC by port 389 (without ssl) everything works fine. When we try to use SSL by port 636 we have issue. ldapsearch -x -D "cn=user,ou=users,dc=dc,dc=local" -p 636 -h PDC -b "DC=dc,DC=local" -w pass output: ldap_result: Can't contact LDAP server (-1) ldapsearch -x -D

I have tried configure Postfix with Dovecot SASL to authenticate remote users in LDAP (Active Directory). Below my dovecot.conf: protocols = none ssl = none auth default { ??? mechanisms = plain login ?? ?passdb ldap { ??????? args = /usr/local/etc/dovecot-ldap.conf ? } ?? ?userdb ldap { ??????? args = /usr/local/etc/dovecot-ldap-userdb.conf ? } }

My environment is "heterogeneous" my authentication and home server are currently stuck on a 1G shared network, the production servers and storage servers are on a bonded 40G network, all are in the same VLAN. I have about 100 servers on the 40GB bonded network each with 12cores and 128GB of memory. They are running centos 6.6 Except for my storage servers they are all just running

I upgraded dovecot two weeks ago from 0.99.10-0.rc2 to 0.99.10.4-1woody1 (both from the woody backport packages from braincells.com). Dovecot is using LDAP on a separate machine for authentication. (through stunnel if it matters) At 4:00 am, the LDAP server stops, dumps the ldap database, and then starts back up. Because the LDAP server is stopped, anyone who tries to authenticate during

Hi Timo, On 01.03.2016 22:51, Timo Sirainen wrote: > On 29 Feb 2016, at 17:18, Gordon Grubert <gordon.grubert+lists at uni-greifswald.de> wrote: >> >> Hi, >> >> we are using a round robin dns record for connections to our ldap >> system. This works fine for almost all cases. In particular, for >> dovecot does this mean, when an ldap server is stopped,

Hi all, I'd like to perform some ldapsearch against my AD domain. And I'd like to be able to perform these ldapsearch using GSSAPI to avoid usage of password in scripts. DC are using default configuration file: ---------------------------------------- # Global parameters [global] workgroup = SAMBA.DOMAIN realm = SAMBA.DOMAIN.TLD netbios name = M707 server

Hello people! I'm new to the list and to dovecot too. In advance I'd like to thank everybody who could help me, and I'll be very glad if a could help somebody here. I'm working in a project to integrate dovecot and active directory authentication for 2 weeks without total success. I've tried so many waysto solve my problem, but no one gave me the right answer. I'll

Hello, I am running a Dovecot server (version 1.2.17) on FreeBSD 8.2, using LDAP to authenticate Active Directory users. I can successfully bind and authenticate using PLAIN and LDAP without SASL, but obviously passwords for the bind user and the user being authenticated are being passed in plain text. I've attempted to configure my server to us SASL however when I attempt to authenticate a

I also keep on getting funny errors of dovecot EVEN THOUGH I authenticated successfully through SMTP (Dovecto SASL) ?!?! Just for debugging this entire issue I set those parameters: debug_level = -1 auth_verbose = yes auth_verbose_passwords = yes auth_debug = yes auth_debug_passwords = yes mail_debug = yes verbose_ssl = yes cat /var/loca/maillog Jan 26 12:08:22 WM-01

I hope that someone will be so kind to help me into solving this really strange thing (don't know if it is a bug or not) I have a samba4 server and want to use postfix+dovecot - dovecot version is 2.0.11 as for the postfix side everything is OK (all the LDAP lookups works without any error, tested also manually with postmap -q) the real pain is with dovecot deliver: it seems that

Hello list, I am struggling with setting up dovecot 2.1.7 with samba 4.1.2 on debian wheezy. Dovecot should authenticate via LDAP, but I?cannot get it to work reliably. Sometimes auth works, sometimes not. Referals are already activated in ldap.conf ? LDAP-authentication works fine with other clients (Apache Directory Studio, ?)? Has somebody got a similar setup running? I would love some hints

Hello Timo, We have installed dovecot 2.0.10. With LDAP authentication. Users authenticate successfully but in the authentication process there are errors that I don't understand because it's everything all right: May 10 18:00:49 carpe3 dovecot: auth: Error: ldap_unbind May 10 18:00:49 carpe3 dovecot: auth: Error: ldap_free_connection 1 1 May 10 18:00:49 carpe3 dovecot: auth: Error:

Hello list, I'm using dovecot 1.0.2 on OpenBSD 4.1. About every month, dovecot will just stall, without any error messages. The processes are still running, the network ports are open, but the login just hangs. The following error message does occur on a very regular basis: Aug 15 00:52:37 mail dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Aug 15

Hallo, I want to run postfix - dovecot - openldap working together The first problem is, that dovecot doesn't create the directories /usr/local/mail/abcshop.at/bamm/Maildir cur new tmp although I can contact the Dovecot-Server telnet localhost 143 OK .... 1 login bamm at abcshop.at secret OK Logged in /usr/local/mail/ is owned by virtual:virtual If I uncomment the line #mail_location =