Database Maps and m4
Some databases, such as user, are a part of UNIX. Others are a part of sendmail, like the User Database described above. Many, however, are implemented in rules and rule sets. This latter sort of database is therefore available via the m4 technique. Currently, all m4 available databases are implemented as FEATUREs. Table 33.7 lists those available. The second column shows you where to find information about each.
| Feature | Version | Description | |
|---|---|---|---|
| domaintable | FEATURE(domaintable) | and above | Accept other domains as equivalent to the local domain |
| genericstable | FEATURE(genericstable) | and above | Transform sender addresses |
| mailertable | FEATURE(mailertable) | and above | Select new delivery agents based on an external database |
| virtusertable | FEATURE(virtusertable) | and above | Support for virtual domains |
Note that these FEATUREs do not necessarily need to be used with database files. To illustrate, consider the domaintable feature (see ). It is included in your mc file like this:
FEATURE(`domaintable',`nis domaintable')
Here, we specify that the database is to be an nis map. This causes the key to be looked up via the nis services and any match to be returned the same way.