Manual browser: postmap(1)
|POSTMAP(1)||General Commands Manual||POSTMAP(1)|
NAMEpostmap - Postfix lookup table management
postmap [-Nbfhimnoprsvw] [-c config_dir] [ -d key] [-q key]
The postmap(1) command creates or queries one or more Postfix lookup tables, or updates an existing one. The input and output file formats are expected to be compatible with:
makemap file_type file_name < file_name
INPUT FILE FORMAT
The format of a lookup table input file is as follows:
A table entry has the form
key whitespace value
- Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace character is a `#'.
- A logical line starts with non-whitespace text. A line that starts with whitespace continues a logical line.
The key and value are processed as is, except that surrounding white space is stripped off. Unlike with Postfix alias databases, quotes cannot be used to protect lookup keys that contain special characters such as `#' or whitespace.
Enable message body query mode. When reading lookup keys from standard input with " -q -", process the input as if it is an email message in RFC 2822 format. Each line of body content becomes one lookup key.
- -c config_dir
- Read the main.cf configuration file in the named directory instead of the default configuration directory.
- -d key
Search the specified maps for key and remove one entry per map. The exit status is zero when the requested information was found.
Do not fold the lookup key to lower case while creating or querying a table.
Enable message header query mode. When reading lookup keys from standard input with " -q -", process the input as if it is an email message in RFC 2822 format. Each logical header line becomes one lookup key. A multi-line header becomes one lookup key with one or more embedded newline characters.
- Incremental mode. Read entries from standard input and do not truncate an existing database. By default, postmap(1) creates a new database from the entries in file_name.
Enable MIME parsing with "-b" and "-h".
- Include the terminating null character that terminates lookup keys and values. By default, postmap(1) does whatever is the default for the host operating system.
- Don't include the terminating null character that terminates lookup keys and values. By default, postmap(1) does whatever is the default for the host operating system.
- Do not release root privileges when processing a non-root input file. By default, postmap(1) drops root privileges and runs as the source file owner instead.
- Do not inherit the file access permissions from the input file when creating a new file. Instead, create a new file with default access permissions (mode 0644).
- -q key
Search the specified maps for key and write the first value found to the standard output stream. The exit status is zero when the requested information was found.
- When updating a table, do not complain about attempts to update existing entries, and make those updates anyway.
Retrieve all database elements, and write one line of key value output for each element. The elements are printed in database order, which is not necessarily the same as the original input order.
- Enable verbose logging for debugging purposes. Multiple -v options make the software increasingly verbose.
- When updating a table, do not complain about attempts to update existing entries, and ignore those attempts.
The database type. To find out what types are supported, use the " postconf -m" command.
- The output file is a btree file, named file_name.db. This is available on systems with support for db databases.
- The output consists of one file, named file_name.cdb. This is available on systems with support for cdb databases.
- The output consists of two files, named file_name.pag and file_name.dir. This is available on systems with support for dbm databases.
- The output file is a hashed file, named file_name.db. This is available on systems with support for db databases.
- A table that reliably fails all requests. The lookup table name is used for logging only. This table exists to simplify Postfix error tests.
- The output consists of two files, named file_name.pag and file_name.dir. This is available on systems with support for sdbm databases.
When no file_type is specified, the software uses the database type specified via the default_database_type configuration parameter.
- The name of the lookup table source file when rebuilding a database.
Problems are logged to the standard error stream and to syslogd(8). No output means that no problems were detected. Duplicate entries are skipped and are flagged with a warning.
- Directory with Postfix configuration files.
- Enable verbose logging for debugging purposes.
The following main.cf parameters are especially relevant to this program. The text below provides only a parameter summary. See postconf(5) for more details including examples.
- berkeley_db_create_buffer_size (16777216)
- The per-table I/O buffer size for programs that create Berkeley DB hash or btree tables.
- berkeley_db_read_buffer_size (131072)
- The per-table I/O buffer size for programs that read Berkeley DB hash or btree tables.
- config_directory (see 'postconf -d' output)
- The default location of the Postfix main.cf and master.cf configuration files.
- default_database_type (see 'postconf -d' output)
- The default database type for use in newaliases(1), postalias(1) and postmap(1) commands.
- syslog_facility (mail)
- The syslog facility of Postfix logging.
- syslog_name (see 'postconf -d' output)
- The mail system name that is prepended to the process name in syslog records, so that "smtpd" becomes, for example, "postfix/smtpd".
postalias(1), create/update/query alias database
postconf(1), supported database types
postconf(5), configuration parameters
syslogd(8), system logging
Use "postconf readme_directory" or " postconf html_directory" to locate this information.
DATABASE_README, Postfix lookup table overview
The Secure Mailer license must be distributed with this software.
IBM T.J. Watson Research
P.O. Box 704
Yorktown Heights, NY 10598, USA