Include spares1 MTA option

Access mapping table MTA options:  (bitmask)
(New in Messaging Server 7u2, renamed from  to   in MS 8.0.2.2.) LDAP attribute values associated with originator or  recipient address processing may be included in    or the  various  recipient address access mapping  probes, respectively. This is all controlled by the   MTA option. This option is bit-encoded, with the bits defined as follows:

Bit 0 is the least significant bit.

The default is 0, meaning that no LDAP spare attribute values are included in the   mapping table probes. If inclusion of any spare attribute values is enabled, those spare attribute values are  suffixed to the probe after the optional (see   )  conversion tag value(s). Any spare attribute values enabled are suffixed in order (first a vertical bar and    if enabled,  then a vertical bar and    if enabled,  etc.).

Note that spare attribute slots can be assigned to point to attributes already used for other purposes by the MTA. That is, via this mechanism, the   mapping tables can in fact be sensitive to the  value of any attribute available to the MTA during the relevant mapping  table probe: just about any recipient or sender attribute likely to be  of interest could be made available to the mapping probe.

See also:
 * Access mapping table MTA options
 * ldap_spare_1 MTA Option
 * ldap_spare_2 MTA Option
 * ldap_spare_3 MTA Option
 * ldap_spare_4 MTA Option
 * ldap_spare_5 MTA Option
 * ldap_spare_6 MTA Option
 * include_spares2 MTA Option
 * include_conversiontag MTA Option
 * Recipient access mapping tables
 * FROM_ACCESS mapping table