Extra concerns for address canonicalization

Proper address canonicalization (converting any "internal" address forms to canonicalized, appropriate-for-external-use, forms) is, nowadays, typically part of proper domain provisioning in LDAP, in particular proper use of LDAP domain attributes such as (in Schema 1)   and    and   (or more precisely, those LDAP domain attributes named by the   and   MTA options) or (in Schema 2)   and     (or more precisely, those LDAP domain attributes named by the   and   MTA options) and proper user provisioning in LDAP, in  particular proper use of ,  , and   LDAP attributes (or more precisely, those LDAP user attributes named by the  ,  , and    MTA options). However, there are a few additional configuration items that may be of interest.



 Put the  keyword on (at least) your channels    outgoing to the external world so that address rewriting will be    applied to address in embedded message parts (message/rfc822 parts). 

 If you do not wish notification messages generated by MTA systems the internal address, then you may wish to    use the     channel option. 



See also:
 * ldap_domain_attr_canonical MTA Option
 * ldap_domain_attr_alias Option
 * ldap_attr_domain1_schema2 MTA Option
 * ldap_attr_domain2_schema2 MTA Option
 * ldap_primary_address MTA Option
 * ldap_alias_addresses MTA Option
 * ldap_equivalence_addresses MTA Option
 * inner Option
 * suppressfinal Option
 * Restricting information emitted