Quelle socketmap_table.5.html

Sprache: HTML

products/Sources/formale Sprachen/C/Postfix/html/socketmap_table.5.html

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
 "https://www.w3.org/TR/html4/loose.dtd">
<html> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel='stylesheet' type='text/css' href='postfix-doc.css'>
<title> Postfix manual - socketmap_table(5) </title>
</head> <body> <pre>
SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)

<a name="name">NAME</a>
 socketmap_table - Postfix socketmap table lookup client

<a name="synopsis">SYNOPSIS</a>
 postmap -q "string" <a href="socketmap_table.html">socketmap</a>:inet:host:port:name
 postmap -q "string" <a href="socketmap_table.html">socketmap</a>:unix:pathname:name

 postmap -q - <a href="socketmap_table.html">socketmap</a>:inet:host:port:name <inputfile
 postmap -q - <a href="socketmap_table.html">socketmap</a>:unix:pathname:name <inputfile

<a name="description">DESCRIPTION</a>
 The Postfix mail system uses optional tables for address rewriting or
 mail routing. These tables are usually in <a href="lmdb_table.5.html">lmdb</a>:, <a href="CDB_README.html">cdb</a>:, <a href="DATABASE_README.html#types">hash</a>:, or <a href="DATABASE_README.html#types">dbm</a>:
 format.

 The Postfix socketmap client expects TCP endpoint names of the form
 inet:host:port:name, or UNIX-domain endpoints of the form unix:path-
 name:name. In both cases, name specifies the name field in a socketmap
 client request (see "REQUEST FORMAT" below).

<a name="protocol">PROTOCOL</a>
 Socketmaps use a simple protocol: the client sends one request, and the
 server sends one reply. Each request and each reply are sent as one
 netstring object.

<a name="request_format">REQUEST FORMAT</a>
 The socketmap protocol supports only the lookup request. The request
 has the following form:

 name <space> key
 Search the named socketmap for the specified key.

 Postfix will not generate partial search keys such as domain names
 without one or more subdomains, network addresses without one or more
 least-significant octets, or email addresses without the localpart,
 address extension or domain portion. This behavior is also found with
 <a href="cidr_table.5.html">cidr</a>:, <a href="pcre_table.5.html">pcre</a>:, and <a href="regexp_table.5.html">regexp</a>: tables.

<a name="reply_format">REPLY FORMAT</a>
 Replies must have the following form:

 OK <space> data
 The requested data was found.

 NOTFOUND <space>
 The requested data was not found.

 TEMP <space> reason

 TIMEOUT <space> reason

 PERM <space> reason
 The request failed. The reason, if non-empty, is descriptive
 text.

<a name="protocol_limits">PROTOCOL LIMITS</a>
 The Postfix socketmap client requires that replies are no longer than
 100000 bytes (not including the netstring encapsulation). This limit
 can be changed with the <a href="postconf.5.html#socketmap_max_reply_size">socketmap_max_reply_size</a> configuration parame-
 ter (Postfix 3.10 and later).

 The Postfix socketmap client enforces a 100s time limit to connect to a
 socketmap server, to send a request, and to receive a reply. It closes
 an idle connection after 10s, and closes an active connection after
 100s. These limits are not (yet) configurable.

<a name="security">SECURITY</a>
 This map cannot be used for security-sensitive information, because
 neither the connection nor the server are authenticated.

<a name="configuration_parameters">CONFIGURATION PARAMETERS</a>
 <a href="postconf.5.html#socketmap_max_reply_size">socketmap_max_reply_size</a> (100000)
 The maximum allowed reply size from a socketmap server, not
 including the netstring encapsulation.

<a name="see_also">SEE ALSO</a>
 <a href="https://cr.yp.to/proto/netstrings.txt">https://cr.yp.to/proto/netstrings.txt</a>, netstring definition
 <a href="postconf.1.html">postconf(1)</a>, Postfix supported lookup tables
 <a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
 <a href="regexp_table.5.html">regexp_table(5)</a>, format of regular expression tables
 <a href="pcre_table.5.html">pcre_table(5)</a>, format of PCRE tables
 <a href="cidr_table.5.html">cidr_table(5)</a>, format of CIDR tables

<a name="readme_files">README FILES</a>
 <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview

<a name="bugs">BUGS</a>
 The protocol time limits are not yet configurable.

<a name="license">LICENSE</a>
 The Secure Mailer license must be distributed with this software.

<a name="history">HISTORY</a>
 Socketmap support was introduced with Postfix version 2.10.

 The socketmap protocol was published with Sendmail v8.13.

AUTHOR(S)
 Wietse Venema
 IBM T.J. Watson Research
 P.O. Box 704
 Yorktown Heights, NY 10598, USA

 Wietse Venema
 Google, Inc.
 111 8th Avenue
 New York, NY 10011, USA

 Wietse Venema
 porcupine.org

 SOCKETMAP_TABLE(5)
</pre> </body> </html>

Messung V0.5 in Prozent

¤ Dauer der Verarbeitung: 0.10 Sekunden (vorverarbeitet am 2026-08-10) ¤

Wurzel

Suchen

PVS Prover

Isabelle Prover

NIST Cobol Testsuite

Cephes Mathematical Library

Vienna Development Method

Haftungshinweis

Die Informationen auf dieser Webseite wurden nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit, noch Qualität der bereit gestellten Informationen zugesichert.

Bemerkung:

Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.