Ok,
I must be doing something wrong.. I always have an aweful time
populating the open-ldap database with qmail information.
For instance.. I've tried the Elvis example given in life with qmail as well as:
dn: cn=Andre Oppermann, o=Internet Pipeline, c=CH
cn: Andre Oppermann
sn: Oppermann
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: qmailUser
mail: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailHost: opi.flirtbox.ch
mailMessageStore: /usr/home/opi/Maildir/
mailForwardingAddress: [EMAIL PROTECTED]
deliveryProgramPath: /usr/home/opi/bin/smsinformer -q
deliveryMode: noprogram
mailQuotaSize: 1000000
mailQuotaCount: 1000
qmailUID: 1001
qmailGID: 1001
uid: opi
userPassword: {SMD5}b28a87511da157f147ed4766b0474a8a
accountStatus: active
When I try to import it I get:
daemon: activity on: 8r
daemon: read activity on 8
connection_get(8): got connid=2
connection_read(8): checking for input on id=2
ber_get_next
ber_get_next: tag 0x30 len 691 contents:
ber_get_next
ber_get_next on fd 8 failed errno=11 (Resource temporarily unavailable)
do_modify
ber_scanf fmt ({m) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
ber_scanf fmt ({i{m[W]}}) ber:
>>> dnPrettyNormal: <cn=Andre Oppermann, o=Internet Pipeline, c=CH>
=> ldap_bv2dn(cn=Andre Oppermann, o=Internet Pipeline, c=CH,0)
<= ldap_bv2dn(cn=Andre Oppermann, o=Internet Pipeline, c=CH,0)=0
daemon: select: listen=6 active_threads=0 tvp=NULL
daemon: select: listen=7 active_threads=0 tvp=NULL
=> ldap_dn2bv(272)
<= ldap_dn2bv(cn=Andre Oppermann,o=Internet Pipeline,c=CH,272)=0
=> ldap_dn2bv(272)
<= ldap_dn2bv(cn=andre oppermann,o=internet pipeline,c=ch,272)=0
<<< dnPrettyNormal: <cn=Andre Oppermann,o=Internet Pipeline,c=CH>,
<cn=andre oppermann,o=internet pipeline,c=ch>
send_ldap_result: conn=2 op=8 p=3
send_ldap_response: msgid=9 tag=103 err=53
ber_flush: 42 bytes to sd 8
my slapd config file looks like:
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
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/qmail.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
pidfile /var/run/slapd.pid
argsfile /var/run/slapd.args
# Load dynamic backend modules:
# modulepath /usr/sbin/openldap
# moduleload back_bdb.la
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la
# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it. Your client software
# may balk at self-signed certificates, however.
# TLSCACertificateFile /usr/share/ssl/certs/ca-bundle.crt
# TLSCertificateFile /usr/share/ssl/certs/slapd.pem
# TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem
# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64
# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
# by self write
# by users read
# by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn. (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!
#######################################################################
# ldbm and/or bdb database definitions
#######################################################################
#database bdb
database ldbm
suffix "dc=chilitech,dc=net"
rootdn "cn=manager,dc=chilitech,dc=net"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
# rootpw secret
# rootpw {crypt}ijFYNcSNctBYg
rootpw XXXXXXX
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /var/lib/ldap
# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub
# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 starttls=critical
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/[EMAIL PROTECTED]
Any thoughts?
