Uh, no, that's not what Michael meant. The problem is that the objectclass list for the entry you're trying to add doesn't include any class that allows a 'mailHost' attribute. His suggestion was that you need:
... objectClass: inetLocalMailRecipient mailHost: asia.example.com would work. ... Remember that in LDAP, an entry can have any number of (auxiliary) object classes - but the ones it has determines what attributes it may have values for. Hope this helps -- -- ReC ________________________________ From: David Damon [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2007 4:01 PM To: [email protected] Subject: [ldap] Re: IA5 string Michael, Thank you for answering so quickly. Well this is what I've tried in my ldif file so far. ......... mailHost: asia.example.com --| mailRoutingAddress: [EMAIL PROTECTED] --|----> and got Error: Object class violation (65), additional info: attribute 'mailHost' not allowed tried .......... mailRoutingAddress: [EMAIL PROTECTED] -------> and got Error: Object class violation (65), additional info: attribute 'mailRoutingAddress' not allowed just tried ......... mailHost: asia.example.com ----| mailRoutingAddress: [EMAIL PROTECTED] ----|------> and got Error: Undefined attribute type (17), additional info: | inetLocalMailRecipient: attribute type undefined inetLocalMailRecipient: [EMAIL PROTECTED] ----| I know that "asia.example.com" and "[EMAIL PROTECTED]" are both IA5 syntax compliant. I also know that "mailHost", "mailRoutingAddress", and "inetLocalMailRecipient" are all defined in misc.schema. I know that error 65 means an empty value or a value for an attribute which the class definition does not contain. I know that error 17 means the attribute doesn't exist. Is "mailHost" and "mailRoutingAddress" looking for values other than "asia.example.com" and "[EMAIL PROTECTED]" This is the misc.schema that I am including in my slapd.conf file. attributetype ( 2.16.840.1.113730.3.1.13 NAME 'mailLocalAddress' DESC 'RFC822 email address of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} ) attributetype ( 2.16.840.1.113730.3.1.18 NAME 'mailHost' DESC 'FQDN of the SMTP/MTA of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} SINGLE-VALUE ) attributetype ( 2.16.840.1.113730.3.1.47 NAME 'mailRoutingAddress' DESC 'RFC822 routing address of this recipient' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} SINGLE-VALUE ) # I-D leaves this OID TBD. # iPlanet uses 2.16.840.1.113.730.3.2.147 but that is an # improperly delegated OID. A typo is likely. objectclass ( 2.16.840.1.113730.3.2.147 NAME 'inetLocalMailRecipient' DESC 'Internet local mail recipient' SUP top AUXILIARY MAY ( mailLocalAddress $ mailHost $ mailRoutingAddress ) ) Regards, David Damon Senior Systems Integration Analyst Michael Ströder <[EMAIL PROTECTED]> 01/26/2007 03:10 PM To David Damon <[EMAIL PROTECTED]> cc [email protected] Subject [ldap] Re: IA5 string David Damon wrote: > > What is an IA5 string? It's a LDAP syntax. Mainly but not exactly for ASCII chars. > "Error: Object class violation (65), additional info: > attribute 'mailHost' not allowed" This has nothing to do with the syntax. It clearly states that the none of the object classes chosen for this entry allow the attribute 'mailHost'. Wild guess: You might wanna add the object class 'inetLocalMailRecipient' to the entry. Ciao, Michael. --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message. --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message. --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
