makemap(1M)

Synopsis

Description

Depending on how it is compiled, makemap handles up to three different database formats, selected using the maptype parameter. The formats are:

dbm

DBM format maps. This requires the ndbm(3bsd) library.

btree

B-Tree format maps. This requires the new Berkeley DB library.

hash

Hash format maps. This also requires the DB library.

In all cases, makemap reads lines from the standard input, consisting of two words separated by white space. The first is the database key; the second is the value. The value may contain %n strings to indicate parameter substitution. Literal percents should be doubled (%%). Blank lines and lines beginning with # are ignored.

If the TrustedUser option is set in the sendmail configuration file and makemap is invoked as root, the generated files will be owned by the specified TrustedUser.

Options

C

Use the specified sendmail configuration file for looking up the TrustedUser option.

N

Include the null byte that terminates strings in the map. This must match the -N flag in the sendmail.cf K line.

d

Allow duplicate keys in the map. This is only allowed on B-Tree format maps. If two identical keys are read, they will both be inserted into the map.

e

Allow empty value (right hand side).

f

Normally, all uppercase letters in the key are folded to lowercase. This flag disables that behavior. This is intended to mesh with the -f flag in the K line in sendmail.cf. The value is never case-folded.

o

Append to an old file. This allows you to augment an existing file.

r

Allow replacement of existing keys. Normally, makemap complains if you repeat a key, and does not perform the insert.

s

Ignore safety checks on maps being created. This includes checking for hard or symbolic links in world writable directories.

u

dump (unmap) the content of the database to standard output.

v

Verbosely print what makemap is doing.

References

Backward compatibility