Difference between revisions of "Conversion tags"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (Bulk update)
 
Line 7: Line 7:
  
 
Conversion tags may be added via channel options,  ([[destinationconversiontag,  sourceconversiontag channel options#destinationconversiontag|<code>sourceconversiontag</code>,  <code>destinationconversiontag</code>]], [[deliveryflags, flagtransfer, noflagtransfer Channel Options#deliveryflags|<code>deliveryflags</code>]]), via LDAP attributes ([[ldap_source_conversion_tag MTA option#ldap_source_conversion_tag|<code>ldap_source_conversion_tag</code>]], [[ldap_conversion_tag MTA option#ldap_conversion_tag|<code>ldap_conversion_tag</code>]], [[ldap_domain_attr_source_conversion_tag MTA options#ldap_domain_attr_source_conversion_tag|<code>ldap_domain_attr_source_conversion_tag</code>]],  [[ldap_domain_attr_conversion_tag MTA options#ldap_domain_attr_conversion_tag|<code>ldap_domain_attr_conversion_tag</code>]]),  via an alias option ([[alias_conversion_tag alias option#alias_conversion_tag|<code>alias_conversion_tag</code>]]) or  [[Alias file named parameters#Alias_file_named_parameters|&#x5b;CONVERSION_TAG&#x5d; alias file named parameter]], via  [[Recipient access mapping tables#Recipient_access_mapping_tables|recipient access mapping tables]]  or the  [[FROM_ACCESS mapping table#FROM_ACCESS_mapping_table|<code>FROM_ACCESS</code> mapping table]],  or via the  [[Sieve conversiontag extensions#Sieve_conversiontag_extensions|Sieve conversiontag extensions]]. Conversion tags present on a message may influence certain mapping table operations  ([[CONVERSIONS mapping table#CONVERSIONS_mapping_table|<code>CONVERSIONS</code> mapping table]],  [[CHARSET-CONVERSION mapping table#CHARSET-CONVERSION_mapping_table|<code>CHARSET-CONVERSION</code>  mapping table]],  [[MESSAGE-SAVE-COPY mapping table format and examples#MESSAGE-SAVE-COPY_mapping_table_format_and_examples|<code>MESSAGE-SAVE-COPY</code> mapping table]] when selected via [[message_save_copy_flags MTA option#message_save_copy_flags|<code>message_save_copy_flags</code>]],  as well as various address mapping tables as controlled by the [[include_conversiontag MTA option#include_conversiontag|<code>include_conversiontag</code>]] MTA option),  and control matching and hence application of specific conversions entries. Complex effects due to, and manipulations of, conversion tags are also possible via [[Sieve conversiontag extensions#Sieve_conversiontag_extensions|Sieve conversiontag extensions]].  
 
Conversion tags may be added via channel options,  ([[destinationconversiontag,  sourceconversiontag channel options#destinationconversiontag|<code>sourceconversiontag</code>,  <code>destinationconversiontag</code>]], [[deliveryflags, flagtransfer, noflagtransfer Channel Options#deliveryflags|<code>deliveryflags</code>]]), via LDAP attributes ([[ldap_source_conversion_tag MTA option#ldap_source_conversion_tag|<code>ldap_source_conversion_tag</code>]], [[ldap_conversion_tag MTA option#ldap_conversion_tag|<code>ldap_conversion_tag</code>]], [[ldap_domain_attr_source_conversion_tag MTA options#ldap_domain_attr_source_conversion_tag|<code>ldap_domain_attr_source_conversion_tag</code>]],  [[ldap_domain_attr_conversion_tag MTA options#ldap_domain_attr_conversion_tag|<code>ldap_domain_attr_conversion_tag</code>]]),  via an alias option ([[alias_conversion_tag alias option#alias_conversion_tag|<code>alias_conversion_tag</code>]]) or  [[Alias file named parameters#Alias_file_named_parameters|&#x5b;CONVERSION_TAG&#x5d; alias file named parameter]], via  [[Recipient access mapping tables#Recipient_access_mapping_tables|recipient access mapping tables]]  or the  [[FROM_ACCESS mapping table#FROM_ACCESS_mapping_table|<code>FROM_ACCESS</code> mapping table]],  or via the  [[Sieve conversiontag extensions#Sieve_conversiontag_extensions|Sieve conversiontag extensions]]. Conversion tags present on a message may influence certain mapping table operations  ([[CONVERSIONS mapping table#CONVERSIONS_mapping_table|<code>CONVERSIONS</code> mapping table]],  [[CHARSET-CONVERSION mapping table#CHARSET-CONVERSION_mapping_table|<code>CHARSET-CONVERSION</code>  mapping table]],  [[MESSAGE-SAVE-COPY mapping table format and examples#MESSAGE-SAVE-COPY_mapping_table_format_and_examples|<code>MESSAGE-SAVE-COPY</code> mapping table]] when selected via [[message_save_copy_flags MTA option#message_save_copy_flags|<code>message_save_copy_flags</code>]],  as well as various address mapping tables as controlled by the [[include_conversiontag MTA option#include_conversiontag|<code>include_conversiontag</code>]] MTA option),  and control matching and hence application of specific conversions entries. Complex effects due to, and manipulations of, conversion tags are also possible via [[Sieve conversiontag extensions#Sieve_conversiontag_extensions|Sieve conversiontag extensions]].  
 +
 +
Conversion tags are normally subject to duplicate elimination and are compared in a case-insensitive fashion. This can be adjusted using the [[conversion_tag_case MTA option#conversion_tag_case|<code>conversion_tag_case</code>]] MTA option.
  
  
 
See also:
 
See also:
 
* [[include_conversiontag MTA option#include_conversiontag|include_conversiontag MTA Option]]
 
* [[include_conversiontag MTA option#include_conversiontag|include_conversiontag MTA Option]]
 +
* [[conversion_tag_case MTA option#conversion_tag_case|conversion_tag_case MTA Option]]
 
* [[destinationconversiontag,  sourceconversiontag channel options#destinationconversiontag|destinationconversiontag Option]]
 
* [[destinationconversiontag,  sourceconversiontag channel options#destinationconversiontag|destinationconversiontag Option]]
 
* [[destinationconversiontag,  sourceconversiontag channel options#sourceconversiontag|sourceconversiontag Option]]
 
* [[destinationconversiontag,  sourceconversiontag channel options#sourceconversiontag|sourceconversiontag Option]]

Latest revision as of 02:47, 27 July 2020


The MTA has a private mechanism of conversion tags. Conversion tags may be set and used in a variety of ways and for a variety of purposes; besides the original use for triggering user-specific automatic documention conversion, another common use is for causing or influencing special routing of messages.

Note that conversion tags are stored in a private-to-the-MTA field in the message envelope; they are not visible in received messages. (However, message conversion tags present on messages transitting the MTA will be included in MTA message transaction log entries if the log_conversion_tag MTA option is enabled.)

Conversion tags may be added via channel options, (sourceconversiontag, destinationconversiontag, deliveryflags), via LDAP attributes (ldap_source_conversion_tag, ldap_conversion_tag, ldap_domain_attr_source_conversion_tag, ldap_domain_attr_conversion_tag), via an alias option (alias_conversion_tag) or [CONVERSION_TAG] alias file named parameter, via recipient access mapping tables or the FROM_ACCESS mapping table, or via the Sieve conversiontag extensions. Conversion tags present on a message may influence certain mapping table operations (CONVERSIONS mapping table, CHARSET-CONVERSION mapping table, MESSAGE-SAVE-COPY mapping table when selected via message_save_copy_flags, as well as various address mapping tables as controlled by the include_conversiontag MTA option), and control matching and hence application of specific conversions entries. Complex effects due to, and manipulations of, conversion tags are also possible via Sieve conversiontag extensions.

Conversion tags are normally subject to duplicate elimination and are compared in a case-insensitive fashion. This can be adjusted using the conversion_tag_case MTA option.


See also: