15
15
<b>postmap -q - "<a href="nisplus_table.5.html">nisplus</a>:[</b><i>name</i><b>=%s];</b><i>name.name.</i><b>"</b> <<i>inputfile</i>
18
The Postfix mail system uses optional lookup tables.
19
These tables are usually in <b>dbm</b> or <b>db</b> format. Alterna-
20
tively, lookup tables can be specified as NIS+ databases.
22
To find out what types of lookup tables your Postfix sys-
23
tem supports use the "<b>postconf -m</b>" command.
25
To test Postfix NIS+ lookup tables, use the "<b>postmap -q</b>"
26
command as described in the SYNOPSIS above.
18
The Postfix mail system uses optional lookup tables. These tables are
19
usually in <b>dbm</b> or <b>db</b> format. Alternatively, lookup tables can be spec-
20
ified as NIS+ databases.
22
To find out what types of lookup tables your Postfix system supports
23
use the "<b>postconf -m</b>" command.
25
To test Postfix NIS+ lookup tables, use the "<b>postmap -q</b>" command as
26
described in the SYNOPSIS above.
28
28
<b>QUERY SYNTAX</b>
29
Most of the NIS+ query is specified via the NIS+ map name.
30
The general format of a Postfix NIS+ map name is as fol-
29
Most of the NIS+ query is specified via the NIS+ map name. The general
30
format of a Postfix NIS+ map name is as follows:
33
32
<b><a href="nisplus_table.5.html">nisplus</a>:[</b><i>name</i><b>=%s];</b><i>name.name.name</i><b>.:</b><i>column</i>
35
Postfix NIS+ map names differ from what one normally would
36
use with commands such as <b>niscat</b>:
38
<b>o</b> With each NIS+ table lookup, "<b>%s</b>" is replaced by a
39
version of the lookup string. There can be only
40
one "<b>%s</b>" instance in a Postfix NIS+ map name.
42
<b>o</b> Postfix NIS+ map names use "<b>;</b>" instead of "<b>,</b>",
43
because the latter character is special in the
44
Postfix <a href="postconf.5.html">main.cf</a> file. Postfix replaces "<b>;</b>" charac-
45
ters in the map name by "<b>,</b>" before making NIS+
48
<b>o</b> The ":<i>column</i>" part in the NIS+ map name is not part
49
of the actual NIS+ query. Instead, it specifies the
50
number of the table column that provides the lookup
51
result. When no ":<i>column</i>" is specified the first
34
Postfix NIS+ map names differ from what one normally would use with
35
commands such as <b>niscat</b>:
37
<b>o</b> With each NIS+ table lookup, "<b>%s</b>" is replaced by a version of
38
the lookup string. There can be only one "<b>%s</b>" instance in a
39
Postfix NIS+ map name.
41
<b>o</b> Postfix NIS+ map names use "<b>;</b>" instead of "<b>,</b>", because the lat-
42
ter character is special in the Postfix <a href="postconf.5.html">main.cf</a> file. Postfix
43
replaces "<b>;</b>" characters in the map name by "<b>,</b>" before making
46
<b>o</b> The ":<i>column</i>" part in the NIS+ map name is not part of the
47
actual NIS+ query. Instead, it specifies the number of the table
48
column that provides the lookup result. When no ":<i>column</i>" is
49
specified the first column (1) is used.
55
52
A NIS+ aliases map might be queried as follows:
57
<a href="postconf.5.html#alias_maps">alias_maps</a> = dbm:/etc/mail/aliases,
54
<a href="postconf.5.html#alias_maps">alias_maps</a> = <a href="DATABASE_README.html#types">dbm</a>:/etc/mail/aliases,
58
55
<a href="nisplus_table.5.html">nisplus</a>:[alias=%s];mail_aliases.org_dir.$<a href="postconf.5.html#mydomain">mydomain</a>.:1
60
This queries the local aliases file before the NIS+ file.
57
This queries the local aliases file before the NIS+ file.
63
60
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
added
removed
html/nisplus_table.5.html
