Difference between revisions of "Process substitutions MTA option"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (Bulk update)
 
Line 5: Line 5:
 
== Direct LDAP attribute interpretation MTA options:  <code>process_substitutions</code> (bit-encoded integer) ==
 
== Direct LDAP attribute interpretation MTA options:  <code>process_substitutions</code> (bit-encoded integer) ==
  
New in MS 6.3.  The <code>process_substitutions</code> MTA option controls  whether to process substitution sequences in the URL values of various LDAP attributes. See  [[LDAP URL substitution sequences#table_ldap_substitutions|Table of LDAP URL substitution sequences]] for a list of substitution sequences (though only some such substitution sequences make sense and are available in the contexts discussed below). The default is 0, meaning that all such substitutions are disabled by default.  
+
New in MS 6.3.  The <code>process_substitutions</code> MTA option controls  whether to process substitution sequences in the URL values of various LDAP attributes. See  [[URL and address substitution sequences#table_url_address_substitutions|Table of LDAP URL substitution sequences]] for a list of substitution sequences (though only some such substitution sequences make sense and are available in the contexts discussed below). The default is 0, meaning that all such substitutions are disabled by default.  
  
 
{| border="1"
 
{| border="1"
Line 66: Line 66:
 
See also:
 
See also:
 
* [[Direct LDAP attribute interpretation MTA options#Direct_LDAP_attribute_interpretation_MTA_options|Direct LDAP attribute interpretation MTA options]]
 
* [[Direct LDAP attribute interpretation MTA options#Direct_LDAP_attribute_interpretation_MTA_options|Direct LDAP attribute interpretation MTA options]]
* [[LDAP URL substitution sequences#LDAP_URL_substitution_sequences|LDAP URL substitution sequences]]
+
* [[URL and address substitution sequences#URL_and_address_substitution_sequences|URL and address substitution sequences]]
 
* [[ldap_cant_url MTA option#ldap_cant_url|ldap_cant_url MTA Option]]
 
* [[ldap_cant_url MTA option#ldap_cant_url|ldap_cant_url MTA Option]]
 
* [[ldap_auth_url MTA option#ldap_auth_url|ldap_auth_url MTA Option]]
 
* [[ldap_auth_url MTA option#ldap_auth_url|ldap_auth_url MTA Option]]

Latest revision as of 15:24, 9 July 2020



Direct LDAP attribute interpretation MTA options: process_substitutions (bit-encoded integer)

New in MS 6.3. The process_substitutions MTA option controls whether to process substitution sequences in the URL values of various LDAP attributes. See Table of LDAP URL substitution sequences for a list of substitution sequences (though only some such substitution sequences make sense and are available in the contexts discussed below). The default is 0, meaning that all such substitutions are disabled by default.

process_substitutions MTA option bits
Bit Value Usage
0 1 If set, enables substitutions in mgrpDisallowedBroadcaster (ldap_cant_url)
1 2 If set, enables substitutions in mgrpAllowedBroadcaster (ldap_auth_url)
2 4 If set, enables substitutions in mgrpModerator (ldap_moderator_url)
3 8 If set, enables substitutions in mgrpDeliverTo (ldap_group_url1)
4 16 If set, enables substitutions in memberURL (ldap_group_url2)
5 32 (New in Messaging Server 7.0) If set, enables subaddress $S substitution in mgrpErrorsTo (ldap_errors_to)
6 64 (New in Messaging Server 7.0u3) If set, enables substitutions in mgrpJettisonBroadcasters (ldap_jettison_url)

Bit 0 is the least significant bit.


Note that the information source for substitution values varies depending on whether the attribute in question is used for authorization checks, or for actual list expansion. For authorization attributes, the whole address ($A), domain ($D), host ($H), and local-part ($L) are all derived from the authenticated sender address. In the case of list expansion attributes, all of these substitution values are derived from the envelope recipient address that specified the list. In both cases, however, the subaddress substitution ($S) is derived from the current envelope recipient address.

In particular, the ability to access subaddress information in list expansion URLs makes it possible and convenient to define a "meta-group"; that is, a single group entry that in effect creates an entire collection of different groups. For example, a group with attributes including:


mail: group@domain.com
mgrpDeliverTo: ldap:///o=usergroup?mail?sub?(department=$S)

would make it possible to send mail to every member of a given department with an address of the form


group+department@domain.com

Note that creation and use of such a "meta-group" does not require the use of subaddresses (though subaddresses are often a convenient syntax for such a purpose). Other mechanisms, such as other forms of "special" addresses transformed via a FORWARD mapping table or ldap_url_result_mapping attribute's value mapping table, could be used instead to provide "meta-group" functionality. Note that process_substitutions effects, if any, occur after the ldap_url_result_mapping table, if any, has been applied.


See also: