A preserve is the same as strip except that if a
mail routing address matchis found (with ldapmra), the +detail is copied from the original
address and appended to the new address. If neither preserve nor strip is specified, the
address is looked up only with the +detail attached.
For FEATURE(ldap_routing) to work, you need to set your LDAP entries withan objectClass
of inetLocalMailRecipient. If present, there must be only one mailHost attribute, and it
must contain a fully qualified hostname as its value. If present, there must be only one
mailRoutingAddress attribute, and it must contain a legal RFC2822 address as its value. For
example:
dn: uid=alice, o=your.domain, c=US
uid: alice
objectClass: inetLocalMailRecipient
mailLocalAddress: alice@your.domain
mailRoutingAddress: alice@another.domain
This entry would cause mail destined for alice@your.domain to be delivered to the new
address alice@another.domain.
The flow of FEATURE(ldap_routing) through the parse rule set 0 looks like this:
1. Basic canonicalization (list syntax, delete local host, etc.)
2. LOCAL_RULE_0 (?§17.3.3.2 on page 596)
Table 23-17. FEATURE(ldap_routing) lookup relationships
Value of mailHost Value of mailRoutingAddress Result
Is a local host Exists Deliver to mailRoutingAddress address.
Is a local host Does not exist Deliver to original address.
Pages:
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632