8.16 on page 621 V8.1 and later Accept other domains as equivalent to the local
domain
enhdnsbl ?§7.2.2 on page 263 V8.12 and later Enhanced dnsbl lookups
genericstable ?§17.8.19 on page 622 V8.8 and later Transform sender addresses
ldap_routing ?§23.7.11.22 on page 922 V8.10 and later Reroute recipients based on LDAP lookups
mailertable ?§17.8.28 on page 629 V8.1 and later Select new delivery agents based on an external
database
uucpdomain ?§17.8.57 on page 644 Deprecated Convert UUCP hosts via a database
virtusertable ?§17.8.59 on page 645 V8.8 and later Support for virtual domains
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
23.6 Pitfalls | 897
23.5.1 Set a Default Database-Map Type for Features
FEATUREs that employ on-disk database files all share the common default databasemap
type hash. But if you wish to change that default to another type, you can do so
with the following mc configuration command:
define(`DATABASE_MAP_TYPE??, `dbm??)
Here, we declare the default to be dbm, thereby causing all such FEATUREs to use
ndbm(3) database files. Note that if you declare a default, you must do so before
declaring any database FEATUREs.
Many FEATUREs that take arguments require you to declare the database type. For
example:
FEATURE(`authinfo??, `dbm /etc/security/authinfo??)
That is, this DATABASE_MAP_TYPE??™s default is used only if no argument is given
for the feature.
Pages:
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582