Difference between revisions of "Include conversiontag MTA option"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (Bulk update)
 
Line 112: Line 112:
 
* [[ldap_domain_attr_catchall_mapping MTA options#ldap_domain_attr_catchall_mapping|ldap_domain_attr_catchall_mapping MTA Option]]
 
* [[ldap_domain_attr_catchall_mapping MTA options#ldap_domain_attr_catchall_mapping|ldap_domain_attr_catchall_mapping MTA Option]]
 
* [[ldap_spare_N MTA options#ldap_spare_1|ldap_spare_1 MTA Option]]
 
* [[ldap_spare_N MTA options#ldap_spare_1|ldap_spare_1 MTA Option]]
 +
* [[conversion_tag_case MTA option#conversion_tag_case|conversion_tag_case MTA Option]]
 
* [[Conversion tags#Conversion_tags|Conversion tags]]
 
* [[Conversion tags#Conversion_tags|Conversion tags]]
 
[[Category: MTA]]
 
[[Category: MTA]]
 
[[Category: Reference]]
 
[[Category: Reference]]

Latest revision as of 01:49, 27 July 2020



Access mapping table MTA options: include_conversiontag (bitmask)

New in MS 6.3. This option selectively enables the inclusion of conversion tag information in various mapping table probes. When enabled, the current set of conversion tags will appear in the relevant mapping table probe as a comma separated list. The option takes a bit-encoded integer value. The following bits are defined:

include_conversiontag MTA option bit values
Bit Value Usage
0 1 CHARSET-CONVERSION : include as a ;TAG=comma-separated-values field before ;CONVERT
1 2 CONVERSIONS : include as a ;TAG=comma-separated-values field before ;CONVERT
2 4 FORWARD : include just after any authenticated sender and to any ldap_spare_* fields (with a vertical bar, |, delimiter)
3 8 ORIG_SEND_ACCESS : include as a final (barring any ldap_spare_* fields) field; that is, include after the optional access count field and prior to any ldap_spare_* fields (with a vertical bar, |, delimiter)
4 16 SEND_ACCESS : include as a final (barring any ldap_spare_* fields) field; that is, include as a field after the optional access count field and prior to any ldap_spare_* fields (with a vertical bar, |, delimiter)
5 32 ORIG_MAIL_ACCESS : include as a final (barring any ldap_spare_* fields) field; that is, include as a field after the optional access count field and prior to any ldap_spare_* fields (with a vertical bar, |, delimiter)
6 64 MAIL_ACCESS : include as a final (barring any ldap_spare_* fields) field; that is, include as a field after the optional access count field and prior to any ldap_spare_* fields (with a vertical bar, |, delimiter)
7 128 FROM_ACCESS : (New in 7.0-3.01? post MS 6.3) include as a final (barring any ldap_spare_* fields) field; that is, include as a field after the optional access count field and prior to any ldap_spare_* fields (with a vertical bar, |, delimiter)
8 256 REVERSE : (New in 7.0.5) include as a field after any source or destination channel fields, but before the actual address in the probe (with a vertical bar, |, delimiter). Note that only the "final" REVERSE mapping table probe, used to (possibly) modify addresses as a message is being enqueued, includes the conversion tags; earlier probes, such as for (possibly) modifying the envelope From for *_ACCESS mapping table probe purposes, or for (possibly) setting an "override" postmaster address do not include conversion tags regardless of the setting of this bit of include_conversiontag.
9 512 PERSONAL_NAMES : (New in 8.0) include as a field after any source or destination channel fields, but before any addresses in the probe (with a vertical bar, |, delimiter).
10 1024 Domain catchall mappings: (New in 8.0) include as a field after any authenticated sender address, but before any MT-PRIORITY and recipient address in the probe (with a vertical bar, |, delimiter).
11 2048 AUTH_ACCESS mapping: (New in 8.0.2.2) include as a field after the username, but before the destination system in the probe (with a vertical bar, |, delimiter).
12 4096 DEQUEUE_ACCESS mapping: (New in 8.0.2.3) include as a field after the auth-sender, but before the priority in the probe (with a vertical bar, |, delimiter).
13 8192 AUTH_REWRITE mapping: (New in 8.1.0.1) include as a field after the auth-param, but before any extra header fields in the probe (with a vertical bar, |, delimiter).
14 16384 (New in 8.1.0.1) Include the global conversion tag list as an X-Tags: field in the first section of the second part of any DSNs that are generated. Note that this may expose internal information and is only intended for use when all DSNs are processed internally.
15 32768 (New in 8.1.0.1) Include the global conversion tag list in any SMTP_ACTIONS mapping probe.
16 65536 (New in 8.1.0.1) Include the global conversion tag list in any MX_ACCESS mapping probe.

Bit 0 is the least significant bit.

The default is 0, meaning that conversion tag values are not included in any mapping table probes.


See also: