Am Sonntag, den 11.12.2005, 00:36 +0200 schrieb Timo Sirainen:
And smaller new features:
- If LDAP lookup fails because connection gets closed, try retrying it again after reconnect. This is however untested, hopefully didn't break LDAP code completely..
about complete LDAP breakdown ... is the problem that I posted for alpha3 and 4 solved now (or did I maybe miss something important):
---------CUT----------
All of our data is ldap based and everything is working as before for our IMAP customers, but our POP3 users fail.
Obviously the pop3 login process does not read the data correctly that comes from ldap.
after enabling mail_debug, I saw the following error in our log:
--------CUT-------- dovecot: Nov 02 18:01:32 Info: pop3(some.one.at.work): mbox:
--------CUT--------
The INBOX should be /virtual/at.work/var/mail/some.one.at.work, yet
data=/virtual/at.work/home/some.one/mail/:INBOX=/var/mail/some.one.at.work the
POP3 process obviously uses the default_mail_env settings.
the relevant line in our dovecot-ldap configuration looks like this: -------CUT-------- user_attrs = uid,homeDirectory,MailMessageStore,,uidNumber,gidNumber -------CUT--------
As I said, the IMAP process uses the ldap data correctly. ---------CUT----------
thanks
Udo Rader
-- BestSolution.at EDV Systemhaus GmbH http://www.bestsolution.at