Difference between revisions of "Domain uplevel MTA option"

From Messaging Server Technical Reference Wiki
Jump to: navigation, search
m (Bulk update)
m (Bulk update)
 
Line 37: Line 37:
 
| |        5     
 
| |        5     
 
| |        32     
 
| |        32     
| |  New in 6.2-0.04.  Check the "canonical" form the address, that is, the address with the  domain part replaced by the canonical domain, against the  [[ldap_primary_address MTA option#ldap_primary_address|<tt>mail</tt>  attribute]], and disable address reversal if it matches.     
+
| |  New in 6.2-0.04.  Check the "canonical" form of the address, that is, the address with the  domain part replaced by the canonical domain, against the  [[ldap_primary_address MTA option#ldap_primary_address|<tt>mail</tt>  attribute]], and disable address reversal if it matches.   
 +
|- style="background:blanchedalmond"
 +
| |        6   
 +
| |        64   
 +
| |  New in 8.1.0.6.  Bits 3 (value 8) and 5 (value 32) include any subaddress that&#x27;s present in  the comparison. Setting this bit causes an additional check to be made  against the form of the address without the subaddress.     
 
|}
 
|}
 
----
 
----

Latest revision as of 01:49, 27 July 2020



Subdomain handling in domain lookups (domain_uplevel)

The domain_uplevel MTA option affects how domain names are searched for and used in direct LDAP mode. The option takes a bit-encoded integer argument, where each bit controls a particular aspect of domain name searching/usage; see below. The default value is 0.

domain_uplevel option bit values
Bit Value Usage
0 1 When set, domain map searches, such as the $V search in the typical configuration's $* rewrite rule, iterate with successive initial portions of the domain name stripped off until a match is found (or the domain name is exhausted). That is, with this bit set then a domain entry in the DC tree implicitly causes all subdomains of that domain to also "match" for purposes of domain lookups.
1 2 When set, searches on user addresses also look for the user address with the original domain name replaced by the domain name found during the domain map process (the "canonical" domain name). In particular, this can be useful either when bit 0 (value 1) is set (subdomains implicitly present due to the presence of a domain in the DC tree), or when aliased domains are in use.
2 4 Controls whether the domain name found during the domain map process (the "canonical" domain name) is compared with the configutil parameter service.defaultdomain (which can be overridden by the ldap_default_domain MTA option) when deciding whether an entry is in a hosted domain.
3 8 New in 6.1-0.01. Check the "canonical" form of the address, that is, the address with the domain part replaced by the canonical domain, against any mailEquivalentAddress attributes, and disable address reversal if any match occurs. This bit and bit 5 (value 32) are useful in preventing unwanted address rewriting when canonical domains are in use.
4 16 New in 6.3-0.15. For address reversal purposes, do not reverse unless the address (original or possibly the original with domain replaced by the "canonical" domain) matches a mailAlternateAddress value. In particular, this allows mail domain aliases to effectively cause all users to implicitly have a mailEquivalentAddress value using the domain alias as the domain name.
5 32 New in 6.2-0.04. Check the "canonical" form of the address, that is, the address with the domain part replaced by the canonical domain, against the mail attribute, and disable address reversal if it matches.
6 64 New in 8.1.0.6. Bits 3 (value 8) and 5 (value 32) include any subaddress that's present in the comparison. Setting this bit causes an additional check to be made against the form of the address without the subaddress.

Bit 0 is the least significant bit.

See also the ldap_domain_attr_uplevel MTA option for specifying the name of a domain-level LDAP attribute which allows some domain-level override of the MTA-wide setting of domain_uplevel.


See also: