15
15
<b>postmap -q - <a href="tcp_table.5.html">tcp</a>:</b><i>host:port</i> <<i>inputfile</i>
18
The Postfix mail system uses optional tables for address
19
rewriting or mail routing. These tables are usually in <b>dbm</b>
20
or <b>db</b> format. Alternatively, table lookups can be directed
23
To find out what types of lookup tables your Postfix sys-
24
tem supports use the "<b>postconf -m</b>" command.
26
To test lookup tables, use the "<b>postmap -q</b>" command as
27
described in the SYNOPSIS above.
18
The Postfix mail system uses optional tables for address rewriting or
19
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format. Alterna-
20
tively, table lookups can be directed to a TCP server.
22
To find out what types of lookup tables your Postfix system supports
23
use the "<b>postconf -m</b>" command.
25
To test lookup tables, use the "<b>postmap -q</b>" command as described in the
29
28
<b>PROTOCOL DESCRIPTION</b>
30
The TCP map class implements a very simple protocol: the
31
client sends a request, and the server sends one reply.
32
Requests and replies are sent as one line of ASCII text,
33
terminated by the ASCII newline character. Request and
34
reply parameters (see below) are separated by whitespace.
29
The TCP map class implements a very simple protocol: the client sends a
30
request, and the server sends one reply. Requests and replies are sent
31
as one line of ASCII text, terminated by the ASCII newline character.
32
Request and reply parameters (see below) are separated by whitespace.
36
Send and receive operations must complete in 100 seconds.
34
Send and receive operations must complete in 100 seconds.
38
36
<b>REQUEST FORMAT</b>
39
Each request specifies a command, a lookup key, and possi-
37
Each request specifies a command, a lookup key, and possibly a lookup
42
40
<b>get</b> SPACE <i>key</i> NEWLINE
43
41
Look up data under the specified key.
46
44
This request is currently not implemented.
48
46
<b>REPLY FORMAT</b>
49
Each reply specifies a status code and text. Replies must
50
be no longer than 4096 characters including the newline
47
Each reply specifies a status code and text. Replies must be no longer
48
than 4096 characters including the newline terminator.
53
50
<b>500</b> SPACE <i>text</i> NEWLINE
54
In case of a lookup request, the requested data
55
does not exist. In case of an update request, the
56
request was rejected. The text describes the
57
nature of the problem.
51
In case of a lookup request, the requested data does not exist.
52
In case of an update request, the request was rejected. The
53
text describes the nature of the problem.
59
55
<b>400</b> SPACE <i>text</i> NEWLINE
60
This indicates an error condition. The text
61
describes the nature of the problem. The client
62
should retry the request later.
56
This indicates an error condition. The text describes the nature
57
of the problem. The client should retry the request later.
64
59
<b>200</b> SPACE <i>text</i> NEWLINE
65
The request was successful. In the case of a lookup
66
request, the text contains an encoded version of
60
The request was successful. In the case of a lookup request, the
61
text contains an encoded version of the requested data.
70
In request and reply parameters, the character %, each
71
non-printing character, and each whitespace character must
72
be replaced by %XX, where XX is the corresponding ASCII
73
hexadecimal character value. The hexadecimal codes can be
74
specified in any case (upper, lower, mixed).
64
In request and reply parameters, the character %, each non-printing
65
character, and each whitespace character must be replaced by %XX, where
66
XX is the corresponding ASCII hexadecimal character value. The hexadec-
67
imal codes can be specified in any case (upper, lower, mixed).
76
The Postfix client always encodes a request. The server
77
may omit the encoding as long as the reply is guaranteed
78
to not contain the % or NEWLINE character.
69
The Postfix client always encodes a request. The server may omit the
70
encoding as long as the reply is guaranteed to not contain the % or
81
Do not use TCP lookup tables for security critical pur-
82
poses. The client-server connection is not protected and
83
the server is not authenticated.
74
Do not use TCP lookup tables for security critical purposes. The
75
client-server connection is not protected and the server is not authen-
86
79
Only the lookup method is currently implemented.
88
The client does not hang up when the connection is idle
81
The client does not hang up when the connection is idle for a long
92
85
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
added
removed
html/tcp_table.5.html
