If sucha database map were called mailservers, you could use the following
configuration file line to look up your domain in that database map:
Kmailservers nis -o mailservers
...
R $* <@ $+ > $* $: $1<@$2>$3 <$(mailservers $2 $)>
R $* <@ $+ > $* <$+> $#smtp $@ $4 $: $1 < @ $2 > $3
...
Here, we look up the host part of an address ($2) in th emailservers NIS database map.
The -o makes the existence of the database map optional. If the host part is found, it is
rewritten to be the name of the mail server for that host. In the last rule, we forward the
original address to that server.
Without the -o, the nonexistence of a database map will cause this error to be logged:
Cannot bind to map name in domain domain: reason here
If NIS is not running or if sendmail cannot bind to the domain specified for the default
domain, the following error is logged:
421 4.3.5 NIS map name specified, but NIS not running
Only a few database switches are available with this nis database-map type. They can be
found in Table 23-19.
Table 23-19. The nis database-map type K command switches
Switch ?§ Description
-a ?§23.3.2 on page 887 Append tag on successful match.
-D ?§23.3.3 on page 887 Don??™t use this database map if DeliveryMode=defer.
-f ?§23.3.4 on page 887 Don??™t fold keys to lowercase.
-m ?§23.3.7 on page 888 Suppress replacement on match.
Pages:
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640