socketmap_table man page on DragonFly

Man page or keyword search:  
man Server   44335 pages
apropos Keyword Search (all sections)
Output format
DragonFly logo
[printable version]

SOCKETMAP_TABLE(5)					    SOCKETMAP_TABLE(5)

NAME
       socketmap_table - Postfix socketmap table lookup client

SYNOPSIS
       postmap -q "string" socketmap:inet:host:port:name
       postmap -q "string" socketmap:unix:pathname:name

       postmap -q - socketmap:inet:host:port:name <inputfile
       postmap -q - socketmap:unix:pathname:name <inputfile

DESCRIPTION
       The  Postfix  mail  system  uses optional tables for address rewriting.
       mail routing or policy lookup.

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

PROTOCOL
       Socketmaps use a simple protocol: the client sends one request, and the
       server sends one reply.	Each request and reply are sent	 as  one  net‐
       string object.

REQUEST FORMAT
       The socketmap protocol supports only the lookup request.

       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
       cidr:, pcre:, and regexp: tables.

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

REPLY FORMAT
       The  Postfix socketmap client requires that replies are not longer than
       100000 characters (not including the netstring encapsulation).  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.

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

SEE ALSO
       http://cr.yp.to/proto/netstrings.txt, netstring definition
       postconf(1), Postfix supported lookup tables
       postmap(1), Postfix lookup table manager
       regexp_table(5), format of regular expression tables
       pcre_table(5), format of PCRE tables
       cidr_table(5), format of CIDR tables

README FILES
       Use "postconf readme_directory" or "postconf html_directory" to	locate
       this information.
       DATABASE_README, Postfix lookup table overview

BUGS
       The protocol limits are not yet configurable.

LICENSE
       The Secure Mailer license must be distributed with this software.

HISTORY
       Socketmap support was introduced with Postfix version 2.10.

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

							    SOCKETMAP_TABLE(5)
[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net