On 5/22/19 6:02 PM, Quanah Gibson-Mount wrote:
--On Wednesday, May 22, 2019 12:51 PM -0400 Christopher Wood
Adding the custom schema went fine apart from the replication issue:
dn: cn=schema,cn=config changetype: modify add: olcAttributeTypes olcAttributeTypes: ( 1.3.6.1.4.1.4203.666.1.200 NAME 'mailacceptinggeneralid' DESC 'Postfix mail local address alias attribute' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ) olcAttributeTypes: ( 1.3.6.1.4.1.4203.666.1.201 NAME 'maildrop' DESC 'Postfix mail final destination attribute' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ) - add: olcObjectClasses olcObjectClasses: ( 1.3.6.1.4.1.4203.666.1.100 NAME 'postfixUser' DESC 'Postfix mail user class' SUP top AUXILIARY MAY ( mailacceptinggeneralid $ maildrop ))
You did this wrong. You shouldn't be appending it to cn=schema, which is internal. You need to add it as its own schema object. I suggest looking at other schema objects such as inetOrgPerson, etc.
The 2nd thing which is asking for trouble is hijacking the OID space 1.3.6.1.4.1.4203.666 which will sooner or later clash with schema or other extensions defined by OpenLDAP project (the owner of the OID tree 1.3.6.1.4.1.4203).
Ciao, Michael.