On 12/2/25 5:39 PM, Johnnie Adams wrote:
On Tue, Dec 2, 2025 at 10:16 AM Thierry Bordaz via 389-users
<[email protected]> wrote:
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.
I don't find an error; I do find a listing when I search:
Good so the all definitions were valid
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.
I didn't find the access log entry terribly informative:
doing 'grep "conn=62436 op=13 " /var/lib/dirsrv/slapd-instance/access'
will give the target entry, then you can look if this entry is missing
or not 'objectclass: inetMailUser'
[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
--
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
