Linux vps-61133.fhnet.fr 4.9.0-19-amd64 #1 SMP Debian 4.9.320-2 (2022-06-30) x86_64
Apache/2.4.25 (Debian)
Server IP : 93.113.207.21 & Your IP : 216.73.216.122
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
postfix /
html /
Delete
Unzip
Name
Size
Permission
Date
Action
ADDRESS_CLASS_README.html
13.12
KB
-rw-r--r--
2020-02-16 20:59
ADDRESS_REWRITING_README.html
51.57
KB
-rw-r--r--
2020-02-16 20:59
ADDRESS_VERIFICATION_README.html
29.08
KB
-rw-r--r--
2020-02-16 20:59
BACKSCATTER_README.html
14.58
KB
-rw-r--r--
2020-02-16 20:59
BASIC_CONFIGURATION_README.html
28.25
KB
-rw-r--r--
2020-02-16 20:59
BUILTIN_FILTER_README.html
19.44
KB
-rw-r--r--
2020-02-16 20:59
CDB_README.html
4.01
KB
-rw-r--r--
2020-02-16 20:59
COMPATIBILITY_README.html
12.47
KB
-rw-r--r--
2020-02-16 20:59
CONNECTION_CACHE_README.html
12.02
KB
-rw-r--r--
2020-02-16 20:59
CONTENT_INSPECTION_README.html
3.57
KB
-rw-r--r--
2020-02-16 20:59
DATABASE_README.html
20.07
KB
-rw-r--r--
2020-02-16 20:59
DB_README.html
8.32
KB
-rw-r--r--
2020-02-16 20:59
DEBUG_README.html
20.59
KB
-rw-r--r--
2020-02-16 20:59
DSN_README.html
5.14
KB
-rw-r--r--
2020-02-16 20:59
ETRN_README.html
13.83
KB
-rw-r--r--
2020-02-16 20:59
FILTER_README.html
38.25
KB
-rw-r--r--
2020-02-16 20:59
FORWARD_SECRECY_README.html
29.03
KB
-rw-r--r--
2020-02-16 20:59
INSTALL.html
58.1
KB
-rw-r--r--
2020-02-16 20:59
IPV6_README.html
14.29
KB
-rw-r--r--
2020-02-16 20:59
LDAP_README.html
23.62
KB
-rw-r--r--
2020-02-16 20:59
LINUX_README.html
2.71
KB
-rw-r--r--
2020-02-16 20:59
LMDB_README.html
14.61
KB
-rw-r--r--
2020-02-16 20:59
LOCAL_RECIPIENT_README.html
7.71
KB
-rw-r--r--
2020-02-16 20:59
MAILDROP_README.html
6.99
KB
-rw-r--r--
2020-02-16 20:59
MEMCACHE_README.html
2.85
KB
-rw-r--r--
2020-02-16 20:59
MILTER_README.html
33.84
KB
-rw-r--r--
2020-02-16 20:59
MULTI_INSTANCE_README.html
54.29
KB
-rw-r--r--
2020-02-16 20:59
MYSQL_README.html
6.54
KB
-rw-r--r--
2020-02-16 20:59
NFS_README.html
5.19
KB
-rw-r--r--
2020-02-16 20:59
OVERVIEW.html
33.49
KB
-rw-r--r--
2020-02-16 20:59
PACKAGE_README.html
5.49
KB
-rw-r--r--
2020-02-16 20:59
PCRE_README.html
3.97
KB
-rw-r--r--
2020-02-16 20:59
PGSQL_README.html
5.86
KB
-rw-r--r--
2020-02-16 20:59
POSTSCREEN_README.html
52.75
KB
-rw-r--r--
2020-02-16 20:59
QSHAPE_README.html
46.6
KB
-rw-r--r--
2020-02-16 20:59
RESTRICTION_CLASS_README.html
9.08
KB
-rw-r--r--
2020-02-16 20:59
SASL_README.html
69.85
KB
-rw-r--r--
2020-02-16 20:59
SCHEDULER_README.html
72.05
KB
-rw-r--r--
2020-02-16 20:59
SMTPD_ACCESS_README.html
21.38
KB
-rw-r--r--
2020-02-16 20:59
SMTPD_POLICY_README.html
32.2
KB
-rw-r--r--
2020-02-16 20:59
SMTPD_PROXY_README.html
16.09
KB
-rw-r--r--
2020-02-16 20:59
SMTPUTF8_README.html
13.81
KB
-rw-r--r--
2020-02-16 20:59
SOHO_README.html
16.35
KB
-rw-r--r--
2020-02-16 20:59
SQLITE_README.html
3.53
KB
-rw-r--r--
2020-02-16 20:59
STANDARD_CONFIGURATION_README.html
33.36
KB
-rw-r--r--
2020-02-16 20:59
STRESS_README.html
24.34
KB
-rw-r--r--
2020-02-16 20:59
TLS_LEGACY_README.html
64.9
KB
-rw-r--r--
2020-02-16 20:59
TLS_README.html
141.53
KB
-rw-r--r--
2020-02-16 20:59
TUNING_README.html
29.65
KB
-rw-r--r--
2020-02-16 20:59
UUCP_README.html
6.37
KB
-rw-r--r--
2020-02-16 20:59
VERP_README.html
9.36
KB
-rw-r--r--
2020-02-16 20:59
VIRTUAL_README.html
29.75
KB
-rw-r--r--
2020-02-16 20:59
XCLIENT_README.html
8.35
KB
-rw-r--r--
2020-02-16 20:59
XFORWARD_README.html
8.08
KB
-rw-r--r--
2020-02-16 20:59
access.5.html
23.14
KB
-rw-r--r--
2020-02-16 20:59
aliases.5.html
10.73
KB
-rw-r--r--
2020-02-16 20:59
anvil.8.html
10.36
KB
-rw-r--r--
2020-02-16 20:59
bounce.5.html
9.61
KB
-rw-r--r--
2020-02-16 20:59
bounce.8.html
9.51
KB
-rw-r--r--
2020-02-16 20:59
canonical.5.html
14.12
KB
-rw-r--r--
2020-02-16 20:59
cidr_table.5.html
4.65
KB
-rw-r--r--
2020-02-16 20:59
cleanup.8.html
27.79
KB
-rw-r--r--
2020-02-16 20:59
defer.8.html
9.51
KB
-rw-r--r--
2020-02-16 20:59
discard.8.html
5.99
KB
-rw-r--r--
2020-02-16 20:59
dnsblog.8.html
4.42
KB
-rw-r--r--
2020-02-16 20:59
error.8.html
6.65
KB
-rw-r--r--
2020-02-16 20:59
flush.8.html
8.43
KB
-rw-r--r--
2020-02-16 20:59
generic.5.html
11.6
KB
-rw-r--r--
2020-02-16 20:59
header_checks.5.html
25.89
KB
-rw-r--r--
2020-02-16 20:59
index.html
4.52
KB
-rw-r--r--
2020-02-16 20:59
ldap_table.5.html
36.07
KB
-rw-r--r--
2020-02-16 20:59
lmdb_table.5.html
5.41
KB
-rw-r--r--
2020-02-16 20:59
lmtp.8.html
50.41
KB
-rw-r--r--
2020-02-16 20:59
local.8.html
36.49
KB
-rw-r--r--
2020-02-16 20:59
mailq.1.html
23.52
KB
-rw-r--r--
2020-02-16 20:59
master.5.html
13.86
KB
-rw-r--r--
2020-02-16 20:59
master.8.html
10.41
KB
-rw-r--r--
2020-02-16 20:59
memcache_table.5.html
12.07
KB
-rw-r--r--
2020-02-16 20:59
mysql_table.5.html
16.72
KB
-rw-r--r--
2020-02-16 20:59
newaliases.1.html
23.52
KB
-rw-r--r--
2020-02-16 20:59
nisplus_table.5.html
3.51
KB
-rw-r--r--
2020-02-16 20:59
oqmgr.8.html
22.08
KB
-rw-r--r--
2020-02-16 20:59
pcre_table.5.html
9.94
KB
-rw-r--r--
2020-02-16 20:59
pgsql_table.5.html
16
KB
-rw-r--r--
2020-02-16 20:59
pickup.8.html
5.83
KB
-rw-r--r--
2020-02-16 20:59
pipe.8.html
24.79
KB
-rw-r--r--
2020-02-16 20:59
postalias.1.html
12.17
KB
-rw-r--r--
2020-02-16 20:59
postcat.1.html
3.91
KB
-rw-r--r--
2020-02-16 20:59
postconf.1.html
29.45
KB
-rw-r--r--
2020-02-16 20:59
postconf.5.html
715.88
KB
-rw-r--r--
2020-02-16 20:59
postdrop.1.html
5.83
KB
-rw-r--r--
2020-02-16 20:59
postfix-logo.jpg
3.58
KB
-rw-r--r--
2020-02-16 20:59
postfix-manuals.html
7.27
KB
-rw-r--r--
2020-02-16 20:59
postfix-power.png
5.26
KB
-rw-r--r--
2020-02-16 20:59
postfix-tls.1.html
14.53
KB
-rw-r--r--
2020-02-16 20:59
postfix-wrapper.5.html
15.48
KB
-rw-r--r--
2020-02-16 20:59
postfix.1.html
21.65
KB
-rw-r--r--
2020-02-16 20:59
postkick.1.html
3.7
KB
-rw-r--r--
2020-02-16 20:59
postlock.1.html
4.89
KB
-rw-r--r--
2020-02-16 20:59
postlog.1.html
3.9
KB
-rw-r--r--
2020-02-16 20:59
postmap.1.html
15.17
KB
-rw-r--r--
2020-02-16 20:59
postmulti.1.html
23.16
KB
-rw-r--r--
2020-02-16 20:59
postqueue.1.html
12.01
KB
-rw-r--r--
2020-02-16 20:59
postscreen.8.html
28.23
KB
-rw-r--r--
2020-02-16 20:59
postsuper.1.html
14.22
KB
-rw-r--r--
2020-02-16 20:59
posttls-finger.1.html
18.53
KB
-rw-r--r--
2020-02-16 20:59
proxymap.8.html
11.34
KB
-rw-r--r--
2020-02-16 20:59
qmgr.8.html
26.61
KB
-rw-r--r--
2020-02-16 20:59
qmqp-sink.1.html
2.36
KB
-rw-r--r--
2020-02-16 20:59
qmqp-source.1.html
3.88
KB
-rw-r--r--
2020-02-16 20:59
qmqpd.8.html
8.78
KB
-rw-r--r--
2020-02-16 20:59
qshape.1.html
7.33
KB
-rw-r--r--
2020-02-16 20:59
regexp_table.5.html
7.89
KB
-rw-r--r--
2020-02-16 20:59
relocated.5.html
7.96
KB
-rw-r--r--
2020-02-16 20:59
scache.8.html
7.5
KB
-rw-r--r--
2020-02-16 20:59
sendmail.1.html
23.52
KB
-rw-r--r--
2020-02-16 20:59
showq.8.html
5.55
KB
-rw-r--r--
2020-02-16 20:59
smtp-sink.1.html
13.2
KB
-rw-r--r--
2020-02-16 20:59
smtp-source.1.html
5.55
KB
-rw-r--r--
2020-02-16 20:59
smtp.8.html
50.41
KB
-rw-r--r--
2020-02-16 20:59
smtpd.8.html
79.32
KB
-rw-r--r--
2020-02-16 20:59
socketmap_table.5.html
4.36
KB
-rw-r--r--
2020-02-16 20:59
spawn.8.html
7.16
KB
-rw-r--r--
2020-02-16 20:59
sqlite_table.5.html
13.42
KB
-rw-r--r--
2020-02-16 20:59
tcp_table.5.html
4.31
KB
-rw-r--r--
2020-02-16 20:59
tlsmgr.8.html
9.85
KB
-rw-r--r--
2020-02-16 20:59
tlsproxy.8.html
14.63
KB
-rw-r--r--
2020-02-16 20:59
trace.8.html
9.51
KB
-rw-r--r--
2020-02-16 20:59
transport.5.html
14.87
KB
-rw-r--r--
2020-02-16 20:59
trivial-rewrite.8.html
19.13
KB
-rw-r--r--
2020-02-16 20:59
verify.8.html
12.06
KB
-rw-r--r--
2020-02-16 20:59
virtual.5.html
15.06
KB
-rw-r--r--
2020-02-16 20:59
virtual.8.html
16.9
KB
-rw-r--r--
2020-02-16 20:59
Save
Rename
<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <title> Postfix manual - proxymap(8) </title> </head> <body> <pre> PROXYMAP(8) PROXYMAP(8) <b>NAME</b> proxymap - Postfix lookup table proxy server <b>SYNOPSIS</b> <b>proxymap</b> [generic Postfix daemon options] <b>DESCRIPTION</b> The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server provides read-only or read-write table lookup service to Postfix processes. These services are implemented with dis- tinct service names: <b>proxymap</b> and <b>proxywrite</b>, respectively. The purpose of these services is: <b>o</b> To overcome chroot restrictions. For example, a chrooted SMTP server needs access to the system passwd file in order to reject mail for non-existent local addresses, but it is not practical to maintain a copy of the passwd file in the chroot jail. The solution: <a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a> = <a href="proxymap.8.html">proxy</a>:unix:passwd.byname $<a href="postconf.5.html#alias_maps">alias_maps</a> <b>o</b> 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 connections" errors. The solution: <a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a> = <a href="proxymap.8.html">proxy</a>:<a href="mysql_table.5.html">mysql</a>:/etc/postfix/virtual_alias.cf The total number of connections is limited by the number of proxymap server processes. <b>o</b> To provide single-updater functionality for lookup tables that do not reliably support multiple writers (i.e. all file-based tables). The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server implements the following requests: <b>open</b> <i>maptype:mapname flags</i> Open the table with type <i>maptype</i> and name <i>mapname</i>, as controlled by <i>flags</i>. The reply includes the <i>maptype</i> dependent flags (to distinguish a fixed string table from a regular expression ta- ble). <b>lookup</b> <i>maptype:mapname flags key</i> Look up the data stored under the requested key. The reply is the request completion status code and the lookup result value. The <i>maptype:mapname</i> and <i>flags</i> are the same as with the <b>open</b> request. <b>update</b> <i>maptype:mapname flags key value</i> Update the data stored under the requested key. The reply is the request completion status code. The <i>maptype:mapname</i> and <i>flags</i> are the same as with the <b>open</b> request. To implement single-updater maps, specify a process limit of 1 in the <a href="master.5.html">master.cf</a> file entry for the <b>proxywrite</b> service. This request is supported in Postfix 2.5 and later. <b>delete</b> <i>maptype:mapname flags key</i> Delete the data stored under the requested key. The reply is the request completion status code. The <i>maptype:mapname</i> and <i>flags</i> are the same as with the <b>open</b> request. This request is supported in Postfix 2.5 and later. <b>sequence</b> <i>maptype:mapname flags function</i> Iterate over the specified database. The <i>function</i> is one of DICT_SEQ_FUN_FIRST or DICT_SEQ_FUN_NEXT. The reply is the request completion status code and a lookup key and result value, if found. This request is supported in Postfix 2.9 and later. The request completion status is one of OK, RETRY, NOKEY (lookup failed because the key was not found), BAD (malformed request) or DENY (the table is not approved for proxy read or update access). There is no <b>close</b> command, nor are tables implicitly closed when a client disconnects. The purpose is to share tables among multiple client processes. <b>SERVER PROCESS MANAGEMENT</b> <a href="proxymap.8.html"><b>proxymap</b>(8)</a> servers run under control by the Postfix <a href="master.8.html"><b>master</b>(8)</a> server. Each server can handle multiple simultaneous connections. When all servers are busy while a client connects, the <a href="master.8.html"><b>master</b>(8)</a> creates a new <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server process, provided that the process limit is not exceeded. Each server terminates after serving at least <b>$<a href="postconf.5.html#max_use">max_use</a></b> clients or after <b>$<a href="postconf.5.html#max_idle">max_idle</a></b> seconds of idle time. <b>SECURITY</b> The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server opens only tables that are approved via the <b><a href="postconf.5.html#proxy_read_maps">proxy_read_maps</a></b> or <b><a href="postconf.5.html#proxy_write_maps">proxy_write_maps</a></b> configuration parameters, does not talk to users, and can run at fixed low privilege, chrooted or not. However, running the proxymap server chrooted severely limits usabil- ity, because it can open only chrooted tables. The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server is not a trusted daemon process, and must not be used to look up sensitive information such as UNIX user or group IDs, mailbox file/directory names or external commands. In Postfix version 2.2 and later, the proxymap client recognizes requests to access a table for security-sensitive purposes, and opens the table directly. This allows the same <a href="postconf.5.html">main.cf</a> setting to be used by sensitive and non-sensitive processes. Postfix-writable data files should be stored under a dedicated direc- tory that is writable only by the Postfix mail system, such as the Postfix-owned <b><a href="postconf.5.html#data_directory">data_directory</a></b>. In particular, Postfix-writable files should never exist in root-owned directories. That would open up a particular type of security hole where ownership of a file or directory does not match the provider of its content. <b>DIAGNOSTICS</b> Problems and transactions are logged to <b>syslogd</b>(8). <b>BUGS</b> The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server provides service to multiple clients, and must therefore not be used for tables that have high-latency lookups. The <a href="proxymap.8.html"><b>proxymap</b>(8)</a> read-write service does not explicitly close lookup tables (even if it did, this could not be relied on, because the process may be terminated between table updates). The read-write ser- vice should therefore not be used with tables that leave persistent storage in an inconsistent state between updates (for example, CDB). Tables that support "sync on update" should be safe (for example, Berkeley DB) as should tables that are implemented by a real DBMS. <b>CONFIGURATION PARAMETERS</b> On busy mail systems a long time may pass before <a href="proxymap.8.html"><b>proxymap</b>(8)</a> relevant changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up. Use the command "<b>postfix reload</b>" to speed up a change. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for more details including examples. <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b> The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con- figuration files. <b><a href="postconf.5.html#data_directory">data_directory</a> (see 'postconf -d' output)</b> The directory with Postfix-writable data files (for example: caches, pseudo-random numbers). <b><a href="postconf.5.html#daemon_timeout">daemon_timeout</a> (18000s)</b> How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer. <b><a href="postconf.5.html#ipc_timeout">ipc_timeout</a> (3600s)</b> The time limit for sending or receiving information over an internal communication channel. <b><a href="postconf.5.html#max_idle">max_idle</a> (100s)</b> The maximum amount of time that an idle Postfix daemon process waits for an incoming connection before terminating voluntarily. <b><a href="postconf.5.html#max_use">max_use</a> (100)</b> The maximal number of incoming connections that a Postfix daemon process will service before terminating voluntarily. <b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b> The process ID of a Postfix command or daemon process. <b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b> The process name of a Postfix command or daemon process. <b><a href="postconf.5.html#proxy_read_maps">proxy_read_maps</a> (see 'postconf -d' output)</b> The lookup tables that the <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server is allowed to access for the read-only service. Available in Postfix 2.5 and later: <b><a href="postconf.5.html#data_directory">data_directory</a> (see 'postconf -d' output)</b> The directory with Postfix-writable data files (for example: caches, pseudo-random numbers). <b><a href="postconf.5.html#proxy_write_maps">proxy_write_maps</a> (see 'postconf -d' output)</b> The lookup tables that the <a href="proxymap.8.html"><b>proxymap</b>(8)</a> server is allowed to access for the read-write service. <b>SEE ALSO</b> <a href="postconf.5.html">postconf(5)</a>, configuration parameters <a href="master.5.html">master(5)</a>, generic daemon options <b>README FILES</b> <a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview <b>LICENSE</b> The Secure Mailer license must be distributed with this software. <b>HISTORY</b> The proxymap service was introduced with Postfix 2.0. <b>AUTHOR(S)</b> 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 PROXYMAP(8) </pre> </body> </html>