Use reverse database MTA option

Alias and address MTA options:  (bitmask)
The  MTA  option controls whether or not the MTA makes  use of the address reversal database  and    mapping table  as a source of substitution addresses. (Note that it cannot disable use of any    setting, although its  bit 2, value 4, does affect the scope of    application.)  Its value is a decimal integer representing a bit-encoded integer, the  interpretation of which is given in the table below.

+In initial iMS 5.2 and earlier versions, the 0th and 1st bits of   not only controlled when, but also  whether a    mapping table  would be consulted at all for  address rewriting; now if a   mapping table exists, it definitely  will be consulted for address reversal (at least) subsequent  to address rewriting; (depending upon bit 1, it may also be consulted  prior to address rewriting). So this is a change from iMS 5.2 and earlier versions.

Bit 0 is the least significant bit.

The default value for  is 5, which means that in  addition to consulting any    setting to reverse  envelope  From addresses and both backwards and forwards pointing header  addresses after they have passed through the normal address rewriting  process, the MTA will also consult any reverse database or    mapping  to reverse Envelope From addresses and both backwards and  forwards pointing header addresses after they have passed through the  normal address rewriting process. Simple address strings are presented to both the   mapping and  the reverse database. Note that a value of 0 disables the use of the address reversal completely. (Note that the default of 5 represents a change from early versions of PMDF in  which this option had a default value of 1 (reverse only backwards  pointing addresses).)

Note that as of 8.0.1.3, the  source channel option can be used to override the setting of   on a channel by channel basis.

See also:
 * Alias and address MTA options
 * Database MTA options
 * Reverse database
 * REVERSE mapping table
 * reverse_url MTA Option
 * Intended side effects of LDAP address reversal
 * usereversedatabase Option