mirror of
https://github.com/vdukhovni/postfix
synced 2025-08-22 09:57:34 +00:00
postfix-3.10-20240930
This commit is contained in:
parent
f57aaf90a7
commit
a269182156
@ -28322,9 +28322,22 @@ Apologies for any names omitted.
|
||||
case with lower case, and after replacing spaces with
|
||||
underscores. File: mantools/man2html.
|
||||
|
||||
Cleanaup (no code change): regenerate all man-style pages
|
||||
Cleanup (no code change): regenerate all man-style pages
|
||||
so that the parameter summaries at the end match the text
|
||||
in postconf(5). This also updates embedded man-style
|
||||
comments in Postfix source code. Files: mantools/man2html,
|
||||
proto/aliases, cleanup/cleanup.c, local/local.c, smtpd/smtpd.c,
|
||||
tlsproxy/tlsproxy.c.
|
||||
|
||||
20240930
|
||||
|
||||
Bugfix (defect introduced: Postfix 2.9, date 20111218):
|
||||
with "smtpd_sasl_auth_enable = no", info received with
|
||||
XCLIENT LOGIN was ignored by permit_sasl_authenticated.
|
||||
Problem reported by Antonin Verrier. The fix was to REMOVE
|
||||
a test and to rely solely on the sasl_mechanism property
|
||||
which is always null when a remote SMTP client is not
|
||||
authenticated. File: src/smtpd/smtpd_check.c.
|
||||
|
||||
Cleanup (no code change): regenerated HTML manpages that
|
||||
weren't updated because of a simplistic make(1) dependency.
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
ACCESS(5) ACCESS(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
access - Postfix SMTP server access table
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/access</b>
|
||||
|
||||
<b>postmap -q "</b><i>string</i><b>" /etc/postfix/access</b>
|
||||
|
||||
<b>postmap -q - /etc/postfix/access</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
This document describes access control on remote SMTP client informa-
|
||||
tion: host names, network addresses, and envelope sender or recipient
|
||||
addresses; it is implemented by the Postfix SMTP server. See
|
||||
@ -39,13 +39,13 @@ ACCESS(5) ACCESS(5)
|
||||
a slightly different way as described below under "REGULAR EXPRESSION
|
||||
TABLES" or "TCP-BASED TABLES".
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<i>pattern action</i>
|
||||
@ -60,7 +60,7 @@ ACCESS(5) ACCESS(5)
|
||||
A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>EMAIL ADDRESS PATTERNS IN INDEXED TABLES</b>
|
||||
<b><a name="email_address_patterns_in_indexed_tables">EMAIL ADDRESS PATTERNS IN INDEXED TABLES</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, patterns are tried in the order as
|
||||
listed below:
|
||||
@ -87,7 +87,7 @@ ACCESS(5) ACCESS(5)
|
||||
addresses. The value is specified with the <b><a href="postconf.5.html#smtpd_null_access_lookup_key">smtpd_null_access_lookup_key</a></b>
|
||||
parameter in the Postfix <a href="postconf.5.html"><b>main.cf</b></a> file.
|
||||
|
||||
<b>EMAIL ADDRESS EXTENSION</b>
|
||||
<b><a name="email_address_extension">EMAIL ADDRESS EXTENSION</a></b>
|
||||
When a mail address localpart contains the optional recipient delimiter
|
||||
(e.g., <i>user+foo</i>@<i>domain</i>), the lookup order becomes: <i>user+foo</i>@<i>domain</i>,
|
||||
<i>user</i>@<i>domain</i>, <i>domain</i>, <i>user+foo</i>@, and <i>user</i>@.
|
||||
@ -149,7 +149,7 @@ ACCESS(5) ACCESS(5)
|
||||
|
||||
IPv6 support is available in Postfix 2.2 and later.
|
||||
|
||||
<b>ACCEPT ACTIONS</b>
|
||||
<b><a name="accept_actions">ACCEPT ACTIONS</a></b>
|
||||
<b>OK</b> Accept the address etc. that matches the pattern.
|
||||
|
||||
<i>all-numerical</i>
|
||||
@ -159,7 +159,7 @@ ACCESS(5) ACCESS(5)
|
||||
|
||||
For other accept actions, see "OTHER ACTIONS" below.
|
||||
|
||||
<b>REJECT ACTIONS</b>
|
||||
<b><a name="reject_actions">REJECT ACTIONS</a></b>
|
||||
Postfix version 2.3 and later support enhanced status codes as defined
|
||||
in <a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a>. When no code is specified at the beginning of the <i>text</i>
|
||||
below, Postfix inserts a default enhanced status code of "5.7.1" in the
|
||||
@ -226,7 +226,7 @@ ACCESS(5) ACCESS(5)
|
||||
|
||||
For other reject actions, see "OTHER ACTIONS" below.
|
||||
|
||||
<b>OTHER ACTIONS</b>
|
||||
<b><a name="other_actions">OTHER ACTIONS</a></b>
|
||||
<i>restriction...</i>
|
||||
Apply the named UCE restriction(s) (<b>permit</b>, <b>reject</b>,
|
||||
<b><a href="postconf.5.html#reject_unauth_destination">reject_unauth_destination</a></b>, and so on).
|
||||
@ -343,7 +343,7 @@ ACCESS(5) ACCESS(5)
|
||||
|
||||
This feature is available in Postfix 2.1 and later.
|
||||
|
||||
<b>ENHANCED STATUS CODES</b>
|
||||
<b><a name="enhanced_status_codes">ENHANCED STATUS CODES</a></b>
|
||||
Postfix version 2.3 and later support enhanced status codes as defined
|
||||
in <a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a>. When an enhanced status code is specified in an access
|
||||
table, it is subject to modification. The following transformations are
|
||||
@ -360,7 +360,7 @@ ACCESS(5) ACCESS(5)
|
||||
Postfix SMTP server will transform a sender or recipient DSN
|
||||
status into a generic non-address DSN status (e.g., 4.0.0).
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions. For a description of regular
|
||||
expression lookup table syntax, see <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
|
||||
@ -379,7 +379,7 @@ ACCESS(5) ACCESS(5)
|
||||
feature that parenthesized substrings from the pattern can be interpo-
|
||||
lated as <b>$1</b>, <b>$2</b> and so on.
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is not
|
||||
@ -394,7 +394,7 @@ ACCESS(5) ACCESS(5)
|
||||
|
||||
Actions are the same as with indexed file lookups.
|
||||
|
||||
<b>EXAMPLE</b>
|
||||
<b><a name="example">EXAMPLE</a></b>
|
||||
The following example uses an indexed file, so that the order of table
|
||||
entries does not matter. The example permits access by the client at
|
||||
address 1.2.3.4 but rejects all other clients in 1.2.3.0/24. Instead of
|
||||
@ -412,20 +412,20 @@ ACCESS(5) ACCESS(5)
|
||||
Execute the command "<b>postmap /etc/postfix/access</b>" after editing the
|
||||
file.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The table format does not understand quoting conventions.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, SMTP server
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="transport.5.html">transport(5)</a>, transport:nexthop syntax
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="SMTPD_ACCESS_README.html">SMTPD_ACCESS_README</a>, built-in SMTP server access control
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
ANVIL(8) ANVIL(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
anvil - Postfix session count and request rate control
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>anvil</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="anvil.8.html"><b>anvil</b>(8)</a> server maintains statistics about client connec-
|
||||
tion counts or client request rates. This information can be used to
|
||||
defend against clients that hammer a server with either too many simul-
|
||||
@ -50,7 +50,7 @@ ANVIL(8) ANVIL(8)
|
||||
|
||||
<b>status=0</b>
|
||||
|
||||
<b>MESSAGE RATE CONTROL</b>
|
||||
<b><a name="message_rate_control">MESSAGE RATE CONTROL</a></b>
|
||||
To register a message delivery request send the following request to
|
||||
the <a href="anvil.8.html"><b>anvil</b>(8)</a> server:
|
||||
|
||||
@ -64,7 +64,7 @@ ANVIL(8) ANVIL(8)
|
||||
<b>status=0</b>
|
||||
<b>rate=</b><i>number</i>
|
||||
|
||||
<b>RECIPIENT RATE CONTROL</b>
|
||||
<b><a name="recipient_rate_control">RECIPIENT RATE CONTROL</a></b>
|
||||
To register a recipient request send the following request to the
|
||||
<a href="anvil.8.html"><b>anvil</b>(8)</a> server:
|
||||
|
||||
@ -77,7 +77,7 @@ ANVIL(8) ANVIL(8)
|
||||
<b>status=0</b>
|
||||
<b>rate=</b><i>number</i>
|
||||
|
||||
<b>TLS SESSION NEGOTIATION RATE CONTROL</b>
|
||||
<b><a name="tls_session_negotiation_rate_control">TLS SESSION NEGOTIATION RATE CONTROL</a></b>
|
||||
The features described in this section are available with Postfix 2.3
|
||||
and later.
|
||||
|
||||
@ -107,7 +107,7 @@ ANVIL(8) ANVIL(8)
|
||||
<b>status=0</b>
|
||||
<b>rate=</b><i>number</i>
|
||||
|
||||
<b>AUTH RATE CONTROL</b>
|
||||
<b><a name="auth_rate_control">AUTH RATE CONTROL</a></b>
|
||||
To register an AUTH request send the following request to the <a href="anvil.8.html"><b>anvil</b>(8)</a>
|
||||
server:
|
||||
|
||||
@ -120,7 +120,7 @@ ANVIL(8) ANVIL(8)
|
||||
<b>status=0</b>
|
||||
<b>rate=</b><i>number</i>
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="anvil.8.html"><b>anvil</b>(8)</a> server does not talk to the network or to local users, and
|
||||
can run chrooted at fixed low privilege.
|
||||
|
||||
@ -134,7 +134,7 @@ ANVIL(8) ANVIL(8)
|
||||
clients. To reduce memory usage, reduce the time unit over which state
|
||||
is kept.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
Upon exit, and every <b><a href="postconf.5.html#anvil_status_update_time">anvil_status_update_time</a></b> seconds, the server logs
|
||||
@ -143,7 +143,7 @@ ANVIL(8) ANVIL(8)
|
||||
In order to avoid unnecessary overhead, no measurements are done for
|
||||
activity that isn't concurrency limited or rate limited.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Systems behind network address translating routers or proxies appear to
|
||||
have the same client address and can run into connection count and/or
|
||||
rate limits falsely.
|
||||
@ -159,7 +159,7 @@ ANVIL(8) ANVIL(8)
|
||||
service should always register connect/disconnect events even when it
|
||||
does not explicitly limit them.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
On low-traffic mail systems, changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automati-
|
||||
cally as <a href="anvil.8.html"><b>anvil</b>(8)</a> processes run for only a limited amount of time. On
|
||||
other mail systems, use the command "<b>postfix reload</b>" to speed up a
|
||||
@ -214,18 +214,18 @@ ANVIL(8) ANVIL(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
|
||||
<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>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="TUNING_README.html">TUNING_README</a>, performance tuning
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The anvil service is available in Postfix 2.2 and later.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
BOUNCE(5) BOUNCE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
bounce - Postfix bounce message template format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a> = /etc/postfix/bounce.cf</b>
|
||||
|
||||
<b>postconf -b</b> [<i>template</i><b>_</b><i>file</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="bounce.8.html"><b>bounce</b>(8)</a> server produces delivery status notification
|
||||
(DSN) messages for undeliverable mail, delayed mail, successful deliv-
|
||||
ery or address verification requests.
|
||||
@ -29,7 +29,7 @@ BOUNCE(5) BOUNCE(5)
|
||||
plate file, followed by the specific details of bounce template for-
|
||||
mats.
|
||||
|
||||
<b>GENERAL PROCEDURE</b>
|
||||
<b><a name="general_procedure">GENERAL PROCEDURE</a></b>
|
||||
To create a customized bounce template file, create a temporary copy of
|
||||
the file <b>/etc/postfix/bounce.cf.default</b> and edit the temporary file.
|
||||
|
||||
@ -51,7 +51,7 @@ BOUNCE(5) BOUNCE(5)
|
||||
/etc/postfix/<a href="postconf.5.html">main.cf</a>:
|
||||
<a href="postconf.5.html#bounce_template_file">bounce_template_file</a> = /etc/postfix/bounce.cf
|
||||
|
||||
<b>TEMPLATE FILE FORMAT</b>
|
||||
<b><a name="template_file_format">TEMPLATE FILE FORMAT</a></b>
|
||||
The template file can specify templates for failed mail, delayed mail,
|
||||
successful delivery or for address verification. These templates are
|
||||
named <b>failure_template</b>, <b>delay_template</b>, <b>success_template</b> and <b>ver-</b>
|
||||
@ -99,7 +99,7 @@ BOUNCE(5) BOUNCE(5)
|
||||
Examples of all templates can be found in the file <b>bounce.cf.default</b> in
|
||||
the Postfix configuration directory.
|
||||
|
||||
<b>TEMPLATE HEADER FORMAT</b>
|
||||
<b><a name="template_header_format">TEMPLATE HEADER FORMAT</a></b>
|
||||
The first portion of a bounce template consists of optional template
|
||||
headers. Some become message headers in the delivery status notifica-
|
||||
tion; some control the formatting of that notification. Headers not
|
||||
@ -137,7 +137,7 @@ BOUNCE(5) BOUNCE(5)
|
||||
<b>o</b> Template message headers must contain ASCII characters only, and
|
||||
must not contain ASCII null characters.
|
||||
|
||||
<b>TEMPLATE MESSAGE TEXT FORMAT</b>
|
||||
<b><a name="template_message_text_format">TEMPLATE MESSAGE TEXT FORMAT</a></b>
|
||||
The second portion of a bounce template consists of message text. As
|
||||
the above example shows, template message text may contain <a href="postconf.5.html">main.cf</a>
|
||||
$parameters. Besides the parameters that are defined in <a href="postconf.5.html">main.cf</a>, the
|
||||
@ -180,14 +180,14 @@ BOUNCE(5) BOUNCE(5)
|
||||
needed because Postfix appends ASCII text after the message tem-
|
||||
plate when it sends a delivery status notification.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="bounce.8.html">bounce(8)</a>, Postfix delivery status notifications
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The Postfix bounce template format was originally developed by Nicolas
|
||||
Riendeau.
|
||||
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
BOUNCE(8) BOUNCE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
bounce - Postfix delivery status reports
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>bounce</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="bounce.8.html"><b>bounce</b>(8)</a> daemon maintains per-message log files with delivery sta-
|
||||
tus information. Each log file is named after the queue file that it
|
||||
corresponds to, and is kept in a queue subdirectory named after the
|
||||
@ -39,7 +39,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
This is used by clients that cannot retry transactions by themselves,
|
||||
and that depend on retry logic in their own client.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
<a href="https://tools.ietf.org/html/rfc2045">RFC 2045</a> (Format of Internet Message Bodies)
|
||||
<a href="https://tools.ietf.org/html/rfc2822">RFC 2822</a> (Internet Message Format)
|
||||
@ -51,10 +51,10 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="https://tools.ietf.org/html/rfc6532">RFC 6532</a> (Internationalized Message Format)
|
||||
<a href="https://tools.ietf.org/html/rfc6533">RFC 6533</a> (Internationalized Delivery Status Notifications)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="bounce.8.html"><b>bounce</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -166,12 +166,12 @@ BOUNCE(8) BOUNCE(8)
|
||||
<b><a href="postconf.5.html#header_from_format">header_from_format</a> (standard)</b>
|
||||
The format of the Postfix-generated <b>From:</b> header.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/bounce/* non-delivery records
|
||||
/var/spool/postfix/defer/* non-delivery records
|
||||
/var/spool/postfix/trace/* delivery status records
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="bounce.5.html">bounce(5)</a>, bounce message template format
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -180,7 +180,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
CANONICAL(5) CANONICAL(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
canonical - Postfix canonical table format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/canonical</b>
|
||||
|
||||
<b>postmap -q "</b><i>string</i><b>" /etc/postfix/canonical</b>
|
||||
|
||||
<b>postmap -q - /etc/postfix/canonical</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The optional <a href="canonical.5.html"><b>canonical</b>(5)</a> table specifies an address mapping for local
|
||||
and non-local addresses. The mapping is used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon,
|
||||
before mail is stored into the queue. The address mapping is recur-
|
||||
@ -59,13 +59,13 @@ CANONICAL(5) CANONICAL(5)
|
||||
port or with <a href="ADDRESS_REWRITING_README.html#aliases">local aliasing</a>. To change the destination but not the
|
||||
headers, use the <a href="virtual.5.html"><b>virtual</b>(5)</a> or <a href="aliases.5.html"><b>aliases</b>(5)</a> map instead.
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<i>pattern address</i>
|
||||
@ -80,7 +80,7 @@ CANONICAL(5) CANONICAL(5)
|
||||
A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, each <i>user</i>@<i>domain</i> query produces a
|
||||
sequence of query patterns as described below.
|
||||
@ -130,7 +130,7 @@ CANONICAL(5) CANONICAL(5)
|
||||
In the above example, Postfix may contact a remote server if the
|
||||
recipient is rewritten to a remote address.
|
||||
|
||||
<b>RESULT ADDRESS REWRITING</b>
|
||||
<b><a name="result_address_rewriting">RESULT ADDRESS REWRITING</a></b>
|
||||
The lookup result is subject to address rewriting:
|
||||
|
||||
<b>o</b> When the result has the form @<i>otherdomain</i>, the result becomes
|
||||
@ -142,7 +142,7 @@ CANONICAL(5) CANONICAL(5)
|
||||
<b>o</b> When "<b><a href="postconf.5.html#append_dot_mydomain">append_dot_mydomain</a>=yes</b>", append "<b>.$<a href="postconf.5.html#mydomain">mydomain</a></b>" to addresses
|
||||
without ".domain".
|
||||
|
||||
<b>ADDRESS EXTENSION</b>
|
||||
<b><a name="address_extension">ADDRESS EXTENSION</a></b>
|
||||
When a mail address localpart contains the optional recipient delimiter
|
||||
(e.g., <i>user+foo</i>@<i>domain</i>), the lookup order becomes: <i>user+foo</i>@<i>domain</i>,
|
||||
<i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>.
|
||||
@ -151,7 +151,7 @@ CANONICAL(5) CANONICAL(5)
|
||||
unmatched address extension (<i>+foo</i>) is propagated to the result of table
|
||||
lookup.
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions. For a description of regular
|
||||
expression lookup table syntax, see <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
|
||||
@ -168,7 +168,7 @@ CANONICAL(5) CANONICAL(5)
|
||||
feature that parenthesized substrings from the pattern can be interpo-
|
||||
lated as <b>$1</b>, <b>$2</b> and so on.
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is not
|
||||
@ -180,10 +180,10 @@ CANONICAL(5) CANONICAL(5)
|
||||
|
||||
Results are the same as with indexed file lookups.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The table format does not understand quoting conventions.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant. The text
|
||||
below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for more
|
||||
details including examples.
|
||||
@ -257,17 +257,17 @@ CANONICAL(5) CANONICAL(5)
|
||||
<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter, and adding missing head-
|
||||
ers.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue mail
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="virtual.5.html">virtual(5)</a>, <a href="ADDRESS_REWRITING_README.html#virtual">virtual aliasing</a>
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
cidr_table - format of Postfix CIDR tables
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="cidr_table.5.html">cidr</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="cidr_table.5.html">cidr</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional lookup tables. These tables are
|
||||
usually in <b>dbm</b> or <b>db</b> format. Alternatively, lookup tables can be spec-
|
||||
ified in CIDR (Classless Inter-Domain Routing) form. In this case, each
|
||||
@ -28,7 +28,7 @@ CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
To test lookup tables, use the "<b>postmap -q</b>" command as described in the
|
||||
SYNOPSIS above.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The general form of a Postfix CIDR table is:
|
||||
|
||||
<i>pattern result</i>
|
||||
@ -73,11 +73,11 @@ CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
Patterns are applied in the order as specified in the table, until a
|
||||
pattern is found that matches the search string.
|
||||
|
||||
<b>ADDRESS PATTERN SYNTAX</b>
|
||||
<b><a name="address_pattern_syntax">ADDRESS PATTERN SYNTAX</a></b>
|
||||
Postfix CIDR tables are pattern-based. A pattern is either a <i>net-</i>
|
||||
<i>work</i><b>_</b><i>address</i> which requires an exact match, or a <i>network</i><b>_</b><i>address/pre-</i>
|
||||
<i>fix</i><b>_</b><i>length</i> where the <i>prefix</i><b>_</b><i>length</i> part specifies the length of the
|
||||
@ -99,7 +99,7 @@ CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
Note: address information may be enclosed inside "[]" but this form is
|
||||
not required.
|
||||
|
||||
<b>INLINE SPECIFICATION</b>
|
||||
<b><a name="inline_specification">INLINE SPECIFICATION</a></b>
|
||||
The contents of a table may be specified in the table name (Postfix 3.7
|
||||
and later). The basic syntax is:
|
||||
|
||||
@ -122,7 +122,7 @@ CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
Note: if a rule contains <b>$</b>, specify <b>$$</b> to keep Postfix from trying to
|
||||
do <i>$name</i> expansion as it evaluates a parameter value.
|
||||
|
||||
<b>EXAMPLE SMTPD ACCESS MAP</b>
|
||||
<b><a name="example_smtpd_access_map">EXAMPLE SMTPD ACCESS MAP</a></b>
|
||||
/etc/postfix/<a href="postconf.5.html">main.cf</a>:
|
||||
<a href="postconf.5.html#smtpd_client_restrictions">smtpd_client_restrictions</a> = ... <a href="cidr_table.5.html">cidr</a>:/etc/postfix/client.cidr ...
|
||||
|
||||
@ -134,15 +134,15 @@ CIDR_TABLE(5) CIDR_TABLE(5)
|
||||
2001:db8::1 OK
|
||||
2001:db8::/32 REJECT
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<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
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
CIDR table support was introduced with Postfix version 2.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
BOUNCE(8) BOUNCE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
bounce - Postfix delivery status reports
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>bounce</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="bounce.8.html"><b>bounce</b>(8)</a> daemon maintains per-message log files with delivery sta-
|
||||
tus information. Each log file is named after the queue file that it
|
||||
corresponds to, and is kept in a queue subdirectory named after the
|
||||
@ -39,7 +39,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
This is used by clients that cannot retry transactions by themselves,
|
||||
and that depend on retry logic in their own client.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
<a href="https://tools.ietf.org/html/rfc2045">RFC 2045</a> (Format of Internet Message Bodies)
|
||||
<a href="https://tools.ietf.org/html/rfc2822">RFC 2822</a> (Internet Message Format)
|
||||
@ -51,10 +51,10 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="https://tools.ietf.org/html/rfc6532">RFC 6532</a> (Internationalized Message Format)
|
||||
<a href="https://tools.ietf.org/html/rfc6533">RFC 6533</a> (Internationalized Delivery Status Notifications)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="bounce.8.html"><b>bounce</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -166,12 +166,12 @@ BOUNCE(8) BOUNCE(8)
|
||||
<b><a href="postconf.5.html#header_from_format">header_from_format</a> (standard)</b>
|
||||
The format of the Postfix-generated <b>From:</b> header.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/bounce/* non-delivery records
|
||||
/var/spool/postfix/defer/* non-delivery records
|
||||
/var/spool/postfix/trace/* delivery status records
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="bounce.5.html">bounce(5)</a>, bounce message template format
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -180,7 +180,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
DISCARD(8) DISCARD(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
discard - Postfix discard mail delivery agent
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>discard</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="discard.8.html"><b>discard</b>(8)</a> delivery agent processes delivery requests from
|
||||
the queue manager. Each request specifies a queue file, a sender
|
||||
address, a next-hop destination that is treated as the reason for dis-
|
||||
@ -29,20 +29,20 @@ DISCARD(8) DISCARD(8)
|
||||
|
||||
Delivery status reports are sent to the <a href="trace.8.html"><b>trace</b>(8)</a> daemon as appropriate.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="discard.8.html"><b>discard</b>(8)</a> mailer is not security-sensitive. It does not talk to
|
||||
the network, and can be run chrooted at fixed low privilege.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced Status Codes)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces and of other trouble.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="discard.8.html"><b>discard</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -99,7 +99,7 @@ DISCARD(8) DISCARD(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="error.8.html">error(8)</a>, Postfix error delivery agent
|
||||
@ -109,10 +109,10 @@ DISCARD(8) DISCARD(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.2.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,18 +7,18 @@
|
||||
</head> <body> <pre>
|
||||
DNSBLOG(8) DNSBLOG(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
dnsblog - Postfix DNS allow/denylist logger
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>dnsblog</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="dnsblog.8.html"><b>dnsblog</b>(8)</a> server implements an ad-hoc DNS allow/denylist lookup
|
||||
service. This may eventually be replaced by an UDP client that is built
|
||||
directly into the <a href="postscreen.8.html"><b>postscreen</b>(8)</a> server.
|
||||
|
||||
<b>PROTOCOL</b>
|
||||
<b><a name="protocol">PROTOCOL</a></b>
|
||||
With each connection, the <a href="dnsblog.8.html"><b>dnsblog</b>(8)</a> server receives a DNS
|
||||
allow/denylist domain name, an IP address, and an ID. If the IP
|
||||
address is listed under the DNS allow/denylist, the <a href="dnsblog.8.html"><b>dnsblog</b>(8)</a> server
|
||||
@ -29,10 +29,10 @@ DNSBLOG(8) DNSBLOG(8)
|
||||
reply, or a negative reply that contains no SOA record. Finally, the
|
||||
<a href="dnsblog.8.html"><b>dnsblog</b>(8)</a> server closes the connection.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="dnsblog.8.html"><b>dnsblog</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -77,16 +77,16 @@ DNSBLOG(8) DNSBLOG(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.8.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
ERROR(8) ERROR(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
error - Postfix error/retry mail delivery agent
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>error</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="error.8.html"><b>error</b>(8)</a> delivery agent processes delivery requests from
|
||||
the queue manager. Each request specifies a queue file, a sender
|
||||
address, the reason for non-delivery (specified as the next-hop desti-
|
||||
@ -30,20 +30,20 @@ ERROR(8) ERROR(8)
|
||||
Delivery status reports are sent to the <a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or <a href="trace.8.html"><b>trace</b>(8)</a>
|
||||
daemon as appropriate.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="error.8.html"><b>error</b>(8)</a> mailer is not security-sensitive. It does not talk to the
|
||||
network, and can be run chrooted at fixed low privilege.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced Status Codes)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces and of other trouble.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="error.8.html"><b>error</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -112,7 +112,7 @@ ERROR(8) ERROR(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="discard.8.html">discard(8)</a>, Postfix discard delivery agent
|
||||
@ -122,7 +122,7 @@ ERROR(8) ERROR(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
FLUSH(8) FLUSH(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
flush - Postfix fast flush server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>flush</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="flush.8.html"><b>flush</b>(8)</a> server maintains a record of deferred mail by destination.
|
||||
This information is used to improve the performance of the SMTP <b>ETRN</b>
|
||||
request, and of its command-line equivalent, "<b>sendmail -qR</b>" or
|
||||
@ -56,15 +56,15 @@ FLUSH(8) FLUSH(8)
|
||||
|
||||
<b>purge</b> Do a <b>refresh</b> for all per-destination logfiles.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="flush.8.html"><b>flush</b>(8)</a> server is not security-sensitive. It does not talk to the
|
||||
network, and it does not talk to local users. The fast flush server
|
||||
can run chrooted at fixed low privilege.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Fast flush logfiles are truncated only after a "send" request, not when
|
||||
mail is actually delivered, and therefore can accumulate outdated or
|
||||
redundant data. In order to maintain sanity, "refresh" must be executed
|
||||
@ -78,7 +78,7 @@ FLUSH(8) FLUSH(8)
|
||||
destination because such mail typically only has recipients in one
|
||||
domain.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="flush.8.html"><b>flush</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -144,10 +144,10 @@ FLUSH(8) FLUSH(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/flush, "fast flush" logfiles.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, SMTP server
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -156,13 +156,13 @@ FLUSH(8) FLUSH(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ETRN_README.html">ETRN_README</a>, Postfix ETRN howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 1.0.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
GENERIC(5) GENERIC(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
generic - Postfix generic table format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/generic</b>
|
||||
|
||||
<b>postmap -q "</b><i>string</i><b>" /etc/postfix/generic</b>
|
||||
|
||||
<b>postmap -q - /etc/postfix/generic</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The optional <a href="generic.5.html"><b>generic</b>(5)</a> table specifies an address mapping that applies
|
||||
when mail is delivered. This is the opposite of <a href="canonical.5.html"><b>canonical</b>(5)</a> mapping,
|
||||
which applies when mail is received.
|
||||
@ -48,13 +48,13 @@ GENERIC(5) GENERIC(5)
|
||||
a slightly different way as described below under "REGULAR EXPRESSION
|
||||
TABLES" or "TCP-BASED TABLES".
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<i>pattern result</i>
|
||||
@ -69,7 +69,7 @@ GENERIC(5) GENERIC(5)
|
||||
A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, each <i>user</i>@<i>domain</i> query produces a
|
||||
sequence of query patterns as described below.
|
||||
@ -90,7 +90,7 @@ GENERIC(5) GENERIC(5)
|
||||
Replace other addresses in <i>domain</i> by <i>address</i>. This form has the
|
||||
lowest precedence.
|
||||
|
||||
<b>RESULT ADDRESS REWRITING</b>
|
||||
<b><a name="result_address_rewriting">RESULT ADDRESS REWRITING</a></b>
|
||||
The lookup result is subject to address rewriting:
|
||||
|
||||
<b>o</b> When the result has the form @<i>otherdomain</i>, the result becomes
|
||||
@ -102,7 +102,7 @@ GENERIC(5) GENERIC(5)
|
||||
<b>o</b> When "<b><a href="postconf.5.html#append_dot_mydomain">append_dot_mydomain</a>=yes</b>", append "<b>.$<a href="postconf.5.html#mydomain">mydomain</a></b>" to addresses
|
||||
without ".domain".
|
||||
|
||||
<b>ADDRESS EXTENSION</b>
|
||||
<b><a name="address_extension">ADDRESS EXTENSION</a></b>
|
||||
When a mail address localpart contains the optional recipient delimiter
|
||||
(e.g., <i>user+foo</i>@<i>domain</i>), the lookup order becomes: <i>user+foo</i>@<i>domain</i>,
|
||||
<i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>.
|
||||
@ -111,7 +111,7 @@ GENERIC(5) GENERIC(5)
|
||||
unmatched address extension (<i>+foo</i>) is propagated to the result of table
|
||||
lookup.
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions. For a description of regular
|
||||
expression lookup table syntax, see <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
|
||||
@ -128,7 +128,7 @@ GENERIC(5) GENERIC(5)
|
||||
feature that parenthesized substrings from the pattern can be interpo-
|
||||
lated as <b>$1</b>, <b>$2</b> and so on.
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is
|
||||
@ -140,7 +140,7 @@ GENERIC(5) GENERIC(5)
|
||||
|
||||
Results are the same as with indexed file lookups.
|
||||
|
||||
<b>EXAMPLE</b>
|
||||
<b><a name="example">EXAMPLE</a></b>
|
||||
The following shows a generic mapping with an indexed file. When mail
|
||||
is sent to a remote host via SMTP, this replaces <i>his@localdomain.local</i>
|
||||
by his ISP mail address, replaces <i>her@localdomain.local</i> by her ISP mail
|
||||
@ -161,10 +161,10 @@ GENERIC(5) GENERIC(5)
|
||||
find out what tables your system supports use the command "<b>postconf</b>
|
||||
<b>-m</b>".
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The table format does not understand quoting conventions.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant. The text
|
||||
below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for more
|
||||
details including examples.
|
||||
@ -204,20 +204,20 @@ GENERIC(5) GENERIC(5)
|
||||
<i>name</i>-request address localparts when the <a href="postconf.5.html#recipient_delimiter">recipient_delimiter</a> is
|
||||
set to "-".
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="smtp.8.html">smtp(8)</a>, Postfix SMTP client
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="STANDARD_CONFIGURATION_README.html">STANDARD_CONFIGURATION_README</a>, configuration examples
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
A genericstable feature appears in the Sendmail MTA.
|
||||
|
||||
This feature is available in Postfix 2.2 and later.
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
<a href="postconf.5.html#header_checks">header_checks</a> - Postfix built-in content inspection
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b><a href="postconf.5.html#header_checks">header_checks</a> = <a href="pcre_table.5.html">pcre</a>:/etc/postfix/header_checks</b>
|
||||
<b><a href="postconf.5.html#mime_header_checks">mime_header_checks</a> = <a href="pcre_table.5.html">pcre</a>:/etc/postfix/mime_header_checks</b>
|
||||
<b><a href="postconf.5.html#nested_header_checks">nested_header_checks</a> = <a href="pcre_table.5.html">pcre</a>:/etc/postfix/nested_header_checks</b>
|
||||
@ -26,7 +26,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="pcre_table.5.html">pcre</a>:/etc/postfix/</b><i>filename</i>
|
||||
<b>postmap -q - <a href="pcre_table.5.html">pcre</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
This document describes access control on the content of message head-
|
||||
ers and message body lines; it is implemented by the Postfix <a href="cleanup.8.html"><b>cleanup</b>(8)</a>
|
||||
server before mail is queued. See <a href="access.5.html"><b>access</b>(5)</a> for access control on
|
||||
@ -48,7 +48,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
archives. See the documents referenced below in the README FILES sec-
|
||||
tion if you need more sophisticated content analysis.
|
||||
|
||||
<b>FILTERS WHILE RECEIVING MAIL</b>
|
||||
<b><a name="filters_while_receiving_mail">FILTERS WHILE RECEIVING MAIL</a></b>
|
||||
Postfix implements the following four built-in content inspection
|
||||
classes while receiving mail:
|
||||
|
||||
@ -75,7 +75,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
With Postfix versions before 2.0, all content after the initial
|
||||
message headers is treated as body content.
|
||||
|
||||
<b>FILTERS AFTER RECEIVING MAIL</b>
|
||||
<b><a name="filters_after_receiving_mail">FILTERS AFTER RECEIVING MAIL</a></b>
|
||||
Postfix supports a subset of the built-in content inspection classes
|
||||
after the message is received:
|
||||
|
||||
@ -85,7 +85,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
|
||||
This feature is available in Postfix 2.7 and later.
|
||||
|
||||
<b>FILTERS WHILE DELIVERING MAIL</b>
|
||||
<b><a name="filters_while_delivering_mail">FILTERS WHILE DELIVERING MAIL</a></b>
|
||||
Postfix supports all four content inspection classes while delivering
|
||||
mail via SMTP.
|
||||
|
||||
@ -98,12 +98,12 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
<b><a href="postconf.5.html#smtp_body_checks">smtp_body_checks</a></b> (default: empty)
|
||||
These features are available in Postfix 2.5 and later.
|
||||
|
||||
<b>COMPATIBILITY</b>
|
||||
<b><a name="compatibility">COMPATIBILITY</a></b>
|
||||
With Postfix version 2.2 and earlier specify "<b>postmap -fq</b>" to query a
|
||||
table that contains case sensitive patterns. By default, <a href="regexp_table.5.html">regexp</a>: and
|
||||
<a href="pcre_table.5.html">pcre</a>: patterns are case insensitive.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
This document assumes that header and <a href="postconf.5.html#body_checks">body_checks</a> rules are specified
|
||||
in the form of Postfix regular expression lookup tables. Usually the
|
||||
best performance is obtained with <b>pcre</b> (Perl Compatible Regular Expres-
|
||||
@ -145,13 +145,13 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
A pattern/action line starts with non-whitespace text. A line
|
||||
that starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
For each line of message input, the patterns are applied in the order
|
||||
as specified in the table. When a pattern is found that matches the
|
||||
input line, the corresponding action is executed and then the next
|
||||
input line is inspected.
|
||||
|
||||
<b>TEXT SUBSTITUTION</b>
|
||||
<b><a name="text_substitution">TEXT SUBSTITUTION</a></b>
|
||||
Substitution of substrings from the matched expression into the <i>action</i>
|
||||
string is possible using the conventional Perl syntax (<b>$1</b>, <b>$2</b>, etc.).
|
||||
The macros in the result string may need to be written as <b>${n}</b> or <b>$(n)</b>
|
||||
@ -161,7 +161,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
the expression does not match, substitutions are not available for
|
||||
negated patterns.
|
||||
|
||||
<b>ACTIONS</b>
|
||||
<b><a name="actions">ACTIONS</a></b>
|
||||
Action names are case insensitive. They are shown in upper case for
|
||||
consistency with other Postfix documentation.
|
||||
|
||||
@ -369,7 +369,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
useful for debugging and for testing a pattern before applying
|
||||
more drastic actions.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Empty lines never match, because some map types mis-behave when given a
|
||||
zero-length search string. This limitation may be removed for regular
|
||||
expression tables in a future release.
|
||||
@ -395,7 +395,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
before they are deleted. Examples are: <b>Bcc:</b>, <b>Content-Length:</b>,
|
||||
<b>Return-Path:</b>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
<b><a href="postconf.5.html#body_checks">body_checks</a> (empty)</b>
|
||||
Optional lookup tables for content inspection as specified in
|
||||
the <a href="header_checks.5.html"><b>body_checks</b>(5)</a> manual page.
|
||||
@ -422,7 +422,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
<b><a href="postconf.5.html#disable_mime_input_processing">disable_mime_input_processing</a> (no)</b>
|
||||
Turn off MIME processing while receiving mail.
|
||||
|
||||
<b>EXAMPLES</b>
|
||||
<b><a name="examples">EXAMPLES</a></b>
|
||||
Header pattern to block attachments with bad file name extensions. For
|
||||
convenience, the PCRE /x flag is specified, so that there is no need to
|
||||
collapse the pattern into a single line of text. The purpose of the
|
||||
@ -450,7 +450,7 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
/^<iframe src=(3D)?cid:.* height=(3D)?0 width=(3D)?0>$/
|
||||
REJECT IFRAME vulnerability exploit
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue Postfix message
|
||||
<a href="pcre_table.5.html">pcre_table(5)</a>, format of PCRE lookup tables
|
||||
<a href="regexp_table.5.html">regexp_table(5)</a>, format of POSIX regular expression tables
|
||||
@ -461,13 +461,13 @@ HEADER_CHECKS(5) HEADER_CHECKS(5)
|
||||
<a href="https://tools.ietf.org/html/rfc2045">RFC 2045</a>, base64 and quoted-printable encoding rules
|
||||
<a href="https://tools.ietf.org/html/rfc2047">RFC 2047</a>, message header encoding for non-ASCII text
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="CONTENT_INSPECTION_README.html">CONTENT_INSPECTION_README</a>, Postfix content inspection overview
|
||||
<a href="BUILTIN_FILTER_README.html">BUILTIN_FILTER_README</a>, Postfix built-in content inspection
|
||||
<a href="BACKSCATTER_README.html">BACKSCATTER_README</a>, blocking returned forged mail
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
ldap_table - Postfix LDAP client configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="ldap_table.5.html">ldap</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="ldap_table.5.html">ldap</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -37,7 +37,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
For details about LDAP SSL and STARTTLS, see the section on SSL and
|
||||
STARTTLS below.
|
||||
|
||||
<b>LIST MEMBERSHIP</b>
|
||||
<b><a name="list_membership">LIST MEMBERSHIP</a></b>
|
||||
When using LDAP to store lists such as $<a href="postconf.5.html#mynetworks">mynetworks</a>, $<a href="postconf.5.html#mydestination">mydestination</a>,
|
||||
$<a href="postconf.5.html#relay_domains">relay_domains</a>, $<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a>, etc., it is important to under-
|
||||
stand that the table must store each list member as a separate key. The
|
||||
@ -60,7 +60,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
query_filter = domain=%s
|
||||
result_attribute = domain
|
||||
|
||||
<b>GENERAL LDAP PARAMETERS</b>
|
||||
<b><a name="general_ldap_parameters">GENERAL LDAP PARAMETERS</a></b>
|
||||
In the text below, default values are given in parentheses. Note:
|
||||
don't use quotes in these variables; at least, not until the Postfix
|
||||
configuration routines understand how to deal with quoted strings.
|
||||
@ -484,7 +484,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
<b>debuglevel (default: 0)</b>
|
||||
What level to set for debugging in the OpenLDAP libraries.
|
||||
|
||||
<b>LDAP SASL PARAMETERS</b>
|
||||
<b><a name="ldap_sasl_parameters">LDAP SASL PARAMETERS</a></b>
|
||||
If you're using the OpenLDAP libraries compiled with SASL support,
|
||||
Postfix 2.8 and later built with LDAP SASL support as described in
|
||||
<a href="LDAP_README.html">LDAP_README</a> can authenticate to LDAP servers via SASL.
|
||||
@ -524,7 +524,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
The minimum required sasl security factor required to establish
|
||||
a connection.
|
||||
|
||||
<b>LDAP SSL AND STARTTLS PARAMETERS</b>
|
||||
<b><a name="ldap_ssl_and_starttls_parameters">LDAP SSL AND STARTTLS PARAMETERS</a></b>
|
||||
If you're using the OpenLDAP libraries compiled with SSL support, Post-
|
||||
fix can connect to LDAP SSL servers and can issue the STARTTLS command.
|
||||
|
||||
@ -621,7 +621,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
<b>tls_cipher_suite (No default)</b>
|
||||
Cipher suite to use in SSL/TLS negotiations.
|
||||
|
||||
<b>EXAMPLE</b>
|
||||
<b><a name="example">EXAMPLE</a></b>
|
||||
Here's a basic example for using LDAP to look up <a href="local.8.html">local(8)</a> aliases.
|
||||
Assume that in <a href="postconf.5.html">main.cf</a>, you have:
|
||||
|
||||
@ -654,7 +654,7 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
<a href="postconf.5.html">main.cf</a>, which is normally world-readable. Support for this form will
|
||||
be removed in a future Postfix version.
|
||||
|
||||
<b>OTHER OBSOLETE FEATURES</b>
|
||||
<b><a name="other_obsolete_features">OTHER OBSOLETE FEATURES</a></b>
|
||||
<b>result_filter (No default)</b>
|
||||
For backwards compatibility with the pre 2.2 LDAP clients,
|
||||
<b>result_filter</b> can for now be used instead of <b>result_format</b>, when
|
||||
@ -662,17 +662,17 @@ LDAP_TABLE(5) LDAP_TABLE(5)
|
||||
reflects the function of the parameter. This compatibility
|
||||
interface may be removed in a future release.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="mysql_table.5.html">mysql_table(5)</a>, MySQL lookup tables
|
||||
<a href="pgsql_table.5.html">pgsql_table(5)</a>, PostgreSQL lookup tables
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="LDAP_README.html">LDAP_README</a>, Postfix LDAP client guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
lmdb_table - Postfix LMDB adapter
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap <a href="lmdb_table.5.html">lmdb</a>:/etc/postfix/</b><i>filename</i>
|
||||
<b>postmap -i <a href="lmdb_table.5.html">lmdb</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
@ -20,13 +20,13 @@ LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
<b>postmap -q "</b><i>key</i><b>" <a href="lmdb_table.5.html">lmdb</a>:/etc/postfix/</b><i>filename</i>
|
||||
<b>postmap -q - <a href="lmdb_table.5.html">lmdb</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix LMDB adapter provides access to a persistent, mem-
|
||||
ory-mapped, key-value store. The database size is limited only by the
|
||||
size of the memory address space (typically 31 or 47 bits on 32-bit or
|
||||
64-bit CPUs, respectively) and by the available file system space.
|
||||
|
||||
<b>REQUESTS</b>
|
||||
<b><a name="requests">REQUESTS</a></b>
|
||||
The LMDB adapter supports all Postfix lookup table operations. This
|
||||
makes LMDB suitable for Postfix address rewriting, routing, access
|
||||
policies, caches, or any information that can be stored under a fixed
|
||||
@ -44,7 +44,7 @@ LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
Changes to an LMDB database do not trigger an automatic daemon restart,
|
||||
and do not require a daemon restart with "<b>postfix reload</b>".
|
||||
|
||||
<b>RELIABILITY</b>
|
||||
<b><a name="reliability">RELIABILITY</a></b>
|
||||
LMDB's copy-on-write architecture provides safe updates, at the cost of
|
||||
using more space than some other flat-file databases. Read operations
|
||||
are memory-mapped for speed. Write operations are not memory-mapped to
|
||||
@ -54,7 +54,7 @@ LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
ing requests through the <a href="proxymap.8.html">proxymap(8)</a> service. This makes LMDB suitable
|
||||
as a shared cache for <a href="verify.8.html">verify(8)</a> or <a href="postscreen.8.html">postscreen(8)</a> services.
|
||||
|
||||
<b>SYNCHRONIZATION</b>
|
||||
<b><a name="synchronization">SYNCHRONIZATION</a></b>
|
||||
The Postfix LMDB adapter does not use LMDB's built-in locking scheme,
|
||||
because that would require world-writable lockfiles and would violate
|
||||
the Postfix security model. Instead, Postfix uses fcntl(2) locks with
|
||||
@ -71,7 +71,7 @@ LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
neous database requests, then it must protect its transactions with
|
||||
in-process locks, in addition to the per-process fcntl(2) locks.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Short-lived programs automatically pick up changes to <a href="postconf.5.html">main.cf</a>. With
|
||||
long-running daemon programs, Use the command "<b>postfix reload</b>" after a
|
||||
configuration change.
|
||||
@ -79,19 +79,19 @@ LMDB_TABLE(5) LMDB_TABLE(5)
|
||||
<b><a href="postconf.5.html#lmdb_map_size">lmdb_map_size</a> (16777216)</b>
|
||||
The initial OpenLDAP LMDB database size limit in bytes.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.1.html">postconf(1)</a>, Postfix supported lookup tables
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table maintenance
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="LMDB_README.html">LMDB_README</a>, Postfix OpenLDAP LMDB howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
LMDB support was introduced with Postfix version 2.11.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
SMTP,(LMTP) SMTP,(LMTP)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
smtp, lmtp - Postfix SMTP+LMTP client
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>smtp</b> [generic Postfix daemon options] [flags=DORX]
|
||||
|
||||
<b>lmtp</b> [generic Postfix daemon options] [flags=DORX]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix SMTP+LMTP client implements the SMTP and LMTP mail delivery
|
||||
protocols. It processes message delivery requests from the queue man-
|
||||
ager. Each request specifies a queue file, a sender address, a domain
|
||||
@ -40,7 +40,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
that have a high volume of mail in the <a href="QSHAPE_README.html#active_queue">active queue</a>. Connection caching
|
||||
can be enabled permanently for specific destinations.
|
||||
|
||||
<b>SMTP SERVER LOOKUP</b>
|
||||
<b><a name="smtp_server_lookup">SMTP SERVER LOOKUP</a></b>
|
||||
The Postfix SMTP client supports multiple destinations separated by
|
||||
comma or whitespace (Postfix 3.5 and later). Each destination is tried
|
||||
in the specified order.
|
||||
@ -68,7 +68,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
specified service (default: <b>smtp</b>). An IPv6 address must be for-
|
||||
matted as [<b>ipv6</b>:<i>address</i>].
|
||||
|
||||
<b>LMTP SERVER LOOKUP</b>
|
||||
<b><a name="lmtp_server_lookup">LMTP SERVER LOOKUP</a></b>
|
||||
The Postfix LMTP client supports multiple destinations separated by
|
||||
comma or whitespace (Postfix 3.5 and later). Each destination is tried
|
||||
in the specified order.
|
||||
@ -101,7 +101,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
(default: <b>lmtp</b>). An IPv6 address must be formatted as
|
||||
[<b>ipv6</b>:<i>address</i>].
|
||||
|
||||
<b>SINGLE-RECIPIENT DELIVERY</b>
|
||||
<b><a name="single-recipient_delivery">SINGLE-RECIPIENT DELIVERY</a></b>
|
||||
By default, the Postfix SMTP+LMTP client delivers mail to multiple
|
||||
recipients per delivery request. This is undesirable when prepending a
|
||||
<b>Delivered-to:</b> or <b>X-Original-To:</b> message header. To prevent Postfix from
|
||||
@ -112,7 +112,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
in the Postfix <a href="postconf.5.html"><b>main.cf</b></a> file, where <i>transport</i> is the name in the first
|
||||
column of the Postfix <a href="master.5.html"><b>master.cf</b></a> entry for this mail delivery service.
|
||||
|
||||
<b>COMMAND ATTRIBUTE SYNTAX</b>
|
||||
<b><a name="command_attribute_syntax">COMMAND ATTRIBUTE SYNTAX</a></b>
|
||||
<b>flags=DORX</b> (optional)
|
||||
Optional message processing flags.
|
||||
|
||||
@ -147,12 +147,12 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
|
||||
This feature is available as of Postfix 3.5.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The SMTP+LMTP client is moderately security-sensitive. It talks to SMTP
|
||||
or LMTP servers and to DNS servers on the network. The SMTP+LMTP client
|
||||
can be run chrooted at fixed low privilege.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc821">RFC 821</a> (SMTP protocol)
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
<a href="https://tools.ietf.org/html/rfc1651">RFC 1651</a> (SMTP service extensions)
|
||||
@ -175,7 +175,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="https://tools.ietf.org/html/rfc6533">RFC 6533</a> (Internationalized Delivery Status Notifications)
|
||||
<a href="https://tools.ietf.org/html/rfc7672">RFC 7672</a> (SMTP security via opportunistic DANE TLS)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
Corrupted message files are marked so that the queue manager can move
|
||||
them to the <b>corrupt</b> queue for further inspection.
|
||||
@ -183,14 +183,14 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces, protocol problems, and of other trouble.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
SMTP and LMTP connection reuse for TLS (without closing the SMTP or
|
||||
LMTP connection) is not supported before Postfix 3.4.
|
||||
|
||||
SMTP and LMTP connection reuse assumes that SASL credentials are valid
|
||||
for all destinations that map onto the same IP address and TCP port.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Postfix versions 2.3 and later implement the SMTP and LMTP client with
|
||||
the same program, and choose the protocol and configuration parameters
|
||||
based on the process name, <b>smtp</b> or <b>lmtp</b>.
|
||||
@ -206,7 +206,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
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>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#ignore_mx_lookup_error">ignore_mx_lookup_error</a> (no)</b>
|
||||
Ignore DNS MX lookups that produce no response.
|
||||
|
||||
@ -422,7 +422,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
to MX or IP address lookup as if SRV record lookup was not
|
||||
enabled.
|
||||
|
||||
<b>MIME PROCESSING CONTROLS</b>
|
||||
<b><a name="mime_processing_controls">MIME PROCESSING CONTROLS</a></b>
|
||||
Available in Postfix version 2.0 and later:
|
||||
|
||||
<b><a href="postconf.5.html#disable_mime_output_conversion">disable_mime_output_conversion</a> (no)</b>
|
||||
@ -434,14 +434,14 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<b><a href="postconf.5.html#mime_nesting_limit">mime_nesting_limit</a> (100)</b>
|
||||
The maximal recursion level that the MIME processor will handle.
|
||||
|
||||
<b>EXTERNAL CONTENT INSPECTION CONTROLS</b>
|
||||
<b><a name="external_content_inspection_controls">EXTERNAL CONTENT INSPECTION CONTROLS</a></b>
|
||||
Available in Postfix version 2.1 and later:
|
||||
|
||||
<b><a href="postconf.5.html#smtp_send_xforward_command">smtp_send_xforward_command</a> (no)</b>
|
||||
Send the non-standard XFORWARD command when the Postfix SMTP
|
||||
server EHLO response announces XFORWARD support.
|
||||
|
||||
<b>SASL AUTHENTICATION CONTROLS</b>
|
||||
<b><a name="sasl_authentication_controls">SASL AUTHENTICATION CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#smtp_sasl_auth_enable">smtp_sasl_auth_enable</a> (no)</b>
|
||||
Enable SASL authentication in the Postfix SMTP client.
|
||||
|
||||
@ -506,7 +506,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
The delimiter between username and password in sasl_passwd_maps
|
||||
lookup results.
|
||||
|
||||
<b>STARTTLS SUPPORT CONTROLS</b>
|
||||
<b><a name="starttls_support_controls">STARTTLS SUPPORT CONTROLS</a></b>
|
||||
Detailed information about STARTTLS configuration may be found in the
|
||||
<a href="TLS_README.html">TLS_README</a> document.
|
||||
|
||||
@ -758,7 +758,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
reuse a previously-negotiated TLS session (there is no new
|
||||
information to report).
|
||||
|
||||
<b>OBSOLETE STARTTLS CONTROLS</b>
|
||||
<b><a name="obsolete_starttls_controls">OBSOLETE STARTTLS CONTROLS</a></b>
|
||||
The following configuration parameters exist for compatibility with
|
||||
Postfix versions before 2.3. Support for these will be removed in a
|
||||
future release.
|
||||
@ -785,7 +785,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Obsolete Postfix < 2.3 control for the Postfix SMTP client TLS
|
||||
cipher list.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#smtp_connect_timeout">smtp_connect_timeout</a> (30s)</b>
|
||||
The Postfix SMTP client time limit for completing a TCP connec-
|
||||
tion, or zero (use the operating system built-in time limit).
|
||||
@ -921,7 +921,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="postconf.5.html#default_destination_recipient_limit">ient_limit</a> parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a>
|
||||
name of the message delivery transport.
|
||||
|
||||
<b>SMTPUTF8 CONTROLS</b>
|
||||
<b><a name="smtputf8_controls">SMTPUTF8 CONTROLS</a></b>
|
||||
Preliminary SMTPUTF8 support is introduced with Postfix 3.0.
|
||||
|
||||
<b><a href="postconf.5.html#smtputf8_enable">smtputf8_enable</a> (yes)</b>
|
||||
@ -939,7 +939,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
IDNA2008, when converting UTF-8 domain names to/from the ASCII
|
||||
form that is used for DNS lookups.
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b>
|
||||
The increment in verbose logging level when a nexthop destina-
|
||||
tion, remote client or server name or network address matches a
|
||||
@ -964,7 +964,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<b><a href="postconf.5.html#notify_classes">notify_classes</a> (resource, software)</b>
|
||||
The list of error classes that are reported to the postmaster.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#best_mx_transport">best_mx_transport</a> (empty)</b>
|
||||
Where the Postfix SMTP client should deliver mail when it
|
||||
detects a "mail loops back to myself" error condition.
|
||||
@ -1097,7 +1097,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Defer delivery when the Postfix SMTP client cannot apply the
|
||||
<a href="postconf.5.html#smtp_bind_address">smtp_bind_address</a> or <a href="postconf.5.html#smtp_bind_address6">smtp_bind_address6</a> setting.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="generic.5.html">generic(5)</a>, output address rewriting
|
||||
<a href="header_checks.5.html">header_checks(5)</a>, message header content inspection
|
||||
<a href="header_checks.5.html">body_checks(5)</a>, body parts content inspection
|
||||
@ -1111,11 +1111,11 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="SASL_README.html">SASL_README</a>, Postfix SASL howto
|
||||
<a href="TLS_README.html">TLS_README</a>, Postfix STARTTLS howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
SENDMAIL(1) SENDMAIL(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
sendmail - Postfix to Sendmail compatibility interface
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>sendmail</b> [<i>option ...</i>] [<i>recipient ...</i>]
|
||||
|
||||
<b>mailq</b>
|
||||
@ -19,7 +19,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>newaliases</b>
|
||||
<b>sendmail -I</b>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command implements the Postfix to Sendmail com-
|
||||
patibility interface. For the sake of compatibility with existing
|
||||
applications, some Sendmail command-line options are recognized but
|
||||
@ -283,7 +283,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Log mailer traffic. Use the <b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a></b> and <b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a></b>
|
||||
configuration parameters instead.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
By design, this program is not set-user (or group) id. It is prepared
|
||||
to handle message content from untrusted, possibly remote, users.
|
||||
|
||||
@ -318,11 +318,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command options, by specifying an email address that
|
||||
starts with "<b>-</b>".
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>, and to the standard
|
||||
error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
@ -336,19 +336,19 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>NAME</b> The sender full name. This is used only with messages that have
|
||||
no <b>From:</b> message header. See also the <b>-F</b> option above.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
Available with Postfix 2.9 and later:
|
||||
|
||||
<b><a href="postconf.5.html#sendmail_fix_line_endings">sendmail_fix_line_endings</a> (always)</b>
|
||||
Controls how the Postfix sendmail command converts email message
|
||||
line endings from <CR><LF> into UNIX format (<LF>).
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
The <a href="DEBUG_README.html">DEBUG_README</a> file gives examples of how to troubleshoot a Postfix
|
||||
system.
|
||||
|
||||
@ -367,7 +367,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
verbose logging level to increase by the amount specified in
|
||||
$<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>.
|
||||
|
||||
<b>ACCESS CONTROLS</b>
|
||||
<b><a name="access_controls">ACCESS CONTROLS</a></b>
|
||||
Available in Postfix version 2.2 and later:
|
||||
|
||||
<b><a href="postconf.5.html#authorized_flush_users">authorized_flush_users</a> (<a href="DATABASE_README.html#types">static</a>:anyone)</b>
|
||||
@ -381,7 +381,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command (and with the privileged <a href="postdrop.1.html"><b>postdrop</b>(1)</a> helper com-
|
||||
mand).
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#bounce_size_limit">bounce_size_limit</a> (50000)</b>
|
||||
The maximal amount of original message text that is sent in a
|
||||
non-delivery notification.
|
||||
@ -400,7 +400,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue manager;
|
||||
prior to Postfix 2.4 the default value was 1000s.
|
||||
|
||||
<b>FAST FLUSH CONTROLS</b>
|
||||
<b><a name="fast_flush_controls">FAST FLUSH CONTROLS</a></b>
|
||||
The <a href="ETRN_README.html">ETRN_README</a> file describes configuration and operation details for
|
||||
the Postfix "fast flush" service.
|
||||
|
||||
@ -408,7 +408,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Optional list of destinations that are eligible for per-destina-
|
||||
tion logfiles with mail that is queued to those destinations.
|
||||
|
||||
<b>VERP CONTROLS</b>
|
||||
<b><a name="verp_controls">VERP CONTROLS</a></b>
|
||||
The <a href="VERP_README.html">VERP_README</a> file describes configuration and operation details of
|
||||
Postfix support for variable envelope return path addresses.
|
||||
|
||||
@ -419,7 +419,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The characters Postfix accepts as VERP delimiter characters on
|
||||
the Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command line and in SMTP commands.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#alias_database">alias_database</a> (see 'postconf -d' output)</b>
|
||||
The alias databases for <a href="local.8.html"><b>local</b>(8)</a> delivery that are updated with
|
||||
"<b>newaliases</b>" or with "<b>sendmail -bi</b>".
|
||||
@ -483,11 +483,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
the default Postfix instance, and that are started, stopped,
|
||||
etc., together with the default Postfix instance.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, mail queue
|
||||
/etc/postfix, configuration files
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="pickup.8.html">pickup(8)</a>, mail pickup daemon
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, SMTP server
|
||||
@ -500,14 +500,14 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README_FILES</b>
|
||||
<b><a name="readme_files">README_FILES</a></b>
|
||||
Use "<b>postconf <a href="postconf.5.html#readme_directory">readme_directory</a></b>" or "<b>postconf <a href="postconf.5.html#html_directory">html_directory</a></b>" to locate
|
||||
this information.
|
||||
<a href="DEBUG_README.html">DEBUG_README</a>, Postfix debugging howto
|
||||
<a href="ETRN_README.html">ETRN_README</a>, Postfix ETRN howto
|
||||
<a href="VERP_README.html">VERP_README</a>, Postfix VERP howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
MAKEDEFS(1) MAKEDEFS(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
makedefs - Postfix makefile configuration utility
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>make makefiles</b> <i>name=value...</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <b>makedefs</b> command identifies the compilation environment, and emits
|
||||
macro definitions on the standard output stream that can be prepended
|
||||
to template Makefiles. These macros implement an internal interface
|
||||
@ -202,7 +202,7 @@ MAKEDEFS(1) MAKEDEFS(1)
|
||||
Specifies non-default gcc compiler warning options for use when
|
||||
"make" is invoked in a source subdirectory only.
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
MASTER(5) MASTER(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
master - Postfix master process configuration file format
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system is implemented by small number of (mostly)
|
||||
client commands that are invoked by users, and by a larger number of
|
||||
services that run in the background.
|
||||
@ -30,7 +30,7 @@ MASTER(5) MASTER(5)
|
||||
After changing <a href="master.5.html">master.cf</a> you must execute "<b>postfix reload</b>" to reload
|
||||
the configuration.
|
||||
|
||||
<b>SYNTAX</b>
|
||||
<b><a name="syntax">SYNTAX</a></b>
|
||||
The general format of the <a href="master.5.html">master.cf</a> file is as follows:
|
||||
|
||||
<b>o</b> Empty lines and whitespace-only lines are ignored, as are lines
|
||||
@ -249,15 +249,15 @@ MASTER(5) MASTER(5)
|
||||
together with any leading or trailing whitespace in the
|
||||
remaining text.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="master.8.html">master(8)</a>, process manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="BASIC_CONFIGURATION_README.html">BASIC_CONFIGURATION_README</a>, basic configuration
|
||||
<a href="DEBUG_README.html">DEBUG_README</a>, Postfix debugging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
MASTER(8) MASTER(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
master - Postfix master process
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>master</b> [<b>-Dditvw</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-e</b> <i>exit</i><b>_</b><i>time</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="master.8.html"><b>master</b>(8)</a> daemon is the resident process that runs Postfix daemons
|
||||
on demand: daemons to send or receive messages via the network, daemons
|
||||
to deliver mail locally, etc. These daemons are created on demand up
|
||||
@ -92,12 +92,12 @@ MASTER(8) MASTER(8)
|
||||
one would terminate only the master ("<b>postfix stop</b>") and allow
|
||||
running processes to finish what they are doing.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are reported to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>. The exit status is
|
||||
non-zero in case of problems, including problems while initializing as
|
||||
a master daemon process in the background.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_DEBUG</b>
|
||||
After initialization, start a debugger as specified with the
|
||||
<b><a href="postconf.5.html#debugger_command">debugger_command</a></b> configuration parameter in the <a href="postconf.5.html"><b>main.cf</b></a> configu-
|
||||
@ -106,13 +106,13 @@ MASTER(8) MASTER(8)
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Unlike most Postfix daemon processes, the <a href="master.8.html"><b>master</b>(8)</a> server does not
|
||||
automatically pick up changes to <a href="postconf.5.html"><b>main.cf</b></a>. Changes to <a href="master.5.html"><b>master.cf</b></a> are
|
||||
never picked up automatically. Use the "<b>postfix reload</b>" command after
|
||||
a configuration change.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#default_process_limit">default_process_limit</a> (100)</b>
|
||||
The default maximal number of Postfix child processes that pro-
|
||||
vide a given service.
|
||||
@ -135,7 +135,7 @@ MASTER(8) MASTER(8)
|
||||
Selectively disable <a href="master.8.html"><b>master</b>(8)</a> listener ports by service type or
|
||||
by service name and type.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -192,7 +192,7 @@ MASTER(8) MASTER(8)
|
||||
Optional setting that avoids lookups in the <b>services</b>(5) data-
|
||||
base.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
To expand the directory names below into their actual values, use the
|
||||
command "<b>postconf <a href="postconf.5.html#config_directory">config_directory</a></b>" etc.
|
||||
|
||||
@ -201,7 +201,7 @@ MASTER(8) MASTER(8)
|
||||
$<a href="postconf.5.html#queue_directory">queue_directory</a>/pid/master.pid, master lock file.
|
||||
$<a href="postconf.5.html#data_directory">data_directory</a>/master.lock, master lock file.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="verify.8.html">verify(8)</a>, address verification
|
||||
<a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> configuration file syntax
|
||||
@ -209,7 +209,7 @@ MASTER(8) MASTER(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
memcache_table - Postfix memcache client configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="memcache_table.5.html">memcache</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="memcache_table.5.html">memcache</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -32,7 +32,7 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
sequence (first/next) operations. The sequence operation requires a
|
||||
backup database that supports the operation.
|
||||
|
||||
<b>MEMCACHE MAIN PARAMETERS</b>
|
||||
<b><a name="memcache_main_parameters">MEMCACHE MAIN PARAMETERS</a></b>
|
||||
<b>memcache (default: inet:localhost:11211)</b>
|
||||
The memcache server (note: singular) that Postfix will try to
|
||||
connect to. For a TCP server specify "inet:" followed by a
|
||||
@ -98,7 +98,7 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
greater than 30 days (2592000 seconds) specifies absolute UNIX
|
||||
time. Smaller values are relative to the time of the update.
|
||||
|
||||
<b>MEMCACHE KEY PARAMETERS</b>
|
||||
<b><a name="memcache_key_parameters">MEMCACHE KEY PARAMETERS</a></b>
|
||||
<b>key_format (default: %s)</b>
|
||||
Format of the lookup and update keys that the Postfix memcache
|
||||
client sends to the memcache server. By default, these are the
|
||||
@ -161,7 +161,7 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
|
||||
domain = example.com, <a href="DATABASE_README.html#types">hash</a>:/etc/postfix/searchdomains
|
||||
|
||||
<b>MEMCACHE ERROR CONTROLS</b>
|
||||
<b><a name="memcache_error_controls">MEMCACHE ERROR CONTROLS</a></b>
|
||||
<b>data_size_limit (default: 10240)</b>
|
||||
The maximal memcache reply data length in bytes.
|
||||
|
||||
@ -180,7 +180,7 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
The time limit for sending a memcache command and for receiving
|
||||
a memcache reply.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The Postfix memcache client cannot be used for security-sensitive
|
||||
tables such as <b><a href="postconf.5.html#alias_maps">alias_maps</a></b> (these may contain "<i>|command</i> and "<i>/file/name</i>"
|
||||
destinations), or <b><a href="postconf.5.html#virtual_uid_maps">virtual_uid_maps</a></b>, <b><a href="postconf.5.html#virtual_gid_maps">virtual_gid_maps</a></b> and <b><a href="postconf.5.html#virtual_mailbox_maps">virtual_mail</a>-</b>
|
||||
@ -195,18 +195,18 @@ MEMCACHE_TABLE(5) MEMCACHE_TABLE(5)
|
||||
<b>ttl</b> parameter discussions in the MEMCACHE MAIN PARAMETERS section
|
||||
above.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="MEMCACHE_README.html">MEMCACHE_README</a>, Postfix memcache client guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
Memcache support was introduced with Postfix version 2.9.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
MONGODB_TABLE(5) MONGODB_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
mongodb_table - Postfix MongoDB client configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="mongodb_table.5.html">mongodb</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="mongodb_table.5.html">mongodb</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -37,7 +37,7 @@ MONGODB_TABLE(5) MONGODB_TABLE(5)
|
||||
unprivileged postfix user (specified with the Postfix <a href="postconf.5.html#mail_owner">mail_owner</a> con-
|
||||
figuration parameter).
|
||||
|
||||
<b>MONGODB PARAMETERS</b>
|
||||
<b><a name="mongodb_parameters">MONGODB PARAMETERS</a></b>
|
||||
<b>uri</b> The URI of mongo server/cluster that Postfix will try to connect
|
||||
to and query from. Please see
|
||||
<a href="https://www.mongodb.com/docs/manual/reference/connection-string/">https://www.mongodb.com/docs/manual/reference/connection-string/</a>
|
||||
@ -185,18 +185,18 @@ MONGODB_TABLE(5) MONGODB_TABLE(5)
|
||||
mally world-readable, and '$' in a mongodb parameter setting needs to
|
||||
be written as '$$'.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table maintenance
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="MONGODB_README.html">MONGODB_README</a>, Postfix MONGODB client guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
MongoDB support was introduced with Postfix version 3.9.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
mysql_table - Postfix MySQL client configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="mysql_table.5.html">mysql</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="mysql_table.5.html">mysql</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -27,7 +27,7 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
The file /etc/postfix/mysql-aliases.cf has the same format as the Post-
|
||||
fix <a href="postconf.5.html">main.cf</a> file, and can specify the parameters described below.
|
||||
|
||||
<b>LIST MEMBERSHIP</b>
|
||||
<b><a name="list_membership">LIST MEMBERSHIP</a></b>
|
||||
When using SQL to store lists such as $<a href="postconf.5.html#mynetworks">mynetworks</a>, $<a href="postconf.5.html#mydestination">mydestination</a>,
|
||||
$<a href="postconf.5.html#relay_domains">relay_domains</a>, $<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a>, etc., it is important to under-
|
||||
stand that the table must store each list member as a separate key. The
|
||||
@ -41,7 +41,7 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
value. With SQL databases it is not uncommon to return the key itself
|
||||
or a constant value.
|
||||
|
||||
<b>MYSQL PARAMETERS</b>
|
||||
<b><a name="mysql_parameters">MYSQL PARAMETERS</a></b>
|
||||
<b>hosts</b> The hosts that Postfix will try to connect to and query from.
|
||||
Specify <i>unix:</i> for UNIX domain sockets, <i>inet:</i> for TCP connections
|
||||
(default). Examples:
|
||||
@ -258,7 +258,7 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
|
||||
This parameter is available with Postfix 3.2 and later.
|
||||
|
||||
<b>TLS-RELATED SETTINGS</b>
|
||||
<b><a name="tls-related_settings">TLS-RELATED SETTINGS</a></b>
|
||||
See <a href="https://dev.mysql.com/doc/c-api/en/mysql-options.html">https://dev.mysql.com/doc/c-api/en/mysql-options.html</a> or
|
||||
<a href="https://mariadb.com/kb/en/mysql_optionsv/">https://mariadb.com/kb/en/mysql_optionsv/</a> for details of the underlying
|
||||
MYSQL_OPT_SSL_* features.
|
||||
@ -297,7 +297,7 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
|
||||
This parameter is available with Postfix 2.11 and later.
|
||||
|
||||
<b>USING MYSQL STORED PROCEDURES</b>
|
||||
<b><a name="using_mysql_stored_procedures">USING MYSQL STORED PROCEDURES</a></b>
|
||||
Postfix 3.2 and later support calling a stored procedure instead of
|
||||
using a SELECT statement in the query, e.g.
|
||||
|
||||
@ -340,7 +340,7 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
in <a href="postconf.5.html">main.cf</a>, which is normally world-readable. Support for this form
|
||||
will be removed in a future Postfix version.
|
||||
|
||||
<b>OBSOLETE QUERY INTERFACE</b>
|
||||
<b><a name="obsolete_query_interface">OBSOLETE QUERY INTERFACE</a></b>
|
||||
This section describes an interface that is deprecated as of Postfix
|
||||
2.2. It is replaced by the more general <b>query</b> interface described
|
||||
above. If the <b>query</b> parameter is defined, the legacy parameters
|
||||
@ -374,21 +374,21 @@ MYSQL_TABLE(5) MYSQL_TABLE(5)
|
||||
Additional conditions to the SQL query. Example:
|
||||
<b>additional_conditions</b> = AND status = 'paid'
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table maintenance
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="ldap_table.5.html">ldap_table(5)</a>, LDAP lookup tables
|
||||
<a href="pgsql_table.5.html">pgsql_table(5)</a>, PostgreSQL lookup tables
|
||||
<a href="sqlite_table.5.html">sqlite_table(5)</a>, SQLite lookup tables
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="MYSQL_README.html">MYSQL_README</a>, Postfix MYSQL client guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
MySQL support was introduced with Postfix version 1.0.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
SENDMAIL(1) SENDMAIL(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
sendmail - Postfix to Sendmail compatibility interface
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>sendmail</b> [<i>option ...</i>] [<i>recipient ...</i>]
|
||||
|
||||
<b>mailq</b>
|
||||
@ -19,7 +19,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>newaliases</b>
|
||||
<b>sendmail -I</b>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command implements the Postfix to Sendmail com-
|
||||
patibility interface. For the sake of compatibility with existing
|
||||
applications, some Sendmail command-line options are recognized but
|
||||
@ -283,7 +283,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Log mailer traffic. Use the <b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a></b> and <b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a></b>
|
||||
configuration parameters instead.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
By design, this program is not set-user (or group) id. It is prepared
|
||||
to handle message content from untrusted, possibly remote, users.
|
||||
|
||||
@ -318,11 +318,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command options, by specifying an email address that
|
||||
starts with "<b>-</b>".
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>, and to the standard
|
||||
error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
@ -336,19 +336,19 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>NAME</b> The sender full name. This is used only with messages that have
|
||||
no <b>From:</b> message header. See also the <b>-F</b> option above.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
Available with Postfix 2.9 and later:
|
||||
|
||||
<b><a href="postconf.5.html#sendmail_fix_line_endings">sendmail_fix_line_endings</a> (always)</b>
|
||||
Controls how the Postfix sendmail command converts email message
|
||||
line endings from <CR><LF> into UNIX format (<LF>).
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
The <a href="DEBUG_README.html">DEBUG_README</a> file gives examples of how to troubleshoot a Postfix
|
||||
system.
|
||||
|
||||
@ -367,7 +367,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
verbose logging level to increase by the amount specified in
|
||||
$<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>.
|
||||
|
||||
<b>ACCESS CONTROLS</b>
|
||||
<b><a name="access_controls">ACCESS CONTROLS</a></b>
|
||||
Available in Postfix version 2.2 and later:
|
||||
|
||||
<b><a href="postconf.5.html#authorized_flush_users">authorized_flush_users</a> (<a href="DATABASE_README.html#types">static</a>:anyone)</b>
|
||||
@ -381,7 +381,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command (and with the privileged <a href="postdrop.1.html"><b>postdrop</b>(1)</a> helper com-
|
||||
mand).
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#bounce_size_limit">bounce_size_limit</a> (50000)</b>
|
||||
The maximal amount of original message text that is sent in a
|
||||
non-delivery notification.
|
||||
@ -400,7 +400,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue manager;
|
||||
prior to Postfix 2.4 the default value was 1000s.
|
||||
|
||||
<b>FAST FLUSH CONTROLS</b>
|
||||
<b><a name="fast_flush_controls">FAST FLUSH CONTROLS</a></b>
|
||||
The <a href="ETRN_README.html">ETRN_README</a> file describes configuration and operation details for
|
||||
the Postfix "fast flush" service.
|
||||
|
||||
@ -408,7 +408,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Optional list of destinations that are eligible for per-destina-
|
||||
tion logfiles with mail that is queued to those destinations.
|
||||
|
||||
<b>VERP CONTROLS</b>
|
||||
<b><a name="verp_controls">VERP CONTROLS</a></b>
|
||||
The <a href="VERP_README.html">VERP_README</a> file describes configuration and operation details of
|
||||
Postfix support for variable envelope return path addresses.
|
||||
|
||||
@ -419,7 +419,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The characters Postfix accepts as VERP delimiter characters on
|
||||
the Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command line and in SMTP commands.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#alias_database">alias_database</a> (see 'postconf -d' output)</b>
|
||||
The alias databases for <a href="local.8.html"><b>local</b>(8)</a> delivery that are updated with
|
||||
"<b>newaliases</b>" or with "<b>sendmail -bi</b>".
|
||||
@ -483,11 +483,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
the default Postfix instance, and that are started, stopped,
|
||||
etc., together with the default Postfix instance.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, mail queue
|
||||
/etc/postfix, configuration files
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="pickup.8.html">pickup(8)</a>, mail pickup daemon
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, SMTP server
|
||||
@ -500,14 +500,14 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README_FILES</b>
|
||||
<b><a name="readme_files">README_FILES</a></b>
|
||||
Use "<b>postconf <a href="postconf.5.html#readme_directory">readme_directory</a></b>" or "<b>postconf <a href="postconf.5.html#html_directory">html_directory</a></b>" to locate
|
||||
this information.
|
||||
<a href="DEBUG_README.html">DEBUG_README</a>, Postfix debugging howto
|
||||
<a href="ETRN_README.html">ETRN_README</a>, Postfix ETRN howto
|
||||
<a href="VERP_README.html">VERP_README</a>, Postfix VERP howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
NISPLUS_TABLE(5) NISPLUS_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
nisplus_table - Postfix NIS+ client
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" "<a href="nisplus_table.5.html">nisplus</a>:[</b><i>name</i><b>=%s];</b><i>name.name.</i><b>"</b>
|
||||
|
||||
<b>postmap -q - "<a href="nisplus_table.5.html">nisplus</a>:[</b><i>name</i><b>=%s];</b><i>name.name.</i><b>"</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional lookup tables. These tables are
|
||||
usually in <b>dbm</b> or <b>db</b> format. Alternatively, lookup tables can be spec-
|
||||
ified as NIS+ databases.
|
||||
@ -26,7 +26,7 @@ NISPLUS_TABLE(5) NISPLUS_TABLE(5)
|
||||
To test Postfix NIS+ lookup tables, use the "<b>postmap -q</b>" command as
|
||||
described in the SYNOPSIS above.
|
||||
|
||||
<b>QUERY SYNTAX</b>
|
||||
<b><a name="query_syntax">QUERY SYNTAX</a></b>
|
||||
Most of the NIS+ query is specified via the NIS+ map name. The general
|
||||
format of a Postfix NIS+ map name is as follows:
|
||||
|
||||
@ -49,7 +49,7 @@ NISPLUS_TABLE(5) NISPLUS_TABLE(5)
|
||||
column that provides the lookup result. When no ":<i>column</i>" is
|
||||
specified the first column (1) is used.
|
||||
|
||||
<b>EXAMPLE</b>
|
||||
<b><a name="example">EXAMPLE</a></b>
|
||||
A NIS+ aliases map might be queried as follows:
|
||||
|
||||
<a href="postconf.5.html#alias_maps">alias_maps</a> = <a href="DATABASE_README.html#types">dbm</a>:/etc/mail/aliases,
|
||||
@ -57,13 +57,13 @@ NISPLUS_TABLE(5) NISPLUS_TABLE(5)
|
||||
|
||||
This queries the local aliases file before the NIS+ file.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
OQMGR(8) OQMGR(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
oqmgr - old Postfix queue manager
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>oqmgr</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon awaits the arrival of incoming mail and arranges
|
||||
for its delivery via Postfix delivery processes. The actual mail rout-
|
||||
ing strategy is delegated to the <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon. This pro-
|
||||
@ -23,7 +23,7 @@ OQMGR(8) OQMGR(8)
|
||||
carded. This stops potential loops caused by undeliverable bounce
|
||||
notifications.
|
||||
|
||||
<b>MAIL QUEUES</b>
|
||||
<b><a name="mail_queues">MAIL QUEUES</a></b>
|
||||
The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon maintains the following queues:
|
||||
|
||||
<b>incoming</b>
|
||||
@ -45,7 +45,7 @@ OQMGR(8) OQMGR(8)
|
||||
<b>hold</b> Messages that are kept "on hold" are kept here until someone
|
||||
sets them free.
|
||||
|
||||
<b>DELIVERY STATUS REPORTS</b>
|
||||
<b><a name="delivery_status_reports">DELIVERY STATUS REPORTS</a></b>
|
||||
The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon keeps an eye on per-message delivery status reports
|
||||
in the following directories. Each status report file has the same name
|
||||
as the corresponding message file:
|
||||
@ -63,7 +63,7 @@ OQMGR(8) OQMGR(8)
|
||||
The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon is responsible for asking the <a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a>
|
||||
or <a href="trace.8.html"><b>trace</b>(8)</a> daemons to send delivery reports.
|
||||
|
||||
<b>STRATEGIES</b>
|
||||
<b><a name="strategies">STRATEGIES</a></b>
|
||||
The queue manager implements a variety of strategies for either opening
|
||||
queue files (input) or for message delivery (output).
|
||||
|
||||
@ -98,7 +98,7 @@ OQMGR(8) OQMGR(8)
|
||||
taining a short-term, in-memory list of unreachable destina-
|
||||
tions.
|
||||
|
||||
<b>TRIGGERS</b>
|
||||
<b><a name="triggers">TRIGGERS</a></b>
|
||||
On an idle system, the queue manager waits for the arrival of trigger
|
||||
events, or it waits for a timer to go off. A trigger is a one-byte mes-
|
||||
sage. Depending on the message received, the queue manager performs
|
||||
@ -133,18 +133,18 @@ OQMGR(8) OQMGR(8)
|
||||
<a href="QSHAPE_README.html#deferred_queue">deferred queue</a> run, one would request <b>A F D</b>; in order to notify the
|
||||
queue manager of the arrival of new mail one would request <b>I</b>.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced status codes)
|
||||
<a href="https://tools.ietf.org/html/rfc3464">RFC 3464</a> (Delivery status notifications)
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon is not security sensitive. It reads single-charac-
|
||||
ter messages from untrusted local users, and thus may be susceptible to
|
||||
denial of service attacks. The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon does not talk to the
|
||||
outside world, and it can be run at fixed low privilege in a chrooted
|
||||
environment.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to the <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>
|
||||
daemon. Corrupted message files are saved to the <b>corrupt</b> queue for
|
||||
further inspection.
|
||||
@ -152,12 +152,12 @@ OQMGR(8) OQMGR(8)
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces and of other trouble.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
A single queue manager process has to compete for disk access with mul-
|
||||
tiple front-end processes such as <a href="cleanup.8.html"><b>cleanup</b>(8)</a>. A sudden burst of inbound
|
||||
mail can negatively impact outbound delivery rates.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically, as <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> is a
|
||||
persistent process. Use the command "<b>postfix reload</b>" after a configura-
|
||||
tion change.
|
||||
@ -167,7 +167,7 @@ OQMGR(8) OQMGR(8)
|
||||
|
||||
In the text below, <i>transport</i> is the first field in a <a href="master.5.html"><b>master.cf</b></a> entry.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
Available before Postfix version 2.5:
|
||||
|
||||
<b><a href="postconf.5.html#allow_min_user">allow_min_user</a> (no)</b>
|
||||
@ -181,7 +181,7 @@ OQMGR(8) OQMGR(8)
|
||||
next-hop destination, use $<a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> instead; when
|
||||
that value is empty, use the domain in the recipient address.
|
||||
|
||||
<b><a href="QSHAPE_README.html#active_queue">ACTIVE QUEUE</a> CONTROLS</b>
|
||||
<b><a name="active_queue_controls">ACTIVE QUEUE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmgr_clog_warn_time">qmgr_clog_warn_time</a> (300s)</b>
|
||||
The minimal delay between warnings that a specific destination
|
||||
is clogging up the Postfix <a href="QSHAPE_README.html#active_queue">active queue</a>.
|
||||
@ -194,7 +194,7 @@ OQMGR(8) OQMGR(8)
|
||||
queue manager, and the maximal size of the short-term, in-memory
|
||||
"dead" destination status cache.
|
||||
|
||||
<b>DELIVERY CONCURRENCY CONTROLS</b>
|
||||
<b><a name="delivery_concurrency_controls">DELIVERY CONCURRENCY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmgr_fudge_factor">qmgr_fudge_factor</a> (100)</b>
|
||||
Obsolete feature: the percentage of delivery resources that a
|
||||
busy mail system will use up for delivery of a large mailing
|
||||
@ -259,7 +259,7 @@ OQMGR(8) OQMGR(8)
|
||||
Make the queue manager's feedback algorithm verbose for perfor-
|
||||
mance analysis purposes.
|
||||
|
||||
<b>RECIPIENT SCHEDULING CONTROLS</b>
|
||||
<b><a name="recipient_scheduling_controls">RECIPIENT SCHEDULING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#default_destination_recipient_limit">default_destination_recipient_limit</a> (50)</b>
|
||||
The default maximal number of recipients per message delivery.
|
||||
|
||||
@ -269,7 +269,7 @@ OQMGR(8) OQMGR(8)
|
||||
<a href="postconf.5.html#default_destination_recipient_limit">ient_limit</a> parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a>
|
||||
name of the message delivery transport.
|
||||
|
||||
<b>OTHER RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="other_resource_and_rate_controls">OTHER RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#minimal_backoff_time">minimal_backoff_time</a> (300s)</b>
|
||||
The minimal time between attempts to deliver a deferred message;
|
||||
prior to Postfix 2.4 the default value was 1000s.
|
||||
@ -322,7 +322,7 @@ OQMGR(8) OQMGR(8)
|
||||
the parameter name is the <a href="master.5.html">master.cf</a> name of the message delivery
|
||||
transport.
|
||||
|
||||
<b>SAFETY CONTROLS</b>
|
||||
<b><a name="safety_controls">SAFETY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmgr_daemon_timeout">qmgr_daemon_timeout</a> (1000s)</b>
|
||||
How much time a Postfix queue manager process may take to handle
|
||||
a request before it is terminated by a built-in watchdog timer.
|
||||
@ -337,7 +337,7 @@ OQMGR(8) OQMGR(8)
|
||||
A safety limit that prevents address verification requests from
|
||||
overwhelming the Postfix queue.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -387,7 +387,7 @@ OQMGR(8) OQMGR(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/incoming, <a href="QSHAPE_README.html#incoming_queue">incoming queue</a>
|
||||
/var/spool/postfix/active, <a href="QSHAPE_README.html#active_queue">active queue</a>
|
||||
/var/spool/postfix/deferred, <a href="QSHAPE_README.html#deferred_queue">deferred queue</a>
|
||||
@ -395,7 +395,7 @@ OQMGR(8) OQMGR(8)
|
||||
/var/spool/postfix/defer, non-delivery status
|
||||
/var/spool/postfix/trace, delivery status
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="trivial-rewrite.8.html">trivial-rewrite(8)</a>, address routing
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -404,10 +404,10 @@ OQMGR(8) OQMGR(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="QSHAPE_README.html">QSHAPE_README</a>, Postfix queue analysis
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
pcre_table - format of Postfix PCRE tables
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="pcre_table.5.html">pcre</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="pcre_table.5.html">pcre</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
@ -19,7 +19,7 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
|
||||
<b>postmap -bmq - <a href="pcre_table.5.html">pcre</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting,
|
||||
mail routing, or access control. These tables are usually in <b>dbm</b> or <b>db</b>
|
||||
format.
|
||||
@ -40,12 +40,12 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
This driver can be built with the pcre2 library (Postfix 3.7 and
|
||||
later), or with the legacy pcre library (all Postfix versions).
|
||||
|
||||
<b>COMPATIBILITY</b>
|
||||
<b><a name="compatibility">COMPATIBILITY</a></b>
|
||||
With Postfix version 2.2 and earlier specify "<b>postmap -fq</b>" to query a
|
||||
table that contains case sensitive patterns. Patterns are case insensi-
|
||||
tive by default.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The general form of a PCRE table is:
|
||||
|
||||
<b>/</b><i>pattern</i><b>/</b><i>flags result</i>
|
||||
@ -148,7 +148,7 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
|
||||
This feature is not supported with PCRE2.
|
||||
|
||||
<b>SEARCH ORDER</b>
|
||||
<b><a name="search_order">SEARCH ORDER</a></b>
|
||||
Patterns are applied in the order as specified in the table, until a
|
||||
pattern is found that matches the input string.
|
||||
|
||||
@ -159,7 +159,7 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
ken up into their <i>user</i> and <i>domain</i> constituent parts, nor is <i>user+foo</i>
|
||||
broken up into <i>user</i> and <i>foo</i>.
|
||||
|
||||
<b>TEXT SUBSTITUTION</b>
|
||||
<b><a name="text_substitution">TEXT SUBSTITUTION</a></b>
|
||||
Substitution of substrings (text that matches patterns inside "()")
|
||||
from the matched expression into the result string is requested with
|
||||
$1, $2, etc.; specify $$ to produce a $ character as output. The
|
||||
@ -171,7 +171,7 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
the expression does not match, substitutions are not available for
|
||||
negated patterns.
|
||||
|
||||
<b>INLINE SPECIFICATION</b>
|
||||
<b><a name="inline_specification">INLINE SPECIFICATION</a></b>
|
||||
The contents of a table may be specified in the table name (Postfix 3.7
|
||||
and later). The basic syntax is:
|
||||
|
||||
@ -198,7 +198,7 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
able metacharacters such as '.' in the <i>$name</i> expansion. Otherwise, the
|
||||
pattern may have unexpected matches.
|
||||
|
||||
<b>EXAMPLE SMTPD ACCESS MAP</b>
|
||||
<b><a name="example_smtpd_access_map">EXAMPLE SMTPD ACCESS MAP</a></b>
|
||||
# Protect your outgoing majordomo exploders
|
||||
/^(?!owner-)(.*)-outgoing@(.*)/ 550 Use ${1}@${2} instead
|
||||
|
||||
@ -212,23 +212,23 @@ PCRE_TABLE(5) PCRE_TABLE(5)
|
||||
550 This user is a funny one. You really don't want to send mail to
|
||||
them as it only makes their head spin.
|
||||
|
||||
<b>EXAMPLE HEADER FILTER MAP</b>
|
||||
<b><a name="example_header_filter_map">EXAMPLE HEADER FILTER MAP</a></b>
|
||||
/^Subject: make money fast/ REJECT
|
||||
/^To: friend@public\.com/ REJECT
|
||||
|
||||
<b>EXAMPLE BODY FILTER MAP</b>
|
||||
<b><a name="example_body_filter_map">EXAMPLE BODY FILTER MAP</a></b>
|
||||
# First skip over base 64 encoded text to save CPU cycles.
|
||||
# Requires PCRE version 3.
|
||||
~^[[:alnum:]+/]{60,}$~ OK
|
||||
|
||||
# Put your own body patterns here.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="regexp_table.5.html">regexp_table(5)</a>, format of POSIX regular expression tables
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
PGSQL_TABLE(5) PGSQL_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
pgsql_table - Postfix PostgreSQL client configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="pgsql_table.5.html">pgsql</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="pgsql_table.5.html">pgsql</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -27,7 +27,7 @@ PGSQL_TABLE(5) PGSQL_TABLE(5)
|
||||
The file /etc/postfix/pgsql-aliases.cf has the same format as the Post-
|
||||
fix <a href="postconf.5.html">main.cf</a> file, and can specify the parameters described below.
|
||||
|
||||
<b>LIST MEMBERSHIP</b>
|
||||
<b><a name="list_membership">LIST MEMBERSHIP</a></b>
|
||||
When using SQL to store lists such as $<a href="postconf.5.html#mynetworks">mynetworks</a>, $<a href="postconf.5.html#mydestination">mydestination</a>,
|
||||
$<a href="postconf.5.html#relay_domains">relay_domains</a>, $<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a>, etc., it is important to under-
|
||||
stand that the table must store each list member as a separate key. The
|
||||
@ -41,7 +41,7 @@ PGSQL_TABLE(5) PGSQL_TABLE(5)
|
||||
value. With SQL databases it is not uncommon to return the key itself
|
||||
or a constant value.
|
||||
|
||||
<b>PGSQL PARAMETERS</b>
|
||||
<b><a name="pgsql_parameters">PGSQL PARAMETERS</a></b>
|
||||
<b>hosts</b> The hosts that Postfix will try to connect to and query from.
|
||||
Besides a <b>postgresql://</b> connection URI, this setting supports
|
||||
the historical forms <b>unix:/</b><i>pathname</i> for UNIX-domain sockets and
|
||||
@ -235,7 +235,7 @@ PGSQL_TABLE(5) PGSQL_TABLE(5)
|
||||
written in <a href="postconf.5.html">main.cf</a>, which is normally world-readable. Support for this
|
||||
form will be removed in a future Postfix version.
|
||||
|
||||
<b>OBSOLETE QUERY INTERFACES</b>
|
||||
<b><a name="obsolete_query_interfaces">OBSOLETE QUERY INTERFACES</a></b>
|
||||
This section describes query interfaces that are deprecated as of Post-
|
||||
fix 2.2. Please migrate to the new <b>query</b> interface as the old inter-
|
||||
faces are slated to be phased out.
|
||||
@ -286,21 +286,21 @@ PGSQL_TABLE(5) PGSQL_TABLE(5)
|
||||
Additional conditions to the SQL query. Example:
|
||||
<b>additional_conditions</b> = AND status = 'paid'
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="ldap_table.5.html">ldap_table(5)</a>, LDAP lookup tables
|
||||
<a href="mysql_table.5.html">mysql_table(5)</a>, MySQL lookup tables
|
||||
<a href="sqlite_table.5.html">sqlite_table(5)</a>, SQLite lookup tables
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="PGSQL_README.html">PGSQL_README</a>, Postfix PostgreSQL client guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
PgSQL support was introduced with Postfix version 2.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,22 +7,22 @@
|
||||
</head> <body> <pre>
|
||||
PICKUP(8) PICKUP(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
pickup - Postfix local mail pickup
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>pickup</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon waits for hints that new mail has been dropped
|
||||
into the <b>maildrop</b> directory, and feeds it into the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon.
|
||||
Ill-formatted files are deleted without notifying the originator. This
|
||||
program expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
None. The <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon does not interact with the outside world.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon is moderately security sensitive. It runs with
|
||||
fixed low privilege and can run in a chrooted environment. However,
|
||||
the program reads files from potentially hostile users. The <a href="pickup.8.html"><b>pickup</b>(8)</a>
|
||||
@ -30,16 +30,16 @@ PICKUP(8) PICKUP(8)
|
||||
for reading, and does not actually touch any data that is sent to its
|
||||
public service endpoint.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon copies mail from file to the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon.
|
||||
It could avoid message copying overhead by sending a file descriptor
|
||||
instead of file data, but then the already complex <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon
|
||||
would have to deal with unfiltered user data.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
As the <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon is a relatively long-running process, up to an
|
||||
hour may pass before a <a href="postconf.5.html"><b>main.cf</b></a> change takes effect. Use the command
|
||||
"<b>postfix reload</b>" command to speed up a change.
|
||||
@ -47,7 +47,7 @@ PICKUP(8) PICKUP(8)
|
||||
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>CONTENT INSPECTION CONTROLS</b>
|
||||
<b><a name="content_inspection_controls">CONTENT INSPECTION CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#content_filter">content_filter</a> (empty)</b>
|
||||
After the message is queued, send the entire message to the
|
||||
specified <i>transport:destination</i>.
|
||||
@ -56,7 +56,7 @@ PICKUP(8) PICKUP(8)
|
||||
Enable or disable recipient validation, built-in content filter-
|
||||
ing, or address mapping.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -104,7 +104,7 @@ PICKUP(8) PICKUP(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, message canonicalization
|
||||
<a href="sendmail.1.html">sendmail(1)</a>, Sendmail-compatible interface
|
||||
<a href="postdrop.1.html">postdrop(1)</a>, mail posting agent
|
||||
@ -114,7 +114,7 @@ PICKUP(8) PICKUP(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
PIPE(8) PIPE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
pipe - Postfix delivery to external command
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>pipe</b> [generic Postfix daemon options] command_attributes...
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="pipe.8.html"><b>pipe</b>(8)</a> daemon processes requests from the Postfix queue manager to
|
||||
deliver messages to external commands. This program expects to be run
|
||||
from the <a href="master.8.html"><b>master</b>(8)</a> process manager.
|
||||
@ -27,7 +27,7 @@ PIPE(8) PIPE(8)
|
||||
again at a later time. Delivery status reports are sent to the
|
||||
<a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or <a href="trace.8.html"><b>trace</b>(8)</a> daemon as appropriate.
|
||||
|
||||
<b>SINGLE-RECIPIENT DELIVERY</b>
|
||||
<b><a name="single-recipient_delivery">SINGLE-RECIPIENT DELIVERY</a></b>
|
||||
Some destinations cannot handle more than one recipient per delivery
|
||||
request. Examples are pagers or fax machines. In addition,
|
||||
multi-recipient delivery is undesirable when prepending a <b>Delivered-to:</b>
|
||||
@ -42,7 +42,7 @@ PIPE(8) PIPE(8)
|
||||
column of the Postfix <a href="master.5.html"><b>master.cf</b></a> entry for the pipe-based delivery
|
||||
transport.
|
||||
|
||||
<b>COMMAND ATTRIBUTE SYNTAX</b>
|
||||
<b><a name="command_attribute_syntax">COMMAND ATTRIBUTE SYNTAX</a></b>
|
||||
The external command attributes are given in the <a href="master.5.html"><b>master.cf</b></a> file at the
|
||||
end of a service definition. The syntax is as follows:
|
||||
|
||||
@ -353,10 +353,10 @@ PIPE(8) PIPE(8)
|
||||
This information is modified by the <b>u</b> flag for case fold-
|
||||
ing.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced status codes)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Command exit status codes are expected to follow the conventions
|
||||
defined in <<b>sysexits.h</b>>. Exit status 0 means normal successful comple-
|
||||
tion.
|
||||
@ -376,12 +376,12 @@ PIPE(8) PIPE(8)
|
||||
Corrupted message files are marked so that the queue manager can move
|
||||
them to the <b>corrupt</b> queue for further inspection.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
This program needs a dual personality 1) to access the private Postfix
|
||||
queue and IPC mechanisms, and 2) to execute external commands as the
|
||||
specified user. It is therefore security sensitive.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="pipe.8.html"><b>pipe</b>(8)</a> processes run
|
||||
for only a limited amount of time. Use the command "<b>postfix reload</b>" to
|
||||
speed up a change.
|
||||
@ -389,7 +389,7 @@ PIPE(8) PIPE(8)
|
||||
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>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
In the text below, <i>transport</i> is the first field in a <a href="master.5.html"><b>master.cf</b></a> entry.
|
||||
|
||||
<b><a href="postconf.5.html#transport_time_limit">transport_time_limit</a> ($<a href="postconf.5.html#command_time_limit">command_time_limit</a>)</b>
|
||||
@ -411,7 +411,7 @@ PIPE(8) PIPE(8)
|
||||
<a href="postconf.5.html#default_destination_recipient_limit">ient_limit</a> parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a>
|
||||
name of the message delivery transport.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -487,7 +487,7 @@ PIPE(8) PIPE(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -496,7 +496,7 @@ PIPE(8) PIPE(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,14 +7,14 @@
|
||||
</head> <body> <pre>
|
||||
POSTALIAS(1) POSTALIAS(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postalias - Postfix alias database maintenance
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postalias</b> [<b>-Nfinoprsuvw</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-d</b> <i>key</i>] [<b>-q</b> <i>key</i>]
|
||||
[<i>file</i><b>_</b><i>type</i>:]<i>file</i><b>_</b><i>name</i> ...
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postalias.1.html"><b>postalias</b>(1)</a> command creates or queries one or more Postfix alias
|
||||
databases, or updates an existing one. The input and output file for-
|
||||
mats are expected to be compatible with Sendmail version 8, and are
|
||||
@ -155,7 +155,7 @@ POSTALIAS(1) POSTALIAS(1)
|
||||
The name of the alias database source file when creating a data-
|
||||
base.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to the standard error stream and to <b>syslogd</b>(8) or
|
||||
<a href="postlogd.8.html"><b>postlogd</b>(8)</a>. No output means that no problems were detected. Duplicate
|
||||
entries are skipped and are flagged with a warning.
|
||||
@ -164,14 +164,14 @@ POSTALIAS(1) POSTALIAS(1)
|
||||
(including successful "<b>postalias -q</b>" lookup) and terminates with
|
||||
non-zero exit status in case of failure.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>MAIL_VERBOSE</b>
|
||||
Enable verbose logging for debugging purposes.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram.
|
||||
|
||||
@ -219,10 +219,10 @@ POSTALIAS(1) POSTALIAS(1)
|
||||
<b><a href="postconf.5.html#lmdb_map_size">lmdb_map_size</a> (16777216)</b>
|
||||
The initial OpenLDAP LMDB database size limit in bytes.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="aliases.5.html">aliases(5)</a>, format of alias database input file.
|
||||
<a href="local.8.html">local(8)</a>, Postfix local delivery agent.
|
||||
<a href="postconf.1.html">postconf(1)</a>, supported database types
|
||||
@ -232,10 +232,10 @@ POSTALIAS(1) POSTALIAS(1)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTCAT(1) POSTCAT(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postcat - show Postfix queue file contents
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postcat</b> [<b>-bdefhnoqv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<i>files</i>...]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postcat.1.html"><b>postcat</b>(1)</a> command prints the contents of the named <i>files</i> in
|
||||
human-readable form. The files are expected to be in Postfix queue file
|
||||
format. If no <i>files</i> are specified on the command line, the program
|
||||
@ -70,14 +70,14 @@ POSTCAT(1) POSTCAT(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are reported to the standard error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram.
|
||||
|
||||
@ -96,13 +96,13 @@ POSTCAT(1) POSTCAT(1)
|
||||
<b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
|
||||
The location of the Postfix top-level queue directory.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, Postfix queue directory
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, Postfix configuration
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
POSTCONF(1) POSTCONF(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postconf - Postfix configuration utility
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>Managing <a href="postconf.5.html">main.cf</a>:</b>
|
||||
|
||||
<b>postconf</b> [<b>-dfhHnopqvx</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-C</b> <i>class,...</i>] [<i>parameter ...</i>]
|
||||
@ -59,7 +59,7 @@ POSTCONF(1) POSTCONF(1)
|
||||
|
||||
<b>postconf -a</b>|<b>-A</b>|<b>-l</b>|<b>-m</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
By default, the <a href="postconf.1.html"><b>postconf</b>(1)</a> command displays the values of <a href="postconf.5.html"><b>main.cf</b></a> con-
|
||||
figuration parameters, and warns about possible mis-typed parameter
|
||||
names (Postfix 2.9 and later). The command can also change <a href="postconf.5.html"><b>main.cf</b></a>
|
||||
@ -526,14 +526,14 @@ POSTCONF(1) POSTCONF(1)
|
||||
This feature is available with Postfix 2.6 and later. Support
|
||||
for -M was added with Postfix 2.11.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are reported to the standard error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram.
|
||||
|
||||
@ -547,19 +547,19 @@ POSTCONF(1) POSTCONF(1)
|
||||
<b><a href="postconf.5.html#bounce_template_file">bounce_template_file</a> (empty)</b>
|
||||
Pathname of a configuration file with bounce message templates.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/etc/postfix/<a href="postconf.5.html">main.cf</a>, Postfix configuration parameters
|
||||
/etc/postfix/<a href="master.5.html">master.cf</a>, Postfix master daemon configuration
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="bounce.5.html">bounce(5)</a>, bounce template file format
|
||||
<a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> configuration file syntax
|
||||
<a href="postconf.5.html">postconf(5)</a>, <a href="postconf.5.html">main.cf</a> configuration file syntax
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTDROP(1) POSTDROP(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postdrop - Postfix mail posting utility
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postdrop</b> [<b>-rv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postdrop.1.html"><b>postdrop</b>(1)</a> command creates a file in the <b>maildrop</b> directory and
|
||||
copies its standard input to the file.
|
||||
|
||||
@ -32,18 +32,18 @@ POSTDROP(1) POSTDROP(1)
|
||||
options make the software increasingly verbose. As of Postfix
|
||||
2.3, this option is available for the super-user only.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The command is designed to run with set-group ID privileges, so that it
|
||||
can write to the <b>maildrop</b> queue directory and so that it can connect to
|
||||
Postfix daemon processes.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Fatal errors: malformed input, I/O error, out of memory. Problems are
|
||||
logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a> and to the standard error stream.
|
||||
When the input is incomplete, or when the process receives a HUP, INT,
|
||||
QUIT or TERM signal, the queue file is deleted.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
MAIL_CONFIG
|
||||
Directory with the <a href="postconf.5.html"><b>main.cf</b></a> file. In order to avoid exploitation
|
||||
of set-group ID privileges, a non-standard directory is allowed
|
||||
@ -54,7 +54,7 @@ POSTDROP(1) POSTDROP(1)
|
||||
|
||||
<b>o</b> The command is invoked by the super-user.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
@ -110,16 +110,16 @@ POSTDROP(1) POSTDROP(1)
|
||||
The set of characters that can separate an email address local-
|
||||
part, user name, or a .forward file name from its extension.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/<a href="QSHAPE_README.html#maildrop_queue">maildrop</a>, <a href="QSHAPE_README.html#maildrop_queue">maildrop queue</a>
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="sendmail.1.html">sendmail(1)</a>, compatibility interface
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTFIX-TLS(1) POSTFIX-TLS(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postfix-tls - Postfix TLS management
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b><a href="postfix-tls.1.html">postfix tls</a></b> <i>subcommand</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The "<b><a href="postfix-tls.1.html">postfix tls</a></b> <i>subcommand</i>" feature enables opportunistic TLS in the
|
||||
Postfix SMTP client or server, and manages Postfix SMTP server private
|
||||
keys and certificates.
|
||||
@ -148,7 +148,7 @@ POSTFIX-TLS(1) POSTFIX-TLS(1)
|
||||
The default <i>keyfile</i> list consists of the two supported algo-
|
||||
rithms <b>rsa</b> and <b>ecdsa</b>.
|
||||
|
||||
<b>AUXILIARY COMMANDS</b>
|
||||
<b><a name="auxiliary_commands">AUXILIARY COMMANDS</a></b>
|
||||
<b>all-default-client</b>
|
||||
Exit with status 0 (success) if all SMTP client TLS settings are
|
||||
at their default values. Otherwise, exit with a non-zero status.
|
||||
@ -165,7 +165,7 @@ POSTFIX-TLS(1) POSTFIX-TLS(1)
|
||||
<b><a href="postfix-tls.1.html">postfix tls</a> all-default-server</b> &&
|
||||
<b><a href="postfix-tls.1.html">postfix tls</a> enable-server</b>
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The "<b><a href="postfix-tls.1.html">postfix tls</a></b> <i>subcommand</i>" feature reads or updates the following
|
||||
configuration parameters.
|
||||
|
||||
@ -221,17 +221,17 @@ POSTFIX-TLS(1) POSTFIX-TLS(1)
|
||||
The external entropy source for the in-memory <a href="tlsmgr.8.html"><b>tlsmgr</b>(8)</a> pseudo
|
||||
random number generator (PRNG) pool.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="master.8.html">master(8)</a> Postfix master program
|
||||
<a href="postfix.1.html">postfix(1)</a> Postfix administrative interface
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="TLS_README.html">TLS_README</a>, Postfix TLS configuration and operation
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The "<b><a href="postfix-tls.1.html">postfix tls</a></b>" command was introduced with Postfix version 3.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postfix-wrapper - Postfix multi-instance API
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
Support for managing multiple Postfix instances is available as of ver-
|
||||
sion 2.6. Instances share executable files and documentation, but have
|
||||
their own directories for configuration, queue and data files.
|
||||
@ -24,7 +24,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
required. This instance is identified by the <a href="postconf.5.html#config_directory">config_directory</a> parame-
|
||||
ter's default value.
|
||||
|
||||
<b>GENERAL OPERATION</b>
|
||||
<b><a name="general_operation">GENERAL OPERATION</a></b>
|
||||
Multi-instance support is backwards compatible: when you run only one
|
||||
Postfix instance, commands such as "postfix start" will not change
|
||||
behavior at all.
|
||||
@ -46,7 +46,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
This enumerates the status of all Postfix instances within a
|
||||
multi-instance configuration.
|
||||
|
||||
<b>MANAGING AN INDIVIDUAL POSTFIX INSTANCE</b>
|
||||
<b><a name="managing_an_individual_postfix_instance">MANAGING AN INDIVIDUAL POSTFIX INSTANCE</a></b>
|
||||
To manage a specific Postfix instance, specify its configuration direc-
|
||||
tory on the <a href="postfix.1.html">postfix(1)</a> command line:
|
||||
|
||||
@ -127,7 +127,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
|
||||
exit $err
|
||||
|
||||
<b>PER-INSTANCE MULTI-INSTANCE MANAGER CONTROLS</b>
|
||||
<b><a name="per-instance_multi-instance_manager_controls">PER-INSTANCE MULTI-INSTANCE MANAGER CONTROLS</a></b>
|
||||
Each Postfix instance has its own <a href="postconf.5.html">main.cf</a> file with parameters that
|
||||
control how the multi-instance manager operates on that instance. This
|
||||
section discusses the most important settings.
|
||||
@ -145,7 +145,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
"check" so that problems will be reported even when the instance is
|
||||
disabled.
|
||||
|
||||
<b>MAINTAINING SHARED AND NON-SHARED FILES</b>
|
||||
<b><a name="maintaining_shared_and_non-shared_files">MAINTAINING SHARED AND NON-SHARED FILES</a></b>
|
||||
Some files are shared between Postfix instances, such as executables
|
||||
and manpages, and some files are per-instance, such as configuration
|
||||
files, mail queue files, and data files. See the NON-SHARED FILES sec-
|
||||
@ -163,7 +163,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
The consequence of this approach is that the default Postfix instance
|
||||
should be checked and updated before any other instances.
|
||||
|
||||
<b>MULTI-INSTANCE API SUMMARY</b>
|
||||
<b><a name="multi-instance_api_summary">MULTI-INSTANCE API SUMMARY</a></b>
|
||||
Only the multi-instance manager implements support for the
|
||||
<a href="postconf.5.html#multi_instance_enable">multi_instance_enable</a> configuration parameter. The multi-instance man-
|
||||
ager will start only Postfix instances whose <a href="postconf.5.html">main.cf</a> file has
|
||||
@ -205,14 +205,14 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
Postfix, or that are not managed together with the default Postfix
|
||||
instance.
|
||||
|
||||
<b>ENVIRONMENT VARIABLES</b>
|
||||
<b><a name="environment_variables">ENVIRONMENT VARIABLES</a></b>
|
||||
MAIL_CONFIG
|
||||
When present, this forces the <a href="postfix.1.html">postfix(1)</a> command to operate only
|
||||
on the specified Postfix instance. This environment variable is
|
||||
exported by the <a href="postfix.1.html">postfix(1)</a> -c option, so that <a href="postfix.1.html">postfix(1)</a> com-
|
||||
mands in descendant processes will work correctly.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The text below provides only a parameter summary. See <a href="postconf.5.html">postconf(5)</a> for
|
||||
more details.
|
||||
|
||||
@ -238,7 +238,7 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
Allow this Postfix instance to be started, stopped, etc., by a
|
||||
multi-instance manager.
|
||||
|
||||
<b>NON-SHARED FILES</b>
|
||||
<b><a name="non-shared_files">NON-SHARED FILES</a></b>
|
||||
<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.
|
||||
@ -250,12 +250,12 @@ POSTFIX-WRAPPER(5) POSTFIX-WRAPPER(5)
|
||||
<b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
|
||||
The location of the Postfix top-level queue directory.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postfix.1.html">postfix(1)</a> Postfix control program
|
||||
<a href="postmulti.1.html">postmulti(1)</a> full-blown multi-instance manager
|
||||
$<a href="postconf.5.html#daemon_directory">daemon_directory</a>/postfix-wrapper simple multi-instance manager
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTFIX(1) POSTFIX(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postfix - Postfix control program
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postfix</b> [<b>-Dv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <i>command</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
This command is reserved for the superuser. To submit mail, use the
|
||||
Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command.
|
||||
|
||||
@ -138,7 +138,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
The <a href="postfix.1.html"><b>postfix</b>(1)</a> command exports the following environment variables
|
||||
before executing the <b>postfix-script</b> file:
|
||||
|
||||
@ -167,7 +167,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
<b>POSTLOG_HOSTNAME</b>
|
||||
The hostname to prepend to internal logging.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> configuration parameters are exported as environ-
|
||||
ment variables with the same names:
|
||||
|
||||
@ -303,7 +303,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
<b><a href="postconf.5.html#postlog_service_name">postlog_service_name</a> (postlog)</b>
|
||||
The name of the <a href="postlogd.8.html"><b>postlogd</b>(8)</a> service entry in <a href="master.5.html">master.cf</a>.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
Prior to Postfix version 2.6, all of the following files were in <b>$<a href="postconf.5.html#config_directory">con</a>-</b>
|
||||
<b><a href="postconf.5.html#config_directory">fig_directory</a></b>. Some files are now in <b>$<a href="postconf.5.html#daemon_directory">daemon_directory</a></b> or <b>$meta_direc-</b>
|
||||
<b>tory</b> so that they can be shared among multiple instances that run the
|
||||
@ -319,7 +319,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
$<a href="postconf.5.html#meta_directory">meta_directory</a>/dynamicmaps.cf, plug-in database clients
|
||||
$<a href="postconf.5.html#meta_directory">meta_directory</a>/postfix-files, file/directory permissions
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
Commands:
|
||||
<a href="postalias.1.html">postalias(1)</a>, create/update/query alias database
|
||||
<a href="postcat.1.html">postcat(1)</a>, examine Postfix queue file
|
||||
@ -401,7 +401,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
Other:
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="OVERVIEW.html">OVERVIEW</a>, overview of Postfix commands and processes
|
||||
<a href="BASIC_CONFIGURATION_README.html">BASIC_CONFIGURATION_README</a>, Postfix basic configuration
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, Postfix address rewriting
|
||||
@ -409,7 +409,7 @@ POSTFIX(1) POSTFIX(1)
|
||||
<a href="CONTENT_INSPECTION_README.html">CONTENT_INSPECTION_README</a>, Postfix content inspection
|
||||
<a href="QSHAPE_README.html">QSHAPE_README</a>, Postfix queue analysis
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTKICK(1) POSTKICK(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postkick - kick a Postfix service
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postkick</b> [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-v</b>] <i>class service request</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postkick.1.html"><b>postkick</b>(1)</a> command sends <i>request</i> to the specified <i>service</i> over a
|
||||
local transport channel. This command makes Postfix private IPC acces-
|
||||
sible for use in, for example, shell scripts.
|
||||
@ -39,17 +39,17 @@ POSTKICK(1) POSTKICK(1)
|
||||
<i>request</i>
|
||||
A string. The list of valid requests is service-specific.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to the standard error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>MAIL_VERBOSE</b>
|
||||
Enable verbose logging for debugging purposes.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
@ -70,16 +70,16 @@ POSTKICK(1) POSTKICK(1)
|
||||
<b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
|
||||
The location of the Postfix top-level queue directory.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/private, private class endpoints
|
||||
/var/spool/postfix/public, public class endpoints
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager trigger protocol
|
||||
<a href="pickup.8.html">pickup(8)</a>, local pickup daemon
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,14 +7,14 @@
|
||||
</head> <body> <pre>
|
||||
POSTLOCK(1) POSTLOCK(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postlock - lock mail folder and execute command
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postlock</b> [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-l</b> <i>lock</i><b>_</b><i>style</i>]
|
||||
[<b>-v</b>] <i>file command...</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postlock.1.html"><b>postlock</b>(1)</a> command locks <i>file</i> for exclusive access, and executes
|
||||
<i>command</i>. The locking method is compatible with the Postfix UNIX-style
|
||||
local delivery agent.
|
||||
@ -41,29 +41,29 @@ POSTLOCK(1) POSTLOCK(1)
|
||||
access. The command is executed directly, i.e. without inter-
|
||||
pretation by a shell command interpreter.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
The result status is 75 (EX_TEMPFAIL) when <a href="postlock.1.html"><b>postlock</b>(1)</a> could not per-
|
||||
form the requested operation. Otherwise, the exit status is the exit
|
||||
status from the command.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
With remote file systems, the ability to acquire a lock does not neces-
|
||||
sarily eliminate access conflicts. Avoid file access by processes run-
|
||||
ning on different machines.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>MAIL_VERBOSE</b>
|
||||
Enable verbose logging for debugging purposes.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
|
||||
<b>LOCKING CONTROLS</b>
|
||||
<b><a name="locking_controls">LOCKING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#deliver_lock_attempts">deliver_lock_attempts</a> (20)</b>
|
||||
The maximal number of attempts to acquire an exclusive lock on a
|
||||
mailbox file or <a href="bounce.8.html"><b>bounce</b>(8)</a> logfile.
|
||||
@ -80,14 +80,14 @@ POSTLOCK(1) POSTLOCK(1)
|
||||
How to lock a UNIX-style <a href="local.8.html"><b>local</b>(8)</a> mailbox before attempting
|
||||
delivery.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#fork_attempts">fork_attempts</a> (5)</b>
|
||||
The maximal number of attempts to fork() a child process.
|
||||
|
||||
<b><a href="postconf.5.html#fork_delay">fork_delay</a> (1s)</b>
|
||||
The delay between attempts to fork() a child process.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -97,10 +97,10 @@ POSTLOCK(1) POSTLOCK(1)
|
||||
process will import from a non-Postfix parent process, or
|
||||
name=value environment overrides.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTLOG(1) POSTLOG(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postlog - Postfix-compatible logging utility
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postlog</b> [<b>-iv</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-p</b> <i>priority</i>] [<b>-t</b> <i>tag</i>] [<i>text...</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postlog.1.html"><b>postlog</b>(1)</a> command implements a Postfix-compatible logging inter-
|
||||
face for use in, for example, shell scripts.
|
||||
|
||||
@ -48,17 +48,17 @@ POSTLOG(1) POSTLOG(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="postlog.1.html"><b>postlog</b>(1)</a> command is designed to run with set-groupid privileges,
|
||||
so that it can connect to the <a href="postlogd.8.html"><b>postlogd</b>(8)</a> daemon process (Postfix 3.7
|
||||
and later; earlier implementations of this command must not have
|
||||
set-groupid or set-userid permissions).
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
MAIL_CONFIG
|
||||
Directory with the <a href="postconf.5.html"><b>main.cf</b></a> file.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram.
|
||||
|
||||
@ -97,15 +97,15 @@ POSTLOG(1) POSTLOG(1)
|
||||
$<a href="postconf.5.html#maillog_file">maillog_file</a> is created for the first time, or when the file is
|
||||
created after an existing file is rotated.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The <a href="postlog.1.html"><b>postlog</b>(1)</a> command was introduced with Postfix version 3.4.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
POSTLOGD(8) POSTLOGD(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postlogd - Postfix internal log server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postlogd</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
This program logs events on behalf of Postfix programs when the maillog
|
||||
configuration parameter specifies a non-empty value.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Non-daemon Postfix programs don't know that they should log to the
|
||||
internal logging service before they have processed command-line
|
||||
options and <a href="postconf.5.html">main.cf</a> parameters. These programs still log earlier events
|
||||
@ -35,7 +35,7 @@ POSTLOGD(8) POSTLOGD(8)
|
||||
mission. Do not set this permission on programs other than <a href="postdrop.1.html"><b>postdrop</b>(1)</a>,
|
||||
<a href="postqueue.1.html"><b>postqueue</b>(1)</a> and (Postfix >= 3.7) <a href="postlog.1.html"><b>postlog</b>(1)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically, because <a href="postlogd.8.html"><b>postlogd</b>(8)</a>
|
||||
terminates only after reaching the <b><a href="postconf.5.html#max_idle">max_idle</a></b> time limit. Use the com-
|
||||
mand "<b>postfix reload</b>" to speed up a change.
|
||||
@ -75,19 +75,19 @@ POSTLOGD(8) POSTLOGD(8)
|
||||
$<a href="postconf.5.html#maillog_file">maillog_file</a> is created for the first time, or when the file is
|
||||
created after an existing file is rotated.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README_FILES</b>
|
||||
<b><a name="readme_files">README_FILES</a></b>
|
||||
Use "<b>postconf <a href="postconf.5.html#readme_directory">readme_directory</a></b>" or "<b>postconf <a href="postconf.5.html#html_directory">html_directory</a></b>" to locate
|
||||
this information.
|
||||
<a href="MAILLOG_README.html">MAILLOG_README</a>, Postfix logging to file or stdout
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 3.4.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,14 +7,14 @@
|
||||
</head> <body> <pre>
|
||||
POSTMAP(1) POSTMAP(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postmap - Postfix lookup table management
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap</b> [<b>-bfFhimnNoprsuUvw</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-d</b> <i>key</i>] [<b>-q</b> <i>key</i>]
|
||||
[<i>file</i><b>_</b><i>type</i>:]<i>file</i><b>_</b><i>name</i> ...
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postmap.1.html"><b>postmap</b>(1)</a> command creates or queries one or more Postfix lookup
|
||||
tables, or updates an existing one.
|
||||
|
||||
@ -25,7 +25,7 @@ POSTMAP(1) POSTMAP(1)
|
||||
and an exclusive, advisory, lock is placed on the entire table, in
|
||||
order to avoid surprises in spectator processes.
|
||||
|
||||
<b>INPUT FILE FORMAT</b>
|
||||
<b><a name="input_file_format">INPUT FILE FORMAT</a></b>
|
||||
The format of a lookup table input file is as follows:
|
||||
|
||||
<b>o</b> A table entry has the form
|
||||
@ -62,7 +62,7 @@ POSTMAP(1) POSTMAP(1)
|
||||
<a href="regexp_table.5.html">regexp</a>: and <a href="pcre_table.5.html">pcre</a>:. This resulted in loss of information with $<i>number</i>
|
||||
substitutions.
|
||||
|
||||
<b>COMMAND-LINE ARGUMENTS</b>
|
||||
<b><a name="command-line_arguments">COMMAND-LINE ARGUMENTS</a></b>
|
||||
<b>-b</b> Enable message body query mode. When reading lookup keys from
|
||||
standard input with "<b>-q -</b>", process the input as if it is an
|
||||
email message in <a href="https://tools.ietf.org/html/rfc5322">RFC 5322</a> format. Each line of body content
|
||||
@ -235,7 +235,7 @@ POSTMAP(1) POSTMAP(1)
|
||||
The name of the lookup table source file when rebuilding a data-
|
||||
base.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to the standard error stream and to <b>syslogd</b>(8) or
|
||||
<a href="postlogd.8.html"><b>postlogd</b>(8)</a>. No output means that no problems were detected. Duplicate
|
||||
entries are skipped and are flagged with a warning.
|
||||
@ -244,14 +244,14 @@ POSTMAP(1) POSTMAP(1)
|
||||
ing successful "<b>postmap -q</b>" lookup) and terminates with non-zero exit
|
||||
status in case of failure.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
<b>MAIL_VERBOSE</b>
|
||||
Enable verbose logging for debugging purposes.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
@ -293,17 +293,17 @@ POSTMAP(1) POSTMAP(1)
|
||||
<b><a href="postconf.5.html#lmdb_map_size">lmdb_map_size</a> (16777216)</b>
|
||||
The initial OpenLDAP LMDB database size limit in bytes.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postalias.1.html">postalias(1)</a>, create/update/query alias database
|
||||
<a href="postconf.1.html">postconf(1)</a>, supported database types
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
POSTMULTI(1) POSTMULTI(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postmulti - Postfix multi-instance manager
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>Enabling multi-instance management:</b>
|
||||
|
||||
<b>postmulti -e init</b> [<b>-v</b>]
|
||||
@ -41,7 +41,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
|
||||
<b>postmulti -e assign</b> [<b>-v</b>] <b>-i</b> <i>name</i> [<b>-I</b> <i>name</i>] [-G <i>group</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postmulti.1.html"><b>postmulti</b>(1)</a> command allows a Postfix administrator to manage mul-
|
||||
tiple Postfix instances on a single host.
|
||||
|
||||
@ -53,7 +53,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
Each mode of operation has its own command syntax. For this reason,
|
||||
each mode is documented in separate sections below.
|
||||
|
||||
<b>BACKGROUND</b>
|
||||
<b><a name="background">BACKGROUND</a></b>
|
||||
A multi-instance configuration consists of one primary Postfix
|
||||
instance, and one or more secondary instances whose configuration
|
||||
directory pathnames are recorded in the primary instance's <a href="postconf.5.html">main.cf</a>
|
||||
@ -69,7 +69,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
See the <a href="MULTI_INSTANCE_README.html">MULTI_INSTANCE_README</a> tutorial for a more detailed discussion
|
||||
of multi-instance management with <a href="postmulti.1.html"><b>postmulti</b>(1)</a>.
|
||||
|
||||
<b>ITERATOR MODE</b>
|
||||
<b><a name="iterator_mode">ITERATOR MODE</a></b>
|
||||
In iterator mode, <b>postmulti</b> performs the same operation on all Postfix
|
||||
instances in turn.
|
||||
|
||||
@ -143,7 +143,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>LIFE-CYCLE MANAGEMENT MODE</b>
|
||||
<b><a name="life-cycle_management_mode">LIFE-CYCLE MANAGEMENT MODE</a></b>
|
||||
With the <b>-e</b> option <a href="postmulti.1.html"><b>postmulti</b>(1)</a> can be used to add or delete a Postfix
|
||||
instance, and to manage the multi-instance status of an existing
|
||||
instance.
|
||||
@ -301,7 +301,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
The <a href="postmulti.1.html"><b>postmulti</b>(1)</a> command exports the following environment variables
|
||||
before executing the requested <i>command</i> for a given instance:
|
||||
|
||||
@ -311,7 +311,7 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
<b>MAIL_CONFIG</b>
|
||||
The location of the configuration directory of the instance.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
<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.
|
||||
@ -374,22 +374,22 @@ POSTMULTI(1) POSTMULTI(1)
|
||||
(postfix-*.so) that have a relative pathname in the dynam-
|
||||
icmaps.cf file.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
$<a href="postconf.5.html#meta_directory">meta_directory</a>/<a href="postconf.5.html">main.cf</a>.proto, stock configuration file
|
||||
$<a href="postconf.5.html#meta_directory">meta_directory</a>/<a href="master.5.html">master.cf</a>.proto, stock configuration file
|
||||
$<a href="postconf.5.html#daemon_directory">daemon_directory</a>/postmulti-script, life-cycle helper program
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postfix.1.html">postfix(1)</a>, Postfix control program
|
||||
<a href="postfix-wrapper.5.html">postfix-wrapper(5)</a>, Postfix multi-instance API
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="MULTI_INSTANCE_README.html">MULTI_INSTANCE_README</a>, Postfix multi-instance management
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The <a href="postmulti.1.html"><b>postmulti</b>(1)</a> command was introduced with Postfix version 2.6.
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
POSTQUEUE(1) POSTQUEUE(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postqueue - Postfix queue control
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>To flush the mail queue</b>:
|
||||
|
||||
<b>postqueue</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <b>-f</b>
|
||||
@ -25,7 +25,7 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
|
||||
<b>postqueue</b> [<b>-v</b>] [<b>-c</b> <i>config</i><b>_</b><i>dir</i>] <b>-p</b>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postqueue.1.html"><b>postqueue</b>(1)</a> command implements the Postfix user interface for
|
||||
queue management. It implements operations that are traditionally
|
||||
available via the <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command. See the <a href="postsuper.1.html"><b>postsuper</b>(1)</a> command
|
||||
@ -99,7 +99,7 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
options make the software increasingly verbose. As of Postfix
|
||||
2.3, this option is available for the super-user only.
|
||||
|
||||
<b>JSON OBJECT FORMAT</b>
|
||||
<b><a name="json_object_format">JSON OBJECT FORMAT</a></b>
|
||||
Each JSON object represents one queue file; it is emitted as a single
|
||||
text line followed by a newline character.
|
||||
|
||||
@ -150,18 +150,18 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
delivery is in progress, or after the system was stopped
|
||||
before it could record the reason.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
This program is designed to run with set-group ID privileges, so that
|
||||
it can connect to Postfix daemon processes.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc7159">RFC 7159</a> (JSON notation)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>, and to the standard
|
||||
error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
MAIL_CONFIG
|
||||
Directory with the <a href="postconf.5.html"><b>main.cf</b></a> file. In order to avoid exploitation
|
||||
of set-group ID privileges, a non-standard directory is allowed
|
||||
@ -172,7 +172,7 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
|
||||
<b>o</b> The command is invoked by the super-user.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
@ -221,10 +221,10 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
<b><a href="postconf.5.html#authorized_mailq_users">authorized_mailq_users</a> (<a href="DATABASE_README.html#types">static</a>:anyone)</b>
|
||||
List of users who are authorized to view the queue.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, mail queue
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="showq.8.html">showq(8)</a>, list mail queue
|
||||
<a href="flush.8.html">flush(8)</a>, fast flush service
|
||||
@ -233,13 +233,13 @@ POSTQUEUE(1) POSTQUEUE(1)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ETRN_README.html">ETRN_README</a>, Postfix ETRN howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The postqueue command was introduced with Postfix version 1.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
POSTSCREEN(8) POSTSCREEN(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postscreen - Postfix zombie blocker
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postscreen</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="postscreen.8.html"><b>postscreen</b>(8)</a> server provides additional protection against
|
||||
mail server overload. One <a href="postscreen.8.html"><b>postscreen</b>(8)</a> process handles multiple
|
||||
inbound SMTP connections, and decides which clients may talk to a Post-
|
||||
@ -50,12 +50,12 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
is to keep spambots away from Postfix SMTP server processes, while min-
|
||||
imizing overhead for legitimate traffic.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="postscreen.8.html"><b>postscreen</b>(8)</a> server is moderately security-sensitive. It talks to
|
||||
untrusted clients on the network. The process can be run chrooted at
|
||||
fixed low privilege.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc821">RFC 821</a> (SMTP protocol)
|
||||
<a href="https://tools.ietf.org/html/rfc1123">RFC 1123</a> (Host requirements)
|
||||
<a href="https://tools.ietf.org/html/rfc1652">RFC 1652</a> (8bit-MIME transport)
|
||||
@ -71,10 +71,10 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced Status Codes)
|
||||
<a href="https://tools.ietf.org/html/rfc5321">RFC 5321</a> (SMTP protocol, including multi-line 220 banners)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The <a href="postscreen.8.html"><b>postscreen</b>(8)</a> built-in SMTP protocol engine currently does not
|
||||
announce support for AUTH, XCLIENT or XFORWARD. If you need to make
|
||||
these services available on port 25, then do not enable the optional
|
||||
@ -87,7 +87,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
mail. See <a href="POSTSCREEN_README.html">POSTSCREEN_README</a>, section "Tests after the 220 SMTP server
|
||||
greeting", for a discussion.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html">main.cf</a> are not picked up automatically, as <a href="postscreen.8.html"><b>postscreen</b>(8)</a>
|
||||
processes may run for several hours. Use the command "postfix reload"
|
||||
after a configuration change.
|
||||
@ -102,7 +102,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
Other parameters always evaluate as if the <b>stress</b> parameter value is
|
||||
the empty string.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#postscreen_command_filter">postscreen_command_filter</a> ($<a href="postconf.5.html#smtpd_command_filter">smtpd_command_filter</a>)</b>
|
||||
A mechanism to transform commands from remote SMTP clients.
|
||||
|
||||
@ -134,7 +134,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
<b><a href="postconf.5.html#respectful_logging">respectful_logging</a> (see 'postconf -d' output)</b>
|
||||
Avoid logging that implies white is better than black.
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#postscreen_expansion_filter">postscreen_expansion_filter</a> (see 'postconf -d' output)</b>
|
||||
List of characters that are permitted in
|
||||
<a href="postconf.5.html#postscreen_reject_footer">postscreen_reject_footer</a> attribute expansions.
|
||||
@ -147,7 +147,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
Safety net to keep mail queued that would otherwise be returned
|
||||
to the sender.
|
||||
|
||||
<b>BEFORE-POSTSCREEN PROXY AGENT</b>
|
||||
<b><a name="before-postscreen_proxy_agent">BEFORE-POSTSCREEN PROXY AGENT</a></b>
|
||||
Available in Postfix version 2.10 and later:
|
||||
|
||||
<b><a href="postconf.5.html#postscreen_upstream_proxy_protocol">postscreen_upstream_proxy_protocol</a> (empty)</b>
|
||||
@ -169,7 +169,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
<b><a href="postconf.5.html#postscreen_blacklist_action">postscreen_blacklist_action</a> (ignore)</b>
|
||||
Renamed to <a href="postconf.5.html#postscreen_denylist_action">postscreen_denylist_action</a> in Postfix 3.6.
|
||||
|
||||
<b>MAIL EXCHANGER POLICY TESTS</b>
|
||||
<b><a name="mail_exchanger_policy_tests">MAIL EXCHANGER POLICY TESTS</a></b>
|
||||
When <a href="postscreen.8.html"><b>postscreen</b>(8)</a> is configured to monitor all primary and backup MX
|
||||
addresses, it can refuse to allowlist clients that connect to a backup
|
||||
MX address only. For small sites, this requires configuring primary and
|
||||
@ -182,7 +182,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
non-allowlisted remote SMTP client can obtain <a href="postscreen.8.html"><b>postscreen</b>(8)</a>'s
|
||||
temporary allowlist status.
|
||||
|
||||
<b>BEFORE 220 GREETING TESTS</b>
|
||||
<b><a name="before_220_greeting_tests">BEFORE 220 GREETING TESTS</a></b>
|
||||
These tests are executed before the remote SMTP client receives the
|
||||
"220 servername" greeting. If no tests remain after the successful com-
|
||||
pletion of this phase, the client will be handed off immediately to a
|
||||
@ -259,7 +259,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
greeting" protocol tests, based on its combined DNSBL score as
|
||||
defined with the <a href="postconf.5.html#postscreen_dnsbl_sites">postscreen_dnsbl_sites</a> parameter.
|
||||
|
||||
<b>AFTER 220 GREETING TESTS</b>
|
||||
<b><a name="after_220_greeting_tests">AFTER 220 GREETING TESTS</a></b>
|
||||
These tests are executed after the remote SMTP client receives the "220
|
||||
servername" greeting. If a client passes all tests during this phase,
|
||||
it will receive a 4XX response to all RCPT TO commands. After the
|
||||
@ -303,7 +303,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
Enable "pipelining" SMTP protocol tests in the <a href="postscreen.8.html"><b>postscreen</b>(8)</a>
|
||||
server.
|
||||
|
||||
<b>CACHE CONTROLS</b>
|
||||
<b><a name="cache_controls">CACHE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#postscreen_cache_cleanup_interval">postscreen_cache_cleanup_interval</a> (12h)</b>
|
||||
The amount of time between <a href="postscreen.8.html"><b>postscreen</b>(8)</a> cache cleanup runs.
|
||||
|
||||
@ -345,7 +345,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
address passed a "pipelining" SMTP protocol test, before it is
|
||||
required to pass that test again.
|
||||
|
||||
<b>RESOURCE CONTROLS</b>
|
||||
<b><a name="resource_controls">RESOURCE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#line_length_limit">line_length_limit</a> (2048)</b>
|
||||
Upon input, long lines are chopped up into pieces of at most
|
||||
this length; upon delivery, long lines are reconstructed.
|
||||
@ -377,7 +377,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
remote SMTP client command or to perform a cache operation
|
||||
before it is terminated by a built-in watchdog timer.
|
||||
|
||||
<b>STARTTLS CONTROLS</b>
|
||||
<b><a name="starttls_controls">STARTTLS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#postscreen_tls_security_level">postscreen_tls_security_level</a> ($<a href="postconf.5.html#smtpd_tls_security_level">smtpd_tls_security_level</a>)</b>
|
||||
The SMTP TLS security level for the <a href="postscreen.8.html"><b>postscreen</b>(8)</a> server; when a
|
||||
non-empty value is specified, this overrides the obsolete param-
|
||||
@ -386,7 +386,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
<b><a href="postconf.5.html#tlsproxy_service_name">tlsproxy_service_name</a> (tlsproxy)</b>
|
||||
The name of the <a href="tlsproxy.8.html"><b>tlsproxy</b>(8)</a> service entry in <a href="master.5.html">master.cf</a>.
|
||||
|
||||
<b>OBSOLETE STARTTLS SUPPORT CONTROLS</b>
|
||||
<b><a name="obsolete_starttls_support_controls">OBSOLETE STARTTLS SUPPORT CONTROLS</a></b>
|
||||
These parameters are supported for compatibility with <a href="smtpd.8.html"><b>smtpd</b>(8)</a> legacy
|
||||
parameters.
|
||||
|
||||
@ -398,7 +398,7 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
Mandatory TLS: announce STARTTLS support to remote SMTP clients,
|
||||
and require that clients use TLS encryption.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -438,20 +438,20 @@ POSTSCREEN(8) POSTSCREEN(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
|
||||
<a href="tlsproxy.8.html">tlsproxy(8)</a>, Postfix TLS proxy server
|
||||
<a href="dnsblog.8.html">dnsblog(8)</a>, DNS allow/denylist logger
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="POSTSCREEN_README.html">POSTSCREEN_README</a>, Postfix Postscreen Howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.8.
|
||||
|
||||
Many ideas in <a href="postscreen.8.html"><b>postscreen</b>(8)</a> were explored in earlier work by Michael
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
POSTSUPER(1) POSTSUPER(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
postsuper - Postfix superintendent
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postsuper</b> [<b>-psSv</b>]
|
||||
[<b>-c</b> <i>config</i><b>_</b><i>dir</i>] [<b>-d</b> <i>queue</i><b>_</b><i>id</i>]
|
||||
[<b>-e</b> <i>queue</i><b>_</b><i>id</i>] [<b>-f</b> <i>queue</i><b>_</b><i>id</i>]
|
||||
[<b>-h</b> <i>queue</i><b>_</b><i>id</i>] [<b>-H</b> <i>queue</i><b>_</b><i>id</i>]
|
||||
[<b>-r</b> <i>queue</i><b>_</b><i>id</i>] [<i>directory ...</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="postsuper.1.html"><b>postsuper</b>(1)</a> command does maintenance jobs on the Postfix queue.
|
||||
Use of the command is restricted to the superuser. See the
|
||||
<a href="postqueue.1.html"><b>postqueue</b>(1)</a> command for unprivileged queue operations such as listing
|
||||
@ -238,7 +238,7 @@ POSTSUPER(1) POSTSUPER(1)
|
||||
<b>-v</b> Enable verbose logging for debugging purposes. Multiple <b>-v</b>
|
||||
options make the software increasingly verbose.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are reported to the standard error stream and to <b>syslogd</b>(8) or
|
||||
<a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
@ -249,15 +249,15 @@ POSTSUPER(1) POSTSUPER(1)
|
||||
queue file name was fixed with <b>-s</b>. The report is written to the stan-
|
||||
dard error stream and to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
MAIL_CONFIG
|
||||
Directory with the <a href="postconf.5.html"><b>main.cf</b></a> file.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Mail that is not sanitized by Postfix (i.e. mail in the <b>maildrop</b> queue)
|
||||
cannot be placed "on hold".
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
@ -294,13 +294,13 @@ POSTSUPER(1) POSTSUPER(1)
|
||||
<b><a href="postconf.5.html#enable_long_queue_ids">enable_long_queue_ids</a> (no)</b>
|
||||
Enable long, non-repeating, queue IDs (queue file names).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="sendmail.1.html">sendmail(1)</a>, Sendmail-compatible user interface
|
||||
<a href="postqueue.1.html">postqueue(1)</a>, unprivileged queue operations
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,14 +7,14 @@
|
||||
</head> <body> <pre>
|
||||
POSTTLS-FINGER(1) POSTTLS-FINGER(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
posttls-finger - Probe the TLS properties of an ESMTP or LMTP server.
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>posttls-finger</b> [<i>options</i>] [<b>inet:</b>]<i>domain</i>[:<i>port</i>] [<i>match ...</i>]
|
||||
<b>posttls-finger</b> -S [<i>options</i>] <b>unix:</b><i>pathname</i> [<i>match ...</i>]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
<a href="posttls-finger.1.html"><b>posttls-finger</b>(1)</a> connects to the specified destination and reports
|
||||
TLS-related information about the server. With SMTP, the destination is
|
||||
a domainname; with LMTP it is either a domainname prefixed with <b>inet:</b>
|
||||
@ -341,21 +341,21 @@ POSTTLS-FINGER(1) POSTTLS-FINGER(1)
|
||||
is <b>dane</b>, or <b>dane-only</b> the match names are ignored, and <b>hostname,</b>
|
||||
<b>nexthop</b> strategies are used.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Read configuration parameters from a non-default location.
|
||||
|
||||
<b>MAIL_VERBOSE</b>
|
||||
Same as <b>-v</b> option.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtp-source.1.html">smtp-source(1)</a>, SMTP/LMTP message source
|
||||
<a href="smtp-sink.1.html">smtp-sink(1)</a>, SMTP/LMTP message dump
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="TLS_README.html">TLS_README</a>, Postfix STARTTLS howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
PROXYMAP(8) PROXYMAP(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
proxymap - Postfix lookup table proxy server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>proxymap</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></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
|
||||
@ -90,7 +90,7 @@ PROXYMAP(8) PROXYMAP(8)
|
||||
client disconnects. The purpose is to share tables among multiple
|
||||
client processes.
|
||||
|
||||
<b>SERVER PROCESS MANAGEMENT</b>
|
||||
<b><a name="server_process_management">SERVER PROCESS MANAGEMENT</a></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
|
||||
@ -98,7 +98,7 @@ PROXYMAP(8) PROXYMAP(8)
|
||||
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>
|
||||
<b><a name="security">SECURITY</a></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.
|
||||
@ -123,10 +123,10 @@ PROXYMAP(8) PROXYMAP(8)
|
||||
where ownership of a file or directory does not match the provider of
|
||||
its content.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></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.
|
||||
|
||||
@ -138,7 +138,7 @@ PROXYMAP(8) PROXYMAP(8)
|
||||
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>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></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.
|
||||
@ -195,17 +195,17 @@ PROXYMAP(8) PROXYMAP(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></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>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The proxymap service was introduced with Postfix 2.0.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
QMGR(8) QMGR(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
qmgr - Postfix queue manager
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>qmgr</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon awaits the arrival of incoming mail and arranges for
|
||||
its delivery via Postfix delivery processes. The actual mail routing
|
||||
strategy is delegated to the <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon. This program
|
||||
@ -23,7 +23,7 @@ QMGR(8) QMGR(8)
|
||||
carded. This stops potential loops caused by undeliverable bounce
|
||||
notifications.
|
||||
|
||||
<b>MAIL QUEUES</b>
|
||||
<b><a name="mail_queues">MAIL QUEUES</a></b>
|
||||
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon maintains the following queues:
|
||||
|
||||
<b>incoming</b>
|
||||
@ -45,7 +45,7 @@ QMGR(8) QMGR(8)
|
||||
<b>hold</b> Messages that are kept "on hold" are kept here until someone
|
||||
sets them free.
|
||||
|
||||
<b>DELIVERY STATUS REPORTS</b>
|
||||
<b><a name="delivery_status_reports">DELIVERY STATUS REPORTS</a></b>
|
||||
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon keeps an eye on per-message delivery status reports
|
||||
in the following directories. Each status report file has the same name
|
||||
as the corresponding message file:
|
||||
@ -63,7 +63,7 @@ QMGR(8) QMGR(8)
|
||||
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is responsible for asking the <a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or
|
||||
<a href="trace.8.html"><b>trace</b>(8)</a> daemons to send delivery reports.
|
||||
|
||||
<b>STRATEGIES</b>
|
||||
<b><a name="strategies">STRATEGIES</a></b>
|
||||
The queue manager implements a variety of strategies for either opening
|
||||
queue files (input) or for message delivery (output).
|
||||
|
||||
@ -103,7 +103,7 @@ QMGR(8) QMGR(8)
|
||||
delay while still preserving the correct per-message delays,
|
||||
using a sophisticated preemptive message scheduling.
|
||||
|
||||
<b>TRIGGERS</b>
|
||||
<b><a name="triggers">TRIGGERS</a></b>
|
||||
On an idle system, the queue manager waits for the arrival of trigger
|
||||
events, or it waits for a timer to go off. A trigger is a one-byte mes-
|
||||
sage. Depending on the message received, the queue manager performs
|
||||
@ -138,18 +138,18 @@ QMGR(8) QMGR(8)
|
||||
<a href="QSHAPE_README.html#deferred_queue">deferred queue</a> run, one would request <b>A F D</b>; in order to notify the
|
||||
queue manager of the arrival of new mail one would request <b>I</b>.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced status codes)
|
||||
<a href="https://tools.ietf.org/html/rfc3464">RFC 3464</a> (Delivery status notifications)
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is not security sensitive. It reads single-character
|
||||
messages from untrusted local users, and thus may be susceptible to
|
||||
denial of service attacks. The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon does not talk to the out-
|
||||
side world, and it can be run at fixed low privilege in a chrooted
|
||||
environment.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
Corrupted message files are saved to the <b>corrupt</b> queue for further
|
||||
inspection.
|
||||
@ -157,12 +157,12 @@ QMGR(8) QMGR(8)
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces and of other trouble.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
A single queue manager process has to compete for disk access with mul-
|
||||
tiple front-end processes such as <a href="cleanup.8.html"><b>cleanup</b>(8)</a>. A sudden burst of inbound
|
||||
mail can negatively impact outbound delivery rates.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically as <a href="qmgr.8.html"><b>qmgr</b>(8)</a> is a per-
|
||||
sistent process. Use the "<b>postfix reload</b>" command after a configuration
|
||||
change.
|
||||
@ -172,7 +172,7 @@ QMGR(8) QMGR(8)
|
||||
|
||||
In the text below, <i>transport</i> is the first field in a <a href="master.5.html"><b>master.cf</b></a> entry.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
Available before Postfix version 2.5:
|
||||
|
||||
<b><a href="postconf.5.html#allow_min_user">allow_min_user</a> (no)</b>
|
||||
@ -186,7 +186,7 @@ QMGR(8) QMGR(8)
|
||||
next-hop destination, use $<a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> instead; when
|
||||
that value is empty, use the domain in the recipient address.
|
||||
|
||||
<b><a href="QSHAPE_README.html#active_queue">ACTIVE QUEUE</a> CONTROLS</b>
|
||||
<b><a name="active_queue_controls">ACTIVE QUEUE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmgr_clog_warn_time">qmgr_clog_warn_time</a> (300s)</b>
|
||||
The minimal delay between warnings that a specific destination
|
||||
is clogging up the Postfix <a href="QSHAPE_README.html#active_queue">active queue</a>.
|
||||
@ -240,7 +240,7 @@ QMGR(8) QMGR(8)
|
||||
<a href="postconf.5.html#default_recipient_refill_delay">ent_refill_delay</a> parameter value, where <i>transport</i> is the <a href="master.5.html">mas-
|
||||
ter.cf</a> name of the message delivery transport.
|
||||
|
||||
<b>DELIVERY CONCURRENCY CONTROLS</b>
|
||||
<b><a name="delivery_concurrency_controls">DELIVERY CONCURRENCY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#initial_destination_concurrency">initial_destination_concurrency</a> (5)</b>
|
||||
The initial per-destination concurrency level for parallel
|
||||
delivery to the same destination.
|
||||
@ -300,7 +300,7 @@ QMGR(8) QMGR(8)
|
||||
Make the queue manager's feedback algorithm verbose for perfor-
|
||||
mance analysis purposes.
|
||||
|
||||
<b>RECIPIENT SCHEDULING CONTROLS</b>
|
||||
<b><a name="recipient_scheduling_controls">RECIPIENT SCHEDULING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#default_destination_recipient_limit">default_destination_recipient_limit</a> (50)</b>
|
||||
The default maximal number of recipients per message delivery.
|
||||
|
||||
@ -310,7 +310,7 @@ QMGR(8) QMGR(8)
|
||||
<a href="postconf.5.html#default_destination_recipient_limit">ient_limit</a> parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a>
|
||||
name of the message delivery transport.
|
||||
|
||||
<b>MESSAGE SCHEDULING CONTROLS</b>
|
||||
<b><a name="message_scheduling_controls">MESSAGE SCHEDULING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#default_delivery_slot_cost">default_delivery_slot_cost</a> (5)</b>
|
||||
How often the Postfix queue manager's scheduler is allowed to
|
||||
preempt delivery of one message with another.
|
||||
@ -347,7 +347,7 @@ QMGR(8) QMGR(8)
|
||||
parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a> name of the
|
||||
message delivery transport.
|
||||
|
||||
<b>OTHER RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="other_resource_and_rate_controls">OTHER RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#minimal_backoff_time">minimal_backoff_time</a> (300s)</b>
|
||||
The minimal time between attempts to deliver a deferred message;
|
||||
prior to Postfix 2.4 the default value was 1000s.
|
||||
@ -400,7 +400,7 @@ QMGR(8) QMGR(8)
|
||||
the parameter name is the <a href="master.5.html">master.cf</a> name of the message delivery
|
||||
transport.
|
||||
|
||||
<b>SAFETY CONTROLS</b>
|
||||
<b><a name="safety_controls">SAFETY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmgr_daemon_timeout">qmgr_daemon_timeout</a> (1000s)</b>
|
||||
How much time a Postfix queue manager process may take to handle
|
||||
a request before it is terminated by a built-in watchdog timer.
|
||||
@ -415,7 +415,7 @@ QMGR(8) QMGR(8)
|
||||
A safety limit that prevents address verification requests from
|
||||
overwhelming the Postfix queue.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -465,7 +465,7 @@ QMGR(8) QMGR(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/incoming, <a href="QSHAPE_README.html#incoming_queue">incoming queue</a>
|
||||
/var/spool/postfix/active, <a href="QSHAPE_README.html#active_queue">active queue</a>
|
||||
/var/spool/postfix/deferred, <a href="QSHAPE_README.html#deferred_queue">deferred queue</a>
|
||||
@ -473,7 +473,7 @@ QMGR(8) QMGR(8)
|
||||
/var/spool/postfix/defer, non-delivery status
|
||||
/var/spool/postfix/trace, delivery status
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="trivial-rewrite.8.html">trivial-rewrite(8)</a>, address routing
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -482,11 +482,11 @@ QMGR(8) QMGR(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="SCHEDULER_README.html">SCHEDULER_README</a>, scheduling algorithm
|
||||
<a href="QSHAPE_README.html">QSHAPE_README</a>, Postfix queue analysis
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
QMQP-SINK(1) QMQP-SINK(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
qmqp-sink - parallelized QMQP test server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>qmqp-sink</b> [<b>-46cv</b>] [<b>-x</b> <i>time</i>] [<b>inet:</b>][<i>host</i>]:<i>port backlog</i>
|
||||
|
||||
<b>qmqp-sink</b> [<b>-46cv</b>] [<b>-x</b> <i>time</i>] <b>unix:</b><i>pathname backlog</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
<b>qmqp-sink</b> listens on the named host (or address) and port. It receives
|
||||
messages from the network and throws them away. The purpose is to mea-
|
||||
sure QMQP client performance, not protocol compliance. Connections can
|
||||
@ -44,10 +44,10 @@ QMQP-SINK(1) QMQP-SINK(1)
|
||||
Terminate after <i>time</i> seconds. This is to facilitate memory leak
|
||||
testing.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmqp-source.1.html">qmqp-source(1)</a>, QMQP message generator
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
QMQP-SOURCE(1) QMQP-SOURCE(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
qmqp-source - parallelized QMQP test generator
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>qmqp-source</b> [<i>options</i>] [<b>inet:</b>]<i>host</i>[:<i>port</i>]
|
||||
|
||||
<b>qmqp-source</b> [<i>options</i>] <b>unix:</b><i>pathname</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
<b>qmqp-source</b> connects to the named host and TCP port (default 628) and
|
||||
sends one or more messages to it, either sequentially or in parallel.
|
||||
The program speaks the QMQP protocol. Connections can be made to
|
||||
@ -77,10 +77,10 @@ QMQP-SOURCE(1) QMQP-SOURCE(1)
|
||||
Wait a fixed time between messages. Suspending one thread does
|
||||
not affect other delivery threads.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmqp-sink.1.html">qmqp-sink(1)</a>, QMQP message dump
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
QMQPD(8) QMQPD(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
qmqpd - Postfix QMQP server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>qmqpd</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix QMQP server receives one message per connection. Each mes-
|
||||
sage is piped through the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon, and is placed into the
|
||||
<a href="QSHAPE_README.html#incoming_queue"><b>incoming</b> queue</a> as one single queue file. The program expects to be run
|
||||
@ -22,15 +22,15 @@ QMQPD(8) QMQPD(8)
|
||||
The QMQP server implements one access policy: only explicitly autho-
|
||||
rized client hosts are allowed to use the service.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The QMQP server is moderately security-sensitive. It talks to QMQP
|
||||
clients and to DNS servers on the network. The QMQP server can be run
|
||||
chrooted at fixed low privilege.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The QMQP protocol provides only one server reply per message delivery.
|
||||
It is therefore not possible to reject individual recipients.
|
||||
|
||||
@ -39,7 +39,7 @@ QMQPD(8) QMQPD(8)
|
||||
nent is longer than acceptable, Postfix replies immediately and closes
|
||||
the connection. It is left up to the client to handle the situation.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="qmqpd.8.html"><b>qmqpd</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -47,7 +47,7 @@ QMQPD(8) QMQPD(8)
|
||||
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>CONTENT INSPECTION CONTROLS</b>
|
||||
<b><a name="content_inspection_controls">CONTENT INSPECTION CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#content_filter">content_filter</a> (empty)</b>
|
||||
After the message is queued, send the entire message to the
|
||||
specified <i>transport:destination</i>.
|
||||
@ -56,7 +56,7 @@ QMQPD(8) QMQPD(8)
|
||||
Enable or disable recipient validation, built-in content filter-
|
||||
ing, or address mapping.
|
||||
|
||||
<b>SMTPUTF8 CONTROLS</b>
|
||||
<b><a name="smtputf8_controls">SMTPUTF8 CONTROLS</a></b>
|
||||
Preliminary SMTPUTF8 support is introduced with Postfix 3.0.
|
||||
|
||||
<b><a href="postconf.5.html#smtputf8_enable">smtputf8_enable</a> (yes)</b>
|
||||
@ -74,7 +74,7 @@ QMQPD(8) QMQPD(8)
|
||||
IDNA2008, when converting UTF-8 domain names to/from the ASCII
|
||||
form that is used for DNS lookups.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#line_length_limit">line_length_limit</a> (2048)</b>
|
||||
Upon input, long lines are chopped up into pieces of at most
|
||||
this length; upon delivery, long lines are reconstructed.
|
||||
@ -91,7 +91,7 @@ QMQPD(8) QMQPD(8)
|
||||
The time limit for sending or receiving information over the
|
||||
network.
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b>
|
||||
The increment in verbose logging level when a nexthop destina-
|
||||
tion, remote client or server name or network address matches a
|
||||
@ -107,12 +107,12 @@ QMQPD(8) QMQPD(8)
|
||||
Safety net to keep mail queued that would otherwise be returned
|
||||
to the sender.
|
||||
|
||||
<b>TARPIT CONTROLS</b>
|
||||
<b><a name="tarpit_controls">TARPIT CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#qmqpd_error_delay">qmqpd_error_delay</a> (1s)</b>
|
||||
How long the Postfix QMQP server will pause before sending a
|
||||
negative reply to the remote QMQP client.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -168,20 +168,20 @@ QMQPD(8) QMQPD(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="http://cr.yp.to/proto/qmqp.html">http://cr.yp.to/proto/qmqp.html</a>, QMQP protocol
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, message canonicalization
|
||||
<a href="master.8.html">master(8)</a>, process manager
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="QMQP_README.html">QMQP_README</a>, Postfix ezmlm-idx howto.
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
The qmqpd service was introduced with Postfix version 1.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
QSHAPE(1) QSHAPE(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
qshape - Print Postfix queue domain and age distribution
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>qshape</b> [<b>-s</b>] [<b>-p</b>] [<b>-m</b> <i>min</i><b>_</b><i>subdomains</i>]
|
||||
[<b>-b</b> <i>bucket</i><b>_</b><i>count</i>] [<b>-t</b> <i>bucket</i><b>_</b><i>time</i>]
|
||||
[<b>-l</b>] [<b>-w</b> <i>terminal</i><b>_</b><i>width</i>]
|
||||
[<b>-N</b> <i>batch</i><b>_</b><i>msg</i><b>_</b><i>count</i>] [<b>-n</b> <i>batch</i><b>_</b><i>top</i><b>_</b><i>domains</i>]
|
||||
[<b>-c</b> <i>config</i><b>_</b><i>directory</i>] [<i>queue</i><b>_</b><i>name</i> ...]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <b>qshape</b> program helps the administrator understand the Postfix queue
|
||||
message distribution in time and by sender domain or recipient domain.
|
||||
The program needs read access to the queue directories and queue files,
|
||||
@ -103,11 +103,11 @@ QSHAPE(1) QSHAPE(1)
|
||||
tory even if you want the default <a href="QSHAPE_README.html#incoming_queue">incoming</a> and <a href="QSHAPE_README.html#active_queue">active queue</a> dis-
|
||||
tribution.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="mailq.1.html">mailq(1)</a>, List all messages in the queue.
|
||||
<a href="QSHAPE_README.html">QSHAPE_README</a> Examples and background material.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
$<a href="postconf.5.html#config_directory">config_directory</a>/<a href="postconf.5.html">main.cf</a>, Postfix installation parameters.
|
||||
$<a href="postconf.5.html#queue_directory">queue_directory</a>/maildrop/, local submission directory.
|
||||
$<a href="postconf.5.html#queue_directory">queue_directory</a>/incoming/, new message queue.
|
||||
@ -115,7 +115,7 @@ QSHAPE(1) QSHAPE(1)
|
||||
$<a href="postconf.5.html#queue_directory">queue_directory</a>/active/, messages scheduled for delivery.
|
||||
$<a href="postconf.5.html#queue_directory">queue_directory</a>/deferred/, messages postponed for later delivery.
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
regexp_table - format of Postfix regular expression tables
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="regexp_table.5.html">regexp</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="regexp_table.5.html">regexp</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting,
|
||||
mail routing, or access control. These tables are usually in <b>dbm</b> or <b>db</b>
|
||||
format.
|
||||
@ -33,12 +33,12 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
terns, and "<b>postmap -bmq -</b> <<i>file</i>" for <a href="header_checks.5.html">body_checks(5)</a> (Postfix 2.6 and
|
||||
later).
|
||||
|
||||
<b>COMPATIBILITY</b>
|
||||
<b><a name="compatibility">COMPATIBILITY</a></b>
|
||||
With Postfix version 2.2 and earlier specify "<b>postmap -fq</b>" to query a
|
||||
table that contains case sensitive patterns. Patterns are case insensi-
|
||||
tive by default.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The general form of a Postfix regular expression table is:
|
||||
|
||||
<b>/</b><i>pattern</i><b>/</b><i>flags result</i>
|
||||
@ -106,7 +106,7 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
Toggles the extended expression syntax flag. By default, support
|
||||
for extended expression syntax is enabled.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
Patterns are applied in the order as specified in the table, until a
|
||||
pattern is found that matches the input string.
|
||||
|
||||
@ -117,7 +117,7 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
ken up into their <i>user</i> and <i>domain</i> constituent parts, nor is <i>user+foo</i>
|
||||
broken up into <i>user</i> and <i>foo</i>.
|
||||
|
||||
<b>TEXT SUBSTITUTION</b>
|
||||
<b><a name="text_substitution">TEXT SUBSTITUTION</a></b>
|
||||
Substitution of substrings (text that matches patterns inside "()")
|
||||
from the matched expression into the result string is requested with
|
||||
$1, $2, etc.; specify $$ to produce a $ character as output. The
|
||||
@ -128,7 +128,7 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
the expression does not match, substitutions are not available for
|
||||
negated patterns.
|
||||
|
||||
<b>INLINE SPECIFICATION</b>
|
||||
<b><a name="inline_specification">INLINE SPECIFICATION</a></b>
|
||||
The contents of a table may be specified in the table name (Postfix 3.7
|
||||
and later). The basic syntax is:
|
||||
|
||||
@ -155,7 +155,7 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
metacharacters such as '.' in the <i>$name</i> expansion. To prevent unex-
|
||||
pected matches, use a <a href="pcre_table.5.html">pcre</a>: table, and specify \Q<i>$name</i>\E.
|
||||
|
||||
<b>EXAMPLE SMTPD ACCESS MAP</b>
|
||||
<b><a name="example_smtpd_access_map">EXAMPLE SMTPD ACCESS MAP</a></b>
|
||||
# Disallow sender-specified routing. This is a must if you relay mail
|
||||
# for other domains.
|
||||
/[%!@].*[%!@]/ 550 Sender-specified routing rejected
|
||||
@ -169,23 +169,23 @@ REGEXP_TABLE(5) REGEXP_TABLE(5)
|
||||
/^(.*)-outgoing@(.*)$/ 550 Use ${1}@${2} instead
|
||||
endif
|
||||
|
||||
<b>EXAMPLE HEADER FILTER MAP</b>
|
||||
<b><a name="example_header_filter_map">EXAMPLE HEADER FILTER MAP</a></b>
|
||||
# These were once common in junk mail.
|
||||
/^Subject: make money fast/ REJECT
|
||||
/^To: friend@public\.com/ REJECT
|
||||
|
||||
<b>EXAMPLE BODY FILTER MAP</b>
|
||||
<b><a name="example_body_filter_map">EXAMPLE BODY FILTER MAP</a></b>
|
||||
# First skip over base 64 encoded text to save CPU cycles.
|
||||
~^[[:alnum:]+/]{60,}$~ OK
|
||||
|
||||
# Put your own body patterns here.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<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
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
RELOCATED(5) RELOCATED(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
relocated - Postfix relocated table format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/relocated</b>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The optional <a href="relocated.5.html"><b>relocated</b>(5)</a> table provides the information that is used
|
||||
in "user has moved to <i>new</i><b>_</b><i>location</i>" bounce messages.
|
||||
|
||||
@ -34,13 +34,13 @@ RELOCATED(5) RELOCATED(5)
|
||||
|
||||
Table lookups are case insensitive.
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<b>o</b> An entry has one of the following form:
|
||||
@ -56,7 +56,7 @@ RELOCATED(5) RELOCATED(5)
|
||||
<b>o</b> A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, patterns are tried in the order as
|
||||
listed below:
|
||||
@ -73,12 +73,12 @@ RELOCATED(5) RELOCATED(5)
|
||||
Matches other addresses in <i>domain</i>. This form has the lowest
|
||||
precedence.
|
||||
|
||||
<b>ADDRESS EXTENSION</b>
|
||||
<b><a name="address_extension">ADDRESS EXTENSION</a></b>
|
||||
When a mail address localpart contains the optional recipient delimiter
|
||||
(e.g., <i>user+foo</i>@<i>domain</i>), the lookup order becomes: <i>user+foo</i>@<i>domain</i>,
|
||||
<i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>.
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions or when lookups are directed
|
||||
to a TCP-based server. For a description of regular expression lookup
|
||||
@ -98,7 +98,7 @@ RELOCATED(5) RELOCATED(5)
|
||||
feature that parenthesized substrings from the pattern can be interpo-
|
||||
lated as <b>$1</b>, <b>$2</b> and so on.
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is
|
||||
@ -110,10 +110,10 @@ RELOCATED(5) RELOCATED(5)
|
||||
|
||||
Results are the same as with indexed file lookups.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The table format does not understand quoting conventions.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant. The text
|
||||
below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for more
|
||||
details including examples.
|
||||
@ -141,16 +141,16 @@ RELOCATED(5) RELOCATED(5)
|
||||
receives mail on by way of a proxy or network address transla-
|
||||
tion unit.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="trivial-rewrite.8.html">trivial-rewrite(8)</a>, address resolver
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
SCACHE(8) SCACHE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
scache - Postfix shared connection cache server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>scache</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="scache.8.html"><b>scache</b>(8)</a> server maintains a shared multi-connection cache. This
|
||||
information can be used by, for example, Postfix SMTP clients or other
|
||||
Postfix delivery agents.
|
||||
@ -65,7 +65,7 @@ SCACHE(8) SCACHE(8)
|
||||
ties, and a cached file descriptor for the specified logical
|
||||
destination.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="scache.8.html"><b>scache</b>(8)</a> server is not security-sensitive. It does not talk to the
|
||||
network, and it does not talk to local users. The <a href="scache.8.html"><b>scache</b>(8)</a> server can
|
||||
run chrooted at fixed low privilege.
|
||||
@ -73,16 +73,16 @@ SCACHE(8) SCACHE(8)
|
||||
The <a href="scache.8.html"><b>scache</b>(8)</a> server is not a trusted process. It must not be used to
|
||||
store information that is security sensitive.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The session cache cannot be shared among multiple machines.
|
||||
|
||||
When a connection expires from the cache, it is closed without the
|
||||
appropriate protocol specific handshake.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="scache.8.html"><b>scache</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -90,7 +90,7 @@ SCACHE(8) SCACHE(8)
|
||||
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>RESOURCE CONTROLS</b>
|
||||
<b><a name="resource_controls">RESOURCE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#connection_cache_ttl_limit">connection_cache_ttl_limit</a> (2s)</b>
|
||||
The maximal time-to-live value that the <a href="scache.8.html"><b>scache</b>(8)</a> connection
|
||||
cache server allows.
|
||||
@ -100,7 +100,7 @@ SCACHE(8) SCACHE(8)
|
||||
connection cache hit and miss rates for logical destinations and
|
||||
for physical endpoints.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -135,20 +135,20 @@ SCACHE(8) SCACHE(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtp.8.html">smtp(8)</a>, SMTP client
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="master.8.html">master(8)</a>, process manager
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="CONNECTION_CACHE_README.html">CONNECTION_CACHE_README</a>, Postfix connection cache
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.2.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,10 +7,10 @@
|
||||
</head> <body> <pre>
|
||||
SENDMAIL(1) SENDMAIL(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
sendmail - Postfix to Sendmail compatibility interface
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>sendmail</b> [<i>option ...</i>] [<i>recipient ...</i>]
|
||||
|
||||
<b>mailq</b>
|
||||
@ -19,7 +19,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>newaliases</b>
|
||||
<b>sendmail -I</b>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command implements the Postfix to Sendmail com-
|
||||
patibility interface. For the sake of compatibility with existing
|
||||
applications, some Sendmail command-line options are recognized but
|
||||
@ -283,7 +283,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Log mailer traffic. Use the <b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a></b> and <b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a></b>
|
||||
configuration parameters instead.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
By design, this program is not set-user (or group) id. It is prepared
|
||||
to handle message content from untrusted, possibly remote, users.
|
||||
|
||||
@ -318,11 +318,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command options, by specifying an email address that
|
||||
starts with "<b>-</b>".
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>, and to the standard
|
||||
error stream.
|
||||
|
||||
<b>ENVIRONMENT</b>
|
||||
<b><a name="environment">ENVIRONMENT</a></b>
|
||||
<b>MAIL_CONFIG</b>
|
||||
Directory with Postfix configuration files.
|
||||
|
||||
@ -336,19 +336,19 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<b>NAME</b> The sender full name. This is used only with messages that have
|
||||
no <b>From:</b> message header. See also the <b>-F</b> option above.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this pro-
|
||||
gram. The text below provides only a parameter summary. See <a href="postconf.5.html"><b>post-</b></a>
|
||||
<a href="postconf.5.html"><b>conf</b>(5)</a> for more details including examples.
|
||||
|
||||
<b>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
Available with Postfix 2.9 and later:
|
||||
|
||||
<b><a href="postconf.5.html#sendmail_fix_line_endings">sendmail_fix_line_endings</a> (always)</b>
|
||||
Controls how the Postfix sendmail command converts email message
|
||||
line endings from <CR><LF> into UNIX format (<LF>).
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
The <a href="DEBUG_README.html">DEBUG_README</a> file gives examples of how to troubleshoot a Postfix
|
||||
system.
|
||||
|
||||
@ -367,7 +367,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
verbose logging level to increase by the amount specified in
|
||||
$<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>.
|
||||
|
||||
<b>ACCESS CONTROLS</b>
|
||||
<b><a name="access_controls">ACCESS CONTROLS</a></b>
|
||||
Available in Postfix version 2.2 and later:
|
||||
|
||||
<b><a href="postconf.5.html#authorized_flush_users">authorized_flush_users</a> (<a href="DATABASE_README.html#types">static</a>:anyone)</b>
|
||||
@ -381,7 +381,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="sendmail.1.html"><b>mail</b>(1)</a> command (and with the privileged <a href="postdrop.1.html"><b>postdrop</b>(1)</a> helper com-
|
||||
mand).
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#bounce_size_limit">bounce_size_limit</a> (50000)</b>
|
||||
The maximal amount of original message text that is sent in a
|
||||
non-delivery notification.
|
||||
@ -400,7 +400,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue manager;
|
||||
prior to Postfix 2.4 the default value was 1000s.
|
||||
|
||||
<b>FAST FLUSH CONTROLS</b>
|
||||
<b><a name="fast_flush_controls">FAST FLUSH CONTROLS</a></b>
|
||||
The <a href="ETRN_README.html">ETRN_README</a> file describes configuration and operation details for
|
||||
the Postfix "fast flush" service.
|
||||
|
||||
@ -408,7 +408,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
Optional list of destinations that are eligible for per-destina-
|
||||
tion logfiles with mail that is queued to those destinations.
|
||||
|
||||
<b>VERP CONTROLS</b>
|
||||
<b><a name="verp_controls">VERP CONTROLS</a></b>
|
||||
The <a href="VERP_README.html">VERP_README</a> file describes configuration and operation details of
|
||||
Postfix support for variable envelope return path addresses.
|
||||
|
||||
@ -419,7 +419,7 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
The characters Postfix accepts as VERP delimiter characters on
|
||||
the Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command line and in SMTP commands.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#alias_database">alias_database</a> (see 'postconf -d' output)</b>
|
||||
The alias databases for <a href="local.8.html"><b>local</b>(8)</a> delivery that are updated with
|
||||
"<b>newaliases</b>" or with "<b>sendmail -bi</b>".
|
||||
@ -483,11 +483,11 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
the default Postfix instance, and that are started, stopped,
|
||||
etc., together with the default Postfix instance.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, mail queue
|
||||
/etc/postfix, configuration files
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="pickup.8.html">pickup(8)</a>, mail pickup daemon
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, SMTP server
|
||||
@ -500,14 +500,14 @@ SENDMAIL(1) SENDMAIL(1)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README_FILES</b>
|
||||
<b><a name="readme_files">README_FILES</a></b>
|
||||
Use "<b>postconf <a href="postconf.5.html#readme_directory">readme_directory</a></b>" or "<b>postconf <a href="postconf.5.html#html_directory">html_directory</a></b>" to locate
|
||||
this information.
|
||||
<a href="DEBUG_README.html">DEBUG_README</a>, Postfix debugging howto
|
||||
<a href="ETRN_README.html">ETRN_README</a>, Postfix ETRN howto
|
||||
<a href="VERP_README.html">VERP_README</a>, Postfix VERP howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
SHOWQ(8) SHOWQ(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
showq - list the Postfix mail queue
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>showq</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="showq.8.html"><b>showq</b>(8)</a> daemon reports the Postfix mail queue status. The output
|
||||
is meant to be formatted by the <a href="postqueue.1.html">postqueue(1)</a> command, as it emulates
|
||||
the Sendmail `mailq' command.
|
||||
@ -22,19 +22,19 @@ SHOWQ(8) SHOWQ(8)
|
||||
ruser. This mode of operation is used to emulate the `mailq' command
|
||||
while the Postfix mail system is down.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="showq.8.html"><b>showq</b>(8)</a> daemon can run in a chroot jail at fixed low privilege,
|
||||
and takes no input from the client. Its service port is accessible to
|
||||
local untrusted users, so the service can be susceptible to denial of
|
||||
service attacks.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
None. The <a href="showq.8.html"><b>showq</b>(8)</a> daemon does not interact with the outside world.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="showq.8.html"><b>showq</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -96,10 +96,10 @@ SHOWQ(8) SHOWQ(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix, queue directories
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="pickup.8.html">pickup(8)</a>, local mail pickup service
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue mail
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
@ -108,7 +108,7 @@ SHOWQ(8) SHOWQ(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
SMTP-SINK(1) SMTP-SINK(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
smtp-sink - parallelized SMTP/LMTP test server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>smtp-sink</b> [<i>options</i>] [<b>inet:</b>][<i>host</i>]:<i>port backlog</i>
|
||||
|
||||
<b>smtp-sink</b> [<i>options</i>] <b>unix:</b><i>pathname backlog</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
<b>smtp-sink</b> listens on the named host (or address) and port. It takes
|
||||
SMTP messages from the network and throws them away. The purpose is to
|
||||
measure client performance, not protocol compliance.
|
||||
@ -217,7 +217,7 @@ SMTP-SINK(1) SMTP-SINK(1)
|
||||
The maximum length of the queue of pending connections, as
|
||||
defined by the <b>listen</b>(2) system call.
|
||||
|
||||
<b>DUMP FILE FORMAT</b>
|
||||
<b><a name="dump_file_format">DUMP FILE FORMAT</a></b>
|
||||
Each dumped message contains a sequence of text lines, terminated with
|
||||
the newline character. The sequence of information is as follows:
|
||||
|
||||
@ -272,10 +272,10 @@ SMTP-SINK(1) SMTP-SINK(1)
|
||||
<i>time-stamp</i>
|
||||
A time stamp as defined in <a href="https://tools.ietf.org/html/rfc2822">RFC 2822</a>.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtp-source.1.html">smtp-source(1)</a>, SMTP/LMTP message generator
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
SMTP-SOURCE(1) SMTP-SOURCE(1)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
smtp-source - parallelized SMTP/LMTP test generator
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>smtp-source</b> [<i>options</i>] [<b>inet:</b>]<i>host</i>[:<i>port</i>]
|
||||
|
||||
<b>smtp-source</b> [<i>options</i>] <b>unix:</b><i>pathname</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
<b>smtp-source</b> connects to the named <i>host</i> and TCP <i>port</i> (default: port 25)
|
||||
and sends one or more messages to it, either sequentially or in paral-
|
||||
lel. The program speaks either SMTP (default) or LMTP. Connections can
|
||||
@ -129,13 +129,13 @@ SMTP-SOURCE(1) SMTP-SOURCE(1)
|
||||
<b>unix:</b><i>pathname</i>
|
||||
Connect to the UNIX-domain socket at <i>pathname</i>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
No SMTP command pipelining support.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtp-sink.1.html">smtp-sink(1)</a>, SMTP/LMTP message dump
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
SMTP,(LMTP) SMTP,(LMTP)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
smtp, lmtp - Postfix SMTP+LMTP client
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>smtp</b> [generic Postfix daemon options] [flags=DORX]
|
||||
|
||||
<b>lmtp</b> [generic Postfix daemon options] [flags=DORX]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix SMTP+LMTP client implements the SMTP and LMTP mail delivery
|
||||
protocols. It processes message delivery requests from the queue man-
|
||||
ager. Each request specifies a queue file, a sender address, a domain
|
||||
@ -40,7 +40,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
that have a high volume of mail in the <a href="QSHAPE_README.html#active_queue">active queue</a>. Connection caching
|
||||
can be enabled permanently for specific destinations.
|
||||
|
||||
<b>SMTP SERVER LOOKUP</b>
|
||||
<b><a name="smtp_server_lookup">SMTP SERVER LOOKUP</a></b>
|
||||
The Postfix SMTP client supports multiple destinations separated by
|
||||
comma or whitespace (Postfix 3.5 and later). Each destination is tried
|
||||
in the specified order.
|
||||
@ -68,7 +68,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
specified service (default: <b>smtp</b>). An IPv6 address must be for-
|
||||
matted as [<b>ipv6</b>:<i>address</i>].
|
||||
|
||||
<b>LMTP SERVER LOOKUP</b>
|
||||
<b><a name="lmtp_server_lookup">LMTP SERVER LOOKUP</a></b>
|
||||
The Postfix LMTP client supports multiple destinations separated by
|
||||
comma or whitespace (Postfix 3.5 and later). Each destination is tried
|
||||
in the specified order.
|
||||
@ -101,7 +101,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
(default: <b>lmtp</b>). An IPv6 address must be formatted as
|
||||
[<b>ipv6</b>:<i>address</i>].
|
||||
|
||||
<b>SINGLE-RECIPIENT DELIVERY</b>
|
||||
<b><a name="single-recipient_delivery">SINGLE-RECIPIENT DELIVERY</a></b>
|
||||
By default, the Postfix SMTP+LMTP client delivers mail to multiple
|
||||
recipients per delivery request. This is undesirable when prepending a
|
||||
<b>Delivered-to:</b> or <b>X-Original-To:</b> message header. To prevent Postfix from
|
||||
@ -112,7 +112,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
in the Postfix <a href="postconf.5.html"><b>main.cf</b></a> file, where <i>transport</i> is the name in the first
|
||||
column of the Postfix <a href="master.5.html"><b>master.cf</b></a> entry for this mail delivery service.
|
||||
|
||||
<b>COMMAND ATTRIBUTE SYNTAX</b>
|
||||
<b><a name="command_attribute_syntax">COMMAND ATTRIBUTE SYNTAX</a></b>
|
||||
<b>flags=DORX</b> (optional)
|
||||
Optional message processing flags.
|
||||
|
||||
@ -147,12 +147,12 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
|
||||
This feature is available as of Postfix 3.5.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The SMTP+LMTP client is moderately security-sensitive. It talks to SMTP
|
||||
or LMTP servers and to DNS servers on the network. The SMTP+LMTP client
|
||||
can be run chrooted at fixed low privilege.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc821">RFC 821</a> (SMTP protocol)
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
<a href="https://tools.ietf.org/html/rfc1651">RFC 1651</a> (SMTP service extensions)
|
||||
@ -175,7 +175,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="https://tools.ietf.org/html/rfc6533">RFC 6533</a> (Internationalized Delivery Status Notifications)
|
||||
<a href="https://tools.ietf.org/html/rfc7672">RFC 7672</a> (SMTP security via opportunistic DANE TLS)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
Corrupted message files are marked so that the queue manager can move
|
||||
them to the <b>corrupt</b> queue for further inspection.
|
||||
@ -183,14 +183,14 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces, protocol problems, and of other trouble.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
SMTP and LMTP connection reuse for TLS (without closing the SMTP or
|
||||
LMTP connection) is not supported before Postfix 3.4.
|
||||
|
||||
SMTP and LMTP connection reuse assumes that SASL credentials are valid
|
||||
for all destinations that map onto the same IP address and TCP port.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Postfix versions 2.3 and later implement the SMTP and LMTP client with
|
||||
the same program, and choose the protocol and configuration parameters
|
||||
based on the process name, <b>smtp</b> or <b>lmtp</b>.
|
||||
@ -206,7 +206,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
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>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#ignore_mx_lookup_error">ignore_mx_lookup_error</a> (no)</b>
|
||||
Ignore DNS MX lookups that produce no response.
|
||||
|
||||
@ -422,7 +422,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
to MX or IP address lookup as if SRV record lookup was not
|
||||
enabled.
|
||||
|
||||
<b>MIME PROCESSING CONTROLS</b>
|
||||
<b><a name="mime_processing_controls">MIME PROCESSING CONTROLS</a></b>
|
||||
Available in Postfix version 2.0 and later:
|
||||
|
||||
<b><a href="postconf.5.html#disable_mime_output_conversion">disable_mime_output_conversion</a> (no)</b>
|
||||
@ -434,14 +434,14 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<b><a href="postconf.5.html#mime_nesting_limit">mime_nesting_limit</a> (100)</b>
|
||||
The maximal recursion level that the MIME processor will handle.
|
||||
|
||||
<b>EXTERNAL CONTENT INSPECTION CONTROLS</b>
|
||||
<b><a name="external_content_inspection_controls">EXTERNAL CONTENT INSPECTION CONTROLS</a></b>
|
||||
Available in Postfix version 2.1 and later:
|
||||
|
||||
<b><a href="postconf.5.html#smtp_send_xforward_command">smtp_send_xforward_command</a> (no)</b>
|
||||
Send the non-standard XFORWARD command when the Postfix SMTP
|
||||
server EHLO response announces XFORWARD support.
|
||||
|
||||
<b>SASL AUTHENTICATION CONTROLS</b>
|
||||
<b><a name="sasl_authentication_controls">SASL AUTHENTICATION CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#smtp_sasl_auth_enable">smtp_sasl_auth_enable</a> (no)</b>
|
||||
Enable SASL authentication in the Postfix SMTP client.
|
||||
|
||||
@ -506,7 +506,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
The delimiter between username and password in sasl_passwd_maps
|
||||
lookup results.
|
||||
|
||||
<b>STARTTLS SUPPORT CONTROLS</b>
|
||||
<b><a name="starttls_support_controls">STARTTLS SUPPORT CONTROLS</a></b>
|
||||
Detailed information about STARTTLS configuration may be found in the
|
||||
<a href="TLS_README.html">TLS_README</a> document.
|
||||
|
||||
@ -758,7 +758,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
reuse a previously-negotiated TLS session (there is no new
|
||||
information to report).
|
||||
|
||||
<b>OBSOLETE STARTTLS CONTROLS</b>
|
||||
<b><a name="obsolete_starttls_controls">OBSOLETE STARTTLS CONTROLS</a></b>
|
||||
The following configuration parameters exist for compatibility with
|
||||
Postfix versions before 2.3. Support for these will be removed in a
|
||||
future release.
|
||||
@ -785,7 +785,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Obsolete Postfix < 2.3 control for the Postfix SMTP client TLS
|
||||
cipher list.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#smtp_connect_timeout">smtp_connect_timeout</a> (30s)</b>
|
||||
The Postfix SMTP client time limit for completing a TCP connec-
|
||||
tion, or zero (use the operating system built-in time limit).
|
||||
@ -921,7 +921,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="postconf.5.html#default_destination_recipient_limit">ient_limit</a> parameter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a>
|
||||
name of the message delivery transport.
|
||||
|
||||
<b>SMTPUTF8 CONTROLS</b>
|
||||
<b><a name="smtputf8_controls">SMTPUTF8 CONTROLS</a></b>
|
||||
Preliminary SMTPUTF8 support is introduced with Postfix 3.0.
|
||||
|
||||
<b><a href="postconf.5.html#smtputf8_enable">smtputf8_enable</a> (yes)</b>
|
||||
@ -939,7 +939,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
IDNA2008, when converting UTF-8 domain names to/from the ASCII
|
||||
form that is used for DNS lookups.
|
||||
|
||||
<b>TROUBLE SHOOTING CONTROLS</b>
|
||||
<b><a name="trouble_shooting_controls">TROUBLE SHOOTING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b>
|
||||
The increment in verbose logging level when a nexthop destina-
|
||||
tion, remote client or server name or network address matches a
|
||||
@ -964,7 +964,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<b><a href="postconf.5.html#notify_classes">notify_classes</a> (resource, software)</b>
|
||||
The list of error classes that are reported to the postmaster.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#best_mx_transport">best_mx_transport</a> (empty)</b>
|
||||
Where the Postfix SMTP client should deliver mail when it
|
||||
detects a "mail loops back to myself" error condition.
|
||||
@ -1097,7 +1097,7 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
Defer delivery when the Postfix SMTP client cannot apply the
|
||||
<a href="postconf.5.html#smtp_bind_address">smtp_bind_address</a> or <a href="postconf.5.html#smtp_bind_address6">smtp_bind_address6</a> setting.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="generic.5.html">generic(5)</a>, output address rewriting
|
||||
<a href="header_checks.5.html">header_checks(5)</a>, message header content inspection
|
||||
<a href="header_checks.5.html">body_checks(5)</a>, body parts content inspection
|
||||
@ -1111,11 +1111,11 @@ SMTP,(LMTP) SMTP,(LMTP)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="SASL_README.html">SASL_README</a>, Postfix SASL howto
|
||||
<a href="TLS_README.html">TLS_README</a>, Postfix STARTTLS howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
socketmap_table - Postfix socketmap table lookup client
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="socketmap_table.html">socketmap</a>:inet:</b><i>host</i><b>:</b><i>port</i><b>:</b><i>name</i>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="socketmap_table.html">socketmap</a>:unix:</b><i>pathname</i><b>:</b><i>name</i>
|
||||
|
||||
<b>postmap -q - <a href="socketmap_table.html">socketmap</a>:inet:</b><i>host</i><b>:</b><i>port</i><b>:</b><i>name</i> <<i>inputfile</i>
|
||||
<b>postmap -q - <a href="socketmap_table.html">socketmap</a>:unix:</b><i>pathname</i><b>:</b><i>name</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting,
|
||||
mail routing or policy lookup.
|
||||
|
||||
@ -26,12 +26,12 @@ SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)
|
||||
<i>name</i><b>:</b><i>name</i>. In both cases, <i>name</i> specifies the name field in a socketmap
|
||||
client request (see "REQUEST FORMAT" below).
|
||||
|
||||
<b>PROTOCOL</b>
|
||||
<b><a name="protocol">PROTOCOL</a></b>
|
||||
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.
|
||||
|
||||
<b>REQUEST FORMAT</b>
|
||||
<b><a name="request_format">REQUEST FORMAT</a></b>
|
||||
The socketmap protocol supports only the lookup request. The request
|
||||
has the following form:
|
||||
|
||||
@ -44,7 +44,7 @@ SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)
|
||||
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.
|
||||
|
||||
<b>REPLY FORMAT</b>
|
||||
<b><a name="reply_format">REPLY FORMAT</a></b>
|
||||
The Postfix socketmap client requires that replies are not longer than
|
||||
100000 characters (not including the netstring encapsulation). Replies
|
||||
must have the following form:
|
||||
@ -63,11 +63,11 @@ SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)
|
||||
The request failed. The reason, if non-empty, is descriptive
|
||||
text.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
This map cannot be used for security-sensitive information,
|
||||
because neither the connection nor the server are authenticated.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="http://cr.yp.to/proto/netstrings.txt">http://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
|
||||
@ -75,16 +75,16 @@ SOCKETMAP_TABLE(5) SOCKETMAP_TABLE(5)
|
||||
<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
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The protocol limits are not yet configurable.
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
Socketmap support was introduced with Postfix version 2.10.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
SPAWN(8) SPAWN(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
spawn - Postfix external command spawner
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>spawn</b> [generic Postfix daemon options] command_attributes...
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="spawn.8.html"><b>spawn</b>(8)</a> daemon provides the Postfix equivalent of <b>inetd</b>. It lis-
|
||||
tens on a port as specified in the Postfix <a href="master.5.html"><b>master.cf</b></a> file and spawns an
|
||||
external command whenever a connection is established. The connection
|
||||
@ -24,7 +24,7 @@ SPAWN(8) SPAWN(8)
|
||||
|
||||
This daemon expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager.
|
||||
|
||||
<b>COMMAND ATTRIBUTE SYNTAX</b>
|
||||
<b><a name="command_attribute_syntax">COMMAND ATTRIBUTE SYNTAX</a></b>
|
||||
The external command attributes are given in the <a href="master.5.html"><b>master.cf</b></a> file at the
|
||||
end of a service definition. The syntax is as follows:
|
||||
|
||||
@ -43,7 +43,7 @@ SPAWN(8) SPAWN(8)
|
||||
out interpretation of shell meta characters by a shell command
|
||||
interpreter.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
In order to enforce standard Postfix process resource controls, each
|
||||
<a href="spawn.8.html"><b>spawn</b>(8)</a> daemon process runs only one external command, and blocks
|
||||
until the command terminates or a time limit is reached. As such, it
|
||||
@ -51,17 +51,17 @@ SPAWN(8) SPAWN(8)
|
||||
The <a href="spawn.8.html"><b>spawn</b>(8)</a> daemon is expected to be replaced by a more structural
|
||||
solution.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
The <a href="spawn.8.html"><b>spawn</b>(8)</a> daemon reports abnormal child exits. Problems are logged
|
||||
to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
This program needs root privilege in order to execute external commands
|
||||
as the specified user. It is therefore security sensitive. However the
|
||||
<a href="spawn.8.html"><b>spawn</b>(8)</a> daemon does not talk to the external command and thus is not
|
||||
vulnerable to data-driven attacks.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically as <a href="spawn.8.html"><b>spawn</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -72,13 +72,13 @@ SPAWN(8) SPAWN(8)
|
||||
In the text below, <i>transport</i> is the first field of the entry in the
|
||||
<a href="master.5.html"><b>master.cf</b></a> file.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROL</b>
|
||||
<b><a name="resource_and_rate_control">RESOURCE AND RATE CONTROL</a></b>
|
||||
<b><a href="postconf.5.html#transport_time_limit">transport_time_limit</a> ($<a href="postconf.5.html#command_time_limit">command_time_limit</a>)</b>
|
||||
A transport-specific override for the <a href="postconf.5.html#command_time_limit">command_time_limit</a> parame-
|
||||
ter value, where <i>transport</i> is the <a href="master.5.html">master.cf</a> name of the message
|
||||
delivery transport.
|
||||
|
||||
<b>MISCELLANEOUS</b>
|
||||
<b><a name="miscellaneous">MISCELLANEOUS</a></b>
|
||||
<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.
|
||||
@ -128,13 +128,13 @@ SPAWN(8) SPAWN(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="master.8.html">master(8)</a>, process manager
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
SQLITE_TABLE(5) SQLITE_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
sqlite_table - Postfix SQLite configuration
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="sqlite_table.5.html">sqlite</a>:/etc/postfix/</b><i>filename</i>
|
||||
|
||||
<b>postmap -q - <a href="sqlite_table.5.html">sqlite</a>:/etc/postfix/</b><i>filename</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format.
|
||||
|
||||
@ -27,7 +27,7 @@ SQLITE_TABLE(5) SQLITE_TABLE(5)
|
||||
The file /etc/postfix/sqlite-aliases.cf has the same format as the
|
||||
Postfix <a href="postconf.5.html">main.cf</a> file, and can specify the parameters described below.
|
||||
|
||||
<b>LIST MEMBERSHIP</b>
|
||||
<b><a name="list_membership">LIST MEMBERSHIP</a></b>
|
||||
When using SQL to store lists such as $<a href="postconf.5.html#mynetworks">mynetworks</a>, $<a href="postconf.5.html#mydestination">mydestination</a>,
|
||||
$<a href="postconf.5.html#relay_domains">relay_domains</a>, $<a href="postconf.5.html#local_recipient_maps">local_recipient_maps</a>, etc., it is important to under-
|
||||
stand that the table must store each list member as a separate key. The
|
||||
@ -41,7 +41,7 @@ SQLITE_TABLE(5) SQLITE_TABLE(5)
|
||||
value. With SQL databases it is not uncommon to return the key itself
|
||||
or a constant value.
|
||||
|
||||
<b>SQLITE PARAMETERS</b>
|
||||
<b><a name="sqlite_parameters">SQLITE PARAMETERS</a></b>
|
||||
<b>dbpath</b> The SQLite database file location. Example:
|
||||
dbpath = customer_database
|
||||
|
||||
@ -180,7 +180,7 @@ SQLITE_TABLE(5) SQLITE_TABLE(5)
|
||||
example, if the map is specified as "<a href="sqlite_table.5.html">sqlite</a>:<i>sqlitename</i>", the parameter
|
||||
"query" would be defined in <a href="postconf.5.html">main.cf</a> as "<i>sqlitename</i>_query".
|
||||
|
||||
<b>OBSOLETE QUERY INTERFACE</b>
|
||||
<b><a name="obsolete_query_interface">OBSOLETE QUERY INTERFACE</a></b>
|
||||
This section describes an interface that is deprecated as of Postfix
|
||||
2.2. It is replaced by the more general <b>query</b> interface described
|
||||
above. If the <b>query</b> parameter is defined, the legacy parameters
|
||||
@ -214,21 +214,21 @@ SQLITE_TABLE(5) SQLITE_TABLE(5)
|
||||
Additional conditions to the SQL query. Example:
|
||||
<b>additional_conditions</b> = AND status = 'paid'
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table maintenance
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="ldap_table.5.html">ldap_table(5)</a>, LDAP lookup tables
|
||||
<a href="mysql_table.5.html">mysql_table(5)</a>, MySQL lookup tables
|
||||
<a href="pgsql_table.5.html">pgsql_table(5)</a>, PostgreSQL lookup tables
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="SQLITE_README.html">SQLITE_README</a>, Postfix SQLITE howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
SQLite support was introduced with Postfix version 2.8.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,15 +7,15 @@
|
||||
</head> <body> <pre>
|
||||
TCP_TABLE(5) TCP_TABLE(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
tcp_table - Postfix client/server table lookup protocol
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap -q "</b><i>string</i><b>" <a href="tcp_table.5.html">tcp</a>:</b><i>host:port</i>
|
||||
|
||||
<b>postmap -q - <a href="tcp_table.5.html">tcp</a>:</b><i>host:port</i> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The Postfix mail system uses optional tables for address rewriting or
|
||||
mail routing. These tables are usually in <b>dbm</b> or <b>db</b> format. Alterna-
|
||||
tively, table lookups can be directed to a TCP server.
|
||||
@ -26,7 +26,7 @@ TCP_TABLE(5) TCP_TABLE(5)
|
||||
To test lookup tables, use the "<b>postmap -q</b>" command as described in the
|
||||
SYNOPSIS above.
|
||||
|
||||
<b>PROTOCOL DESCRIPTION</b>
|
||||
<b><a name="protocol_description">PROTOCOL DESCRIPTION</a></b>
|
||||
The TCP map class implements a very simple protocol: the client sends a
|
||||
request, and the server sends one reply. Requests and replies are sent
|
||||
as one line of ASCII text, terminated by the ASCII newline character.
|
||||
@ -34,7 +34,7 @@ TCP_TABLE(5) TCP_TABLE(5)
|
||||
|
||||
Send and receive operations must complete in 100 seconds.
|
||||
|
||||
<b>REQUEST FORMAT</b>
|
||||
<b><a name="request_format">REQUEST FORMAT</a></b>
|
||||
The tcp_table protocol supports only the lookup request. The request
|
||||
has the following form:
|
||||
|
||||
@ -47,7 +47,7 @@ TCP_TABLE(5) TCP_TABLE(5)
|
||||
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.
|
||||
|
||||
<b>REPLY FORMAT</b>
|
||||
<b><a name="reply_format">REPLY FORMAT</a></b>
|
||||
Each reply specifies a status code and text. Replies must be no longer
|
||||
than 4096 characters including the newline terminator.
|
||||
|
||||
@ -63,7 +63,7 @@ TCP_TABLE(5) TCP_TABLE(5)
|
||||
The request was successful. In the case of a lookup request, the
|
||||
text contains an encoded version of the requested data.
|
||||
|
||||
<b>ENCODING</b>
|
||||
<b><a name="encoding">ENCODING</a></b>
|
||||
In request and reply parameters, the character %, each non-printing
|
||||
character, and each whitespace character must be replaced by %XX, where
|
||||
XX is the corresponding ASCII hexadecimal character value. The hexadec-
|
||||
@ -73,27 +73,27 @@ TCP_TABLE(5) TCP_TABLE(5)
|
||||
encoding as long as the reply is guaranteed to not contain the % or
|
||||
NEWLINE character.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
Do not use TCP lookup tables for security critical purposes. The
|
||||
client-server connection is not protected and the server is not authen-
|
||||
ticated.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Only the lookup method is currently implemented.
|
||||
|
||||
The client does not hang up when the connection is idle for a long
|
||||
time.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<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
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
TLSMGR(8) TLSMGR(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
tlsmgr - Postfix TLS session cache and PRNG manager
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>tlsmgr</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="tlsmgr.8.html"><b>tlsmgr</b>(8)</a> manages the Postfix TLS session caches. It stores and
|
||||
retrieves cache entries on request by <a href="smtpd.8.html"><b>smtpd</b>(8)</a> and <a href="smtp.8.html"><b>smtp</b>(8)</a> processes,
|
||||
and periodically removes entries that have expired.
|
||||
@ -33,7 +33,7 @@ TLSMGR(8) TLSMGR(8)
|
||||
when the process terminates, and reads the exchange file when initial-
|
||||
izing its PRNG.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="tlsmgr.8.html"><b>tlsmgr</b>(8)</a> is not security-sensitive. The code that maintains the
|
||||
external and internal PRNG pools does not "trust" the data that it
|
||||
manipulates, and the code that maintains the TLS session cache does not
|
||||
@ -50,14 +50,14 @@ TLSMGR(8) TLSMGR(8)
|
||||
to open a cache file under a non-Postfix directory is redirected to the
|
||||
Postfix-owned <b><a href="postconf.5.html#data_directory">data_directory</a></b>, and a warning is logged.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
There is no automatic means to limit the number of entries in the TLS
|
||||
session caches and/or the size of the TLS cache files.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically, because <a href="tlsmgr.8.html"><b>tlsmgr</b>(8)</a>
|
||||
is a persistent processes. Use the command "<b>postfix reload</b>" after a
|
||||
configuration change.
|
||||
@ -65,7 +65,7 @@ TLSMGR(8) TLSMGR(8)
|
||||
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>TLS SESSION CACHE</b>
|
||||
<b><a name="tls_session_cache">TLS SESSION CACHE</a></b>
|
||||
<b><a href="postconf.5.html#lmtp_tls_loglevel">lmtp_tls_loglevel</a> (0)</b>
|
||||
The LMTP-specific version of the <a href="postconf.5.html#smtp_tls_loglevel">smtp_tls_loglevel</a> configuration
|
||||
parameter.
|
||||
@ -100,7 +100,7 @@ TLSMGR(8) TLSMGR(8)
|
||||
The expiration time of Postfix SMTP server TLS session cache
|
||||
information.
|
||||
|
||||
<b>PSEUDO RANDOM NUMBER GENERATOR</b>
|
||||
<b><a name="pseudo_random_number_generator">PSEUDO RANDOM NUMBER GENERATOR</a></b>
|
||||
<b><a href="postconf.5.html#tls_random_source">tls_random_source</a> (see 'postconf -d' output)</b>
|
||||
The external entropy source for the in-memory <a href="tlsmgr.8.html"><b>tlsmgr</b>(8)</a> pseudo
|
||||
random number generator (PRNG) pool.
|
||||
@ -124,7 +124,7 @@ TLSMGR(8) TLSMGR(8)
|
||||
in-memory pseudo random number generator (PRNG) pool from exter-
|
||||
nal sources.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -155,7 +155,7 @@ TLSMGR(8) TLSMGR(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtp.8.html">smtp(8)</a>, Postfix SMTP client
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -164,13 +164,13 @@ TLSMGR(8) TLSMGR(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="TLS_README.html">TLS_README</a>, Postfix TLS configuration and operation
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.2.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
BOUNCE(8) BOUNCE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
bounce - Postfix delivery status reports
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>bounce</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="bounce.8.html"><b>bounce</b>(8)</a> daemon maintains per-message log files with delivery sta-
|
||||
tus information. Each log file is named after the queue file that it
|
||||
corresponds to, and is kept in a queue subdirectory named after the
|
||||
@ -39,7 +39,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
This is used by clients that cannot retry transactions by themselves,
|
||||
and that depend on retry logic in their own client.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
<a href="https://tools.ietf.org/html/rfc2045">RFC 2045</a> (Format of Internet Message Bodies)
|
||||
<a href="https://tools.ietf.org/html/rfc2822">RFC 2822</a> (Internet Message Format)
|
||||
@ -51,10 +51,10 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="https://tools.ietf.org/html/rfc6532">RFC 6532</a> (Internationalized Message Format)
|
||||
<a href="https://tools.ietf.org/html/rfc6533">RFC 6533</a> (Internationalized Delivery Status Notifications)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="bounce.8.html"><b>bounce</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -166,12 +166,12 @@ BOUNCE(8) BOUNCE(8)
|
||||
<b><a href="postconf.5.html#header_from_format">header_from_format</a> (standard)</b>
|
||||
The format of the Postfix-generated <b>From:</b> header.
|
||||
|
||||
<b>FILES</b>
|
||||
<b><a name="files">FILES</a></b>
|
||||
/var/spool/postfix/bounce/* non-delivery records
|
||||
/var/spool/postfix/defer/* non-delivery records
|
||||
/var/spool/postfix/trace/* delivery status records
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="bounce.5.html">bounce(5)</a>, bounce message template format
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
@ -180,7 +180,7 @@ BOUNCE(8) BOUNCE(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
TRANSPORT(5) TRANSPORT(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
transport - Postfix transport table format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/transport</b>
|
||||
|
||||
<b>postmap -q "</b><i>string</i><b>" /etc/postfix/transport</b>
|
||||
|
||||
<b>postmap -q - /etc/postfix/transport</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The optional <a href="transport.5.html"><b>transport</b>(5)</a> table specifies a mapping from email
|
||||
addresses to message delivery transports and next-hop destinations.
|
||||
Message delivery transports such as <b>local</b> or <b>smtp</b> are defined in the
|
||||
@ -66,13 +66,13 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
a slightly different way as described below under "REGULAR EXPRESSION
|
||||
TABLES" or "TCP-BASED TABLES".
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<i>pattern result</i>
|
||||
@ -93,7 +93,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
The <i>result</i> is of the form <i>transport:nexthop</i> and specifies how or where
|
||||
to deliver mail. This is described in section "RESULT FORMAT".
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, patterns are tried in the order as
|
||||
listed below:
|
||||
@ -126,7 +126,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
Note 2: <i>user@domain</i> or <i>user+extension@domain</i> lookup is available in
|
||||
Postfix 2.0 and later.
|
||||
|
||||
<b>RESULT FORMAT</b>
|
||||
<b><a name="result_format">RESULT FORMAT</a></b>
|
||||
The lookup result is of the form <i>transport</i><b>:</b><i>nexthop</i>. The <i>transport</i>
|
||||
field specifies a mail delivery transport such as <b>smtp</b> or <b>local</b>. The
|
||||
<i>nexthop</i> field specifies where and how to deliver mail.
|
||||
@ -155,7 +155,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
A null <i>transport</i> field with non-null <i>nexthop</i> field does not modify the
|
||||
transport information.
|
||||
|
||||
<b>EXAMPLES</b>
|
||||
<b><a name="examples">EXAMPLES</a></b>
|
||||
In order to deliver internal mail directly, while using a mail relay
|
||||
for all other mail, specify a null entry for internal destinations (do
|
||||
not change the delivery transport or the nexthop information) and spec-
|
||||
@ -213,7 +213,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
|
||||
This causes all mail for <i>user</i>@<i>anything</i><b>.example.com</b> to be bounced.
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions. For a description of regular
|
||||
expression lookup table syntax, see <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
|
||||
@ -230,7 +230,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
of $1 etc. in regular expression lookup tables, because that could open
|
||||
a security hole (Postfix version 2.3 and later).
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is not
|
||||
@ -242,7 +242,7 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
|
||||
Results are the same as with indexed file lookups.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant. The text
|
||||
below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for more
|
||||
details including examples.
|
||||
@ -259,18 +259,18 @@ TRANSPORT(5) TRANSPORT(5)
|
||||
Optional lookup tables with mappings from recipient address to
|
||||
(message delivery transport, next-hop destination).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="trivial-rewrite.8.html">trivial-rewrite(8)</a>, rewrite and resolve addresses
|
||||
<a href="master.5.html">master(5)</a>, <a href="master.5.html">master.cf</a> file format
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="FILTER_README.html">FILTER_README</a>, external content filter
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
trivial-rewrite - Postfix address rewriting and resolving daemon
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>trivial-rewrite</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon processes three types of client service
|
||||
requests:
|
||||
|
||||
@ -56,7 +56,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
<b>verify</b> <i>sender address</i>
|
||||
Resolve the address for address verification purposes.
|
||||
|
||||
<b>SERVER PROCESS MANAGEMENT</b>
|
||||
<b><a name="server_process_management">SERVER PROCESS MANAGEMENT</a></b>
|
||||
The <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> servers run under control by the Postfix <a href="master.8.html">mas-</a>
|
||||
<a href="master.8.html">ter(8)</a> server. Each server can handle multiple simultaneous connec-
|
||||
tions. When all servers are busy while a client connects, the master
|
||||
@ -65,18 +65,18 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
after serving at least <b>$<a href="postconf.5.html#max_use">max_use</a></b> clients of after <b>$<a href="postconf.5.html#max_idle">max_idle</a></b> seconds of
|
||||
idle time.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
None. The command does not interact with the outside world.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon is not security sensitive. By default,
|
||||
this daemon does not talk to remote or local users. It can run at a
|
||||
fixed low privilege in a chrooted environment.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
On busy mail systems a long time may pass before a <a href="postconf.5.html"><b>main.cf</b></a> change
|
||||
affecting <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> is picked up. Use the command "<b>postfix</b>
|
||||
<b>reload</b>" to speed up a change.
|
||||
@ -84,7 +84,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
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>COMPATIBILITY CONTROLS</b>
|
||||
<b><a name="compatibility_controls">COMPATIBILITY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#resolve_dequoted_address">resolve_dequoted_address</a> (yes)</b>
|
||||
Resolve a recipient address safely instead of correctly, by
|
||||
looking inside quotes.
|
||||
@ -108,7 +108,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
Allow a sender or recipient address to have `-' as the first
|
||||
character.
|
||||
|
||||
<b>ADDRESS REWRITING CONTROLS</b>
|
||||
<b><a name="address_rewriting_controls">ADDRESS REWRITING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#myorigin">myorigin</a> ($<a href="postconf.5.html#myhostname">myhostname</a>)</b>
|
||||
The domain name that locally-posted mail appears to come from,
|
||||
and that locally posted mail is delivered to.
|
||||
@ -140,7 +140,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
<a href="postconf.5.html#remote_header_rewrite_domain">remote_header_rewrite_domain</a> parameter, and adding missing head-
|
||||
ers.
|
||||
|
||||
<b>ROUTING CONTROLS</b>
|
||||
<b><a name="routing_controls">ROUTING CONTROLS</a></b>
|
||||
The following is applicable to Postfix version 2.0 and later. Earlier
|
||||
versions do not have support for: <a href="postconf.5.html#virtual_transport">virtual_transport</a>, <a href="postconf.5.html#relay_transport">relay_transport</a>,
|
||||
<a href="postconf.5.html#virtual_alias_domains">virtual_alias_domains</a>, <a href="postconf.5.html#virtual_mailbox_domains">virtual_mailbox_domains</a> or <a href="postconf.5.html#proxy_interfaces">proxy_interfaces</a>.
|
||||
@ -201,7 +201,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
A sender-dependent override for the global <a href="postconf.5.html#default_transport">default_transport</a>
|
||||
parameter setting.
|
||||
|
||||
<b>ADDRESS VERIFICATION CONTROLS</b>
|
||||
<b><a name="address_verification_controls">ADDRESS VERIFICATION CONTROLS</a></b>
|
||||
Postfix version 2.1 introduces sender and recipient address verifica-
|
||||
tion. This feature is implemented by sending probe email messages that
|
||||
are not actually delivered. By default, address verification probes
|
||||
@ -247,7 +247,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
Overrides the <a href="postconf.5.html#sender_dependent_default_transport_maps">sender_dependent_default_transport_maps</a> parameter
|
||||
setting for address verification probes.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -306,7 +306,7 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="transport.5.html">transport(5)</a>, transport table format
|
||||
<a href="relocated.5.html">relocated(5)</a>, format of the "user has moved" table
|
||||
@ -314,11 +314,11 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8)
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ADDRESS_CLASS_README.html">ADDRESS_CLASS_README</a>, Postfix address classes howto
|
||||
<a href="ADDRESS_VERIFICATION_README.html">ADDRESS_VERIFICATION_README</a>, Postfix address verification
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
VERIFY(8) VERIFY(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
verify - Postfix address verification server
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>verify</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="verify.8.html"><b>verify</b>(8)</a> address verification server maintains a record of what
|
||||
recipient addresses are known to be deliverable or undeliverable.
|
||||
|
||||
@ -41,7 +41,7 @@ VERIFY(8) VERIFY(8)
|
||||
status is unknown, a probe is sent and an "in progress" status
|
||||
is returned.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The address verification server is not security-sensitive. It does not
|
||||
talk to the network, and it does not talk to local users. The verify
|
||||
server can run chrooted at fixed low privilege.
|
||||
@ -58,10 +58,10 @@ VERIFY(8) VERIFY(8)
|
||||
directory is redirected to the Postfix-owned <b><a href="postconf.5.html#data_directory">data_directory</a></b>, and a
|
||||
warning is logged.
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Problems and transactions are logged to <b>syslogd</b>(8) or <a href="postlogd.8.html"><b>postlogd</b>(8)</a>.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
Address verification probe messages add additional traffic to the mail
|
||||
queue. Recipient verification may cause an increased load on
|
||||
down-stream servers in the case of a dictionary attack or a flood of
|
||||
@ -72,7 +72,7 @@ VERIFY(8) VERIFY(8)
|
||||
an end and human intervention is needed. This violates a basic Postfix
|
||||
principle.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically, as <a href="verify.8.html"><b>verify</b>(8)</a> pro-
|
||||
cesses are long-lived. Use the command "<b>postfix reload</b>" after a config-
|
||||
uration change.
|
||||
@ -80,7 +80,7 @@ VERIFY(8) VERIFY(8)
|
||||
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>PROBE MESSAGE CONTROLS</b>
|
||||
<b><a name="probe_message_controls">PROBE MESSAGE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#address_verify_sender">address_verify_sender</a> ($<a href="postconf.5.html#double_bounce_sender">double_bounce_sender</a>)</b>
|
||||
The sender address to use in address verification probes; prior
|
||||
to Postfix 2.5 the default was "postmaster".
|
||||
@ -91,7 +91,7 @@ VERIFY(8) VERIFY(8)
|
||||
The time between changes in the time-dependent portion of
|
||||
address verification probe sender addresses.
|
||||
|
||||
<b>CACHE CONTROLS</b>
|
||||
<b><a name="cache_controls">CACHE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#address_verify_map">address_verify_map</a> (see 'postconf -d' output)</b>
|
||||
Lookup table for persistent address verification status storage.
|
||||
|
||||
@ -120,7 +120,7 @@ VERIFY(8) VERIFY(8)
|
||||
The amount of time between <a href="verify.8.html"><b>verify</b>(8)</a> address verification data-
|
||||
base cleanup runs.
|
||||
|
||||
<b>PROBE MESSAGE ROUTING CONTROLS</b>
|
||||
<b><a name="probe_message_routing_controls">PROBE MESSAGE ROUTING CONTROLS</a></b>
|
||||
By default, probe messages are delivered via the same route as regular
|
||||
messages. The following parameters can be used to override specific
|
||||
message routing mechanisms.
|
||||
@ -163,7 +163,7 @@ VERIFY(8) VERIFY(8)
|
||||
Overrides the <a href="postconf.5.html#sender_dependent_default_transport_maps">sender_dependent_default_transport_maps</a> parameter
|
||||
setting for address verification probes.
|
||||
|
||||
<b>SMTPUTF8 CONTROLS</b>
|
||||
<b><a name="smtputf8_controls">SMTPUTF8 CONTROLS</a></b>
|
||||
Preliminary SMTPUTF8 support is introduced with Postfix 3.0.
|
||||
|
||||
<b><a href="postconf.5.html#smtputf8_autodetect_classes">smtputf8_autodetect_classes</a> (sendmail, verify)</b>
|
||||
@ -177,7 +177,7 @@ VERIFY(8) VERIFY(8)
|
||||
IDNA2008, when converting UTF-8 domain names to/from the ASCII
|
||||
form that is used for DNS lookups.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -211,20 +211,20 @@ VERIFY(8) VERIFY(8)
|
||||
<b><a href="postconf.5.html#service_name">service_name</a> (read-only)</b>
|
||||
The <a href="master.5.html">master.cf</a> service name of a Postfix daemon process.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="smtpd.8.html">smtpd(8)</a>, Postfix SMTP server
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, enqueue Postfix message
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ADDRESS_VERIFICATION_README.html">ADDRESS_VERIFICATION_README</a>, address verification howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This service was introduced with Postfix version 2.1.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,17 +7,17 @@
|
||||
</head> <body> <pre>
|
||||
VIRTUAL(5) VIRTUAL(5)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
virtual - Postfix virtual alias table format
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>postmap /etc/postfix/virtual</b>
|
||||
|
||||
<b>postmap -q "</b><i>string</i><b>" /etc/postfix/virtual</b>
|
||||
|
||||
<b>postmap -q - /etc/postfix/virtual</b> <<i>inputfile</i>
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The optional <a href="virtual.5.html"><b>virtual</b>(5)</a> alias table (<a href="postconf.5.html#virtual_alias_maps">virtual_alias_maps</a>) applies to all
|
||||
recipients: <a href="local.8.html">local(8)</a>, virtual, and remote. This feature is implemented
|
||||
in the Postfix <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon before mail is queued. These tables
|
||||
@ -61,13 +61,13 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
a slightly different way as described below under "REGULAR EXPRESSION
|
||||
TABLES" or "TCP-BASED TABLES".
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
The search string is folded to lowercase before database lookup. As of
|
||||
Postfix 2.3, the search string is not case folded with database types
|
||||
such as <a href="regexp_table.5.html">regexp</a>: or <a href="pcre_table.5.html">pcre</a>: whose lookup fields can match both upper and
|
||||
lower case.
|
||||
|
||||
<b>TABLE FORMAT</b>
|
||||
<b><a name="table_format">TABLE FORMAT</a></b>
|
||||
The input format for the <a href="postmap.1.html"><b>postmap</b>(1)</a> command is as follows:
|
||||
|
||||
<i>pattern address, address, ...</i>
|
||||
@ -82,7 +82,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
A logical line starts with non-whitespace text. A line that
|
||||
starts with whitespace continues a logical line.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
With lookups from indexed files such as DB or DBM, or from networked
|
||||
tables such as NIS, LDAP or SQL, each <i>user</i>@<i>domain</i> query produces a
|
||||
sequence of query patterns as described below.
|
||||
@ -128,7 +128,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
In the above example, Postfix may contact a remote server if the
|
||||
recipient is aliased to a remote address.
|
||||
|
||||
<b>RESULT ADDRESS REWRITING</b>
|
||||
<b><a name="result_address_rewriting">RESULT ADDRESS REWRITING</a></b>
|
||||
The lookup result is subject to address rewriting:
|
||||
|
||||
<b>o</b> When the result has the form @<i>otherdomain</i>, the result becomes
|
||||
@ -141,7 +141,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
<b>o</b> When "<b><a href="postconf.5.html#append_dot_mydomain">append_dot_mydomain</a>=yes</b>", append "<b>.$<a href="postconf.5.html#mydomain">mydomain</a></b>" to addresses
|
||||
without ".domain".
|
||||
|
||||
<b>ADDRESS EXTENSION</b>
|
||||
<b><a name="address_extension">ADDRESS EXTENSION</a></b>
|
||||
When a mail address localpart contains the optional recipient delimiter
|
||||
(e.g., <i>user+foo</i>@<i>domain</i>), the lookup order becomes: <i>user+foo</i>@<i>domain</i>,
|
||||
<i>user</i>@<i>domain</i>, <i>user+foo</i>, <i>user</i>, and @<i>domain</i>.
|
||||
@ -150,7 +150,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
unmatched address extension (<i>+foo</i>) is propagated to the result of a ta-
|
||||
ble lookup.
|
||||
|
||||
<b>VIRTUAL ALIAS DOMAINS</b>
|
||||
<b><a name="virtual_alias_domains">VIRTUAL ALIAS DOMAINS</a></b>
|
||||
Besides virtual aliases, the virtual alias table can also be used to
|
||||
implement <a href="ADDRESS_CLASS_README.html#virtual_alias_class">virtual alias domains</a>. With a virtual alias domain, all
|
||||
recipient addresses are aliased to addresses in other domains.
|
||||
@ -195,7 +195,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
<b>tual_alias_domains</a></b> configuration parameter. This latter parameter uses
|
||||
the same syntax as the <a href="postconf.5.html"><b>main.cf</a> <a href="postconf.5.html#mydestination">mydestination</a></b> configuration parameter.
|
||||
|
||||
<b>REGULAR EXPRESSION TABLES</b>
|
||||
<b><a name="regular_expression_tables">REGULAR EXPRESSION TABLES</a></b>
|
||||
This section describes how the table lookups change when the table is
|
||||
given in the form of regular expressions. For a description of regular
|
||||
expression lookup table syntax, see <a href="regexp_table.5.html"><b>regexp_table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre_table</b>(5)</a>.
|
||||
@ -212,7 +212,7 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
feature that parenthesized substrings from the pattern can be interpo-
|
||||
lated as <b>$1</b>, <b>$2</b> and so on.
|
||||
|
||||
<b>TCP-BASED TABLES</b>
|
||||
<b><a name="tcp-based_tables">TCP-BASED TABLES</a></b>
|
||||
This section describes how the table lookups change when lookups are
|
||||
directed to a TCP-based server. For a description of the TCP
|
||||
client/server lookup protocol, see <a href="tcp_table.5.html"><b>tcp_table</b>(5)</a>. This feature is
|
||||
@ -224,10 +224,10 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
|
||||
Results are the same as with indexed file lookups.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
The table format does not understand quoting conventions.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
The following <a href="postconf.5.html"><b>main.cf</b></a> parameters are especially relevant to this topic.
|
||||
See the Postfix <a href="postconf.5.html"><b>main.cf</b></a> file for syntax details and for default values.
|
||||
Use the "<b>postfix reload</b>" command after a configuration change.
|
||||
@ -273,18 +273,18 @@ VIRTUAL(5) VIRTUAL(5)
|
||||
receives mail on by way of a proxy or network address transla-
|
||||
tion unit.
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="cleanup.8.html">cleanup(8)</a>, canonicalize and enqueue mail
|
||||
<a href="postmap.1.html">postmap(1)</a>, Postfix lookup table manager
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="canonical.5.html">canonical(5)</a>, canonical address mapping
|
||||
|
||||
<b>README FILES</b>
|
||||
<b><a name="readme_files">README FILES</a></b>
|
||||
<a href="ADDRESS_REWRITING_README.html">ADDRESS_REWRITING_README</a>, address rewriting guide
|
||||
<a href="DATABASE_README.html">DATABASE_README</a>, Postfix lookup table overview
|
||||
<a href="VIRTUAL_README.html">VIRTUAL_README</a>, domain hosting guide
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>AUTHOR(S)</b>
|
||||
|
@ -7,13 +7,13 @@
|
||||
</head> <body> <pre>
|
||||
VIRTUAL(8) VIRTUAL(8)
|
||||
|
||||
<b>NAME</b>
|
||||
<b><a name="name">NAME</a></b>
|
||||
virtual - Postfix virtual domain mail delivery agent
|
||||
|
||||
<b>SYNOPSIS</b>
|
||||
<b><a name="synopsis">SYNOPSIS</a></b>
|
||||
<b>virtual</b> [generic Postfix daemon options]
|
||||
|
||||
<b>DESCRIPTION</b>
|
||||
<b><a name="description">DESCRIPTION</a></b>
|
||||
The <a href="virtual.8.html"><b>virtual</b>(8)</a> delivery agent is designed for virtual mail hosting ser-
|
||||
vices. Originally based on the Postfix <a href="local.8.html"><b>local</b>(8)</a> delivery agent, this
|
||||
agent looks up recipients with map lookups of their full recipient
|
||||
@ -24,7 +24,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
forwarding, out-of-office notifications, etc., must be configured via
|
||||
virtual_alias maps or via similar lookup mechanisms.
|
||||
|
||||
<b>MAILBOX LOCATION</b>
|
||||
<b><a name="mailbox_location">MAILBOX LOCATION</a></b>
|
||||
The mailbox location is controlled by the <b><a href="postconf.5.html#virtual_mailbox_base">virtual_mailbox_base</a></b> and <b><a href="postconf.5.html#virtual_mailbox_maps">vir</a>-</b>
|
||||
<b><a href="postconf.5.html#virtual_mailbox_maps">tual_mailbox_maps</a></b> configuration parameters (see below). The <b><a href="postconf.5.html#virtual_mailbox_maps">vir-</b>
|
||||
<b>tual_mailbox_maps</a></b> table is indexed by the recipient address as
|
||||
@ -36,7 +36,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
|
||||
where <i>recipient</i> is the full recipient address.
|
||||
|
||||
<b>UNIX MAILBOX FORMAT</b>
|
||||
<b><a name="unix_mailbox_format">UNIX MAILBOX FORMAT</a></b>
|
||||
When the mailbox location does not end in <b>/</b>, the message is delivered
|
||||
in UNIX mailbox format. This format stores multiple messages in one
|
||||
textfile.
|
||||
@ -52,7 +52,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
progress. In case of problems, an attempt is made to truncate the mail-
|
||||
box to its original length.
|
||||
|
||||
<b>QMAIL MAILDIR FORMAT</b>
|
||||
<b><a name="qmail_maildir_format">QMAIL MAILDIR FORMAT</a></b>
|
||||
When the mailbox location ends in <b>/</b>, the message is delivered in qmail
|
||||
<b>maildir</b> format. This format stores one message per file.
|
||||
|
||||
@ -64,7 +64,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
By definition, <b>maildir</b> format does not require application-level file
|
||||
locking during mail delivery or retrieval.
|
||||
|
||||
<b>MAILBOX OWNERSHIP</b>
|
||||
<b><a name="mailbox_ownership">MAILBOX OWNERSHIP</a></b>
|
||||
Mailbox ownership is controlled by the <b><a href="postconf.5.html#virtual_uid_maps">virtual_uid_maps</a></b> and <b><a href="postconf.5.html#virtual_gid_maps">vir</a>-</b>
|
||||
<b><a href="postconf.5.html#virtual_gid_maps">tual_gid_maps</a></b> lookup tables, which are indexed with the full recipient
|
||||
address. Each table provides a string with the numerical user and group
|
||||
@ -73,12 +73,12 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
The <b><a href="postconf.5.html#virtual_minimum_uid">virtual_minimum_uid</a></b> parameter imposes a lower bound on numerical
|
||||
user ID values that may be specified in any <b><a href="postconf.5.html#virtual_uid_maps">virtual_uid_maps</a></b>.
|
||||
|
||||
<b>CASE FOLDING</b>
|
||||
<b><a name="case_folding">CASE FOLDING</a></b>
|
||||
All delivery decisions are made using the full recipient address,
|
||||
folded to lower case. See also the next section for a few exceptions
|
||||
with optional address extensions.
|
||||
|
||||
<b>TABLE SEARCH ORDER</b>
|
||||
<b><a name="table_search_order">TABLE SEARCH ORDER</a></b>
|
||||
Normally, a lookup table is specified as a text file that serves as
|
||||
input to the <a href="postmap.1.html"><b>postmap</b>(1)</a> command. The result, an indexed file in <b>dbm</b> or
|
||||
<b>db</b> format, is used for fast searching by the mail system.
|
||||
@ -104,7 +104,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
where patterns are given as regular expressions. In that case, only the
|
||||
full recipient address is given to the regular-expression map.
|
||||
|
||||
<b>SECURITY</b>
|
||||
<b><a name="security">SECURITY</a></b>
|
||||
The <a href="virtual.8.html"><b>virtual</b>(8)</a> delivery agent is not security sensitive, provided that
|
||||
the lookup tables with recipient user/group ID information are ade-
|
||||
quately protected. This program is not designed to run chrooted.
|
||||
@ -118,10 +118,10 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
Postfix version 2.2, the virtual delivery agent will terminate with a
|
||||
fatal error.
|
||||
|
||||
<b>STANDARDS</b>
|
||||
<b><a name="standards">STANDARDS</a></b>
|
||||
<a href="https://tools.ietf.org/html/rfc822">RFC 822</a> (ARPA Internet Text Messages)
|
||||
|
||||
<b>DIAGNOSTICS</b>
|
||||
<b><a name="diagnostics">DIAGNOSTICS</a></b>
|
||||
Mail bounces when the recipient has no mailbox or when the recipient is
|
||||
over disk quota. In all other problem cases, mail for an existing
|
||||
recipient is deferred and a warning is logged.
|
||||
@ -133,7 +133,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
|
||||
ter is notified of bounces and of other trouble.
|
||||
|
||||
<b>BUGS</b>
|
||||
<b><a name="bugs">BUGS</a></b>
|
||||
This delivery agent supports address extensions in email addresses and
|
||||
in lookup table keys, but does not propagate address extension informa-
|
||||
tion to the result of table lookup.
|
||||
@ -142,7 +142,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
attributes. In order to avoid the inconvenience of maintaining three
|
||||
tables, use an LDAP or MYSQL database.
|
||||
|
||||
<b>CONFIGURATION PARAMETERS</b>
|
||||
<b><a name="configuration_parameters">CONFIGURATION PARAMETERS</a></b>
|
||||
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as <a href="virtual.8.html"><b>virtual</b>(8)</a> processes
|
||||
run for only a limited amount of time. Use the command "<b>postfix reload</b>"
|
||||
to speed up a change.
|
||||
@ -150,7 +150,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
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>MAILBOX DELIVERY CONTROLS</b>
|
||||
<b><a name="mailbox_delivery_controls">MAILBOX DELIVERY CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#virtual_mailbox_base">virtual_mailbox_base</a> (empty)</b>
|
||||
A prefix that the <a href="virtual.8.html"><b>virtual</b>(8)</a> delivery agent prepends to all
|
||||
pathname results from $<a href="postconf.5.html#virtual_mailbox_maps">virtual_mailbox_maps</a> table lookups.
|
||||
@ -188,7 +188,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
Defer delivery when a mailbox file is not owned by its recipi-
|
||||
ent.
|
||||
|
||||
<b>LOCKING CONTROLS</b>
|
||||
<b><a name="locking_controls">LOCKING CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#virtual_mailbox_lock">virtual_mailbox_lock</a> (see 'postconf -d' output)</b>
|
||||
How to lock a UNIX-style <a href="virtual.8.html"><b>virtual</b>(8)</a> mailbox before attempting
|
||||
delivery.
|
||||
@ -205,7 +205,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
The time after which a stale exclusive mailbox lockfile is
|
||||
removed.
|
||||
|
||||
<b>RESOURCE AND RATE CONTROLS</b>
|
||||
<b><a name="resource_and_rate_controls">RESOURCE AND RATE CONTROLS</a></b>
|
||||
<b><a href="postconf.5.html#virtual_mailbox_limit">virtual_mailbox_limit</a> (51200000)</b>
|
||||
The maximal size in bytes of an individual <a href="virtual.8.html"><b>virtual</b>(8)</a> mailbox or
|
||||
maildir file, or zero (no limit).
|
||||
@ -222,7 +222,7 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
The maximal number of recipients per message for the virtual
|
||||
message delivery transport.
|
||||
|
||||
<b>MISCELLANEOUS CONTROLS</b>
|
||||
<b><a name="miscellaneous_controls">MISCELLANEOUS CONTROLS</a></b>
|
||||
<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.
|
||||
@ -286,22 +286,22 @@ VIRTUAL(8) VIRTUAL(8)
|
||||
The email address form that will be used in non-debug logging
|
||||
(info, warning, etc.).
|
||||
|
||||
<b>SEE ALSO</b>
|
||||
<b><a name="see_also">SEE ALSO</a></b>
|
||||
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
||||
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
||||
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
||||
<a href="postlogd.8.html">postlogd(8)</a>, Postfix logging
|
||||
syslogd(8), system logging
|
||||
|
||||
<b>README_FILES</b>
|
||||
<b><a name="readme_files">README_FILES</a></b>
|
||||
Use "<b>postconf <a href="postconf.5.html#readme_directory">readme_directory</a></b>" or
|
||||
"<b>postconf <a href="postconf.5.html#html_directory">html_directory</a></b>" to locate this information.
|
||||
<a href="VIRTUAL_README.html">VIRTUAL_README</a>, domain hosting howto
|
||||
|
||||
<b>LICENSE</b>
|
||||
<b><a name="license">LICENSE</a></b>
|
||||
The Secure Mailer license must be distributed with this software.
|
||||
|
||||
<b>HISTORY</b>
|
||||
<b><a name="history">HISTORY</a></b>
|
||||
This delivery agent was originally based on the Postfix local delivery
|
||||
agent. Modifications mainly consisted of removing code that either was
|
||||
not applicable or that was not safe in this context: aliases,
|
||||
|
@ -83,3 +83,5 @@ Dilyan
|
||||
Palauzov
|
||||
pkgconf
|
||||
testfiles
|
||||
Antonin
|
||||
Verrier
|
||||
|
@ -20,7 +20,7 @@
|
||||
* Patches change both the patchlevel and the release date. Snapshots have no
|
||||
* patchlevel; they change the release date only.
|
||||
*/
|
||||
#define MAIL_RELEASE_DATE "20240928"
|
||||
#define MAIL_RELEASE_DATE "20240930"
|
||||
#define MAIL_VERSION_NUMBER "3.10"
|
||||
|
||||
#ifdef SNAPSHOT
|
||||
|
@ -4680,13 +4680,11 @@ static int generic_checks(SMTPD_STATE *state, ARGV *restrictions,
|
||||
cpp[1], CHECK_RELAY_DOMAINS);
|
||||
} else if (strcasecmp(name, PERMIT_SASL_AUTH) == 0) {
|
||||
#ifdef USE_SASL_AUTH
|
||||
if (smtpd_sasl_is_active(state)) {
|
||||
status = permit_sasl_auth(state,
|
||||
SMTPD_CHECK_OK, SMTPD_CHECK_DUNNO);
|
||||
if (status == SMTPD_CHECK_OK)
|
||||
status = smtpd_acl_permit(state, name, SMTPD_NAME_CLIENT,
|
||||
state->namaddr, NO_PRINT_ARGS);
|
||||
}
|
||||
status = permit_sasl_auth(state,
|
||||
SMTPD_CHECK_OK, SMTPD_CHECK_DUNNO);
|
||||
if (status == SMTPD_CHECK_OK)
|
||||
status = smtpd_acl_permit(state, name, SMTPD_NAME_CLIENT,
|
||||
state->namaddr, NO_PRINT_ARGS);
|
||||
#endif
|
||||
} else if (strcasecmp(name, PERMIT_TLS_ALL_CLIENTCERTS) == 0) {
|
||||
status = permit_tls_clientcerts(state, 1);
|
||||
|
Loading…
x
Reference in New Issue
Block a user