1SOCKETMAP_TABLE(5)            File Formats Manual           SOCKETMAP_TABLE(5)
2
3
4

NAME

6       socketmap_table - Postfix socketmap table lookup client
7

SYNOPSIS

9       postmap -q "string" socketmap:inet:host:port:name
10       postmap -q "string" socketmap:unix:pathname:name
11
12       postmap -q - socketmap:inet:host:port:name <inputfile
13       postmap -q - socketmap:unix:pathname:name <inputfile
14

DESCRIPTION

16       The  Postfix  mail  system  uses optional tables for address rewriting.
17       mail routing or policy lookup.
18
19       The Postfix socketmap client expects TCP endpoint  names  of  the  form
20       inet:host:port:name,  or  UNIX-domain  endpoints of the form unix:path‐
21       name:name.  In both cases, name specifies the name field in a socketmap
22       client request (see "REQUEST FORMAT" below).
23

PROTOCOL

25       Socketmaps use a simple protocol: the client sends one request, and the
26       server sends one reply.  Each request and each reply are  sent  as  one
27       netstring object.
28

REQUEST FORMAT

30       The  socketmap  protocol supports only the lookup request.  The request
31       has the following form:
32
33
34       name <space> key
35              Search the named socketmap for the specified key.
36
37       Postfix will not generate partial search  keys  such  as  domain  names
38       without  one  or more subdomains, network addresses without one or more
39       least-significant octets, or email  addresses  without  the  localpart,
40       address  extension  or domain portion. This behavior is also found with
41       cidr:, pcre:, and regexp: tables.
42

REPLY FORMAT

44       The Postfix socketmap client requires that replies are not longer  than
45       100000  characters (not including the netstring encapsulation). Replies
46       must have the following form:
47
48       OK <space> data
49              The requested data was found.
50
51       NOTFOUND <space>
52              The requested data was not found.
53
54       TEMP <space> reason
55
56       TIMEOUT <space> reason
57
58       PERM <space> reason
59              The request failed. The reason,  if  non-empty,  is  descriptive
60              text.
61

SECURITY

63       This map cannot be used for security-sensitive information,
64       because neither the connection nor the server are authenticated.
65

SEE ALSO

67       http://cr.yp.to/proto/netstrings.txt, netstring definition
68       postconf(1), Postfix supported lookup tables
69       postmap(1), Postfix lookup table manager
70       regexp_table(5), format of regular expression tables
71       pcre_table(5), format of PCRE tables
72       cidr_table(5), format of CIDR tables
73

README FILES

75       Use  "postconf readme_directory" or "postconf html_directory" to locate
76       this information.
77       DATABASE_README, Postfix lookup table overview
78

BUGS

80       The protocol limits are not yet configurable.
81

LICENSE

83       The Secure Mailer license must be distributed with this software.
84

HISTORY

86       Socketmap support was introduced with Postfix version 2.10.
87

AUTHOR(S)

89       Wietse Venema
90       IBM T.J. Watson Research
91       P.O. Box 704
92       Yorktown Heights, NY 10598, USA
93
94       Wietse Venema
95       Google, Inc.
96       111 8th Avenue
97       New York, NY 10011, USA
98
99
100
101                                                            SOCKETMAP_TABLE(5)