nisplus_table.5.html revision 1.1.1.6.2.1 1 <!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "https://www.w3.org/TR/html4/loose.dtd">
3 <html> <head>
4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
5 <link rel='stylesheet' type='text/css' href='postfix-doc.css'>
6 <title> Postfix manual - nisplus_table(5) </title>
7 </head> <body> <pre>
8 NISPLUS_TABLE(5) NISPLUS_TABLE(5)
9
10 <b><a name="name">NAME</a></b>
11 nisplus_table - Postfix NIS+ client
12
13 <b><a name="synopsis">SYNOPSIS</a></b>
14 <b>postmap -q "</b><i>string</i><b>" "<a href="nisplus_table.5.html">nisplus</a>:[</b><i>name</i><b>=%s];</b><i>name.name.</i><b>"</b>
15
16 <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>
17
18 <b><a name="description">DESCRIPTION</a></b>
19 The Postfix mail system uses optional lookup tables. rewriting or mail
20 routing. These tables are usually in <b><a href="lmdb_table.5.html">lmdb</a>:</b>, <b><a href="CDB_README.html">cdb</a>:</b>, <b><a href="DATABASE_README.html#types">hash</a>:</b>, or <b><a href="DATABASE_README.html#types">dbm</a>:</b> for-
21 mat.
22
23 Alternatively, lookup tables can be specified as NIS+ databases. To
24 find out what types of lookup tables your Postfix system supports use
25 the "<b>postconf -m</b>" command.
26
27 To test Postfix NIS+ lookup tables, use the "<b>postmap -q</b>" command as
28 described in the SYNOPSIS above.
29
30 <b><a name="query_syntax">QUERY SYNTAX</a></b>
31 Most of the NIS+ query is specified via the NIS+ map name. The general
32 format of a Postfix NIS+ map name is as follows:
33
34 <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
36 Postfix NIS+ map names differ from what one normally would use with
37 commands such as <b>niscat</b>:
38
39 <b>o</b> With each NIS+ table lookup, "<b>%s</b>" is replaced by a version of
40 the lookup string. There can be only one "<b>%s</b>" instance in a
41 Postfix NIS+ map name.
42
43 <b>o</b> Postfix NIS+ map names use "<b>;</b>" instead of "<b>,</b>", because the lat-
44 ter character is special in the Postfix <a href="postconf.5.html">main.cf</a> file. Postfix
45 replaces "<b>;</b>" characters in the map name by "<b>,</b>" before making
46 NIS+ queries.
47
48 <b>o</b> The ":<i>column</i>" part in the NIS+ map name is not part of the
49 actual NIS+ query. Instead, it specifies the number of the table
50 column that provides the lookup result. When no ":<i>column</i>" is
51 specified the first column (1) is used.
52
53 <b><a name="example">EXAMPLE</a></b>
54 A NIS+ aliases map might be queried as follows:
55
56 <a href="postconf.5.html#alias_maps">alias_maps</a> = <a href="DATABASE_README.html#types">dbm</a>:/etc/mail/aliases,
57 <a href="nisplus_table.5.html">nisplus</a>:[alias=%s];mail_aliases.org_dir.$<a href="postconf.5.html#mydomain">mydomain</a>.:1
58
59 This queries the local aliases file before the NIS+ file.
60
61 <b><a name="see_also">SEE ALSO</a></b>
62 <a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
63
64 <b><a name="readme_files">README FILES</a></b>
65 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
66
67 <b><a name="license">LICENSE</a></b>
68 The Secure Mailer license must be distributed with this software.
69
70 <b>AUTHOR(S)</b>
71 Geoff Gibbs
72 UK-HGMP-RC
73 Hinxton
74 Cambridge
75 CB10 1SB, UK
76
77 Adopted and adapted by:
78 Wietse Venema
79 IBM T.J. Watson Research
80 P.O. Box 704
81 Yorktown Heights, NY 10598, USA
82
83 Wietse Venema
84 Google, Inc.
85 111 8th Avenue
86 New York, NY 10011, USA
87
88 NISPLUS_TABLE(5)
89 </pre> </body> </html>
90