Edy Sulai wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You much fill out the sn field because in qmailUser object, sn is
required attribute. Make sure each object has their sn entry.
I had vpopmail setup with ldap before, but that was quite a long time
ago. As I remembered, a patch to vpopmail source was required. I'm not
sure on newer vpopmail version.
Edy
Oliver A. Rojo wrote:
Im having a problem with integrating vpopmail with ldap. I've already
installed everything...
What I did:
1. I set these options on vldap.h before compile
#define VLDAP_SERVER "localhost"
#define VLDAP_PORT LDAP_PORT
#define VLDAP_USER "cn=vpopmailuser, o=vpopmail"
#define VLDAP_PASSWORD "vpoppasswd"
#define VLDAP_BASEDN "o=vpopmail"
2. My compile options
--enable-auth-module=ldap
3. Copied the file slapd.conf and qmailUser.schema from the vpopmail
ldap directory to ldap etc/ and schema/ directory
4. Successful creation of vpopmail database
ldapadd -f vpopmail.ldif -x -w vpoppasswd -D'cn=vpopmailuser,o=vpopmail'
The problem is when I add a virtual domain
/home/vpopmail/bin/vadddomain mydomain.com
I get an error saying:
Error: Object class violation (65)
additional info: object class 'qmailUser' requires attribute 'sn'
Failed while attempting to add user to auth backend
Error: (vadduser) no auth connection
What seems to be the problem here? Did I missed something?
Please help!
Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEGiR0zkzx2xIRtA0RAlicAJ0Y/YP5ReSMqzNtof8LEapTfhdJ/gCgj9EY
SFhwQEj7PVvsAnuQjJsXulQ=
=CLJJ
-----END PGP SIGNATURE-----
where will I fill out the 'sn' entry? is it on the schema files? im
sorry im just a newbie openldap user.
--
Oliver A. Rojo
______________________________________________________________
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in error
please notify the system manager. Please note that any views or
opinions presented in this email are solely those of the author
and do not necessarily represent those of the company. Finally,
the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any
damage caused by any virus transmitted by this email.
