Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Cactus

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 71 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

proxymap



SYNOPSIS

       proxymap [generic Postfix daemon options]


DESCRIPTION

       The  proxymap  server provides read-only table lookup ser­
       vice to Postfix client processes. The purpose of the  ser­
       vice is:

       ·      To  overcome  chroot  restrictions.  For example, a
              chrooted SMTP server needs  access  to  the  system
              passwd  file  in order to reject mail for non-exis­
              tent local addresses, but it is  not  practical  to
              maintain  a  copy  of the passwd file in the chroot
              jail.  The solution:

              local_recipient_maps =
                  proxy:unix:passwd.byname $alias_maps

       ·      To consolidate the number of open lookup tables  by
              sharing  one  open  table among multiple processes.
              For example, making mysql  connections  from  every
              Postfix daemon process results in "too many connec­
              tions" errors. The solution:

              virtual_alias_maps =
                  proxy:mysql:/etc/postfix/virtual_alias.cf

              The total number of connections is limited  by  the
              number of proxymap server processes.

       The proxymap server implements the following requests:

       PROXY_REQ_OPEN maptype:mapname flags
              Open  the table with type maptype and name mapname,
              as controlled by flags.  The reply is  the  request
              completion  status  code  (below)  and the map type
              dependent flags.

       PROXY_REQ_LOOKUP maptype:mapname flags key
              Look up the data stored under  the  requested  key.
              The  reply  is  the  request completion status code
              (below) and the  lookup  result  value.   The  map­
              type:mapname  and  flags  are  the same as with the
              PROXY_REQ_OPEN request.

       There is no  close  command,  nor  are  tables  implicitly
       closed  when  a client disconnects. One of the purposes of
       the proxymap server is  to  share  tables  among  multiple
       client processes.

       The request completion status code is one of:

       PROXY_STAT_DENY
              The specified table was not approved for access via
              the proxymap service.


SERVER PROCESS MANAGEMENT

       The proxymap servers run under control by the Postfix mas­
       ter  server.  Each server can handle multiple simultaneous
       connections.  When all servers are  busy  while  a  client
       connects,  the  master  creates a new proxymap server pro­
       cess, provided that the proxymap server process  limit  is
       not exceeded.  Each proxymap server terminates after serv­
       ing at least $max_use clients or after  $max_idle  seconds
       of idle time.


SECURITY

       The  proxymap  server  opens only tables that are approved
       via the proxy_read_maps configuration parameter, does  not
       talk  to  users,  and  can  run  at  fixed  low privilege,
       chrooted or not.  However,  running  the  proxymap  server
       chrooted  severely  limits  usability, because it can open
       only chrooted tables.

       The proxymap server is not a trusted daemon  process,  and
       must  not be used to look up sensitive information such as
       user or group IDs, mailbox file/directory names or  exter­
       nal commands.


DIAGNOSTICS

       Problems and transactions are logged to syslogd(8).


BUGS

       The  proxymap server provides service to multiple clients,
       and must therefore not be used for tables that have  high-
       latency lookups.


CONFIGURATION PARAMETERS

       The  following  main.cf parameters are especially relevant
       to this program. Use the postfix reload  command  after  a
       configuration change.

       proxy_read_maps
              A  list  of  zero or more parameter values that may
              contain references to Postfix lookup  tables.  Only
              table   references   that  begin  with  proxy:  are
              approved for  read-only  access  via  the  proxymap
              server.


SEE ALSO

       dict_proxy(3) proxy map client


LICENSE

       The  Secure  Mailer  license must be distributed with this
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds