Personalinc, personalmap, personalomit, personalstrip, sourcepersonalinc, sourcepersonalmap, sourcepersonalomit, sourcepersonalstrip Channel Options

Personal names in address message headers
The MTA only interprets the contents of header lines when necessary. However, all registered headers containing addresses must be parsed in order to rewrite and eliminate shortform addresses and otherwise convert them to legal addresses. During this process personal names (strings preceding angle-bracket-delimited addresses) are extracted and may optionally be modified or excluded when the header line is rebuilt.

On destination channels, this behavior is controlled by the use of the,  ,  , and   channel options. tells the MTA to retain personal names in the headers. It is the default. tells the MTA to apply the PERSONAL_NAMES mapping table to personal names appearing in addressing header lines if such a mapping table exists, while if no such mapping table exists then  is equivalent to. tells the MTA to remove all personal names. And finally,  tells the MTA to strip any  nonatomic characters from all personal name fields.

On source channels, this behavior is controlled by the use of a,  ,  , or   channel option. tells the MTA to retain personal names in the headers. It is the default. tells the MTA to apply the  mapping table to personal names appearing in addressing header lines if such a mapping table exists, while if no such mapping table exists then   is equivalent to. tells the MTA to remove all personal names. And finally,  tells the MTA to strip any nonatomic characters from all personal name fields.

These options can be applied to any channel.

See also:
 * use_personal_names MTA Option
 * PERSONAL_NAMES mapping table
 * Headers channel options
 * Channel options