Ldap_user_mail_status MTA option

From Messaging Server Technical Reference Wiki
Jump to: navigation, search



Direct LDAP attribute name MTA options: ldap_user_mail_status (LDAP attribute name)

The ldap_user_mail_status MTA option specifies the name of a user LDAP attribute, by default mailUserStatus, used to store the user's status for mail purposes. (Contrast with the ldap_user_status MTA option which names an LDAP attribute, by default inetUserStatus, used to store the user's general status for services in addition to mail. And consider also the ldap_domain_attr_mail_status MTA option which names an analogous domain LDAP attribute.)

For the LDAP attribute named by ldap_user_mail_status, valid values are active, inactive, disabled, deleted, overquota, hold, removed (new in MS 6.0), defer (new in MS 6.3), defer-submit (new in MS 6.3), deliver (new in 7.3-11.01), and deliver-disabled (new in 8.0.1.3/8.0.2.1).

A status of removed is equivalent to deleted from the MTA's point of view; it exists as a distinct status for the benefit of the commcli user purging operation.

The statuses defer and defer-submit tell the MTA to accept all messages to the user but defer them to the reprocess channel for later delivery (re)attempts; or in the case of defer-submit accept and defer to the reprocess channel those messages coming in a submit channel while giving inactive behavior, hence normally temporary errors, for attempted submissions on any other channels.

A status of deliver is treated by the MTA as active active for purposes of message delivery but which other components will treat as inactive (giving the effect that messages can be delivered, but the user can not login); any other value is treated as inactive.

(Note that the acceptalladdresses channel option, if used, modifies the timing and form of recipient rejections due to errors such as "overquota" or "disabled" status. New in MS 8.0.1.1.0, the accepttemporaryfailures channel option, if used, modifies the timing and form of recipient deferrals due to temporary errors such as "inactive" status. Note also that the use_temporary_error and use_permanent_error MTA options, and usetemporaryerror and usepermanenterror channel options, can alter the interpretation of whether such status errors are considered temporary vs. permanent errors.)


See also: