Pre-defined mapping tables

The MTA has a number of pre-defined mapping tables. These include both mapping tables whose use (and names) are "hard-coded" in the MTA code for particular sorts of uses, as well as mapping tables which, while not "hard-coded", are included and referenced as part of a standard distribution. Such mapping tables include:

 mapping table 

 mapping table 

 mapping table 

 mapping table 

 mapping   table 

 mapping table 

 mapping    table 

 mapping table 

 mapping    table </li>

 mapping table </li>

 mapping    table </li>

 mapping    table </li>

 mapping table </li>

 mapping    table </li>

 mapping    table </li>

 mapping    table </li>

 mapping    table </li>

 mapping    table </li>

 mapping    table </li>

 mapping table </li>

 mapping    table </li>

 mapping table </li>

 mapping    table </li>

 mapping    table </li>

<li> mapping    table </li>

<li> mapping table </li>

<li> mapping table </li>

<li> mapping table </li>

<li> mapping table </li>

<li> mapping    table </li>

<li> mapping table </li>

<li> mapping    table </li>

<li> mapping    table </li>

<li> mapping    table </li>

<li> mapping    table </li>

<li> mapping    table </li>

<li> mapping    table </li>

</ul>

Note that to avoid conflicts with these, or to-be-defined-in-future, Oracle-provided mapping tables, it is recommended that all site-supplied mapping tables be given names beginning with , e.g.,.

In addition to the pre-defined mapping tables listed above, the MTA has various alias options, alias file named parameters, and LDAP attributes (or rather in many cases,  MTA options for selecting the name of an LDAP attribute) used to store mapping table names, and a facility for defining Sieve tests via mapping tables with a specific form of name; mapping tables named via such an alias file parameter or LDAP attribute or special Sieve test name syntax  are used in the appropriate way by the MTA. Look for discussions of such mapping table use under topics including:

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li>  </li>

<li> The alias file named parameters ,  ,   ,  ,    ,    ,  ,  and </li>

<li>  </li>

<li>  </li>

<li> mapping tables </li>

<li> The USERNAME_MAPPING SpamAssassin option discussed in SpamAssassin  spamfilterN_config_file. </li>

</ul>

See also:
 * AUTH_ACCESS mapping table
 * AUTH_DEACCESS mapping table
 * AUTH_REWRITE mapping table
 * BURL_ACCESS mapping table
 * CHARSET-CONVERSION mapping table
 * COMMENT_STRINGS mapping table
 * CONVERSIONS mapping table
 * DEQUEUE_ACCESS mapping table
 * DISPOSITION_LANGUAGE mapping table
 * ETRN_ACCESS mapping table
 * FORWARD mapping table
 * FROM_ACCESS mapping table
 * GROUP_AUTH mapping table
 * GROUP_TEMPLATES mapping table
 * INTERNAL_IP mapping table
 * IP_ACCESS mapping table
 * Triggering effects from transaction logging with LOG_ACTION
 * MAC-TO-MIME-CONTENT-TYPES mapping table
 * Recipient access mapping tables
 * MESSAGE-SAVE-COPY mapping table
 * MILTER_ACTIONS mapping table
 * MILTER_MACROS mapping table
 * MX_ACCESS mapping table
 * NOTIFICATION_LANGUAGE mapping table
 * Recipient access mapping tables
 * Recipient access mapping tables
 * PERSONAL_NAMES mapping table
 * PORT_ACCESS mapping table
 * REVERSE mapping table
 * Recipient access mapping tables
 * SMTP_ACTIONS mapping table
 * Sieve external lists
 * SASL_ACCESS mapping table
 * SPF_LOCAL mapping table
 * TLS_ACCESS mapping table
 * alias_auth_mapping Option
 * alias_cant_mapping Option
 * alias_deferred_mapping Option
 * alias_direct_mapping Option
 * alias_hold_mapping Option
 * alias_nohold_mapping Option
 * alias_moderator_mapping Option
 * alias_sasl_auth_mapping Option
 * alias_sasl_cant_mapping Option
 * alias_sasl_moderator_mapping Option
 * Alias file named parameters
 * FILTER_test mapping tables
 * SpamAssassin spamfilterN_config_file
 * Access mapping tables
 * Mapping tables