dovecot - Feb 2015 - "Temporary authentication failure" ? Cant connect with ldap user

Is there a good, foolproof dovecot-openldap tutorial that walks you through
the steps and works with the newest version of both softwares?
I'm giving up and starting anew.

2015-02-24 11:33 GMT+01:00 Mihai Badici <mihai at badici.ro>:
> On Tuesday 24 February 2015 10:51:44 David Scheele wrote:
> > Hmm...
> >
> > *ldapsearch -x cn=admin* gives me:
> > | # A bunch of information not really interesting
> > | # search result
> > | search: 2
> > | result: 32 No such object
> > |
> > | numResponses: 1
> >
> > *ldapsearch -x cn=admin* gives the same.
> > Did i configure the ldap wrong?
> Ldapsearch will search in the default container.
> But probably the admin user is in different container, like
> cn=admin,cn=config
> so you can't find it with this search
>

On Wednesday 25 February 2015 10:31:22 David Scheele
wrote:
> Is there a good, foolproof dovecot-openldap tutorial that walks you through
> the steps and works with the newest version of both softwares?
> I'm giving up and starting anew.
> 2015-02-24 11:33 GMT+01:00 Mihai Badici <mihai at badici.ro>:
> > On Tuesday 24 February 2015 10:51:44 David Scheele wrote:
> > > Hmm...


Well, I'm not sure.  As I said, you can take a look on my templates.
Openldap is maybe to flexible for us :) and the dovecot setup always depend 
on openldap setup.. which depend on your distribution if you install it with 
apt-get.
If you download my packages you don't need to install them but there are
some
configuration templates you can see and modify.

If you have anonymous access you don't need to bind with admin credentials.


> > > *ldapsearch -x cn=admin* gives me:
> > > | # A bunch of information not really interesting
> > > | # search result
> > > | search: 2
> > > | result: 32 No such object
> > > | 
> > > | numResponses: 1
> > > 
> > > *ldapsearch -x cn=admin* gives the same.
> > > Did i configure the ldap wrong?
> > 
> > Ldapsearch will search in the default container.
> > But probably the admin user is in different container, like
> > cn=admin,cn=config
> > so you can't find it with this search
-- 
Mihai B?dici
http://mihai.badici.ro

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 25 Feb 2015, Mihai Badici wrote:
> On Wednesday 25 February 2015 10:31:22 David Scheele wrote:
>> Is there a good, foolproof dovecot-openldap tutorial that walks you
through
>> the steps and works with the newest version of both softwares?
>> I'm giving up and starting anew.
>
>> 2015-02-24 11:33 GMT+01:00 Mihai Badici <mihai at badici.ro>:
>>> On Tuesday 24 February 2015 10:51:44 David Scheele wrote:
>>>> Hmm...
>
> Well, I'm not sure.  As I said, you can take a look on my templates.
> Openldap is maybe to flexible for us :) and the dovecot setup always depend
> on openldap setup.. which depend on your distribution if you install it
with
> apt-get.
> If you download my packages you don't need to install them but there
are some
> configuration templates you can see and modify.
>
> If you have anonymous access you don't need to bind with admin
credentials.
(Y)

@David:
You should know your LDAP setup and craft Dovecot for it.

- From your question I guess that you have not changed the LDAP scheme, but 
use some default posixAccount objectclass.

So tell us:

1) does ldapsearch -x -h server
displays all users ? If yes: No admin access required.

2) How does your users are to login? Mail address, account name, user 
name?

3) Which information is storred in LDAP per account mandatory and in which 
LDAP attribute.
>>>> *ldapsearch -x cn=admin* gives me:
>>>> | # A bunch of information not really interesting
>>>> | # search result
>>>> | search: 2
>>>> | result: 32 No such object
>>>> |
>>>> | numResponses: 1
>>>>
>>>> *ldapsearch -x cn=admin* gives the same.
>>>> Did i configure the ldap wrong?
>>>
>>> Ldapsearch will search in the default container.
>>> But probably the admin user is in different container, like
>>> cn=admin,cn=config
>>> so you can't find it with this search
>
- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVO27x3z1H7kL/d9rAQJGhggAj/DEzn5pl9yGG2tgAo2OvMCAW9ag/saw
D+vDNK2MKgDRYbWk3Rt9pdHGWmTBtXMZltIX/EFe/nFOMMBFpwS0qbEaJedCuNad
ThEVtrYRkliwkXR6XMdLbPWbM47eJt+feftygD/NJ6V5rZ6QmX22aALJbZz8QbRJ
9nq7CsbGai1T99cjUxBny2u6jF96gjXI4DIr8iyva+GIWiehIGUl4n+9NGqgvvky
SBLwefTrRZDQPfMj4+NjNxdjZ/RDKC+aFVSTrbybXQCTUv3LDm9BU5JJchO6q53x
VzJWLmC08gmuv0bG+xc5rmoeV49GoFhkX1C8h5ovDbG5XYbPiP9pQA==Z1Ak
-----END PGP SIGNATURE-----