Route_to_routing_host MTA option

From Messaging Server Technical Reference Wiki
Jump to: navigation, search

Direct LDAP attribute interpretation MTA options: route_to_routing_host (-1, 0 or 1)

When a domain entry includes the attribute named by the ldap_domain_attr_routing_hosts MTA option, (by default, the mailRoutingHosts attribute), this attribute's values are compared against the MTA's own local host name and host aliases ldap_local_host and ldap_host_alias_list values) to determine whether the domain is "owned" (or "local") to this particular MTA. "Local" addresses are of course further processed by the MTA.

The route_to_routing_host MTA option controls what the MTA does with addresses determined in this way to be non-local; that is, what the MTA does with addresses which, while having a local (known) domain in the directory, are marked as having some other authoritative mail host. When the route_to_routing_host MTA option is set to 0 (the default), such addresses are handled as specified by whatever rewrite rules apply to the address. (This was the only behavior available with iMS 5.2.) When this option is instead set to 1, then such addresses are instead routed to the first host listed in the mailRoutingHosts attribute.

New in, a setting of -1, in addition to disabling routing of addresses with nonlocal mailhosts to the mail routing host, acceptance of addresses without a user entry and routing them to the mailRoutingSmartHost defined for the corresponding domain is also disabled. The smart host for the domain will continue to be used for addresses that match user entries that fail to specify a mailhost.

See also: