> Well, does the port 389 work then? It's mentioned there only because
> someone complained that 389 didn't work.. Perhaps because it required
> TLS? Or something, I don't know.
I will have to play with it some. Just switching to port 389 really
slowed everything down and may have caused some othe
> Then there's something different what Dovecot and ldapsearch does. They
> have the same dn, dnpass, neither uses tls, same base, deref, scope?
>
I figured it out, there certainly is something different! The
AuthDatabase/LDAP documentation on the Dovecot Wiki says "When
connecting to AD, use port
> What about pass_filter, does that work with imap/pop3 logins?
Interesting question. Typically users only try to login with their
sAMAccountName and thats always worked just fine. I just tested this
and pass_filter seems to be running in to the same issue. If I set the
pass_filter to:
pass_filte
8 PM, Timo Sirainen wrote:
> On Wed, 2009-10-14 at 16:00 -0400, Mark Schaub wrote:
>> user_filter =
>> (&(objectclass=person)(|(sAMAccountName=%n)(mail...@sau24.org)(othermailbox...@sau24.org)))
>
> My LDAP knowledge isn't that great, but does | accept more th
Good Afternoon,
I have my virtual users stored in an Active Directory database. As far
as mail info goes the 2 important fields are: mail (their primary
email address) and otherMailbox (a multivalue attribute containing
their mail aliases). Right now all email addresses belong in the same
domain a
