MAILSERV list subscription LDAP attribute name MTA options

RESTRICTED. MAILSERV is not yet fully implemented.

By default, the MTA assumes a particular sort of LDAP schema will be used with MAILSERV; in particular, the MTA assumes that certain named attributes (with certain sorts of meanings) are available and used in the LDAP directory to store MAILSERV user data, and MAILSERV list subscription data. However, the exact attribute names that the MTA looks for (recognizes) are configurable via the various    and    MTA options. Thus a different (though semantically compatible) schema may be used by setting the  and   MTA options   to tell the MTA what named attributes to use (recognize).

Note that throughout MAILSERV discussions, for convenience often LDAP attributes will be referred to merely by name. But in general, any such MAILSERV reference to a specific LDAP attribute name really ought to be a reference to the attribute named by the corresponding MTA option. For instance, any use by MAILSERV of the  LDAP attribute is really a use of the attribute named by the   MTA option.

See also:
 * ldap_mlsub_object_class MTA Option
 * ldap_mlsub_list_id MTA Option
 * ldap_mlsub_mail MTA Option
 * ldap_mlsub_role MTA Option
 * ldap_mlsub_digest MTA Option
 * ldap_mlsub_receive_mail MTA Option
 * ldap_mlsub_suppress_duplicates MTA Option
 * ldap_mlsub_join_date MTA Option
 * ldap_mlsub_join_ip MTA Option
 * ldap_mlsub_tentative_email MTA Option
 * ldap_mlsub_track MTA Option
 * ldap_mlsub_action_key MTA Option
 * MAILSERV user LDAP attribute name MTA options
 * MAILSERV MTA options
 * MTA options