Re: ldapadd problem

[Vincent Bonamy <vincent.bonamy@geomath.fr>]

ldapadd stops with your first object:
but maybe after, the others objects will be also wron :(
but here ldapadd stops with your first object (I'm sure of that)

>
> > dn: cn=qmailusers,dc=mail,dc=hollybridge,dc=not
> > objectClass: top
> > objectClass: organization
> > objectClass: dcObject
> > dc: mail
> > sn: hollybridge mail users
> > cn: qmailusers
> > o: qmailusergroup

What I think about this:

What is this object? An organization object or a dcObject?

    If it's an organization,  o: qmailusergroup is an attribute required,
but the others dc: mail, sn: hollybridge mail users, cn: qmailusers can't be add.
(and you must also remove the line objectClass: dcObject, the line  objectClass: top
is optionnal).

    If it's an dcObject,  dc: mail is an attribute required,
but there is'nt optionnal attribute: the others o: qmailusergroup, , sn: hollybridge mail users, cn: qmailusers
can't be add.
(and you must also remove the line objectClass: organization, the line  objectClass: top
is optionnal).



> Look
>
> http://www-eleves.int-evry.fr/~deckmyn/docs/LDAP-ObjectClasses.html
>
> It should be helpfull:
>     "Object class violation" mean that you don't respect the structure of the object.
>      "additional info: attribute not allowed" mean that the object haven't got some
> attributes that you want to add with him.
>
>