[imp] IMP LDAP warnings

Suraj K. Rai surajrai@yahoo.com
Mon, 01 Jul 2002 22:12:14 +0900


Hi All,

Anny updates on this one?  I am having the exact same issue with RH 7.3, 
Horde 2.1 and IMP 3.1.

I managed to get the debug output from the openldap server but only 
after playing around with a lot of settings.  It is not exactly 
obvious... One would think that setting the loglevel option in 
slapd.conf to something like 256 would do it but apparently not. What 
you have to do is provide the -d <loglevel> option to the ldap 
executable. I did this by editing /etc/sysconfig/ldap and adding the line:
	SLAPD_OPTIONS="-d 6"
This causes the -d option to be passwd to slapd when it is started by 
the /etc/rc.d/init.d/ldap script.  One caveat to doing this is that the 
ldap script does not seem to be able to background the process.  But 
that should be good enough for testing.  After doing this, the log 
messages will appear on /var/log/messages

Now to the real issue at hand...you ask below "How did you populate the 
ldap-server?"...Are we supposed to populate by hand?  I thought the 
database would be automatically populated the first time the user logs 
into imp.  If we do have to populate it by hand then please do let us 
know how to do it...

As for the acl...to facilitate things.. I gave default access to "write" 
for all...but to no avail. In any case, here is my slapd.conf:

#######################################################################
# Begin Config

include         /etc/openldap/schema/core.schema
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/inetorgperson.schema
include         /etc/openldap/schema/nis.schema
include         /etc/openldap/schema/redhat/rfc822-MailMember.schema
include         /etc/openldap/schema/redhat/autofs.schema
include         /etc/openldap/schema/redhat/kerberosobject.schema

# NOTE: I copied the schema file from horde/scripts/ldap/horde.schema
include         /etc/openldap/schema/horde/horde.schema

defaultaccess write

loglevel 0

#######################################################################
# ldbm database definitions
#######################################################################

database        ldbm
suffix          "dc=srai,dc=org"
rootdn          "cn=Manager,dc=srai,dc=org"
rootpw          mypasswd
directory       /var/lib/ldap
index   objectClass,uid,uidNumber,gidNumber,memberUid   eq
index   cn,mail,surname,givenname                       eq,subinitial

# End Config
#######################################################################

I apologize for a top-post but I figured I could make myself clearer 
this way.  Thanks for all your help.

Thanks,

S.r.

Timo Boettcher wrote:
> Hi Per,
> 
> Nachricht vom Freitag, 14. Juni 2002, 05:21:29:
> 
> PB> Jon Parise wrote:
> 
> PB> (Thanks for the response!)
> 
> 
>>>These values aren't correct, then.  What is you LDAP server telling
>>>you?
>>
> Hmmm... run slapd with
> loglevel        256
> in slapd.conf.
> what do you get as errormessages?
> 
> Did you configure the schema, and the acl for the necessary
> objects? It would help if you you paste your slapd.conf here.
> How did you populate your ldap-server?
> 
> PB> It's not telling me anything.  What am I supposed to ask it, and how?
> PB> I'm running Red Hat 7.3 with almost everything installed, and
> PB> with an slapd running.
> 
> PB> (The top item on my wishlist for Horde/IMP is real complete
> PB> step-by-step installation instructions.)
> 
> I'm working on that, for RH7.3 + imp + courier + Postfix + ldap
> I'll publish that when my machine does work...
> 
> 
>>>>Warning: Couldn't open stream {bothner.com:143}INBOX in 
>>>>/var/www/html/horde/imp/test.php on line 157
>>>
>>> 
>>>It doesn't look like the host 'bothner.com' is running an IMAP server.
>>
> 
> PB> It is most definitely running an IMAP server (the uw server that is the
> PB> default for Red Hat 7.3), and serving from port 143 - that's how Mozilla
> PB> accesses my email.
> 
> I did get this error to, even as I could acces imap via telnet just
> fine.
> 
> 
>  Timo
> 
> 
>