Use personal names MTA option

Miscellaneous mapping table MTA options:  (bitmask)
(New in MS 6.1.) The  MTA  option takes a bit encoded integer argument. If bit 0 (value 1) of this option is set, then the familiar source-channel&#x7c;destination-channel&#x7c; prefix will be included in    mapping table probes. See the  and   channel options, and  RFC 822 comments strings and personal name modification  for more discussion of the    mapping table.

Setting bit 1 (value 2) causes the inclusion of the name of the header field the address being processed came from in the mapping probe, immediately after source channel, destination channel, and conversion flag information. A trailing colon is always included in the field name.

If bit 2 (value 4) is set any personal name generated during address reverse will not be used by default. Instead the revised name will be added to the  mapping probe immediately following the original personal name associated with the address. If the mapping wishes to use the revised name all it needs to do is return that name and set $Y.

See also:
 * Miscellaneous mapping table MTA options
 * PERSONAL_NAMES mapping table
 * personalmap Option
 * sourcepersonalmap Option