Ldap user object classes MTA option

Direct LDAP schema MTA options:  (list of plus-separated list of objectclass names)
The  MTA option specifies the object classes required to be present in a  user entry.

The default depends upon the schema tag (see the    MTA option). For a schema tag value of , the default for the    option  is. For a schema tag value of , the default for this option is. For a schema tag value of , the default for this option is.

Note that the   LDAP URL  substitution sequence uses these object classes. For instance, when ,  then   results in substituting (&#x7c;(&(objectClass=inetLocalMailRecipient)(objectClass=inetMailUser))) Or if  is set to   inetLocalMailRecipient+inetMailUser,inetMailRouting+inetMailUser then  results in  (&#x7c;(&(objectClass=inetLocalMailRecipient)(objectClass=inetMailUser))         (&(objectClass=inetMailRouting)(objectClass=inetMailUser))) For purposes of authentication (e.g., user IMAP or POP logins, or SMTP AUTH authentication), the definition of valid user  objectClass(es) is implicit in the setting of the    auth option (or in legacy configuration, the   configutil parameter), which  has default value (&(uid=%U)(objectclass=inetmailuser)) hence implicitly includes a schema assumption, and in particular an assumption about what are valid user objectClass(es). If using a non-default schema, this configutil parameter may need to be changed to  cause user lookups (for authentication purposes) to look for  objectclass(es) used in the other schema (e.g., the NMS 4.1  schema).

See also:
 * Direct LDAP schema MTA options
 * Direct LDAP usergroup lookup MTA options
 * ldap_group_object_classes MTA Option
 * ldap_schematag MTA Option
 * LDAP URL substitution sequences
 * searchfilter Option