You can routinely include it in all configuration files.
The database lookup is performed only if the .BITNET suffix is present and the database file
exists. (See ?§23.3.10 on page 889 for a description of the K command??™s -o switch.)
You can also provide an extra argument, where that second argument is a literal LDAP:
FEATURE(`bitdomain??, `LDAP??)
The default in this instance becomes the following (we have wrapped the lines to fit the
page):
Kbitdomain ldap -1 -v sendmailMTAMapValue -k (&(objectClass=sendmailMTAMapObject)
(|(sendmailMTACluster=${sendmailMTACluster})(sendmailMTAHost=$j))
(sendmailMTAMapName=bitdomain)(sendmailMTAKey=%0))
See ?§23.7.11 on page 912 for a description of the ldap database type and its -1, -v, and -k
switches.
Note that you must also define BITNET_RELAY (?§21.9.11 on page 808) if you want .BITNETsuffixed
mail that is not found in the database to be routed to a relay machine. If BITNET_
RELAY is not defined, .BITNET-suffixed mail that is not found in the database is bounced.
17.8.10 FEATURE(blacklist_recipients)
Look up recipients in access database V8.9 and later
FEATURE(access_db) (?§7.5 on page 277) provides a way to selectively reject envelope sender
addresses (and muchmore). By declaring this FEATURE(blacklist_recipients), you enable
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc.
Pages:
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089