9.1.3.2 Entry Status Checks

Next the entry's status is checked. There are two status attributes,
one for the entry in general and another specifically for mail service.

Table 9–2 shows the general
and mail-specific user or group attributes in the schema tag entry to check
against depending on what schema tag are in effect

Table 9–2 Attributes to Check Against

schematag

Type

General

Mail-specific

sims40

users

inetsubscriberstatus

mailuserstatus

sims40

groups

none

inetmailgroupstatus

nms41

users

none

mailuserstatus

nms41

groups

none

none

Messaging Server 5.0

users

inetuserstatus

mailuserstatus

Messaging Server 5.0

groups

none

inetmailgroupstatus

If necessary the LDAP_USER_STATUS and LDAP_GROUP_STATUS MTA options in the option.dat file can be used
to select alternate general status attributes for users and groups respectively.
The mail-specific user and group status attributes are controlled by the LDAP_USER_MAIL_STATUS and LDAP_GROUP_MAIL_STATUS MTA
options.

Another factor that plays into this are the statuses for the domain
itself (LDAP_DOMAIN_ATTR_STATUS and LDAP_DOMAIN_ATTR_MAIL_STATUS). All in all there are four status attributes. They are combined
by considering them in the following order:

Domain status

Domain mail status

User or group status

Mail user or group status

The first of these that specifies something other than “active”
takes precedence over all the others. The other permissible status values
are “inactive,” “deleted,” “removed,” “disabled,” “hold,”
and “overquota.” “Hold,” “disabled,” and “removed”
statuses may only be specified for mail domains, mail users, or mail groups. “Overquota”
status can only be specified as a mail domain or mail user status.

All statuses default to “active” if a particular status
attribute is not present. Unknown status values are interpreted as “inactive.”

When the four statuses are combined, the following statuses for a user
or group are possible: “active,” “inactive,” “deleted,” “removed,” “disabled,” “hold,”
and “overquota.” Active status causes alias processing to continue.
Inactive or overquota status results in immediate rejection of the address
with a 4xx (temporary) error. Deleted, removed, and disabled statuses results
in immediate rejection of the address with a 5xx (permanent) error. Hold status
is treated as active as far as status handling is concerned but it sets an
internal flag so that when delivery options are considered later on, any options
that are there are overridden with an option list containing a single “hold”
entry.