Note that the LDAP server??™s hostname (set with -h) and the base of the lookup (set with -b)
were bothomitted. FEATURE(ldap_routing) presumes you will set those values with the
confLDAP_DEFAULT_SPEC option (?§24.9.60 on page 1039) in your mc configuration file. If you
don??™t, FEATURE(ldap_routing) will fail.
For an example of how these database maps work, consider the following partial listing of
an LDAP record:
mailLocalAddress: alice@your.domain
mailHost: another.domain
mailRoutingAddress: alice@another.domain
Assume that a rule set first checks to see whether the recipients domain is in the class
$={LDAPRoute} (?§23.7.11.23 on page 924). If it isn??™t, it skips these lookups. Otherwise, the
first database map, the ldapmh, looks up the attribute mailLocalAddress, and if the value
following that item matches, it looks for the attribute mailHost. If that attribute is found, it
returns that field??™s value. The second database map, the ldapmra, also looks up the attribute
mailLocalAddress, and if the value following that item matches, it looks for the attribute
mailRoutingAddress. If that is found, it returns that field??™s value.
The preceding two K configuration commands can be replaced withones of your own
design by adding extra arguments to FEATURE(ldap_routing):
replaces the declaration following Kldapmh
?†“
FEATURE(`ldap_routing??, `newldapmh??, ` newldapmra??)
?†‘
replaces the declaration following Kldapmra
For example, the following declaration:
FEATURE(`ldap_routing??, `ldap -1 -T
-v relayHub
-k (&(objectClass=inetLocalMailRecipient)(mailLocalAddress=%0))??)
would result in this new ldapmh K configuration line:
Kldapmh ldap -1 -v relayHub
-k (&(objectClass=inetLocalMailRecipient)(mailLocalAddress=%0))
For backward compatibility, FEATURE(ldap_routing) will not bounce addresses that fail to
be found with a lookup.
Pages:
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630