Dequeueremoveroute, enqueueremoveroute Channel Options

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


Removing source routes (dequeueremoveroute, enqueueremoveroute)

The dequeueremoveroute channel option, when placed on a destination channel, causes source routes to be stripped from envelope recipient addresses when the channel dequeues messages (but after the channel has determined how to route the message). For instance, on a dequeueremoveroute TCP/IP channel that is not a daemon channel, the source route host is used to determine to what remote host to connect, but is stripped from the envelope To addresses before they are presented to that remote host. In particular, this channel option may be useful at sites that use the mailHost LDAP attribute (more precisely, whatever LDAP attribute is named by the ldap_mailhost MTA option) to direct messages (via source routes, @mailhost:orig-address), to NMS systems or other systems that do not support source routes; the dequeueremoveroute channel option would be placed on a special TCP/IP channel set up to send to such an NMS system. But this channel option should not be used on a general channel where source routing in addresses may need to be preserved.

The enqueueremoveroute option, when placed on a destination channel, causes source routes to be stripped from recipient addresses enqueued to that channel after the regular address rewriting has been performed. Thus the enqueueremoveroute channel option may be useful in cases where a mailHost or mailRoutingSmartHost LDAP attribute (more precisely, whatever LDAP attribute is named by the ldap_mailhost or ldap_domain_attr_smarthost MTA option) has been set for a user or domain merely in order to force a particular channel match to some special channel during rewriting, but where the host specified in such an attribute is not relevant for actual mail delivery.

The obsolete dequeue_removeroute and enqueue_removeroute options are aliases for dequeueremoveroute and enqueueremoveroute, respectively. These obsolete options are not supported in unified configuration mode.


See also: