Instead, they will be delivered as is. If you want to bounce those
failed lookups, you can add a third argument to the preceding declaration:
FEATURE(`ldap_routing??, `newldapmh??, ` newldapmra??, `bounce??)
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
23.7 Alphabetized Database-Map Types | 923
If the third argument is present and is neither an empty string nor the string passthru,
failed lookups will bounce. To make your meaning clear, we recommend you restrict your
choices to the two literal words bounce or passthru. Table 23-17 shows the relationship
between the two database maps and the lack or presence of a bounce. Beginning with
V8.13, two additional arguments are allowed (discussed shortly).
Beginning withV8.13, a new literal word, sendertoo, may be used in place of either bounce
or passthru. When you specify sendertoo, you cause the envelope sender to also be rejected
if that address is not found in LDAP. Thus, sendertoo acts as if bounce was also specified
(that is, both not-found recipients and senders will be rejected).
If you wishto define how +detail addresses (?§12.4.4 on page 476) are handled, you can do
so by adding a fourthargument to FEATURE(ldap_routing). That fourth argument must be
either a literal strip or a literal preserve:
FEATURE(`ldap_routing??, `newldapmh??, ` newldapmra??, `bounce??, `strip??)
If an address contains a +detail (suchas george+nospam), strip causes the address to first
be looked up withth e +detail attached, and if no match is found, strip removes the
+detail and looks up the address again.
Pages:
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631