Well, ldapbrowser doesn't accept the change if I removed the value and
leave nothing in 'mail' attribute.
Then I ran ldapmodify against an exisiting entry having the value in
'mail', that was the error return.
Here is the .ldif:
dn: uid=angiecao,ou=People,dc=example,dc=com
objectclass: posixAccount
objectclass: top
objectclass: inetOrgPerson
uid: angiecao
sn: angie cao
cn: Angie Cao
uidNumber: 88888888
homeDirectory: /home/angiecao
employeeNumber: 12345
mail:
modifying entry "uid=angiecao,ou=People,dc=example,dc=com"
ldap_modify: Invalid syntax (21)
additional info: mail: value #0 invalid per syntax
Thanks.
Angie
On Tue, Feb 10, 2009 at 6:35 AM, Hallvard B Furuseth
<[email protected]> wrote:
> Angie Cao writes:
>> Currenty the data type of 'mail' attricute in core.shema is IA5 String
>> (1.3.6.1.4.1.1466.115.121.1.26{256}), in a normal operating, it
>> accepts the empty string when the entry is firstly added, however if
>> there is a value in the 'mail' attribute and you come back and trying
>> to change it to the empty string, it'll return:
>> ldap_modify: Invalid syntax (21)
>> additional info: mail: value #0 invalid per syntax
>
> That does not make sense. My guess is that you or your client confuses
> an absent 'mail' attribute with an empty 'mail' attribute value:
>
> When it "accepts the empty string", that likely means it refrains from
> adding a mail attribute. When you try to change it to the empty string,
> it tries to store a mail attribute containting an empty string, instead
> of removing the attribute.
>
> --
> Hallvard
>
