If you added your schema definitions, 'mailUserStatus' should be present in the schema. You may search the attribute on suffix 'cn=schema' with 'attributetypes' and 'objectclasses' attributes to confirm they are available. If a definition can not be loaded you will find a error message in error log.
objectclasses: ( 2.16.840.1.113730.3.2.146 NAME 'inetMailUser' DESC 'auxiliary
class for a messaging server user' SUP top AUXILIARY MAY ( mailDeliveryOptio
n $ mailForwardingAddress $ mailAlternateAddress $ mail $ mailUserStatus $ ma
ilAllowedServiceAccess ) X-ORIGIN 'Sun ONE Messaging Server' X-SCHEMA-FILE '9
5-mail.ldif' )
The above message means that added/updated entry has not the objectclass allowing 'mailUserStatus'. Looking in access logs for err=65 you will identify what is the target entry.
[02/Dec/2025:09:31:09.233659798 -0600] conn=62436 op=13 RESULT err=65 tag=105 nentries=0 wtime=0.000191603 optime=0.005365186 etime=0.005553484 - attribute "mailUserStatus" not allowed
Thanks,
John A
No comments:
Post a Comment