diff options
| author | itojun <itojun@NetBSD.org> | 2001-03-13 17:45:02 +0000 |
|---|---|---|
| committer | itojun <itojun@NetBSD.org> | 2001-03-13 17:45:02 +0000 |
| commit | 173b2f6655e38657f15bb57fe26dc23e8d054d4e (patch) | |
| tree | 04af30df8438e7c54ceb4e5f4bf0dff83788ce54 /gnu/dist/postfix/html | |
| parent | c7871f80bf97592f2ca4dd16d6d7708bec2c33a2 (diff) | |
postfix release-20010228
Diffstat (limited to 'gnu/dist/postfix/html')
40 files changed, 3576 insertions, 1234 deletions
diff --git a/gnu/dist/postfix/html/Makefile.in b/gnu/dist/postfix/html/Makefile.in index cedbfc1aab5..8f7e91ac162 100644 --- a/gnu/dist/postfix/html/Makefile.in +++ b/gnu/dist/postfix/html/Makefile.in @@ -1,19 +1,22 @@ +SHELL = /bin/sh + # For now, just hard-coded rules for daemons, commands, config files. DAEMONS = bounce.8.html cleanup.8.html defer.8.html error.8.html local.8.html \ - master.8.html pickup.8.html pipe.8.html qmgr.8.html showq.8.html \ - smtp.8.html smtpd.8.html trivial-rewrite.8.html + lmtp.8.html master.8.html pickup.8.html pipe.8.html qmgr.8.html \ + showq.8.html smtp.8.html smtpd.8.html trivial-rewrite.8.html \ + spawn.8.html flush.8.html # nqmgr.8.html virtual.8.html COMMANDS= mailq.1.html newaliases.1.html postalias.1.html postcat.1.html \ postconf.1.html postfix.1.html postkick.1.html postlock.1.html \ postlog.1.html postdrop.1.html postmap.1.html sendmail.1.html \ postsuper.1.html CONFIG = access.5.html aliases.5.html canonical.5.html relocated.5.html \ - transport.5.html virtual.5.html + transport.5.html virtual.5.html pcre_table.5.html regexp_table.5.html update: $(DAEMONS) $(COMMANDS) $(CONFIG) Makefile: Makefile.in - (set -e; echo "# DO NOT EDIT"; $(OPTS) $(SHELL) ../makedefs && cat $?) >$@ + (set -e; echo "# DO NOT EDIT"; $(OPTS) $(SHELL) ../src/makedefs; cat $?) >$@ clean: echo clean @@ -23,77 +26,95 @@ tidy: clean clobber: rm -f $(DAEMONS) $(COMMANDS) $(CONFIG) -bounce.8.html: ../bounce/bounce.c +bounce.8.html: ../src/bounce/bounce.c srctoman $? | nroff -man | man2html | postlink >$@ defer.8.html: bounce.8.html rm -f $@ ln -s $? $@ -error.8.html: ../error/error.c +error.8.html: ../src/error/error.c + srctoman $? | nroff -man | man2html | postlink >$@ + +flush.8.html: ../src/flush/flush.c + srctoman $? | nroff -man | man2html | postlink >$@ + +cleanup.8.html: ../src/cleanup/cleanup.c + srctoman $? | nroff -man | man2html | postlink >$@ + +lmtp.8.html: ../src/lmtp/lmtp.c srctoman $? | nroff -man | man2html | postlink >$@ -cleanup.8.html: ../cleanup/cleanup.c +local.8.html: ../src/local/local.c srctoman $? | nroff -man | man2html | postlink >$@ -local.8.html: ../local/local.c +master.8.html: ../src/master/master.c srctoman $? | nroff -man | man2html | postlink >$@ -master.8.html: ../master/master.c +nqmgr.8.html: ../src/nqmgr/qmgr.c + srctoman $? | sed -e 's/qmgr[^_]/n&/' \ + -e 's/qmgr$$/n&/' \ + -e 's/QMGR[^_]/N&/' | \ + nroff -man | man2html | postlink >$@ + +pickup.8.html: ../src/pickup/pickup.c + srctoman $? | nroff -man | man2html | postlink >$@ + +pipe.8.html: ../src/pipe/pipe.c srctoman $? | nroff -man | man2html | postlink >$@ -pickup.8.html: ../pickup/pickup.c +qmgr.8.html: ../src/qmgr/qmgr.c srctoman $? | nroff -man | man2html | postlink >$@ -pipe.8.html: ../pipe/pipe.c +showq.8.html: ../src/showq/showq.c srctoman $? | nroff -man | man2html | postlink >$@ -qmgr.8.html: ../qmgr/qmgr.c +spawn.8.html: ../src/spawn/spawn.c srctoman $? | nroff -man | man2html | postlink >$@ -showq.8.html: ../showq/showq.c +smtp.8.html: ../src/smtp/smtp.c srctoman $? | nroff -man | man2html | postlink >$@ -smtp.8.html: ../smtp/smtp.c +smtpd.8.html: ../src/smtpd/smtpd.c srctoman $? | nroff -man | man2html | postlink >$@ -smtpd.8.html: ../smtpd/smtpd.c +virtual.8.html: ../src/virtual/virtual.c srctoman $? | nroff -man | man2html | postlink >$@ -trivial-rewrite.8.html: ../trivial-rewrite/trivial-rewrite.c +trivial-rewrite.8.html: ../src/trivial-rewrite/trivial-rewrite.c srctoman $? | nroff -man | man2html | postlink >$@ -postalias.1.html: ../postalias/postalias.c +postalias.1.html: ../src/postalias/postalias.c srctoman $? | nroff -man | man2html | postlink >$@ -postcat.1.html: ../postcat/postcat.c +postcat.1.html: ../src/postcat/postcat.c srctoman $? | nroff -man | man2html | postlink >$@ -postconf.1.html: ../postconf/postconf.c +postconf.1.html: ../src/postconf/postconf.c srctoman $? | nroff -man | man2html | postlink >$@ -postdrop.1.html: ../postdrop/postdrop.c +postdrop.1.html: ../src/postdrop/postdrop.c srctoman $? | nroff -man | man2html | postlink >$@ -postfix.1.html: ../postfix/postfix.c +postfix.1.html: ../src/postfix/postfix.c srctoman $? | nroff -man | man2html | postlink >$@ -postkick.1.html: ../postkick/postkick.c +postkick.1.html: ../src/postkick/postkick.c srctoman $? | nroff -man | man2html | postlink >$@ -postlock.1.html: ../postlock/postlock.c +postlock.1.html: ../src/postlock/postlock.c srctoman $? | nroff -man | man2html | postlink >$@ -postlog.1.html: ../postlog/postlog.c +postlog.1.html: ../src/postlog/postlog.c srctoman $? | nroff -man | man2html | postlink >$@ -postmap.1.html: ../postmap/postmap.c +postmap.1.html: ../src/postmap/postmap.c srctoman $? | nroff -man | man2html | postlink >$@ -postsuper.1.html: ../postsuper/postsuper.c +postsuper.1.html: ../src/postsuper/postsuper.c srctoman $? | nroff -man | man2html | postlink >$@ -sendmail.1.html: ../sendmail/sendmail.c +sendmail.1.html: ../src/sendmail/sendmail.c srctoman $? | nroff -man | man2html | postlink >$@ mailq.1.html: sendmail.1.html @@ -104,20 +125,26 @@ newaliases.1.html: sendmail.1.html rm -f $@ ln -s $? $@ -access.5.html: ../conf/access +access.5.html: ../proto/access + srctoman - $? | nroff -man | man2html | postlink >$@ + +aliases.5.html: ../proto/aliases + srctoman - $? | nroff -man | man2html | postlink >$@ + +canonical.5.html: ../proto/canonical srctoman - $? | nroff -man | man2html | postlink >$@ -aliases.5.html: ../conf/aliases +pcre_table.5.html: ../proto/pcre_table srctoman - $? | nroff -man | man2html | postlink >$@ -canonical.5.html: ../conf/canonical +regexp_table.5.html: ../proto/regexp_table srctoman - $? | nroff -man | man2html | postlink >$@ -relocated.5.html: ../conf/relocated +relocated.5.html: ../proto/relocated srctoman - $? | nroff -man | man2html | postlink >$@ -transport.5.html: ../conf/transport +transport.5.html: ../proto/transport srctoman - $? | nroff -man | man2html | postlink >$@ -virtual.5.html: ../conf/virtual +virtual.5.html: ../proto/virtual srctoman - $? | nroff -man | man2html | postlink >$@ diff --git a/gnu/dist/postfix/html/access.5.html b/gnu/dist/postfix/html/access.5.html index 78284a568f5..0818d204c6f 100644 --- a/gnu/dist/postfix/html/access.5.html +++ b/gnu/dist/postfix/html/access.5.html @@ -17,34 +17,63 @@ ACCESS(5) ACCESS(5) hosts, domains, networks, host addresses or mail addresses. - The table 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. After an update it may - take a minute or so before the change becomes visible. - Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay. - + Normally, the <b>access</b> 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. Execute the command + <b>postmap</b> <b>/etc/postfix/access</b> in order to rebuild the + indexed file after changing the access table. + + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. + + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. + +<b>TABLE</b> <b>FORMAT</b> The format of the access table is as follows: blanks and comments Blank lines are ignored, as are lines beginning with `#'. + leading whitespace + Lines that begin with whitespace continue the pre- + vious line. + <i>pattern</i> <i>action</i> When <i>pattern</i> matches a mail address, domain or host address, perform the corresponding <i>action</i>. <b>PATTERNS</b> - Patterns are tried in the order as listed below: + 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: <i>user</i>@<i>domain</i> Matches the specified mail address. <i>domain.name</i> - Matches the <i>domain.name</i> itself and any subdomain - thereof, either in hostnames or in mail addresses. + Matches the <i>domain.name</i> itself and any subdomain + thereof, either in hostnames or in mail addresses. + + + + 1 + + + + + +ACCESS(5) ACCESS(5) + + Top-level domains will never be matched. - <i>user</i>@ Matches all mail addresses with the specified user + <i>user</i>@ Matches all mail addresses with the specified user part. <i>net.work.addr.ess</i> @@ -53,46 +82,70 @@ ACCESS(5) ACCESS(5) <i>net.work</i> - <i>net</i> Matches any host address in the specified network. - A network address is a sequence of one or more + <i>net</i> Matches any host address in the specified network. + A network address is a sequence of one or more octets separated by ".". <b>ACTIONS</b> + [<b>45</b>]<i>XX</i> <i>text</i> + Reject the address etc. that matches the pattern, + and respond with the numerical code and text. + <b>REJECT</b> Reject the address etc. that matches the pattern. A + generic error response message is generated. + <b>OK</b> Accept the address etc. that matches the pattern. + <i>restriction...</i> + Apply the named UCE restriction (<b>permit</b>, reject, + <b>reject</b><i>_</i><b>unauth</b><i>_</i><b>destination</b>, and so on). - 1 +<b>REGULAR</b> <b>EXPRESSION</b> <b>TABLES</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</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + Each pattern is a regular expression that is applied to + the entire string being looked up. Depending on the appli- + cation, that string is an entire client hostname, an + entire client IP address, or an entire mail address. Thus, + no parent domain or parent network search is done, and + <i>user@domain</i> mail addresses are not broken up into their + <i>user@</i> and <i>domain</i> constituent parts. + Patterns are applied in the order as specified in the + table, until a pattern is found that matches the search + string. + Actions are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. +<b>BUGS</b> + The table format does not understand quoting conventions. -ACCESS(5) ACCESS(5) - [<b>45</b>]<i>XX</i> <i>text</i> - Reject the address etc. that matches the pattern, - and respond with the numerical code and text. - <b>REJECT</b> Reject the address etc. that matches the pattern. A - generic error response message is generated. + 2 + - <b>OK</b> - <i>Any</i> <i>other</i> <i>text</i> - Accept the address etc. that matches the pattern. -<b>BUGS</b> - The table format does not understand quoting conventions. + +ACCESS(5) ACCESS(5) + <b>SEE</b> <b>ALSO</b> <a href="postmap.1.html">postmap(1)</a> create mapping table <a href="smtpd.8.html">smtpd(8)</a> smtp server + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables <b>LICENSE</b> - The Secure Mailer license must be distributed with - this software. + The Secure Mailer license must be distributed with this + software. <b>AUTHOR(S)</b> Wietse Venema @@ -128,7 +181,20 @@ ACCESS(5) ACCESS(5) - 2 + + + + + + + + + + + + + + 3 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/aliases.5.html b/gnu/dist/postfix/html/aliases.5.html index 887e9ec3199..50b5aaa3f91 100644 --- a/gnu/dist/postfix/html/aliases.5.html +++ b/gnu/dist/postfix/html/aliases.5.html @@ -9,17 +9,19 @@ ALIASES(5) ALIASES(5) aliases - format of the Postfix alias database <b>SYNOPSIS</b> - <b>postalias</b> [<b>-c</b> <i>config_dir</i>] [<b>-v</b>] [<i>file_type</i>:]<i>input_file</i> + <b>newaliases</b> <b>DESCRIPTION</b> - The <b>aliases</b> file provides a system-wide mechanism to redi- - rect mail for local recipients. + The <b>aliases</b> table provides a system-wide mechanism to + redirect mail for local recipients. The redirections are + processed by the Postfix <a href="local.8.html"><b>local</b>(8)</a> delivery agent. - The file serves as input to the <a href="postalias.1.html"><b>postalias</b>(1)</a> command. The + Normally, the <b>aliases</b> table is specified as a text file + that serves as input to the <a href="postalias.1.html"><b>postalias</b>(1)</a> command. The result, an indexed file in <b>dbm</b> or <b>db</b> format, is used for - fast lookup by the mail system. After an update it may - take a minute or so before the change becomes visible. - Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay. + fast lookup by the mail system. Execute the command + <b>newaliases</b> in order to rebuild the indexed file after + changing the Postfix alias database. The input and output file formats are expected to be com- patible with Sendmail version 8, and are expected to be @@ -57,8 +59,6 @@ ALIASES(5) ALIASES(5) The <i>value</i> contains one or more of the following: - <i>address</i> - Mail is forwarded to <i>address</i>, which is compatible @@ -71,7 +71,9 @@ ALIASES(5) ALIASES(5) ALIASES(5) ALIASES(5) - with the RFC 822 standard. + <i>address</i> + Mail is forwarded to <i>address</i>, which is compatible + with the <a href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> standard. <i>/file/name</i> Mail is appended to <i>/file/name</i>. See <a href="local.8.html"><b>local</b>(8)</a> for @@ -122,9 +124,7 @@ ALIASES(5) ALIASES(5) Restrict the usage of mail delivery to external command. - <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>files</b> - Restrict the usage of mail delivery to external - file. + @@ -137,23 +137,33 @@ ALIASES(5) ALIASES(5) ALIASES(5) ALIASES(5) + <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>files</b> + Restrict the usage of mail delivery to external + file. + + <b>expand</b><i>_</i><b>owner</b><i>_</i><b>alias</b> + When delivering to an alias that has an <b>owner-</b> com- + panion alias, set the envelope sender address to + the right-hand side of the owner alias, instead + using of the left-hand side address. + <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> addresses. <b>recipient</b><i>_</i><b>delimiter</b> - Delimiter that separates recipients from address + Delimiter that separates recipients from address extensions. <b>STANDARDS</b> - RFC 822 (ARPA Internet Text Messages) + <a href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> (ARPA Internet Text Messages) <b>SEE</b> <b>ALSO</b> <a href="local.8.html">local(8)</a> local delivery agent <a href="postalias.1.html">postalias(1)</a> alias database management <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -184,16 +194,6 @@ ALIASES(5) ALIASES(5) - - - - - - - - - - 3 diff --git a/gnu/dist/postfix/html/backstage.html b/gnu/dist/postfix/html/backstage.html index 5ce551c0427..577a3c0323f 100644 --- a/gnu/dist/postfix/html/backstage.html +++ b/gnu/dist/postfix/html/backstage.html @@ -57,6 +57,22 @@ or in order to resolve a destination. queue status. This is the program behind the <a href="mailq.1.html">mailq</a> command. +<p> + +<li>The <a href="flush.8.html">flush</a> daemon improves the +performance of the SMTP <b>ETRN</b> request, and of its command-line +equivalent, <b>sendmail -qR</b><i>destination</i>, for selected +destinations. For other destinations, Postfix silently falls +back to the equivalent of <b>sendmail -q</b>. + +<p> + +<li>The <a href="spawn.8.html">spawn</a> daemon listens on a TCP +port, UNIX-domain socket or FIFO, and runs non-Postfix commands on +request, with the socket or FIFO connected to the standard input, +output and error streams. It is currently used only in an example +of the Postfix external content filtering system. + </ul> <hr> diff --git a/gnu/dist/postfix/html/basic.html b/gnu/dist/postfix/html/basic.html index 19635f6f9bc..3333296b739 100644 --- a/gnu/dist/postfix/html/basic.html +++ b/gnu/dist/postfix/html/basic.html @@ -32,6 +32,9 @@ three parameters before you can use the Postfix mail system: <li> <a href="#mydestination"> What domains to receive mail for </a> +<p> + +<li> <a href="#relaying"> What clients to relay mail for </a> </ul> @@ -158,6 +161,25 @@ hostnames of the machine, including $myhostname, and localhost.$mydomain. </dl> +<a name="relaying"> <h2> What clients to relay mail for </h2> </a> + +By default, Postfix will relay mail for clients in authorized +networks and in authorized domains. + +<p> + +Authorized client networks are defined by the <a +href="#mynetworks">mynetworks</a> parameter. The default is to +authorize all clients in the IP subnetworks that the local machine +is attached to. + +<p> + +Authorized client domains are by defined by the <a +href="uce.html#relay_domains"> relay_domains</a> configuration +parameter. The default setting trusts clients with hostnames below +the domain(s) listed in <a href="#mydestination">mydestination</a>. + <a name="notify"> <h2> What trouble to report to the postmaster </h2> </a> @@ -286,17 +308,59 @@ top-level domain). <a name="mynetworks"> <h2> My own networks </h2> </a> The <b>mynetworks</b> parameter lists all networks that this machine -is attached to. This information can be used by the <a href="uce.html"> -anti-UCE</a> features to distinguish between local systems and -strangers. +somehow trusts. This information can be used by the <a href="uce.html"> +anti-UCE</a> features to recognize trusted SMTP clients that are +allowed to relay mail through Postfix. + +<p> + +You can specify the list of trusted networks in the <b>main.cf</b> +file, or you can let Postfix deduce the list for you. The default +is to let Postfix do the work for you. + +<p> + +<dl> + +<dt> Default: + +<dd> <b>mynetworks_style = subnet</b> + +<p> + +<dt>The meaning of the styles is as follows: <p> -By default, <b>mynetworks</b> is set to the class A, B or C networks -that the machine is attached to. For example, for my machines at -home, the result is: <b>168.100.0.0/16 127.0.0.0/8. </b> However, -network <b>168.100</b> is owned by my ISP. Of course I do not want -to consider all their customer systems as local, so I use instead: +<dl> + +<dt> <b>class</b> <dd> Trust SMTP clients in the class A/B/C networks +that Postfix is connected to. <b>Don't do this with a dialup site +- it would cause Postfix to "trust" your entire provider's network. +Instead, specify an explicit mynetworks list by hand, as described +below</b>. + +<p> + +<dt> <b>subnet</b> (default) <dd> Trust SMTP clients in the IP +subnetworks that Postfix is connected to. + +<p> + +<dt> <b>host</b> <dd> Trust only the local machine. + +</dl> + +</dl> + +<p> + +Alternatively, you can specify the <b>mynetworks</b> list by hand, +in which case Postfix ignores the <b>mynetworks_style</b> setting. +To specify the list of trusted networks by hand, specify network +blocks in CIDR (network/mask) notation, for example: + +<p> <dl> @@ -304,6 +368,11 @@ to consider all their customer systems as local, so I use instead: </dl> +<p> + +You can also specify the absolute pathname of a pattern file instead +of listing the patterns in the <b>main.cf</b> file. + <a name="inet_interfaces"> <h2> My own network addresses </h2> </a> The <b>inet_interfaces</b> parameter specifies all network interface @@ -316,9 +385,14 @@ as if it is addressed to a domain listed in <b> $mydestination. The default is to listen on all active interfaces. If you run mailers on virtual interfaces, you will have to specify what -interfaces to listen on. This includes the non-virtual mailer that -receives mail for the machine itself as well: it should never listen -on the virtual interfaces or you would have a mailer loop. +interfaces to listen on. + +<p> + +You even have to specify explicit machine interfaces for the +non-virtual mailer that receives mail for the machine itself: the +non-virtual mailer should never listen on the virtual interfaces +or you would have a mailer loop. <dl> diff --git a/gnu/dist/postfix/html/bounce.8.html b/gnu/dist/postfix/html/bounce.8.html index 5dbe797eda1..63e760535e6 100644 --- a/gnu/dist/postfix/html/bounce.8.html +++ b/gnu/dist/postfix/html/bounce.8.html @@ -39,7 +39,8 @@ BOUNCE(8) BOUNCE(8) client. <b>STANDARDS</b> - RFC 822 (ARPA Internet Text Messages) + <a href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> (ARPA Internet Text Messages) + <a href="http://www.faqs.org/rfcs/rfc1894.html">RFC 1894</a> (Delivery Status Notifications) <b>DIAGNOSTICS</b> Problems and transactions are logged to <b>syslogd</b>(8). @@ -61,7 +62,6 @@ BOUNCE(8) BOUNCE(8) - 1 diff --git a/gnu/dist/postfix/html/canonical.5.html b/gnu/dist/postfix/html/canonical.5.html index fdfc525b65b..aedf505260f 100644 --- a/gnu/dist/postfix/html/canonical.5.html +++ b/gnu/dist/postfix/html/canonical.5.html @@ -12,15 +12,25 @@ CANONICAL(5) CANONICAL(5) <b>postmap</b> <b>/etc/postfix/canonical</b> <b>DESCRIPTION</b> - The optional <b>canonical</b> file specifies an address mapping + The optional <b>canonical</b> 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. The address mapping is recursive. - The file 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. After an update it may - take a minute or so before the change becomes visible. - Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay. + Normally, the <b>canonical</b> 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. Execute the command + <b>postmap</b> <b>/etc/postfix/canonical</b> in order to rebuild the + indexed file after changing the text file. + + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. + + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. The <b>canonical</b> mapping affects both message header addresses (i.e. addresses that appear inside messages) and @@ -38,26 +48,16 @@ CANONICAL(5) CANONICAL(5) The <b>canonical</b> mapping is not to be confused with local aliasing. Use the <a href="aliases.5.html"><b>aliases</b>(5)</a> map for that purpose. - The format of the <b>canonical</b> table is as follows, mappings - being tried in the order as listed in this manual page: +<b>TABLE</b> <b>FORMAT</b> + The format of the <b>canonical</b> table is as follows: blanks and comments - Blank lines are ignored, as are lines beginning + Blank lines are ignored, as are lines beginning with `#'. - <i>user</i>@<i>domain</i> <i>address</i> - <i>user</i>@<i>domain</i> is replaced by <i>address</i>. This form has - the highest precedence. - - This form useful to clean up addresses produced by - legacy mail systems. It can also be used to pro- - duce <i>Firstname.Lastname</i> style addresses, but see - below for a simpler solution. - - <i>user</i> <i>address</i> - <i>user</i>@<i>site</i> is replaced by <i>address</i> when <i>site</i> is equal - to $<b>myorigin</b>, when <i>site</i> is listed in $<b>mydestina-</b> - <b>tion</b>, or when it is listed in $<b>inet</b><i>_</i><b>interfaces</b>. + leading whitespace + Lines that begin with whitespace continue the pre- + vious line. @@ -71,32 +71,86 @@ CANONICAL(5) CANONICAL(5) CANONICAL(5) CANONICAL(5) - This form is useful for replacing login names by + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches a mail address, replace it by + the corresponding <i>result</i>. + + 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: + + <i>user</i>@<i>domain</i> <i>address</i> + <i>user</i>@<i>domain</i> is replaced by <i>address</i>. This form has + the highest precedence. + + This form useful to clean up addresses produced by + legacy mail systems. It can also be used to pro- + duce <i>Firstname.Lastname</i> style addresses, but see + below for a simpler solution. + + <i>user</i> <i>address</i> + <i>user</i>@<i>site</i> is replaced by <i>address</i> when <i>site</i> is equal + to $<b>myorigin</b>, when <i>site</i> is listed in $<b>mydestina-</b> + <b>tion</b>, or when it is listed in $<b>inet</b><i>_</i><b>interfaces</b>. + + This form is useful for replacing login names by <i>Firstname.Lastname</i>. @<i>domain</i> <i>address</i> - Every address in <i>domain</i> is replaced by <i>address</i>. + Every address in <i>domain</i> is replaced by <i>address</i>. This form has the lowest precedence. - In all the above forms, when <i>address</i> has the form @<i>other-</i> + In all the above forms, when <i>address</i> has the form @<i>other-</i> <i>domain</i>, the result is the same user in <i>otherdomain</i>. <b>ADDRESS</b> <b>EXTENSION</b> - When table lookup fails, and the address localpart con- - tains the optional recipient delimiter (e.g., - <i>user+foo</i>@<i>domain</i>), the search is repeated for the unex- - tended address (e.g. <i>user</i>@<i>domain</i>), and the unmatched + When table lookup fails, and the address localpart con- + tains the optional recipient delimiter (e.g., + <i>user+foo</i>@<i>domain</i>), the search is repeated for the unex- + tended address (e.g. <i>user</i>@<i>domain</i>), and the unmatched extension is propagated to the result of table lookup. The matching order is: <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</b> <b>EXPRESSION</b> <b>TABLES</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</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + + Each pattern is a regular expression that is applied to + the entire address being looked up. Thus, <i>user@domain</i> mail + addresses are not broken 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>. + + Patterns are applied in the order as specified in the + + + + 2 + + + + + +CANONICAL(5) CANONICAL(5) + + + table, until a pattern is found that matches the search + string. + + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. + <b>BUGS</b> - The table format does not understand quoting conventions. + The table format does not understand quoting conventions. <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this topic. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> + The following <b>main.cf</b> parameters are especially relevant + to this topic. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. <b>canonical</b><i>_</i><b>maps</b> @@ -113,48 +167,49 @@ CANONICAL(5) CANONICAL(5) Other parameters of interest: <b>inet</b><i>_</i><b>interfaces</b> - The network interface addresses that this system + The network interface addresses that this system receives mail on. <b>masquerade</b><i>_</i><b>domains</b> - List of domains that hide their subdomain struc- + List of domains that hide their subdomain struc- ture. <b>masquerade</b><i>_</i><b>exceptions</b> - List of user names that are not subject to address + List of user names that are not subject to address masquerading. + <b>mydestination</b> + List of domains that this mail system considers + local. + <b>myorigin</b> + The domain that is appended to locally-posted mail. + <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> + Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> + addresses. - - 2 +<b>SEE</b> <b>ALSO</b> + <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail + 3 -CANONICAL(5) CANONICAL(5) - <b>mydestination</b> - List of domains that this mail system considers - local. - <b>myorigin</b> - The domain that is appended to locally-posted mail. +CANONICAL(5) CANONICAL(5) - <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> - Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> - addresses. -<b>SEE</b> <b>ALSO</b> - <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail <a href="postmap.1.html">postmap(1)</a> create mapping table <a href="virtual.5.html">virtual(5)</a> virtual domain mapping + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -194,7 +249,18 @@ CANONICAL(5) CANONICAL(5) - 3 + + + + + + + + + + + + 4 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/cleanup.8.html b/gnu/dist/postfix/html/cleanup.8.html index 01827927a48..2c1722d5c27 100644 --- a/gnu/dist/postfix/html/cleanup.8.html +++ b/gnu/dist/postfix/html/cleanup.8.html @@ -104,7 +104,7 @@ CLEANUP(8) CLEANUP(8) <b>hopcount</b><i>_</i><b>limit</b> Limit the number of <b>Received:</b> message headers. - <b>recipients</b><i>_</i><b>witheld</b><i>_</i><b>header</b> + <b>undisclosed</b><i>_</i><b>recipients</b><i>_</i><b>header</b> The header line that is inserted when no recipients were specified in (Resent-)To: or (Resent-)Cc: mes- sage headers. @@ -160,6 +160,10 @@ CLEANUP(8) CLEANUP(8) Limit the amount of memory in bytes used to process a message header. + <b>extract</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> + Limit the amount of recipients extracted from mes- + sage headers. + <b>SEE</b> <b>ALSO</b> <a href="canonical.5.html">canonical(5)</a> canonical address lookup table format <a href="qmgr.8.html">qmgr(8)</a> queue manager daemon @@ -172,7 +176,7 @@ CLEANUP(8) CLEANUP(8) /etc/postfix/virtual*, virtual mapping table <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -190,10 +194,6 @@ CLEANUP(8) CLEANUP(8) - - - - 3 diff --git a/gnu/dist/postfix/html/delivering.html b/gnu/dist/postfix/html/delivering.html index 12036a192eb..ed2a9e533d4 100644 --- a/gnu/dist/postfix/html/delivering.html +++ b/gnu/dist/postfix/html/delivering.html @@ -39,11 +39,11 @@ click on the icon in the upper left-hand corner of this page. <li>The <a href="qmgr.8.html">queue manager</a> is the heart of the Postfix mail system. It contacts the <a href="local.8.html">local</a>, -<a href="smtp.8.html">smtp</a>, or <a href="pipe.8.html">pipe</a> -delivery agents, and sends a delivery request with queue file -pathname information, the message sender address, the host to -deliver to if the destination is remote, and one or more message -recipient addresses. +<a href="smtp.8.html">smtp</a>, <a href="lmtp.8.html">lmtp</a>, or +<a href="pipe.8.html">pipe</a> delivery agents, and sends a delivery +request with queue file pathname information, the message sender +address, the host to deliver to if the destination is remote, and +one or more message recipient addresses. <p> @@ -108,6 +108,20 @@ such as the popular <a href="faq.html#procmail">procmail</a> program. <p> +<li>The <a href="virtual.8.html">virtual</a> delivery agent is a +very much stripped down version of the local delivery agent that +delivers to mailboxes only. This is the most secure Postfix delivery +agent, because it does not aliases expansions and no .forward file +expansions. + +<p> + +This delivery agent can deliver mail for multiple domains, which +makes it especially suitable for hosting lots of small domains on +a single machine. + +<p> + <li>The <a href="smtp.8.html">SMTP client</a> looks up a list of mail exchangers for the destination host, sorts the list by preference, and tries each address in turn until it finds a server @@ -116,6 +130,15 @@ client processes running in parallel. <p> +<li>The <a href="lmtp.8.html">LMTP client</a> speaks a protocol +similar to SMTP. The client can connect to local or remote mailbox +servers such as Cyrus. All the queue management is done by Postfix. +The advantage of this setup is that one Postfix machine can feed +multiple mailbox servers over LMTP. The opposite is true as well: +one mailbox server can be fed over LMTP by multiple Postfix machines. + +<p> + <li>The <a href="pipe.8.html">pipe mailer</a> is the outbound interface to other mail transports (the <a href="sendmail.1.html">sendmail</a> program is the inbound interface). diff --git a/gnu/dist/postfix/html/error.8.html b/gnu/dist/postfix/html/error.8.html index 2a3d401f8c8..d36ab9919bd 100644 --- a/gnu/dist/postfix/html/error.8.html +++ b/gnu/dist/postfix/html/error.8.html @@ -16,8 +16,8 @@ ERROR(8) ERROR(8) requests from the queue manager. Each request specifies a queue file, a sender address, a domain or host name that is treated as the reason for non-delivery, and recipient - information. This program expects to be run from the <a href="master.8.html"><b>mas-</b> - <b>ter</b>(8)</a> process manager. + information. This program expects to be run from the <a href="master.8.html"><b>mas-</b></a> + <a href="master.8.html"><b>ter</b>(8)</a> process manager. The error mailer client forces all recipients to bounce, using the domain or host information as the reason for diff --git a/gnu/dist/postfix/html/faq.html b/gnu/dist/postfix/html/faq.html index e3bc09edba7..d48c5be2f10 100644 --- a/gnu/dist/postfix/html/faq.html +++ b/gnu/dist/postfix/html/faq.html @@ -22,15 +22,25 @@ <ul> +<li><a href="#poppers">POP or IMAP problems</a> + +<li><a href="#warnings">Postfix warnings and error messages</a> + <li><a href="#example_config">Example configurations</a> <li><a href="#sendmail_incompatibility">Sendmail incompatibility</a> +<li><a href="#moby">Running hundreds of Postfix processes</a> + +<li><a href="#performance">Postfix performance</a> + +<li><a href="#receiving">Receiving mail via the network</a> + <li><a href="#relaying">Mail relaying</a> -<li><a href="#remote_delivery">Delivery to remote systems</a> +<li><a href="#remote_delivery">Remote delivery</a> -<li><a href="#local_delivery">Delivery to local (non-virtual) addresses</a> +<li><a href="#local_delivery">Local (non-virtual) delivery</a> <li><a href="#mailing_lists">Mailing lists</a> @@ -42,12 +52,34 @@ <li><a href="#other_transports">Other transports: UUCP, FAX, etc.</a> +<li><a href="#queue_maint">Postfix queue maintenance</a> + <li><a href="#compiling_installing">Compiling and installing Postfix</a> </ul> <p> +<a name="warnings"><h3>Postfix warnings and error messages</h3> + +<ul> + +<li><a href="#biff">What does "biff_notify: Connection refused" mean?</a> + +<li><a href="#nisdom">What does "NIS domain name not set - NIS lookups disabled" mean?</a> + +<li><a href="#dns-again">Mail stays queued with: Host not found, try again</a> + +<li><a href="#timeouts">Mail fails consistently with timeout or lost connection</a> + +<li><a href="#noalias">What does "fatal: open database /etc/aliases.db" mean?</a> + +<li><a href="#nosuid">sendmail has set-uid root file permissions, or is run from a set-uid root process</a> + +</ul> + +<p> + <a name="example_config"><h3>Example configurations</h3> <ul> @@ -66,6 +98,8 @@ </ul> +<p> + <a name="sendmail_incompatibility"><h3>Sendmail incompatibility</h3> <ul> @@ -87,7 +121,41 @@ distribution list</a> <li><a href="#majordomo-approve">Postfix breaks the majordomo "approve" command</a> -<li><a href="#worm">Postfix accepts MAIL FROM/RCPT TO "|command"</a> +<li><a href="#skip_greeting">Postfix does not try all the MX addresses</a> + +<li><a href="#worm">Postfix accepts MAIL FROM and RCPT TO "| command"</a> + +</ul> + +<a name="moby"><h3>Running hundreds of Postfix processes</h3> + +<ul> + +<li><a href="#moby-freebsd">Running hundreds of Postfix processes on FreeBSD</a> + +<li><a href="#moby-linux">Running hundreds of Postfix processes on Linux</a> + +</ul> + + +<a name="performance"><h3>Postfix performance</h3> + +<ul> + +<li><a href="#incoming">Mail stays queued in the incoming queue</a> + +<li><a href="#delay">Postfix responds slowly to incoming SMTP connections</a> + +</ul> + +<a name="receiving"><h3>Receiving mail via the network</h3> + +<ul> + +<li><a href="#delay">Postfix responds slowly to incoming SMTP connections</a> + +<li><a href="#numerical_log">Postfix logs SMTP clients as IP +addresses</a> </ul> @@ -99,27 +167,37 @@ distribution list</a> <li><a href="#mobile">Relaying mail for mobile users</a> -<li><a href="#virtual_setup">Postfix refuses mail for virtual +<li><a href="#virtual_relay">Postfix refuses mail for virtual domains with "relay access denied"</a> <li><a href="#relay_restrict">Restricting what users can send mail to off-site destinations</a> +<li><a href="#backup">Configuring Postfix as backup MX host</a> + </ul> -<a name="remote_delivery"><h3>Delivery to remote systems</h3> +<a name="remote_delivery"><h3>Remote delivery</h3> <ul> +<li><a href="#dns-again">Mail stays queued with: Host not found, try again</a> + <li><a href="#timeouts">Mail fails consistently with timeout or lost connection</a> +<li><a href="#skip_greeting">Postfix does not try all the MX addresses</a> + </ul> -<a name="local_delivery"><h3>Delivery to local (non-virtual) addresses</h3> +<a name="local_delivery"><h3>Local (non-virtual) delivery</h3> <ul> <li><a href="#root">Root's mail is delivered to nobody</a> +<li><a href="#biff">What does "biff_notify: Connection refused" mean?</a> + +<li><a href="#nisdom">What does "NIS domain name not set - NIS lookups disabled" mean?</a> + <li><a href="#bogus">Postfix accepts mail for non-existing local users</a> <li><a href="#some_local">Delivering some users locally while @@ -136,6 +214,10 @@ sending mail as user@domain</a> <li><a href="#metoo">Postfix sends mail to every member of a distribution list</a> +<li><a href="#owner-foo">Postfix ignores the owner-list alias</a> + +<li><a href="#noalias">What does "fatal: open database /etc/aliases.db" mean?</a> + </ul> <a name="mailing_lists"><h3>Mailing lists</h3> @@ -151,27 +233,26 @@ distribution list</a> <li><a href="#metoo">Postfix sends mail to every member of a distribution list</a> +<li><a href="#owner-foo">Postfix ignores the owner-list alias</a> + +<li><a href="#virtual_command">Commands and mailing lists don't work in Postfix virtual maps</a> + </ul> <a name="virtual_domains"><h3>Virtual domains</h3> <ul> -<li><a href="#virtual_setup">How to configure a Postfix virtual domain</a> - -<li><a href="#virtual_setup">Postfix does not refuse mail for -unknown virtual users</a> +<li><a href="#unknown_virtual_accept">Postfix does not refuse mail for +unknown users in virtual domains</a> -<li><a href="#virtual_setup">Mail for unknown virtual users fails -with "mail loops back to myself"</a> +<li><a href="#unknown_virtual_loop">Mail for unknown users in +virtual domains fails with "mail loops back to myself"</a> -<li><a href="#virtual_setup">Postfix refuses mail for virtual -domains with "user unknown"</a> - -<li><a href="#virtual_setup">Postfix refuses mail for virtual +<li><a href="#virtual_relay">Postfix refuses mail for virtual domains with "relay access denied"</a> -<li><a href="#command">Commands don't work in Postfix virtual maps</a> +<li><a href="#virtual_command">Commands and mailing lists don't work in Postfix virtual maps</a> <li><a href="#domain_mailbox">Receiving a virtual domain in a mailbox</a> @@ -206,6 +287,16 @@ mailbox</a> </ul> +<a name="queue_maint"><h3>Postfix queue maintenance</h3></a> + +<ul> + +<li><a href="#deleting">Deleting a message from the Postfix queue</a> + +<li><a href="#copying">Moving or restoring the Postfix queue</a> + +</ul> + <a name="compiling_installing"><h3>Compiling and installing Postfix</h3> <ul> @@ -214,16 +305,56 @@ mailbox</a> <li><a href="#dbm_dirfno">Undefined symbols: dbm_pagfno, dbm_dirfno etc.</a> -<li><a href="#db">Using DB libraries on Solaris etc.</a> +<li><a href="#db">Using third-party DB libraries</a> + +<li><a href="#sgistruct">IRIX problems translating IP address to string</a> + +</ul> + +<hr> + +<a name="poppers"><h3>POP or IMAP problems</h3> + +Postfix is a mail delivery system. Postfix does not implement +services such as POP or IMAP to read mail. Several POP/IMAP +implementations exist that can cooperate with software such as +Postfix. + +<p> + +Examples of software that is used successfully with Postfix: + +<p> + +<ul> + +<li><a href="http://asg.web.cmu.edu/cyrus/">Cyrus IMAP</a> implements +IMAP, POP3, and KPOP, later versions also support TLS. This software +implements its own private mail database system. Not for beginners. + +<p> + +<li><a href="http://www.inter7.com/courierimap/">Courier-Imap</a> +provides POP3, IMAP, POP3 and IMAP, and supports access over SSL. +This software supports the maildir-style mailbox format only +(one message per file, same format as qmail). + +<p> + +<li><a href="http://www.eudora.com/qpopper/">Qpopper</a> supports +POP3, TLS (SSL), and uses the traditional UNIX-style mailbox format +(multiple messages per file, each message starts with "From sender date..."). </ul> +<p> + <hr> <a name="stand_alone"><h3>Stand-alone machine</h3> Out of the box, Postfix should work without change on a stand-alone -machine that is has direct Internet access. At least, that is how +machine that has direct Internet access. At least, that is how Postfix installs when you download the Postfix source code. If you are on a firewalled intranet, or if your machine is dial-up connected only a small part of the time, see the respective sections. @@ -248,7 +379,7 @@ needs tweaking only if you have a very slow or a very fast net/machine. Workstation: <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: myorigin = $mydomain </pre> @@ -256,7 +387,7 @@ Workstation: Server: <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: myorigin = $mydomain mydestination = $myhostname, localhost.$mydomain, $mydomain </pre> @@ -273,7 +404,7 @@ workstation: Server: <pre> - <b>/etc/aliases</b>: + /etc/aliases: joe: joe@joes.workstation jane: jane@janes.workstation </pre> @@ -301,11 +432,11 @@ domain. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: myorigin = $mydomain relayhost = $mydomain - <b>/etc/postfix/master.cf</b>: + /etc/postfix/master.cf: Comment out the SMTP server entry Comment out the local delivery agent entry </pre> @@ -332,7 +463,7 @@ to let that mail gateway take care of forwarding. because it allows users to change machines without hassle. <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: myorigin = $mydomain </pre> @@ -344,7 +475,7 @@ for mail for the local machine: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: relayhost = $mydomain </pre> @@ -361,7 +492,7 @@ specify the intranet mail gateway host itself: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: relayhost = host.my.domain </pre> @@ -373,7 +504,7 @@ DNS lookups as well: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: disable_dns_lookups = yes </pre> @@ -392,13 +523,13 @@ href="transport.5.html">transport</a> table lookups. <p> <pre> - <b>/etc/postfix/transport</b>: + /etc/postfix/transport: my.domain smtp: .my.domain smtp: - thishost.my.domain local: <blink>!important!</blink> - localhost.my.domain local: <blink>!important!</blink> + thishost.my.domain local: !!!important!!! + localhost.my.domain local: !!!important!!! - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/transport </pre> @@ -409,8 +540,9 @@ else mail will bounce with a "mail loops to myself" condition. <p> -Specify <b>dbm:/etc/postfix/transport</b> if your system -uses <b>dbm</b> files instead of <b>db</b>. +Specify <b>dbm</b> instead of <b>hash</b> if your system uses +<b>dbm</b> files instead of <b>db</b>. To find out what map types +Postfix supports, use the command <b>postconf -m</b>. <p> @@ -435,40 +567,49 @@ execute the command <b>postconf mail_version</b>. <p> How to set up Postfix on the firewall machine so that it relays -mail for <i>my.domain</i> to a gateway machine on the inside, and -so that it refuses mail for <i>*.my.domain</i>? The problem is that -the standard <a href="uce.html#relay_domains">relay_domains</a> -mail relaying restriction allows mail to <i>*.my.domain</i> when -you specify <i>my.domain</i>. +mail for <i>domain.com</i> to a gateway machine on the inside, and +so that it refuses mail for <i>*.domain.com</i>? The problem is that +the default <a href="uce.html#relay_domains">relay_domains</a> +mail relaying restriction allows mail to <i>*.domain.com</i> when +you specify <i>domain.com</i>. <p> <ul> -<li>Specify a null <a href="uce.html#relay_domains">relay_domains</a> -parameter plus a <a href="transport.5.html">transport</a> table to -route mail for <i>my.domain</i> to the inside machine: +<li>Specify a <a href="transport.5.html">transport</a> table to +route mail for <i>domain.com</i> to the inside machine. + +<p> + +Specify explicit settings for <a +href="uce.html#smtpd_recipient_restrictions">smtpd_recipient_restrictions</a> +and for <a href="basic.html#mynetworks">mynetworks</a> that allow +local systems to send mail anywhere, and that allow remote systems +to send mail only to <i>user@domain.com</i>. <p> <pre> -<b>/etc/postfix/main.cf</b>: - mydestination = $myhostname, my.domain, localhost.my.domain - relay_domains = +/etc/postfix/main.cf: + myorigin = domain.com + mydestination = domain.com transport_maps = hash:/etc/postfix/transport + mynetworks = 12.34.56.0/24 + smtpd_recipient_restrictions = permit_mynetworks reject_unauth_destination -<b>/etc/postfix/transport</b>: - my.domain smtp:inside-gateway.my.domain (forwards user@domain) - .my.domain smtp:inside-gateway.my.domain (forwards user@firewall) +/etc/postfix/transport: + domain.com smtp:inside-gateway.domain.com (forwards user@domain) -<b>/etc/postfix/master.cf</b>: +/etc/postfix/master.cf: Comment out the local delivery agent </pre> <p> -Specify <b>dbm:/etc/postfix/transport</b> if your system uses <b>dbm</b> -files instead of <b>db</b>. +Specify <b>dbm</b> instead of <b>hash</b> if your system uses +<b>dbm</b> files instead of <b>db</b>. To find out what map types +Postfix supports, use the command <b>postconf -m</b>. <p> @@ -512,7 +653,7 @@ that is connected all the time. <p> <pre> - <b>/etc/postfix/main.cf:</b> + /etc/postfix/main.cf: relayhost = smtprelay.someprovider.com </pre> @@ -532,7 +673,7 @@ calls from being placed, disable spontaneous SMTP mail deliveries. <p> <pre> - <b>/etc/postfix/main.cf:</b> + /etc/postfix/main.cf: defer_transports = smtp (Only for systems that use on-demand dialup IP) </pre> @@ -551,7 +692,7 @@ To prevent these delays, disable all SMTP client DNS lookups. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: disable_dns_lookups = yes (Only for delivery across LANs that are disconnected most of the time) </pre> @@ -658,8 +799,8 @@ four hours, specify: <p> <pre> - <b>/etc/postfix/main.cf</b> - delay_warning_time = 4 + /etc/postfix/main.cf: + delay_warning_time = 4 </pre> <p> @@ -724,6 +865,321 @@ aliasing loops. <hr> +<a name="owner-foo"><h3>Postfix ignores the owner-list alias</h3></a> + +Normally, when a local alias <i>foo</i> has a companion alias +<i>owner-foo</i>, Postfix reports delivery errors to the owner +address rather than the message originator. + +<p> + +However, as a result of a Postfix implementation artefact, the +owner-foo alias takes effect only after the alias expansion is +completed. + +<p> + +Delivery problems that happen while expanding the alias, including +delivery to commands or files, are reported to the original sender +envelope address. + +<p> + +The reason is that bounces are sent by the Postfix queue manager, +which does not know that the sender address is being replaced. + +<p> + +This limitation will be fixed by changing how the Postfix local +delivery agent deals with undeliverable mail. + +<hr> + +<a name="noalias"><h3>What does "fatal: open database /etc/aliases.db" mean?</h3></a> + +Your aliases database is corrupt or it is missing. Execute the +following command as root: + +<p> + +<pre> + # newaliases +</pre> + +<hr> + +<a name="nosuid"><h1>sendmail has set-uid root file permissions, or is run from a +set-uid root process</h3></a> + +Traditionally, the UNIX <b>sendmail</b> command is installed with +set-uid root permissions. Even many MTAs other than Sendmail ship +with a set-uid root <b>sendmail</b> command. This is not the case +with Postfix. The Postfix <b>sendmail</b> command is designed not +to be set-uid. + +<p> + +Unfortunately, some Linux systems have a helpful utility called +<b>linuxconf</b> that automatically "fixes" file permissions to +what they are supposed to be for Sendmail's <b>sendmail</b> command. +Even when you reset the set-uid bit on the Postfix <b>sendmail</b> +executable file, <b>linuxconf</b> will happily turn it on again +for you. + +<p> + +On SuSE systems the file permission fixing utulity is called +<b>SuSEconfig</b>. Other Linux systems may use different names. +The usual disclaimers about mileages etc. apply. + +<p> + +<h4>Solutions</h4> + +<ul> + +<li>Rask Ingemann Lambertsen has a particularly effective +solution :-) + +<blockquote> +<pre> +# /etc/rc.d/init.d/linuxconf stop && rpm --erase linuxconf +</pre> +</blockquote> + +<li>According to Matthias Andree, the band-aid fix for SuSE is to +add to /etc/permissions.local the following line: + +<blockquote> +<pre> +/usr/sbin/sendmail root.root 755 +</pre> +</blockquote> + +and to make sure that in /etc/rc.config, +PERMISSIONS_SECURITY mentions local last, EXAMPLE: + +<blockquote> +<pre> +CHECK_PERMISSIONS=set +PERMISSION_SECURITY="secure local" +</pre> +</blockquote> + +</ul> + +<hr> + +<a name="moby-freebsd"><h3>Running hundreds of Postfix processes on FreeBSD</h3></a> + +With hundreds of Postfix processes, the kernel will eventually +run out of file handles; after that, it will run out of sockets. + +<p> + +To set kernel parameters at boot time, add the following lines to +the <b>/boot/loader.conf</b> file (this is specific to FreeBSD 4.x): + +<p> + +<blockquote> +<pre> +kern.ipc.maxsockets="5000" +kern.maxfiles="16384" +kern.maxfilesperproc="16384" +kern.ipc.nmbclusters="65536" +</pre> +</blockquote> + +<p> + +To set kernel parameters at run time execute the following commands +as root (this is specific to FreeBSD 4.x): + +<p> + +<blockquote> +<pre> +# sysctl -w kern.ipc.maxsockets=5000 +# sysctl -w kern.maxfiles=16384 +# sysctl -w kern.maxfilesperproc=16384 +# sysctl -w kern.ipc.nmbclusters=65536 +</pre> +</blockquote> + +<hr> + +<a name="moby-linux"><h3>Running hundreds of Postfix processes on Linux</h3></a> + +When you increase the number of Postfix processes into the hundreds, +the kernel will eventually run out of file handles; after that it +is likely to run out of process slots. + +<p> + +The following information is kernel version dependent. + +<p> + +To set parameters at boot time on Linux systems that have +<b>/etc/sysctl.conf</b>, add the following lines: + +<p> + +<blockquote> +<pre> +fs.file-max = 16384 +kernel.threads-max = 2048 +</pre> +</blockquote> + +<p> + +To set kernel parameters at run time, execute the following +commands as <b>root</b>: + +<p> + +<blockquote> +<pre> +# echo 16384 > /proc/sys/fs/file-max +# echo 2048 > /proc/sys/kernel/threads-max +</pre> +</blockquote> + +<hr> + +<a name="incoming"><h3>Mail stays queued in the incoming queue</h3></a> + +<blockquote> + +I have lots if mail in the incoming queue, but Postfix only runs +a few outbound SMTP deliveries. Why is it not running more SMTP +clients? + +</blockquote> + +<p> + +Your problem could be that the disk is saturated with I/O from +receiving mail, so that the Postfix queue manager gets insufficient +chance to process the requests (many SMTP server processes are +competing for disk access against one poor queue manager). + +<p> + +You solve the problem by getting faster disks. + +<p> + +I am still solving the scheduling problem from the software side, +but don't hold your breath. + +<p> + +Currently, the workaround is to configure multiple IP addresses +per machine, and to run one Postfix instance per IP address, each +instance preferably on a different disk. The Postfix instances +can't share queue directories, but sharing mailbox directories is +OK. + +<p> + +Just start each Postfix instance with a different configuration +directory: + +<p> + +<pre> + # postfix -c config_directory start +</pre> + +<p> + +Each main.cf file has a different <b>$myhostname</b> setting, +depending on the interface that it is supposed to handle. + +<p> + +<pre> + /my/own/main.cf: + queue_directory = /my/own/queue/directory + myhostname = foo1.my.domain + inet_interfaces = $myhostname +</pre> + +<hr> + +<a name="delay"><h3>Postfix responds slowly to incoming SMTP connections</h3></a> + +<dl> + +<dt>Question: + +<dd> My Postfix server is too slow. When I telnet to the SMTP port +(<tt>telnet hostname 25</tt>), the response comes after 40 seconds. +On the other hand, when I telnet to the the POP port (<tt>telnet +hostname 110</tt>) the response comes with no delay. + +<p> + +<dt>Answer: + +<dd> + +This is a DNS configuration problem. Postfix tries to resolve the +SMTP client IP address to a hostname. Apparently, your POP server +does not look up POP clients. + +<p> + +The fix is to properly configure the naming service. If you can't +have every host in the DNS, then configure the mail server to look +in /etc/hosts before the DNS, and specify the clients in /etc/hosts. + +</dl> + +<hr> + +<a name="numerical_log"><h3>Postfix logs SMTP clients as IP +addresses</h3> + +<blockquote> + +The Postfix SMTP server logs client connections with numerical IP +addresses instead of resolving the hostname. When I use <b>nslookup</b> +the address does resolve to a name. + +</blockquote> + +<p> + +You run the Postfix SMTP server inside a <b>chroot</b> jail for +extra security, but some configuration files are missing. In order +to run inside a chroot jail, the Postfix SMTP client and server +need copies of system configuration files inside the Postfix queue +directory. The exact list of files is very system dependent, but +you will probably need at the very least: + +<p> + +<pre> + /var/spool/postfix/etc/resolv.conf + /var/spool/postfix/etc/services +</pre> + +<p> + +Of course, these directories and files must be owned by root, but +they must be accessible by the postfix user, so directories need +mode 0755 and files need mode 0644. + +<p> +For more details, see the files in the <b>examples/chroot-setup</b> +directory of the Postfix source code distribution. + +<hr> + <a name="open_relay"><h3>Help! Postfix is an open relay</h3> According to some relay checking software, Postfix accepts @@ -745,6 +1201,8 @@ mail for arbitrary non-local destinations: <p> Don't Panic! Upgrade to a Postfix version of 19991227 or later. +To find out what Postfix version you have, execute the command +<b>postconf mail_version</b>. <p> @@ -830,12 +1288,12 @@ ahead of the other SMTPD recipient restrictions: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = - regexp:/etc/postfix/regexp_access - <i>...other restrictions...</i> + regexp:/etc/postfix/regexp_access + ...other restrictions... - <b>/etc/postfix/regexp_access</b>: + /etc/postfix/regexp_access: /[%!@].*[%!@]/ 550 Sender specified routing is not supported here. </pre> @@ -865,20 +1323,21 @@ authenticated protocol instead of plain old SMTP. The next best way is to use plain old SMTP and to authenticate the user first, for example, with a "please login via POP before using -SMTP" scheme. In that case, some non-Postfix software such as <a -href="http://www.mbnet.mb.ca/howto/dynamic.htm">DRAC</a> maintains -a Postfix-compatible access table with client IP address information: +SMTP" scheme. In that case, some software +maintains +a Postfix-compatible access table with client IP address information. +In order to make this work you need Postfix version 19991231 or later. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = permit_mynetworks check_client_access hash:/etc/postfix/client_access check_relay_domains - <b>/etc/postfix/client_access</b>: + /etc/postfix/client_access: 4.3.2.1 OK 5.4.3.2 987654321 </pre> @@ -886,7 +1345,15 @@ a Postfix-compatible access table with client IP address information: <p> Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. + +<p> + +N.B. Some non-Postfix software such as <a +href="http://mail.cc.umanitoba.ca/drac/">DRAC</a> uses <b>btree</b> +files instead of <b>hash</b> files. In that case, you will have +to adjust the above <b>check_client_access</b> restriction accordingly. <p> @@ -907,18 +1374,18 @@ spammer ever finds out the address of your users. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = permit_mynetworks check_client_access hash:/etc/postfix/client_access check_sender_access hash:/etc/postfix/sender_access check_relay_domains - <b>/etc/postfix/client_access</b>: + /etc/postfix/client_access: 11.22.33 OK dialup.isp.com OK - <b>/etc/postfix/sender_access</b>: + /etc/postfix/sender_access: joe@my.domain OK blow@my.domain OK </pre> @@ -947,7 +1414,7 @@ policy have their mail rejected by the SMTP server. Like this: <blockquote> <pre> -550 <user@remote>: Access denied +554 <user@remote>: Access denied </pre> </blockquote> @@ -969,31 +1436,32 @@ LDAP or SQL. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = - hash:/etc/postfix/restricted_senders + check_sender_access hash:/etc/postfix/restricted_senders ...other stuff... - restriction_classes = local_only + smtpd_restriction_classes = local_only local_only = check_recipient_access hash:/etc/postfix/local_domains, reject - <b>/etc/postfix/restricted_senders</b>: + /etc/postfix/restricted_senders: foo@domain local_only bar@domain local_only - <b>/etc/postfix/local_domains</b>: - this.domain OK (matches this.domain and subdomains) - that.domain OK (matches that.domain and subdomains) + /etc/postfix/local_domains: + this.domain OK <i>matches this.domain and subdomains</i> + that.domain OK <i>matches that.domain and subdomains</i> </pre> <p> Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. <p> -The <b>restriction_classes</b> verbiage exists so that Postfix can +The <b>smtpd_restriction_classes</b> verbiage exists so that Postfix can open <b>/etc/postfix/local_domains.db</b> before entering a chroot jail, so it is only an artefact of implementation. @@ -1018,6 +1486,92 @@ host. <hr> +<a name="backup"><h3>Configuring Postfix as backup MX host</h3></a> + +When you are <b>secondary mx</b> for a <b>remote site</b> this is +all you need: + +<p> + +<pre> + DNS: + the.backed-up.domain.name IN MX 100 your.machine.name + + /etc/postfix/main.cf: + relay_domains = $mydestination the.backed-up.domain.name + smtpd_recipient_restrictions = permit_mynetworks check_relay_domains +</pre> + +<p> + +When you are <b>primary mx</b> for a <b>remote site</b> you also +need: + +<p> + +<pre> + /etc/postfix/main.cf: + transport_maps = hash:/etc/postfix/transport + + /etc/postfix/transport: + the.backed-up.domain.name smtp:[their.mail.host.name] +</pre> + +<p> + +Specify <B>dbm</b> instead of <b>hash</b> if your system uses +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. + +<hr> + +<a name="dns-again"><h3>Mail stays queued with: Host not found, try again</h3></a> + +<blockquote> + +When I send mail to a remote address, the following happens: + +<p> + +<pre> + Jul 14 12:45:38 myhostname postfix/qmgr[2246]: 74FBF30501: + from=<sender@sender.domain> size=309 (queue active) + Jul 14 12:45:39 myhostname postfix/smtp[2349]: 74FBF30501: + to=<recip@recip.domain> relay=none, delay=3944, status=deferred (Name + service error for domain recip.domain: Host not found, try again) +</pre> + +<p> + +However, I can nslookup the hostname just fine. + +</blockquote> + +<p> + +There can be several different problems. + +<p> + +<ul> + +<li> First of all, the result of nslookup for the hostname may be +irrelevant. Postfix is required to look up the MX record first. So +your nslookup test should begin with asking for the MX record. Some +DNS servers are broken and produce no reply when asked for a +non-existent MX record. + +<p> <li> + +Check out your Postfix <b>master.cf</b> file. If the SMTP client +runs chrooted, then it needs a bunch of files inside the Postfix +queue directory. Examples are in the source distribution in the +<b>examples</b> subdirectory. + +</ul> + +<hr> + <a name="timeouts"><h3>Mail fails consistently with timeout or lost connection</h3></a> Every now and then, mail fails with "timed out while sending end @@ -1029,10 +1583,40 @@ by itself. <p> However, when you see mail deliveries fail consistently, you may -have a different problem: broken path MTU discovery. +have a different problem: broken path MTU discovery. Or it could +be a broken PIX firewall. + +<h4>Cisco PIX "fixup protocol smtp" bug</h4> + +The Cisco PIX firewall has a bug when running software older than +version 5.2(4) or 6.0(1). + +<p> + +The bug ID is CSCds90792. The "fixup protocol smtp" feature does +not correctly handle the case where the "." and the "CRLF" at the +end of mail are sent in separate packets. <p> +How does one recognize a mailer behind a Cisco PIX with "fixup +protocol smtp" enabled? As of version 5.1 and later, the fixup +protocol smtp command changes the characters in the SMTP banner to +asterisks except for the "2", "0" and "0 SPACE" characters. + +<p> + +When you connect to a mailer behind such a filter you see something +like: + +<blockquote> +<pre> +220 **************************************0******0*********20 ****200**0*********0*00 +</pre> +</blockquote> + +<h4>IP path MTU discovery</h4> + A little background is in order. With the SMTP protocol, the HELO, MAIL FROM and RCPT TO commands and responses are relatively short. When you're talking to sendmail, every command and every response @@ -1091,6 +1675,66 @@ and convince the person responsible for it to fix the configuration. <hr> +<a name="skip_greeting"><h3>Postfix does not try all the MX +addresses</h3> + +When delivering mail, Postfix tries all MX addresses in order of +preference, and stops at the first server that speaks SMTP. + +<p> + +If the first server that speaks SMTP rejects the connection by +greeting the client with a 5xx status code, which means "I will +never accept your mail", Postfix gives up and bounces the message +to the sender. + +<p> + +If the first server that speaks SMTP rejects the connection by +greeting the client with a 4xx status code, which means "come back +later", Postfix backs off and defers delivery until later. + +<p> + +Some people will argue that Postfix should contact the other MX +addresses even when the server greets with 4xx or 5xx, if only +because that is what Sendmail does, and of course we know that +everything Sendmail does is right. + +<p> + +Unfortunately, some people configure their infrastructure badly. +Their most preferred MX server is visible to the world but it +rejects connections from outside with a 5xx or 4xx greeting. Just +because Sendmail goes to the second-best MX server, these people +assume that every mailer will do so. + +<p> + +If such configurations are a problem for you, below are some controls +that work around them. + +<p> + +<pre> + /etc/postfix/main.cf: + smtp_skip_4xx_greeting = yes + smtp_skip_5xx_greeting = yes +</pre> + +<p> + +The <b>smtp_skip_5xx_greeting</b> is present in Postfix releases +later than 20000104. To find out what Postfix version you have, +use the command <b>postconf mail_version</b>. + +<p> + +Execute the command <b>postfix reload</b> to make the change +effective immediately. + +<hr> + <a name="root"> <h3>Root's mail is delivered to nobody</h3> If you use <a href="#procmail">procmail</a> (or some other command) @@ -1115,7 +1759,7 @@ real user. <p> <pre> -<b>/etc/aliases:</b> +/etc/aliases: root: you </pre> @@ -1134,11 +1778,76 @@ To find out the location for your system, execute the command <hr> +<a name="biff"><h3>What does "biff_notify: Connection refused" mean?</h3> + +By default, the Postfix local delivery agent attempts to notify +local users of the arrival of new mail. This feature makes use of +the <b>comsat</b> network service, which is turned off on many UNIX +systems for performance and/or security reasons. + +<p> + +The warning message means that new mail notificiation failed because +the <b>comsat</b> network service is turned off. + +<p> + +To disable the <b>comsat</b> client code in the Postfix delivery agent, +specify: + +<p> + +<pre> +/etc/postfix/main.cf: + biff = no +</pre> + +<p> + +To enable the <b>comsat</b> network service, uncomment the +corresponding entry in the <b>inetd.conf</b> file, and <b>kill -HUP</b> +the <b>inetd</b> process. + +<hr> + +<a name="nisdom"><h3>What does "NIS domain name not set - NIS lookups disabled" mean?</h3> + +<p> + +The warning message means that NIS (Network Information Service) +is not enabled on your machine. That is perfectly OK. It's just +hard for Postfix to find out about these things ahead of time. + +<p> + +To disable the <b>NIS</b> client code in the Postfix local delivery agent, +update the corresponding section in the <b>main.cf</b> file and specify +one of the following, depending on the type of aliases file: + +<p> + +<pre> +/etc/postfix/main.cf: + alias_maps = $alias_database +</pre> + +<p> + +This forces Postfix to use only the local aliases database, if one +is defined. + +<hr> + <a name="bogus"><h3>Postfix accepts mail for non-existing local users</h3> +See elsewhere for how to reject mail for <a +href="#unknown_virtual_accept">unknown users in virtual domains</a>. + +<p> + The information in this section applies to Postfix versions 19991216 -and later. See elsewhere for <a href="#virtual_setup">unknown -virtual</a> users. +and later. To find out what Postfix version you have, execute the +command <b>postconf mail_version</b>. <p> @@ -1153,28 +1862,32 @@ Of course mail for a non-existent local user will eventually bounce as undeliverable, but why accept such mail in the first place? You can tell the Postfix SMTP server how to find out if a user exists by listing all tables with local addresses in the <b>local_recipient_maps</b> -parameter: +parameter. + +<p> + +For example, if you use the default Postfix local delivery agent +in <b>/etc/postfix/master.cf</b>, specify: <p> <pre> - <b>/etc/postfix/main.cf</b>: - local_recipient_maps = $alias_maps, unix:passwd.byname + /etc/postfix/main.cf: + local_recipient_maps = $alias_maps, unix:passwd.byname </pre> <p> -The above should work on UNIX systems, provided that you use the -Postfix local delivery agent. However, if you run the Postfix SMTP -server chrooted, on some systems it will be necessary to have a -copy of the passwd file inside the chroot jail (typically: in -<b>/var/spool/postfix/etc</b>). +However, if you run the Postfix SMTP server chrooted, on some +systems it will be necessary to have a copy of the passwd file +inside the chroot jail (typically: in <b>/var/spool/postfix/etc</b>). +The only way to find out is to try. <p> -By default, the Postfix SMTP server does know about Postfix <a -href="virtual.5.html">virtual</a> maps, and will reject mail for -<i>unknown@virtual.domain</i> without further configuration. +By default, the Postfix SMTP server is aware of Postfix <a +href="virtual.5.html">virtual</a> maps, and will accept mail for +<i>known-user@virtual.domain</i> without further configuration. <hr> @@ -1189,7 +1902,7 @@ domain is to be appended to addresses that do not have a domain: <p> <pre> -<b>/etc/postfix/main.cf</b>: +/etc/postfix/main.cf: myorigin = domain.name </pre> @@ -1202,10 +1915,10 @@ destinations: <p> <pre> -<b>/etc/postfix/main.cf</b>: +/etc/postfix/main.cf: virtual_maps = hash:/etc/postfix/virtual -<b>/etc/postfix/virtual</b>: +/etc/postfix/virtual: root root@localhost postmaster postmaster@localhost </pre> @@ -1213,7 +1926,8 @@ destinations: <p> Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. <p> @@ -1239,7 +1953,7 @@ for example: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: home_mailbox = Maildir/ </pre> @@ -1273,10 +1987,10 @@ For example: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: mailbox_command = /path/to/procmail - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: mailbox_command = /path/to/procmail -a $EXTENSION </pre> @@ -1365,29 +2079,16 @@ expression-based filter at the SMTP port: <p> -<dl> - -<dt><b>/etc/postfix/main.cf:</b> - -<dl> - -<dt><tt>smtpd_recipient_restrictions = ... regexp:/etc/postfix/access_regexp ...</tt> - -<dt><tt>smtpd_recipient_restrictions = ... pcre:/etc/postfix/access_regexp ...</tt> - -</dl> - -<p> - -<dt><b>/etc/postfix/access_regexp:</b> - -<dl> - -<dt><tt>/^(.*)-outgoing@(.*)/ 554 Use $1@$2 instead</tt> - -</dl> +<pre> + /etc/postfix/main.cf: + smtpd_recipient_restrictions = + ... regexp:/etc/postfix/access_regexp ... + smtpd_recipient_restrictions = + ... pcre:/etc/postfix/access_regexp ... -</dl> + /etc/postfix/access_regexp: + /^(.*)-outgoing@(.*)/ 554 Use $1@$2 instead +</pre> <p> @@ -1432,11 +2133,10 @@ script to strip any header lines that match: <p> -<dl> - -<dd><b>/delivered-to/i</b> +<pre> + /delivered-to/i -</dl> +</pre> <p> @@ -1451,12 +2151,13 @@ header</a>". <hr> -<a name="worm"><h3>Postfix accepts MAIL FROM and RCPT TO "|command"</h3> +<a name="worm"><h3>Postfix accepts MAIL FROM and RCPT TO "| command"</h3> With Postfix, | or / has special meaning only when it appears in aliases, .forward files or in :include: files. It has no special meaning in mail addresses. + <p> If you must receive mail for systems with 10-year old vulnerabilities, @@ -1467,16 +2168,16 @@ harmful MAIL FROM or RCPT TO commands. <pre> /etc/postfix/main.cf: - smtpd_sender_restrictions = - regexp:/etc/postfix/envelope-regexp - reject_unknown_sender_domain - smtpd_recipient_restrictions = - regexp:/etc/postfix/envelope-regexp - permit_mynetworks - check_relay_domains + smtpd_sender_restrictions = + regexp:/etc/postfix/envelope-regexp + reject_unknown_sender_domain + smtpd_recipient_restrictions = + regexp:/etc/postfix/envelope-regexp + permit_mynetworks + check_relay_domains /etc/postfix/envelope-regexp: - /[/|]/ REJECT + /[/|]/ REJECT </pre> <p> @@ -1513,19 +2214,20 @@ to IP spoofing. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = hash:/etc/postfix/access ..the usual stuff... - <b>/etc/postfix/access</b>: + /etc/postfix/access: all permit_mynetworks,reject </pre> <p> Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. <p> @@ -1549,7 +2251,7 @@ therefore is subject to SMTP sender spoofing. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: smtpd_recipient_restrictions = hash:/etc/postfix/protected_destinations ..the usual stuff... @@ -1557,11 +2259,11 @@ therefore is subject to SMTP sender spoofing. smtpd_restriction_classes = insiders_only insiders_only = check_sender_access hash:/etc/postfix/insiders, reject - <b>/etc/postfix/protected_destinations</b>: + /etc/postfix/protected_destinations: all@my.domain insiders_only all@my.hostname insiders_only - <b>/etc/postfix/insiders</b>: + /etc/postfix/insiders: my.domain OK another.domain OK </pre> @@ -1584,67 +2286,38 @@ sense to make it moderated. <hr> -<a name="virtual_setup"><h3>How to configure a Postfix virtual domain</h3> - -Problem: +<a name="unknown_virtual_accept"><h3>Postfix does not refuse mail for +unknown users in virtual domains</h3></a> -<p> +<a name="unknown_virtual_loop"><h3>Mail for unknown users in a +virtual domain fails with "mail loops back to myself"</h3></a> -<ul> - -<li>Postfix does not refuse mail for unknown virtual users. - -<li>Mail for unknown virtual users fails with "mail loops back to -myself". +<a name="virtual_relay"><h3>Postfix refuses mail for virtual +domains with "relay access denied"</h3></a> -<li>Postfix refuses mail for virtual domains with "user unknown". - -<li>Postfix refuses mail for virtual domains with "relay access -denied". - -</ul> +Solution: specify a Postfix-style virtual domain or a Sendmail-style +virtual domain. <p> -Solution: +Be sure to follow instructions in the <a href="virtual.5.html"> +virtual</a> manual page. -<p> +<hr> -<ul> +<a name="virtual_command"><h3>Commands and mailing lists don't work +in Postfix virtual maps</h3> -<li> Add a magical entry to the Postfix virtual maps for -each Postfix virtual domain: +Short reply: specify a Sendmail-style <a href="virtual.5.html">virtual</a> +domain, and specify the command or mailing list in the local <a +href="aliases.5.html">aliases</a> file. <p> -<pre> - <b>/etc/postfix/virtual</b>: - virtual.domain whatever -</pre> +Long reply follows. <p> -<li> Do not list Postfix virtual domains in the <a -href="basic.html#mydestination">mydestination</a> parameter. - -<li> Do not list Postfix virtual maps in the <b>local_recipient_maps</b> -parameter. - -<li>As of Postfix version 19991226 it is no longer necessary to -specify virtual maps in the <a -href="uce.html#relay_domains">relay_domains</a> parameter. - -</ul> - -<p> - -For more information on how to set up virtual domains, see the <a -href="virtual.5.html">virtual</a> manual page. - -<hr> - -<a name="command"><h3>Commands don't work in Postfix virtual maps</h3> - Delivering mail to a command is a security-sensitive operation, because the command must be executed with the right privileges. Only <b>root</b>-privileged software such as the Postfix local @@ -1657,56 +2330,6 @@ privileges where possible. In particular, Postfix virtual mapping is done by an unprivileged daemon, so there is no secure way to execute commands found in virtual maps. -<p> - -Solution: specify a local alias instead. The Postfix local delivery -agent has sufficient privilege to execute commands with the right -privileges. - -<p> - -<ul> - -<li>Set up a local alias that executes the command: - -<p> - -<pre> - <b>/etc/aliases</b>: - name-virtual.domain "|/some/where/command..." -</pre> - -<p> - -<li>Execute the command <b>newaliases</b> whenever you edit the -alias database. - -<p> - -<li>Forward mail for the virtual address to the local alias: - -<p> - -<pre> - <b>/etc/postfix/virtual</b>: - virtual.domain whatever - name@virtual.domain name-virtual.domain -</pre> - -<p> - -<li>Execute the command <b>postmap /etc/postfix/virtual</b> whenever -you edit the virtual database. - -</ul> - -<p> - - -Note: on some systems the alias database is not in <b>/etc/aliases</b>. -To find out the location for your system, execute the command -<b>postconf alias_maps</b>. - <hr> <a name="domain_mailbox"><h3>Receiving a virtual domain in a mailbox</h3> @@ -1741,15 +2364,15 @@ headers is sufficient to reliably implement a domain in a mailbox. <p> <pre> - <b>/etc/postfix/main.cf</b> - recipient_delimiter = + - virtual_maps = - <i>...non-regexp virtual maps...</i> - regexp:/etc/postfix/virtual_regexp - - <b>/etc/postfix/virtual_regexp</b> - /^virtual\.domain$/ whatever - /^(.*\)@virtual\.domain$/ joe+$1 + /etc/postfix/main.cf: + recipient_delimiter = + + virtual_maps = + ...non-regexp virtual maps... + regexp:/etc/postfix/virtual_regexp + + /etc/postfix/virtual_regexp: + /^virtual\.domain$/ whatever + /^(.*)@virtual\.domain$/ joe+$1 </pre> <p> @@ -1793,7 +2416,7 @@ coming from <i>user@my.domain</i>, specify: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: masquerade_domains = $mydomain </pre> @@ -1820,7 +2443,7 @@ such as <b>root</b>, specify: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: masquerade_exceptions = root </pre> @@ -1832,7 +2455,7 @@ such as <b>root</b>, specify: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: masquerade_domains = somehost.my.domain otherhost.my.domain $mydomain </pre> @@ -1878,7 +2501,7 @@ Examples: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: mailbox_command = /some/program ... </pre> @@ -1893,7 +2516,7 @@ will not work as expected. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: mailbox_transport = foo </pre> @@ -1932,7 +2555,7 @@ be delivered via UUCP, for example, to a host named <i>uucp-host</i>: <p> <pre> - <b>/etc/postfix/transport</b>: + /etc/postfix/transport: some.domain uucp:uucp-host .some.domain uucp:uucp-host </pre> @@ -1954,21 +2577,22 @@ you change the <b>transport</b> file. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/transport </pre> <p> Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. <p> <li>Define a mail transport for delivery via UUCP: <pre> - <b>/etc/postfix/master.cf</b>: + /etc/postfix/master.cf: uucp unix - n n - - pipe flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) </pre> @@ -1988,7 +2612,7 @@ is willing to relay mail for. <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: relay_domains = some.domain $mydestination ... </pre> @@ -2026,7 +2650,7 @@ mail transport to your UUCP gateway host, say, <i>uucp-gateway</i>: <p> <pre> - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: relayhost = uucp-gateway default_transport = uucp </pre> @@ -2038,7 +2662,7 @@ mail transport to your UUCP gateway host, say, <i>uucp-gateway</i>: <p> <pre> - <b>/etc/postfix/master.cf</b>: + /etc/postfix/master.cf: uucp unix - n n - - pipe flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) </pre> @@ -2065,31 +2689,121 @@ changes effective. The following information is by Joerg Henne: <p> -Over here we are using the scheme <fax number>@fax.our.domain with Postfix and -HylaFax. Here's the setup used: +Over here we are using the scheme <fax number>@fax.our.domain +with Postfix and HylaFax. Here's the setup used: <p> <pre> - <b>/etc/postfix/master.cf</b>: - fax unix - n n - - pipe + /etc/postfix/master.cf: + fax unix - n n - 1 pipe flags= user=fax argv=/usr/bin/faxmail -d -n ${user} - <b>/etc/postfix/transport</b>: + /etc/postfix/transport: fax.your.domain fax:localhost - <b>/etc/postfix/main.cf</b>: + /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/transport + fax_destination_recipient_limit = 1 </pre> <p> +The process limit of 1 in the <b>master.cf</b> file is necessary +with fax software that cannot handle multiple requests at the same +time. It won't hurt otherwise. + +<p> + +The <b>fax_destination_recipient_limit</b> entry (by Simon, Mr. +Simix) is necessary with fax software that can't have more than +one destination on its command line. It won't hurt otherwise. + +<p> + Specify <B>dbm</b> instead of <b>hash</b> if your system uses -<b>dbm</b> files instead of <b>db</b> files. +<b>dbm</b> files instead of <b>db</b> files. To find out what map +types Postfix supports, use the command <b>postconf -m</b>. + +<p> + +Note: be sure to not advertise <b>fax.your.domain</b> in the DNS :-) + +<hr> + +<a name="deleting"><h3>Deleting a message from the Postfix queue</h3></a> + +To delete ONE message with queue id ABCDEF (e.g., from <b>mailq</b> +output) from the Postfix queue, it is not necessary to stop Postfix. + +<p> + +<pre> + # cd /var/spool/postfix + # find incoming active deferred -name ABCDEF -print | sed 1q | xargs rm +</pre> <p> -Note: be sure to not advertise <b>fax.your.domain</b> in the DNS... +The above command is safe because it deletes at most one file. +There is no risk of deleting newly arrived mail that happens to get +the same queue file name. + +<p> + +If you have to delete a large amount of mail, you must stop Postfix +first. + +<p> +<pre> + # postfix stop + # cd /var/spool/postfix + # find incoming active deferred defer -type f -print | + fgrep -xf /file/with/queue-ids | xargs rm + # postfix start +</pre> + +<p> + +Do not use the above <b>find</b> command on a running Postfix +system, because it can delete files that belong to new mail that +arrives while you are deleting queue files. + +<hr> + +<a name="copying"><h3>Moving or restoring the Postfix queue</h3></a> + +It is not safe to simply copy Postfix queue files from one file +system (or backup) to another file system. The reason for this is +that queue file names must be unique across the Postfix <b>incoming</b>, +<b>active</b> and <b>deferred</b> queue directories. If two queue +files have the same file (base) name, then one of the queue files +may be lost as files are moved from queue directory to queue +directory. + +<p> + +Postfix names a queue file after its inode number and after the +microsecond part of the time of day. Thus, if a queue file has a +name based on someone elses inode number there is a small chance +that the file name will collide with another queue file. + +<p> + +To avoid queue file name collisions when copying queue files, +restore queue files in the maildrop directory instead. + +<p> +<pre> + # postfix stop + ... restore queue files under the maildrop directory... + # postfix start +</pre> + +<p> + +When Postfix is started, it will pick up queue files from the +maildrop directory and will give them proper queue file names. <hr> @@ -2149,7 +2863,7 @@ Fix: get rid of the third-party ndbm.h include file. <hr> -<a name="db"><h3>Using DB libraries on Solaris etc.</h3> </a> +<a name="db"><h3>Using third-party DB libraries</h3> </a> The old <b>dbm</b> UNIX database has severe limitations when you try to store lots of information. It breaks when the number of hash @@ -2167,13 +2881,31 @@ href="http://www.sleepycat.com">www.sleepycat.com</a>. See the file <b>DB_README</b> in the Postfix source code distribution for instructions on how to build Postfix with Sleepycat's Berkeley DB. +<hr> + +<a name="sgistruct"> + +<h3>IRIX problems translating IP address to string</h3> + +<dl> + +<dt>Question: <dd> While installing IRIX 6.5.7m on a clean disk +and no special options or software I stumbled upon the following +problem; the inet_ntoa() function seems to return INADDR_NONE +(malformed request?) for every call to it. + <p> -One problem: older DB versions install a file -<b>/usr/local/include/ndbm.h</b> that is incompatible with -<b>/usr/include/ndbm.h</b>. Be sure to get rid of the bogus file. -See the FAQ entry titled "<a href="#dbm_dirfno">Undefined symbols: -dbm_pagfno, dbm_dirfno etc</a>". +<dt>Answer: <dd>There is an incompatibility between gcc and system +libraries compiled with SGI's cc. See a description in <a +href="http://freeware.sgi.com/shared/howto.html"> +http://freeware.sgi.com/shared/howto.html</a>. + +<p>If you must use gcc, a possible workaround is to use the +inet_ntoa() routine from the BIND source code at <a +href="http://www.isc.org/"> http://www.isc.org/</a>. + +</dl> <hr> diff --git a/gnu/dist/postfix/html/flush.8.html b/gnu/dist/postfix/html/flush.8.html new file mode 100644 index 00000000000..c9b6185883a --- /dev/null +++ b/gnu/dist/postfix/html/flush.8.html @@ -0,0 +1,200 @@ +<html> <head> </head> <body> <pre> + + + +FLUSH(8) FLUSH(8) + + +<b>NAME</b> + flush - Postfix fast flush server + +<b>SYNOPSIS</b> + <b>flush</b> [generic Postfix daemon options] + +<b>DESCRIPTION</b> + The flush server maintains a record of deferred mail by + destination. This information is used to improve the per- + formance of the SMTP <b>ETRN</b> request, and of its command-line + equivalent, <b>sendmail</b> <b>-qR</b>. This program expects to be run + from the <a href="master.8.html"><b>master</b>(8)</a> process manager. + + The record is implemented as a per-destination logfile + with as contents the queue IDs of deferred mail. A logfile + is append-only, and is truncated when delivery is + requested for the corresponding destination. A destination + is the part on the right-hand side of the right-most <b>@</b> in + an email address. + + Per-destination logfiles of deferred mail are maintained + only for eligible destinations. The list of eligible des- + tinations is specified with the <b>fast</b><i>_</i><b>flush</b><i>_</i><b>domains</b> config- + uration parameter, which defaults to <b>$relay</b><i>_</i><b>domains</b>. + + This server implements the following requests: + + <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>ADD</b> <i>sitename</i> <i>queue_id</i> + Inform the fast flush server that the specified + message is queued for <i>sitename</i>. Depending on log- + ging policy, the fast flush server stores or + ignores the information. + + <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>SEND</b> <i>sitename</i> + Request delivery of mail that is queued for <i>site-</i> + <i>name</i>. If the destination is eligible for a fast + flush logfile, this request triggers delivery of + messages listed in that destination's logfile, and + the logfile is truncated to zero length; if mail is + undeliverable it will be added back to the logfile. + + If the destination is not eligible for a fast flush + logfile, this request triggers delivery of all + queued mail. + + <b>TRIGGER</b><i>_</i><b>REQ</b><i>_</i><b>WAKEUP</b> + This wakeup request from the master is an alterna- + tive way to request <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>REFRESH</b>. + + <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>REFRESH</b> (completes in the background) + Refresh non-empty per-destination logfiles that + were not read in <b>fast</b><i>_</i><b>flush</b><i>_</i><b>refresh</b><i>_</i><b>time</b> hours, by + simulating send requests (see above) for the corre- + sponding destinations. + + + + 1 + + + + + +FLUSH(8) FLUSH(8) + + + Delete empty per-destination logfiles that were not + updated in <b>fast</b><i>_</i><b>flush</b><i>_</i><b>purge</b><i>_</i><b>time</b> days. + + <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>PURGE</b> (completes in the background) + Refresh all non-empty per-destination logfiles, by + simulating send requests (see above) for the corre- + sponding destinations. This can be incredibly + expensive when logging is enabled for many destina- + tions, and is not recommended. + + Delete empty per-destination logfiles that were not + updated in <b>fast</b><i>_</i><b>flush</b><i>_</i><b>purge</b><i>_</i><b>time</b> days. + + The server response is one of: + + <b>FLUSH</b><i>_</i><b>STAT</b><i>_</i><b>OK</b> + The request completed normally. + + <b>FLUSH</b><i>_</i><b>STAT</b><i>_</i><b>BAD</b> + The flush server rejected the request (bad request + name, bad request parameter value). + + <b>FLUSH</b><i>_</i><b>STAT</b><i>_</i><b>FAIL</b> + The request failed. + +<b>SECURITY</b> + The fast flush 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> + Problems and transactions are logged to <b>syslogd</b>(8). + +<b>BUGS</b> + Fast flush logfiles are truncated only after a + <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>SEND</b> request, not when mail is actually deliv- + ered, and therefore can accumulate outdated or redundant + data. In order to maintain sanity, <b>FLUSH</b><i>_</i><b>REQ</b><i>_</i><b>REFRESH</b> must + be executed periodically. This can be automated with a + suitable wakeup timer setting in the <b>master.cf</b> configura- + tion file. + + Upon receipt of a request to deliver all mail for an eli- + gible destination, the <b>flush</b> server requests delivery of + all messages that are listed in that destination's log- + file, regardless of the recipients of those messages. This + is not an issue for mail that is sent to a <b>relay</b><i>_</i><b>domains</b> + destination because such mail typically only has recipi- + ents in one domain. + +<b>FILES</b> + /var/spool/postfix/flush, location of "fast flush" logfiles. + + + + + 2 + + + + + +FLUSH(8) FLUSH(8) + + +<b>CONFIGURATION</b> <b>PARAMETERS</b> + See the Postfix <b>main.cf</b> file for syntax details and for + default values. Use the <b>postfix</b> <b>reload</b> command after a + configuration change. + + <b>fast</b><i>_</i><b>flush</b><i>_</i><b>domains</b> + What destinations can have a "fast flush" logfile. + By default, this is set to <b>$relay</b><i>_</i><b>domains</b>. + + <b>fast</b><i>_</i><b>flush</b><i>_</i><b>refresh</b><i>_</i><b>time</b> + Refresh a non-empty "fast flush" logfile that was + not read in this amount of time (default time unit: + hours), by simulating a send request for the corre- + sponding destination. + + <b>fast</b><i>_</i><b>flush</b><i>_</i><b>purge</b><i>_</i><b>time</b> + Remove an empty "fast flush" logfile that was not + updated in this amount of time (default time unit: + days). + +<b>SEE</b> <b>ALSO</b> + <a href="smtpd.8.html">smtpd(8)</a> Postfix SMTP server + <a href="qmgr.8.html">qmgr(8)</a> Postfix queue manager + syslogd(8) system logging + +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. + +<b>AUTHOR(S)</b> + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA + + + + + + + + + + + + + + + + + + + + + + + + 3 + + +</pre> </body> </html> diff --git a/gnu/dist/postfix/html/index.html b/gnu/dist/postfix/html/index.html index 5cacb4f3792..32b4627ae33 100644 --- a/gnu/dist/postfix/html/index.html +++ b/gnu/dist/postfix/html/index.html @@ -29,17 +29,15 @@ First of all, thank you for your interest in the Postfix project. <p> What is Postfix? It is <a href="http://www.porcupine.org/wietse/">Wietse -Venema's</a> attempt to provide an alternative to the widely-used -<a href="http://www.sendmail.org/">Sendmail</a> program. Sendmail -is responsible for most of the e-mail delivered on the Internet. -With an estimated 100 million users, that's billions of messages -daily. A stunning number. +Venema's</a> mailer that started life as an alternative to the +widely-used <a href="http://www.sendmail.org/">Sendmail</a> program. <p> Postfix attempts to be fast, easy to administer, and secure, while at the same time being sendmail compatible enough to not upset -existing users. +existing users. Thus, the outside has a sendmail-ish flavor, but +the inside is completely different. <hr> diff --git a/gnu/dist/postfix/html/lmtp.8.html b/gnu/dist/postfix/html/lmtp.8.html new file mode 100644 index 00000000000..653d5d8e40c --- /dev/null +++ b/gnu/dist/postfix/html/lmtp.8.html @@ -0,0 +1,332 @@ +<html> <head> </head> <body> <pre> + + + +LMTP(8) LMTP(8) + + +<b>NAME</b> + lmtp - Postfix local delivery via LMTP + +<b>SYNOPSIS</b> + <b>lmtp</b> [generic Postfix daemon options] + +<b>DESCRIPTION</b> + The LMTP client processes message delivery requests from + the queue manager. Each request specifies a queue file, a + sender address, a domain or host to deliver to, and recip- + ient information. This program expects to be run from the + <a href="master.8.html"><b>master</b>(8)</a> process manager. + + The LMTP client updates the queue file and marks recipi- + ents as finished, or it informs the queue manager that + delivery should be tried again at a later time. Delivery + problem reports are sent to the <a href="bounce.8.html"><b>bounce</b>(8)</a> or <a href="defer.8.html"><b>defer</b>(8)</a> dae- + mon as appropriate. + + The LMTP client connects to the destination specified in + the message delivery request. The destination, usually + specified in the Postfix <a href="transport.5.html"><b>transport</b>(5)</a> table, has the form: + + <b>unix</b>:<i>pathname</i> + Connect to the local UNIX-domain server that is + bound to the specified <i>pathname</i>. If the process + runs chrooted, an absolute pathname is interpreted + relative to the changed root directory. + + <b>inet</b>:<i>host</i>, <b>inet:</b><i>host</i>:<i>port</i> (symbolic host) + + <b>inet</b>:[<i>addr</i>], <b>inet</b>:[<i>addr</i>]:<i>port</i> (numeric host) + Connect to the specified IPV4 TCP port on the spec- + ified local or remote host. If no port is speci- + fied, connect to the port defined as <b>lmtp</b> in <b>ser-</b> + <b>vices</b>(4). If no such service is found, the + <b>lmtp</b><i>_</i><b>tcp</b><i>_</i><b>port</b> configuration parameter (default + value of 24) will be used. + + The LMTP client does not perform MX (mail + exchanger) lookups since those are defined only for + mail delivery via SMTP. + + If neither <b>unix:</b> nor <b>inet:</b> are specified, <b>inet:</b> is + assumed. + +<b>SECURITY</b> + The LMTP client is moderately security-sensitive. It talks + to LMTP servers and to DNS servers on the network. The + LMTP client can be run chrooted at fixed low privilege. + +<b>STANDARDS</b> + <a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a> (SMTP protocol) + <a href="http://www.faqs.org/rfcs/rfc1651.html">RFC 1651</a> (SMTP service extensions) + + + + 1 + + + + + +LMTP(8) LMTP(8) + + + <a href="http://www.faqs.org/rfcs/rfc1870.html">RFC 1870</a> (Message Size Declaration) + <a href="http://www.faqs.org/rfcs/rfc2033.html">RFC 2033</a> (LMTP protocol) + <a href="http://www.faqs.org/rfcs/rfc2197.html">RFC 2197</a> (Pipelining) + <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> (AUTH command) + +<b>DIAGNOSTICS</b> + Problems and transactions are logged to <b>syslogd</b>(8). Cor- + rupted message files are marked so that the queue manager + can move them to the <b>corrupt</b> queue for further inspection. + + Depending on the setting of the <b>notify</b><i>_</i><b>classes</b> parameter, + the postmaster is notified of bounces, protocol problems, + and of other trouble. + +<b>BUGS</b> +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> + command after a configuration change. + +<b>Miscellaneous</b> + <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> + Verbose logging level increment for hosts that + match a pattern in the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> parameter. + + <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> + List of domain or network patterns. When a remote + host matches a pattern, increase the verbose log- + ging level by the amount specified in the + <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> parameter. + + <b>error</b><i>_</i><b>notice</b><i>_</i><b>recipient</b> + Recipient of protocol/policy/resource/software + error notices. + + <b>notify</b><i>_</i><b>classes</b> + When this parameter includes the <b>protocol</b> class, + send mail to the postmaster with transcripts of + LMTP sessions with protocol errors. + + <b>lmtp</b><i>_</i><b>skip</b><i>_</i><b>quit</b><i>_</i><b>response</b> + Do not wait for the server response after sending + QUIT. + + <b>lmtp</b><i>_</i><b>tcp</b><i>_</i><b>port</b> + The TCP port to be used when connecting to a LMTP + server. Used as backup if the <b>lmtp</b> service is not + found in <b>services</b>(4). + +<b>Authentication</b> <b>controls</b> + <b>lmtp</b><i>_</i><b>enable</b><i>_</i><b>sasl</b><i>_</i><b>auth</b> + Enable per-session authentication as per <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> + (SASL). By default, Postfix is built without SASL + + + + 2 + + + + + +LMTP(8) LMTP(8) + + + support. + + <b>lmtp</b><i>_</i><b>sasl</b><i>_</i><b>password</b><i>_</i><b>maps</b> + Lookup tables with per-host or domain <i>name</i>:<i>password</i> + entries. No entry for a host means no attempt to + authenticate. + + <b>lmtp</b><i>_</i><b>sasl</b><i>_</i><b>security</b><i>_</i><b>options</b> + Zero or more of the following. + + <b>noplaintext</b> + Disallow authentication methods that use + plaintext passwords. + + <b>noactive</b> + Disallow authentication methods that are + vulnerable to non-dictionary active attacks. + + <b>nodictionary</b> + Disallow authentication methods that are + vulnerable to passive dictionary attack. + + <b>noanonymous</b> + Disallow anonymous logins. + +<b>Resource</b> <b>controls</b> + <b>lmtp</b><i>_</i><b>cache</b><i>_</i><b>connection</b> + Should we cache the connection to the LMTP server? + The effectiveness of cached connections will be + determined by the number of LMTP servers in use, + and the concurrency limit specified for the LMTP + client. Cached connections are closed under any of + the following conditions: + + <b>o</b> The LMTP client idle time limit is reached. + This limit is specified with the Postfix + <b>max</b><i>_</i><b>idle</b> configuration parameter. + + <b>o</b> A delivery request specifies a different + destination than the one currently cached. + + <b>o</b> The per-process limit on the number of + delivery requests is reached. This limit is + specified with the Postfix <b>max</b><i>_</i><b>use</b> configu- + ration parameter. + + <b>o</b> Upon the onset of another delivery request, + the LMTP server associated with the current + session does not respond to the <b>RSET</b> com- + mand. + + <i>transport_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> + Limit the number of parallel deliveries to the same + destination via this mail delivery transport. + + + + 3 + + + + + +LMTP(8) LMTP(8) + + + <i>transport</i> is the name of the service as specified + in the <b>master.cf</b> file. The default limit is taken + from the <b>default</b><i>_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> + parameter. + + <i>transport_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> + Limit the number of recipients per message delivery + via this mail delivery transport. <i>transport</i> is the + name of the service as specified in the <b>master.cf</b> + file. The default limit is taken from the + <b>default</b><i>_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> parameter. + + This parameter becomes significant if the LMTP + client is used for local delivery. Some LMTP + servers can optimize delivery of the same message + to multiple recipients. The default limit for local + mail delivery is 1. + + Setting this parameter to 0 will lead to an + unbounded number of recipients per delivery. How- + ever, this could be risky since it may make the + machine vulnerable to running out of resources if + messages are encountered with an inordinate number + of recipients. Exercise care when setting this + parameter. + +<b>Timeout</b> <b>controls</b> + The default time unit is seconds; an explicit time unit + can be specified by appending a one-letter suffix to the + value: s (seconds), m (minutes), h (hours), d (days) or w + (weeks). + + <b>lmtp</b><i>_</i><b>connect</b><i>_</i><b>timeout</b> + Timeout for opening a connection to the LMTP + server. If no connection can be made within the + deadline, the message is deferred. + + <b>lmtp</b><i>_</i><b>lhlo</b><i>_</i><b>timeout</b> + Timeout for sending the <b>LHLO</b> command, and for + receiving the server response. + + <b>lmtp</b><i>_</i><b>mail</b><i>_</i><b>timeout</b> + Timeout for sending the <b>MAIL</b> <b>FROM</b> command, and for + receiving the server response. + + <b>lmtp</b><i>_</i><b>rcpt</b><i>_</i><b>timeout</b> + Timeout for sending the <b>RCPT</b> <b>TO</b> command, and for + receiving the server response. + + <b>lmtp</b><i>_</i><b>data</b><i>_</i><b>init</b><i>_</i><b>timeout</b> + Timeout for sending the <b>DATA</b> command, and for + receiving the server response. + + + + + + 4 + + + + + +LMTP(8) LMTP(8) + + + <b>lmtp</b><i>_</i><b>data</b><i>_</i><b>xfer</b><i>_</i><b>timeout</b> + Timeout for sending the message content. + + <b>lmtp</b><i>_</i><b>data</b><i>_</i><b>done</b><i>_</i><b>timeout</b> + Timeout for sending the "<b>.</b>" command, and for + receiving the server response. When no response is + received, a warning is logged that the mail may be + delivered multiple times. + + <b>lmtp</b><i>_</i><b>rset</b><i>_</i><b>timeout</b> + Timeout for sending the <b>RSET</b> command, and for + receiving the server response. + + <b>lmtp</b><i>_</i><b>quit</b><i>_</i><b>timeout</b> + Timeout for sending the <b>QUIT</b> command, and for + receiving the server response. + +<b>SEE</b> <b>ALSO</b> + <a href="bounce.8.html">bounce(8)</a> non-delivery status reports + <a href="local.8.html">local(8)</a> local mail delivery + <a href="master.8.html">master(8)</a> process manager + <a href="qmgr.8.html">qmgr(8)</a> queue manager + services(4) Internet services and aliases + <a href="spawn.8.html">spawn(8)</a> auxiliary command spawner + syslogd(8) system logging + +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. + +<b>AUTHOR(S)</b> + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA + + Alterations for LMTP by: + Philip A. Prindeville + Mirapoint, Inc. + USA. + + Additional work on LMTP by: + Amos Gouaux + University of Texas at Dallas + P.O. Box 830688, MC34 + Richardson, TX 75083, USA + + + + + + + + + + + + 5 + + +</pre> </body> </html> diff --git a/gnu/dist/postfix/html/local.8.html b/gnu/dist/postfix/html/local.8.html index 26e48689e59..e909eaa2848 100644 --- a/gnu/dist/postfix/html/local.8.html +++ b/gnu/dist/postfix/html/local.8.html @@ -16,8 +16,8 @@ LOCAL(8) LOCAL(8) Postfix queue manager to deliver mail to local recipients. Each delivery request specifies a queue file, a sender address, a domain or host to deliver to, and one or more - recipients. This program expects to be run from the <a href="master.8.html"><b>mas-</b> - <b>ter</b>(8)</a> process manager. + recipients. This program expects to be run from the <a href="master.8.html"><b>mas-</b></a> + <a href="master.8.html"><b>ter</b>(8)</a> process manager. The <b>local</b> daemon updates queue files and marks recipients as finished, or it informs the queue manager that delivery @@ -216,7 +216,7 @@ LOCAL(8) LOCAL(8) lope header to each message, prepends an optional <b>Deliv-</b> <b>ered-To:</b> header with the recipient envelope address, prepends a <b>Return-Path:</b> header with the sender envelope - address, and appends an empty line. + address, and appends no empty line. <b>EXTERNAL</b> <b>FILE</b> <b>DELIVERY</b> The <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>files</b> configuration parameter restricts @@ -252,7 +252,7 @@ LOCAL(8) LOCAL(8) <b>ward</b>+<i>foo</i> or in ~<i>name</i>/.<b>forward</b>, to the mailbox owned by the user <i>name</i>, or it is sent back as undeliverable. - In all cases the <b>local</b> daemon prepends an opional `<b>Deliv-</b> + In all cases the <b>local</b> daemon prepends an optional `<b>Deliv-</b> <b>ered-To:</b> <i>name</i>+<i>foo</i>' header line. <b>DELIVERY</b> <b>RIGHTS</b> @@ -277,7 +277,7 @@ LOCAL(8) LOCAL(8) the <b>default</b><i>_</i><b>privs</b> configuration parameter. <b>STANDARDS</b> - RFC 822 (ARPA Internet Text Messages) + <a href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> (ARPA Internet Text Messages) <b>DIAGNOSTICS</b> Problems and transactions are logged to <b>syslogd</b>(8). Cor- @@ -309,20 +309,20 @@ LOCAL(8) LOCAL(8) <b>alias</b><i>_</i><b>maps</b> List of alias databases. + <b>biff</b> Enable or disable notification of new mail via the + <b>comsat</b> network service. + <b>expand</b><i>_</i><b>owner</b><i>_</i><b>alias</b> When delivering to an alias that has an owner- com- - panion alias, set the envelope sender address to - the right-hand side of the owner alias, instead + panion alias, set the envelope sender address to + the right-hand side of the owner alias, instead using of the left-hand side address. - <b>forward</b><i>_</i><b>path</b> - Search list for .forward files. The names are sub- - ject to <i>$name</i> expansion. + <b>export</b><i>_</i><b>environment</b> + List of names of environment parameters that can be + exported to non-Postfix processes. + - <b>local</b><i>_</i><b>command</b><i>_</i><b>shell</b> - Shell to use for external command execution (for - example, /some/where/smrsh -c). When a shell is - specified, it is invoked even when the command @@ -335,7 +335,15 @@ LOCAL(8) LOCAL(8) LOCAL(8) LOCAL(8) - contains no shell built-in commands or meta charac- + <b>forward</b><i>_</i><b>path</b> + Search list for .forward files. The names are sub- + ject to <i>$name</i> expansion. + + <b>local</b><i>_</i><b>command</b><i>_</i><b>shell</b> + Shell to use for external command execution (for + example, /some/where/smrsh -c). When a shell is + specified, it is invoked even when the command con- + tains no shell built-in commands or meta charac- ters. <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> @@ -352,6 +360,11 @@ LOCAL(8) LOCAL(8) <b>recipient</b><i>_</i><b>delimiter</b> Separator between username and address extension. + <b>require</b><i>_</i><b>home</b><i>_</i><b>directory</b> + Require that a recipient's home directory is acces- + sible by the recipient before attempting delivery. + Defer delivery otherwise. + <b>Mailbox</b> <b>delivery</b> <b>fallback</b><i>_</i><b>transport</b> Message transport for recipients that are not found @@ -376,6 +389,18 @@ LOCAL(8) LOCAL(8) External command to use for mailbox delivery. The command executes with the recipient privileges (exception: root). The string is subject to $name + + + + 6 + + + + + +LOCAL(8) LOCAL(8) + + expansions. <b>mailbox</b><i>_</i><b>transport</b> @@ -390,17 +415,6 @@ LOCAL(8) LOCAL(8) Limit the number of attempts to acquire an exclu- sive lock on a mailbox or external file. - - - 6 - - - - - -LOCAL(8) LOCAL(8) - - <b>deliver</b><i>_</i><b>lock</b><i>_</i><b>delay</b> Time in seconds between successive attempts to acquire an exclusive lock. @@ -408,70 +422,81 @@ LOCAL(8) LOCAL(8) <b>stale</b><i>_</i><b>lock</b><i>_</i><b>time</b> Limit the time after which a stale lock is removed. + <b>mailbox</b><i>_</i><b>delivery</b><i>_</i><b>lock</b> + What file locking method(s) to use when delivering + to a UNIX-style mailbox. The default setting is + system dependent. For a list of available file + locking methods, use the <b>postconf</b> <b>-l</b> command. + <b>Resource</b> <b>controls</b> <b>command</b><i>_</i><b>time</b><i>_</i><b>limit</b> - Limit the amount of time for delivery to external + Limit the amount of time for delivery to external command. <b>duplicate</b><i>_</i><b>filter</b><i>_</i><b>limit</b> - Limit the size of the duplicate filter for results + Limit the size of the duplicate filter for results from alias etc. expansion. <b>line</b><i>_</i><b>length</b><i>_</i><b>limit</b> - Limit the amount of memory used for processing a + Limit the amount of memory used for processing a partial input line. <b>local</b><i>_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> Limit the number of parallel deliveries to the same - user. The default limit is taken from the + user. The default limit is taken from the <b>default</b><i>_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> parameter. <b>local</b><i>_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> - Limit the number of recipients per message deliv- - ery. The default limit is taken from the + Limit the number of recipients per message deliv- + ery. The default limit is taken from the <b>default</b><i>_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> parameter. -<b>Security</b> <b>controls</b> - <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>commands</b> - Restrict the usage of mail delivery to external - command. - - <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>files</b> - Restrict the usage of mail delivery to external - file. + <b>mailbox</b><i>_</i><b>size</b><i>_</i><b>limit</b> + Limit the size of a mailbox etc. file (any file + that is written to upon delivery). Set to zero to + disable the limit. - <b>command</b><i>_</i><b>expansion</b><i>_</i><b>filter</b> - What characters are allowed to appear in $name - expansions of mailbox_command. Illegal characters - are replaced by underscores. - <b>default</b><i>_</i><b>privs</b> - Default rights for delivery to external file or - command. - <b>forward</b><i>_</i><b>expansion</b><i>_</i><b>filter</b> - What characters are allowed to appear in $name - expansions of forward_path. Illegal characters are - replaced by underscores. + 7 - 7 +LOCAL(8) LOCAL(8) +<b>Security</b> <b>controls</b> + <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>commands</b> + Restrict the usage of mail delivery to external + command. Specify zero or more of: <b>alias</b>, <b>forward</b>, + <b>include</b>. + <b>allow</b><i>_</i><b>mail</b><i>_</i><b>to</b><i>_</i><b>files</b> + Restrict the usage of mail delivery to external + file. Specify zero or more of: <b>alias</b>, <b>forward</b>, + <b>include</b>. + <b>command</b><i>_</i><b>expansion</b><i>_</i><b>filter</b> + What characters are allowed to appear in $name + expansions of mailbox_command. Illegal characters + are replaced by underscores. -LOCAL(8) LOCAL(8) + <b>default</b><i>_</i><b>privs</b> + Default rights for delivery to external file or + command. + <b>forward</b><i>_</i><b>expansion</b><i>_</i><b>filter</b> + What characters are allowed to appear in $name + expansions of forward_path. Illegal characters are + replaced by underscores. <b>HISTORY</b> - The <b>Delivered-To:</b> header appears in the <b>qmail</b> system by + The <b>Delivered-To:</b> header appears in the <b>qmail</b> system by Daniel Bernstein. - The <i>maildir</i> structure appears in the <b>qmail</b> system by + The <i>maildir</i> structure appears in the <b>qmail</b> system by Daniel Bernstein. <b>SEE</b> <b>ALSO</b> @@ -482,7 +507,7 @@ LOCAL(8) LOCAL(8) <a href="qmgr.8.html">qmgr(8)</a> queue manager <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -499,31 +524,6 @@ LOCAL(8) LOCAL(8) - - - - - - - - - - - - - - - - - - - - - - - - - 8 diff --git a/gnu/dist/postfix/html/master.8.html b/gnu/dist/postfix/html/master.8.html index 723dad55c75..b1784ea0059 100644 --- a/gnu/dist/postfix/html/master.8.html +++ b/gnu/dist/postfix/html/master.8.html @@ -34,16 +34,17 @@ MASTER(8) MASTER(8) <b>-c</b> <i>config_dir</i> Read the <b>main.cf</b> and <b>master.cf</b> configuration files - in the named directory. + in the named directory instead of the default con- + figuration directory. - <b>-D</b> After initialization, run a debugger on the master - process. The debugging command is specified with + <b>-D</b> After initialization, run a debugger on the master + process. The debugging command is specified with the <b>debugger</b><i>_</i><b>command</b> in the <b>main.cf</b> global configu- ration file. - <b>-t</b> Test mode. Return a zero exit status when the <b>mas-</b> - <b>ter.pid</b> lock file does not exist or when that file - is not locked. This is evidence that the <b>master</b> + <b>-t</b> Test mode. Return a zero exit status when the <b>mas-</b> + <b>ter.pid</b> lock file does not exist or when that file + is not locked. This is evidence that the <b>master</b> daemon is not running. <b>-v</b> Enable verbose logging for debugging purposes. This @@ -52,13 +53,12 @@ MASTER(8) MASTER(8) Signals: - <b>SIGHUP</b> Upon receipt of a <b>HUP</b> signal (e.g., after <b>postfix</b> + <b>SIGHUP</b> Upon receipt of a <b>HUP</b> signal (e.g., after <b>postfix</b> <b>reload</b>), the master process re-reads its configura- - tion files. If a service has been removed from the - <b>master.cf</b> file, its running processes are termi- - nated immediately. Otherwise, running processes - are allowed to terminate as soon as is convenient, - so that changes in configuration settings affect + tion files. If a service has been removed from the + <b>master.cf</b> file, its running processes are termi- + nated immediately. Otherwise, running processes + are allowed to terminate as soon as is convenient, @@ -71,14 +71,15 @@ MASTER(8) MASTER(8) MASTER(8) MASTER(8) + so that changes in configuration settings affect only new service requests. <b>SIGTERM</b> - Upon receipt of a <b>TERM</b> signal (e.g., after <b>postfix</b> - <b>abort</b>), the master process passes the signal on to + Upon receipt of a <b>TERM</b> signal (e.g., after <b>postfix</b> + <b>abort</b>), the master process passes the signal on to its child processes and terminates. This is useful - for an emergency shutdown. Normally one would ter- - minate only the master (<b>postfix</b> <b>stop</b>) and allow + for an emergency shutdown. Normally one would ter- + minate only the master (<b>postfix</b> <b>stop</b>) and allow running processes to finish what they are doing. <b>DIAGNOSTICS</b> @@ -88,21 +89,28 @@ MASTER(8) MASTER(8) <b>ENVIRONMENT</b> <b>MAIL</b><i>_</i><b>DEBUG</b> After initialization, start a debugger as specified - with the <b>debugger</b><i>_</i><b>command</b> configuration parameter + with the <b>debugger</b><i>_</i><b>command</b> configuration parameter in the <b>main.cf</b> configuration file. <b>MAIL</b><i>_</i><b>CONFIG</b> Directory with Postfix configuration files. <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. <b>Miscellaneous</b> + <b>import</b><i>_</i><b>environment</b> + + <b>export</b><i>_</i><b>environment</b> + Lists of names of environment parameters that can + be imported from (exported to) non-Postfix pro- + cesses. + <b>mail</b><i>_</i><b>owner</b> - The owner of the mail queue and of most Postfix + The owner of the mail queue and of most Postfix processes. <b>command</b><i>_</i><b>directory</b> @@ -112,18 +120,10 @@ MASTER(8) MASTER(8) Directory with Postfix daemon programs. <b>queue</b><i>_</i><b>directory</b> - Top-level directory of the Postfix queue. This is + Top-level directory of the Postfix queue. This is also the root directory of Postfix daemons that run chrooted. -<b>Resource</b> <b>controls</b> - <b>default</b><i>_</i><b>process</b><i>_</i><b>limit</b> - Default limit for the number of simultaneous child - processes that provide a given service. - - <b>max</b><i>_</i><b>idle</b> - Limit the time in seconds that a child process - waits between service requests. @@ -137,12 +137,21 @@ MASTER(8) MASTER(8) MASTER(8) MASTER(8) +<b>Resource</b> <b>controls</b> + <b>default</b><i>_</i><b>process</b><i>_</i><b>limit</b> + Default limit for the number of simultaneous child + processes that provide a given service. + + <b>max</b><i>_</i><b>idle</b> + Limit the time in seconds that a child process + waits between service requests. + <b>max</b><i>_</i><b>use</b> - Limit the number of service requests handled by a + Limit the number of service requests handled by a child process. <b>service</b><i>_</i><b>throttle</b><i>_</i><b>time</b> - Time to avoid forking a server that appears to be + Time to avoid forking a server that appears to be broken. <b>FILES</b> @@ -156,7 +165,7 @@ MASTER(8) MASTER(8) syslogd(8) system logging <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -185,15 +194,6 @@ MASTER(8) MASTER(8) - - - - - - - - - 3 diff --git a/gnu/dist/postfix/html/motivation.html b/gnu/dist/postfix/html/motivation.html index f27c9569adb..972da06b713 100644 --- a/gnu/dist/postfix/html/motivation.html +++ b/gnu/dist/postfix/html/motivation.html @@ -44,8 +44,9 @@ program will go through its life as Postfix instead. <p> Postfix is a direct competitor to the <a href="http://www.qmail.org"> -qmail </a> by Dan Bernstein. That's competitor, not enemy. I'm sure -that friendly competition will help to improve both programs. +qmail </a> software by Dan Bernstein. That's competitor, not enemy. +I'm sure that friendly competition will help to improve both +programs. <hr> diff --git a/gnu/dist/postfix/html/pcre_table.5.html b/gnu/dist/postfix/html/pcre_table.5.html new file mode 100644 index 00000000000..d27e0bb449f --- /dev/null +++ b/gnu/dist/postfix/html/pcre_table.5.html @@ -0,0 +1,134 @@ +<html> <head> </head> <body> <pre> + + + +PCRE_TABLE(5) PCRE_TABLE(5) + + +<b>NAME</b> + pcre_table - format of Postfix PCRE tables + +<b>SYNOPSIS</b> + pcre:/etc/postfix/filename + +<b>DESCRIPTION</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. Alternatively, lookup tables can be speci- + fied in Perl Compatible Regular Expression form. + + To find out what types of lookup tables your Postfix sys- + tem supports use the <b>postconf</b> <b>-m</b> command. + + The general form of a PCRE table is: + + blanks and comments + Blank lines are ignored, as are lines beginning + with `#'. + + leading whitespace + Lines that begin with whitespace continue the pre- + vious line. + + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches a search string, use the cor- + responding <i>result</i>. A line that starts with white + space continues the preceding line. + + Each pattern is a perl-like regular expression. The + expression delimiter can be any character, except whites- + pace or characters that have special meaning (tradition- + ally the forward slash is used). The regular expression + can contain whitespace. + + By default, matching is case-insensitive, although follow- + ing the second slash with an `i' flag will reverse this. + Other flags are supported, but the only other useful one + is `U', which makes matching ungreedy (see PCRE documenta- + tion and source for more info). + + Each pattern is applied to the entire string being looked + up. Depending on the application, that string is an + entire client hostname, an entire client IP address, or an + entire mail address. Thus, no parent domain or parent + network search is done, and <i>user@domain</i> mail addresses are + not broken 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>. + + Patterns are applied in the order as specified in the + table, until a pattern is found that matches the search + string. + + + + + 1 + + + + + +PCRE_TABLE(5) PCRE_TABLE(5) + + + Substitution of sub-strings from the matched expression is + possible using the conventional perl syntax ($1, $2, + etc.). The macros in the replacement string may need to be + written as ${n} or $(n) if they aren't followed by whites- + pace. + +<b>EXAMPLES</b> + # Protect your outgoing majordomo exploders + /^(?!owner-)(.*)-outgoing@(my.domain)$/ 550 Use ${1}@${2} instead + + # Bounce friend@whatever, except when whatever is our domain (you would + # be better just bouncing all friend@ mail - this is just an example). + /^friend@(?!my.domain).*$/ 550 Stick this in your pipe $0 + + # A multi-line entry. The text is sent as one line. + # + /^noddy@connect.com.au$/ + 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>SEE</b> <b>ALSO</b> + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables + +<b>AUTHOR(S)</b> + The PCRE table lookup code was originally written by: + Andrew McNamara + andrewm@connect.com.au + connect.com.au Pty. Ltd. + Level 3, 213 Miller St + North Sydney, NSW, Australia + + Adopted and adapted by: + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA + + + + + + + + + + + + + + + + + + + + + + 2 + + +</pre> </body> </html> diff --git a/gnu/dist/postfix/html/pickup.8.html b/gnu/dist/postfix/html/pickup.8.html index bf92b71f82e..b70e54e765a 100644 --- a/gnu/dist/postfix/html/pickup.8.html +++ b/gnu/dist/postfix/html/pickup.8.html @@ -47,19 +47,19 @@ PICKUP(8) PICKUP(8) details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. +<b>Content</b> <b>inspection</b> <b>controls</b> + <b>content</b><i>_</i><b>filter</b> + The name of a mail delivery transport that filters + mail and that either bounces mail or re-injects the + result back into Postfix. This parameter uses the + same syntax as the right-hand side of a Postfix + transport table. + <b>Miscellaneous</b> <b>always</b><i>_</i><b>bcc</b> Address to send a copy of each message that enters the system. - <b>mail</b><i>_</i><b>owner</b> - The process privileges used while not opening a - <b>maildrop</b> file. - - <b>queue</b><i>_</i><b>directory</b> - Top-level directory of the Postfix queue. - - 1 @@ -71,6 +71,13 @@ PICKUP(8) PICKUP(8) PICKUP(8) PICKUP(8) + <b>mail</b><i>_</i><b>owner</b> + The process privileges used while not opening a + <b>maildrop</b> file. + + <b>queue</b><i>_</i><b>directory</b> + Top-level directory of the Postfix queue. + <b>SEE</b> <b>ALSO</b> <a href="cleanup.8.html">cleanup(8)</a> message canonicalization <a href="master.8.html">master(8)</a> process manager @@ -121,13 +128,6 @@ PICKUP(8) PICKUP(8) - - - - - - - 2 diff --git a/gnu/dist/postfix/html/pipe.8.html b/gnu/dist/postfix/html/pipe.8.html index eb63c2a48e5..207286715c5 100644 --- a/gnu/dist/postfix/html/pipe.8.html +++ b/gnu/dist/postfix/html/pipe.8.html @@ -30,23 +30,26 @@ PIPE(8) PIPE(8) file at the end of a service definition. The syntax is as follows: - <b>flags=FR.</b>> (optional) + <b>flags=BFR.</b>> (optional) Optional message processing flags. By default, a message is copied unchanged. - <b>F</b> Prepend a "<b>From</b> <i>sender</i> <i>time_stamp</i>" envelope - header to the message content. This is - expected by, for example, <b>UUCP</b> software. The - <b>F</b> flag also causes an empty line to be - appended to the message. + <b>B</b> Append a blank line at the end of each mes- + sage. This is required by some mail user + agents that recognize "<b>From</b> " lines only + when preceded by a blank line. - <b>R</b> Prepend a <b>Return-Path:</b> message header with + <b>F</b> Prepend a "<b>From</b> <i>sender</i> <i>time_stamp</i>" envelope + header to the message content. This is + expected by, for example, <b>UUCP</b> software. + + <b>R</b> Prepend a <b>Return-Path:</b> message header with the envelope sender address. - <b>.</b> Prepend <b>.</b> to lines starting with "<b>.</b>". This + <b>.</b> Prepend <b>.</b> to lines starting with "<b>.</b>". This is needed by, for example, <b>BSMTP</b> software. - > Prepend > to lines starting with "<b>From</b> ". + > Prepend > to lines starting with "<b>From</b> ". This is expected by, for example, <b>UUCP</b> soft- ware. @@ -54,11 +57,8 @@ PIPE(8) PIPE(8) <b>user</b>=<i>username</i>:<i>groupname</i> The external command is executed with the rights of - the specified <i>username</i>. The software refuses to - execute commands with root privileges, or with the - privileges of the mail system owner. If <i>groupname</i> - is specified, the corresponding group ID is used - instead of the group ID of of <i>username</i>. + the specified <i>username</i>. The software refuses to + execute commands with root privileges, or with the @@ -71,33 +71,47 @@ PIPE(8) PIPE(8) PIPE(8) PIPE(8) + privileges of the mail system owner. If <i>groupname</i> + is specified, the corresponding group ID is used + instead of the group ID of <i>username</i>. + + <b>eol=string</b> (default: <b>\n</b>) + The output record delimiter. Typically one would + use either <b>\r\n</b> or <b>\n</b>. The usual C-style backslash + escape sequences are recognized: <b>\a</b> <b>\b</b> <b>\f</b> <b>\n</b> <b>\r</b> <b>\t</b> + <b>\v</b> <b>\</b><i>octal</i> and <b>\\</b>. + + <b>size</b>=<i>size_limit</i> (optional) + Messages greater in size than this limit (in bytes) + will be bounced back to the sender. + <b>argv</b>=<i>command</i>... (required) - The command to be executed. This must be specified + The command to be executed. This must be specified as the last command attribute. The command is exe- cuted directly, i.e. without interpretation of - shell meta characters by a shell command inter- + shell meta characters by a shell command inter- preter. In the command argument vector, the following macros are recognized and replaced with correspond- - ing information from the Postfix queue manager + ing information from the Postfix queue manager delivery request: <b>${extension</b>} - This macro expands to the extension part of - a recipient address. For example, with an + This macro expands to the extension part of + a recipient address. For example, with an address <i>user+foo@domain</i> the extension is - <i>foo</i>. A command-line argument that contains - <b>${extension</b>} expands into as many command- + <i>foo</i>. A command-line argument that contains + <b>${extension</b>} expands into as many command- line arguments as there are recipients. <b>${mailbox</b>} - This macro expands to the complete local - part of a recipient address. For example, - with an address <i>user+foo@domain</i> the mailbox - is <i>user+foo</i>. A command-line argument that - contains <b>${mailbox</b>} expands into as many - command-line arguments as there are recipi- + This macro expands to the complete local + part of a recipient address. For example, + with an address <i>user+foo@domain</i> the mailbox + is <i>user+foo</i>. A command-line argument that + contains <b>${mailbox</b>} expands into as many + command-line arguments as there are recipi- ents. <b>${nexthop</b>} @@ -105,59 +119,68 @@ PIPE(8) PIPE(8) <b>${recipient</b>} This macro expands to the complete recipient - address. A command-line argument that con- + address. A command-line argument that con- tains <b>${recipient</b>} expands into as many com- mand-line arguments as there are recipients. <b>${sender</b>} - This macro expands to the envelope sender - address. + This macro expands to the envelope sender - <b>${user</b>} - This macro expands to the username part of a - recipient address. For example, with an - address <i>user+foo@domain</i> the username part is - <i>user</i>. A command-line argument that contains - <b>${user</b>} expands into as many command-line - arguments as there are recipients. - In addition to the form ${<i>name</i>}, the forms $<i>name</i> and - $(<i>name</i>) are also recognized. Specify <b>$$</b> where a single <b>$</b> - is wanted. + 2 - 2 +PIPE(8) PIPE(8) + address. -PIPE(8) PIPE(8) + <b>${size</b>} + This macro expands to Postfix's idea of the + message size, which is an approximation of + the size of the message as delivered. + + <b>${user</b>} + This macro expands to the username part of a + recipient address. For example, with an + address <i>user+foo@domain</i> the username part is + <i>user</i>. A command-line argument that contains + <b>${user</b>} expands into as many command-line + arguments as there are recipients. + In addition to the form ${<i>name</i>}, the forms $<i>name</i> and + $(<i>name</i>) are also recognized. Specify <b>$$</b> where a single <b>$</b> + is wanted. <b>DIAGNOSTICS</b> - Command exit status codes are expected to follow the con- + Command exit status codes are expected to follow the con- ventions defined in <<b>sysexits.h</b>>. - Problems and transactions are logged to <b>syslogd</b>(8). Cor- - rupted message files are marked so that the queue manager + Problems and transactions are logged to <b>syslogd</b>(8). Cor- + rupted message files are marked so that the queue manager can move them to the <b>corrupt</b> queue for further inspection. <b>SECURITY</b> - This program needs a dual personality 1) to access the - private Postfix queue and IPC mechanisms, and 2) to exe- + This program needs a dual personality 1) to access the + private Postfix queue and IPC mechanisms, and 2) to exe- cute external commands as the specified user. It is there- fore security sensitive. <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. <b>Miscellaneous</b> + <b>export</b><i>_</i><b>environment</b> + List of names of environment parameters that can be + exported to non-Postfix processes. + <b>mail</b><i>_</i><b>owner</b> The process privileges used while not running an external command. @@ -168,6 +191,18 @@ PIPE(8) PIPE(8) <i>transport_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> Limit the number of parallel deliveries to the same + + + + 3 + + + + + +PIPE(8) PIPE(8) + + destination, for delivery via the named <i>transport</i>. The default limit is taken from the <b>default</b><i>_</i><b>desti-</b> <b>nation</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> parameter. The limit is @@ -191,18 +226,6 @@ PIPE(8) PIPE(8) <a href="bounce.8.html">bounce(8)</a> non-delivery status reports <a href="master.8.html">master(8)</a> process manager <a href="qmgr.8.html">qmgr(8)</a> queue manager - - - - 3 - - - - - -PIPE(8) PIPE(8) - - syslogd(8) system logging <b>LICENSE</b> @@ -237,29 +260,6 @@ PIPE(8) PIPE(8) - - - - - - - - - - - - - - - - - - - - - - - 4 diff --git a/gnu/dist/postfix/html/postalias.1.html b/gnu/dist/postfix/html/postalias.1.html index 4d95379f7e0..4d6e097bb92 100644 --- a/gnu/dist/postfix/html/postalias.1.html +++ b/gnu/dist/postfix/html/postalias.1.html @@ -9,7 +9,7 @@ POSTALIAS(1) POSTALIAS(1) postalias - Postfix alias database maintenance <b>SYNOPSIS</b> - <b>postalias</b> [<b>-Ninvw</b>] [<b>-c</b> <i>config_dir</i>] [<b>-q</b> <i>key</i>] + <b>postalias</b> [<b>-Ninrvw</b>] [<b>-c</b> <i>config_dir</i>] [<b>-d</b> <i>key</i>] [<b>-q</b> <i>key</i>] [<i>file_type</i>:]<i>file_name</i> ... <b>DESCRIPTION</b> @@ -33,32 +33,32 @@ POSTALIAS(1) POSTALIAS(1) <b>-c</b> <i>config_dir</i> Read the <b>main.cf</b> configuration file in the named + directory instead of the default configuration directory. - <b>-i</b> Incremental mode. Read entries from standard input + <b>-d</b> <i>key</i> Search the specified maps for <i>key</i> and remove one + entry per map. The exit status is non-zero if the + requested information was not found. + + <b>-i</b> Incremental mode. Read entries from standard input and do not truncate an existing database. By - default, <b>postalias</b> creates a new database from the + default, <b>postalias</b> creates a new database from the entries in <b>file</b><i>_</i><b>name</b>. - <b>-n</b> Don't include the terminating null character that - terminates lookup keys and values. By default, - Postfix does whatever is the default for the host + <b>-n</b> Don't include the terminating null character that + terminates lookup keys and values. By default, + Postfix does whatever is the default for the host operating system. - <b>-q</b> <i>key</i> Search the specified maps for <i>key</i> and print the - first value found on the standard output stream. + <b>-q</b> <i>key</i> Search the specified maps for <i>key</i> and print the + first value found on the standard output stream. The exit status is non-zero if the requested infor- mation was not found. - <b>-v</b> Enable verbose logging for debugging purposes. Mul- - tiple <b>-v</b> options make the software increasingly - verbose. - - <b>-w</b> Do not warn about duplicate entries; silently - ignore them. - - Arguments: + <b>-r</b> When updating a table, do not warn about duplicate + entries; silently replace them. + <b>-v</b> Enable verbose logging for debugging purposes. @@ -71,6 +71,14 @@ POSTALIAS(1) POSTALIAS(1) POSTALIAS(1) POSTALIAS(1) + Multiple <b>-v</b> options make the software increasingly + verbose. + + <b>-w</b> When updating a table, do not warn about duplicate + entries; silently ignore them. + + Arguments: + <i>file_type</i> The type of database to be produced. @@ -101,6 +109,14 @@ POSTALIAS(1) POSTALIAS(1) put means no problems were detected. Duplicate entries are skipped and are flagged with a warning. + <b>postalias</b> terminates with zero exit status in case of suc- + cess (including successful <b>postmap</b> <b>-q</b> lookup) and termi- + nates with non-zero exit status in case of failure. + +<b>BUGS</b> + The "delete key" support is limited to one delete opera- + tion per command invocation. + <b>ENVIRONMENT</b> <b>MAIL</b><i>_</i><b>CONFIG</b> Directory with Postfix configuration files. @@ -108,37 +124,37 @@ POSTALIAS(1) POSTALIAS(1) <b>MAIL</b><i>_</i><b>VERBOSE</b> Enable verbose logging for debugging purposes. -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax - details and for default values. - <b>database</b><i>_</i><b>type</b> - Default alias database type. On many UNIX systems, - the default type is either <b>dbm</b> or <b>hash</b>. -<b>STANDARDS</b> - RFC 822 (ARPA Internet Text Messages) -<b>SEE</b> <b>ALSO</b> - <a href="aliases.5.html">aliases(5)</a> format of alias database input file. - <a href="sendmail.1.html">sendmail(1)</a> mail posting and compatibility interface. + 2 - 2 +POSTALIAS(1) POSTALIAS(1) +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. + <b>database</b><i>_</i><b>type</b> + Default alias database type. On many UNIX systems, + the default type is either <b>dbm</b> or <b>hash</b>. -POSTALIAS(1) POSTALIAS(1) +<b>STANDARDS</b> + <a href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> (ARPA Internet Text Messages) +<b>SEE</b> <b>ALSO</b> + <a href="aliases.5.html">aliases(5)</a> format of alias database input file. + <a href="sendmail.1.html">sendmail(1)</a> mail posting and compatibility interface. <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -178,22 +194,6 @@ POSTALIAS(1) POSTALIAS(1) - - - - - - - - - - - - - - - - 3 diff --git a/gnu/dist/postfix/html/postconf.1.html b/gnu/dist/postfix/html/postconf.1.html index 1455eec3844..1e8e55cb908 100644 --- a/gnu/dist/postfix/html/postconf.1.html +++ b/gnu/dist/postfix/html/postconf.1.html @@ -9,7 +9,7 @@ POSTCONF(1) POSTCONF(1) postconf - Postfix configuration utility <b>SYNOPSIS</b> - <b>postconf</b> [<b>-dhmnv</b>] [<b>-c</b> <i>config_dir</i>] [<i>parameter</i> <i>...</i>] + <b>postconf</b> [<b>-dhmlnv</b>] [<b>-c</b> <i>config_dir</i>] [<i>parameter</i> <i>...</i>] <b>postconf</b> [<b>-ev</b>] [<b>-c</b> <i>config_dir</i>] [<i>parameter=value</i> <i>...</i>] @@ -23,20 +23,24 @@ POSTCONF(1) POSTCONF(1) <b>-c</b> <i>config_dir</i> The <b>main.cf</b> configuration file is in the named + directory instead of the default configuration directory. - <b>-d</b> Print default parameter settings instead of actual + <b>-d</b> Print default parameter settings instead of actual settings. - <b>-e</b> Edit the <b>main.cf</b> configuration file. The file is + <b>-e</b> Edit the <b>main.cf</b> configuration file. The file is copied to a temporary file then renamed into place. - Parameters and values are specified on the command - line. Use quotes in order to protect shell + Parameters and values are specified on the command + line. Use quotes in order to protect shell metacharacters and whitespace. - <b>-h</b> Show parameter values only, not the ``name = '' + <b>-h</b> Show parameter values only, not the ``name = '' label that normally precedes the value. + <b>-l</b> List the names of all supported mailbox locking + methods. + <b>-m</b> List the names of all supported lookup table types. <b>-n</b> Print non-default parameter settings only. @@ -55,6 +59,18 @@ POSTCONF(1) POSTCONF(1) <b>AUTHOR(S)</b> Wietse Venema IBM T.J. Watson Research + + + + 1 + + + + + +POSTCONF(1) POSTCONF(1) + + P.O. Box 704 Yorktown Heights, NY 10598, USA @@ -62,7 +78,57 @@ POSTCONF(1) POSTCONF(1) - 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 2 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/postdrop.1.html b/gnu/dist/postfix/html/postdrop.1.html index a994ce37b67..372b037a392 100644 --- a/gnu/dist/postfix/html/postdrop.1.html +++ b/gnu/dist/postfix/html/postdrop.1.html @@ -19,8 +19,8 @@ POSTDROP(1) POSTDROP(1) and with group write permission to the <b>maildrop</b> queue directory. - The <b>postdrop</b> command is automatically invoked by the <a href="sendmail.1.html"><b>send-</b> - <b>mail</b>(1)</a> mail posting agent when the <b>maildrop</b> queue direc- + The <b>postdrop</b> command is automatically invoked by the <a href="sendmail.1.html"><b>send-</b></a> + <a href="sendmail.1.html"><b>mail</b>(1)</a> mail posting agent when the <b>maildrop</b> queue direc- tory is not world-writable. Options: @@ -53,12 +53,12 @@ POSTDROP(1) POSTDROP(1) default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. - <b>queue</b><i>_</i><b>directory</b> - Top-level directory of the Postfix queue. This is - also the root directory of Postfix daemons that run - chrooted. - + <b>import</b><i>_</i><b>environment</b> + List of names of environment parameters that can be + imported from non-Postfix processes. + <b>queue</b><i>_</i><b>directory</b> + Top-level directory of the Postfix queue. This is @@ -71,12 +71,15 @@ POSTDROP(1) POSTDROP(1) POSTDROP(1) POSTDROP(1) + also the root directory of Postfix daemons that run + chrooted. + <b>SEE</b> <b>ALSO</b> <a href="sendmail.1.html">sendmail(1)</a> compatibility interface syslogd(8) system logging <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -125,9 +128,6 @@ POSTDROP(1) POSTDROP(1) - - - 2 diff --git a/gnu/dist/postfix/html/postfix.1.html b/gnu/dist/postfix/html/postfix.1.html index 6b4a3578a6c..8db5ad60250 100644 --- a/gnu/dist/postfix/html/postfix.1.html +++ b/gnu/dist/postfix/html/postfix.1.html @@ -50,15 +50,15 @@ POSTFIX(1) POSTFIX(1) The following options are implemented: <b>-c</b> <i>config_dir</i> - The absolute path to a directory with Postfix con- - figuration files. Use this to distinguish between - multiple Postfix instances on the same host. + Read the <b>main.cf</b> and <b>master.cf</b> configuration files + in the named directory instead of the default con- + figuration directory. Use this to distinguish + between multiple Postfix instances on the same + host. <b>-D</b> (with <b>postfix</b> <b>start</b> only) Run each Postfix daemon under control of a debugger as specified via the <b>debugger</b><i>_</i><b>command</b> configuration - parameter. - @@ -71,6 +71,8 @@ POSTFIX(1) POSTFIX(1) POSTFIX(1) POSTFIX(1) + parameter. + <b>-v</b> Enable verbose logging for debugging purposes. Mul- tiple <b>-v</b> options make the software increasingly verbose. @@ -126,8 +128,6 @@ POSTFIX(1) POSTFIX(1) - - 2 diff --git a/gnu/dist/postfix/html/postkick.1.html b/gnu/dist/postfix/html/postkick.1.html index 639eea0a096..0a5a5a3a9a8 100644 --- a/gnu/dist/postfix/html/postkick.1.html +++ b/gnu/dist/postfix/html/postkick.1.html @@ -20,25 +20,26 @@ POSTKICK(1) POSTKICK(1) Options: <b>-c</b> <i>config_dir</i> - Read configuration information from <b>main.cf</b> in the - named configuration directory. + Read the <b>main.cf</b> configuration file in the named + directory instead of the default configuration + directory. <b>-v</b> Enable verbose logging for debugging purposes. Mul- - tiple <b>-v</b> options make the software increasingly + tiple <b>-v</b> options make the software increasingly verbose. Arguments: - <i>class</i> Name of a class of local transport channel end- - points, either <b>public</b> (accessible by any local + <i>class</i> Name of a class of local transport channel end- + points, either <b>public</b> (accessible by any local user) or <b>private</b> (administrative access only). <i>service</i> - The name of a local transport endpoint within the + The name of a local transport endpoint within the named class. <i>request</i> - A string. The list of valid requests is service- + A string. The list of valid requests is service- specific. <b>DIAGNOSTICS</b> @@ -53,12 +54,11 @@ POSTKICK(1) POSTKICK(1) Enable verbose logging for debugging purposes. <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax details and for default values. - <b>queue</b><i>_</i><b>directory</b> - Location of the Postfix queue, and of the local IPC + @@ -71,6 +71,8 @@ POSTKICK(1) POSTKICK(1) POSTKICK(1) POSTKICK(1) + <b>queue</b><i>_</i><b>directory</b> + Location of the Postfix queue, and of the local IPC communication endpoints. <b>SEE</b> <b>ALSO</b> @@ -78,7 +80,7 @@ POSTKICK(1) POSTKICK(1) <a href="pickup.8.html">pickup(8)</a> local pickup daemon <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -126,8 +128,6 @@ POSTKICK(1) POSTKICK(1) - - 2 diff --git a/gnu/dist/postfix/html/postlock.1.html b/gnu/dist/postfix/html/postlock.1.html index b061bc96f0a..8cc19092f14 100644 --- a/gnu/dist/postfix/html/postlock.1.html +++ b/gnu/dist/postfix/html/postlock.1.html @@ -9,18 +9,25 @@ POSTLOCK(1) POSTLOCK(1) postlock - lock mail folder and execute command <b>SYNOPSIS</b> - <b>postlock</b> [<b>-c</b> <i>config_dir</i><b>]</b> <b>[-v</b>] <i>file</i> <i>command...</i> + <b>postlock</b> [<b>-c</b> <i>config_dir</i><b>]</b> <b>[-l</b> <i>lock_style</i><b>]</b> <b>[-v</b>] <i>file</i> <i>com-</i> + <i>mand...</i> <b>DESCRIPTION</b> - The <b>postlock</b> command locks <i>file</i> for exclusive access, and - executes <i>command</i>. The locking method is compatible with + The <b>postlock</b> 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. Options: <b>-c</b> <i>config_dir</i> - Read configuration information from <b>main.cf</b> in the - named configuration directory. + Read the <b>main.cf</b> configuration file in the named + directory instead of the default configuration + directory. + + <b>-l</b> <i>lock_style</i> + Override the locking method specified via the <b>mail-</b> + <b>box</b><i>_</i><b>delivery</b><i>_</i><b>lock</b> configuration parameter (see + below). <b>-v</b> Enable verbose logging for debugging purposes. Mul- tiple <b>-v</b> options make the software increasingly @@ -38,11 +45,9 @@ POSTLOCK(1) POSTLOCK(1) command interpreter. <b>DIAGNOSTICS</b> - The result status is 75 (EX_TEMPFAIL) when the file is - locked by another process, 255 (on some systems: -1) when - <b>postlock</b> could not perform the requested operation. Oth- - erwise, the exit status is the exit status from the com- - mand. + The result status is 75 (EX_TEMPFAIL) when <b>postlock</b> could + not perform the requested operation. Otherwise, the exit + status is the exit status from the command. <b>BUGS</b> With remote file systems, the ability to acquire a lock @@ -53,12 +58,7 @@ POSTLOCK(1) POSTLOCK(1) <b>MAIL</b><i>_</i><b>CONFIG</b> Directory with Postfix configuration files. - <b>MAIL</b><i>_</i><b>VERBOSE</b> - Enable verbose logging for debugging purposes. -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax @@ -71,6 +71,12 @@ POSTLOCK(1) POSTLOCK(1) POSTLOCK(1) POSTLOCK(1) + <b>MAIL</b><i>_</i><b>VERBOSE</b> + Enable verbose logging for debugging purposes. + +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax details and for default values. <b>Locking</b> <b>controls</b> @@ -85,17 +91,23 @@ POSTLOCK(1) POSTLOCK(1) <b>stale</b><i>_</i><b>lock</b><i>_</i><b>time</b> Limit the time after which a stale lock is removed. + <b>mailbox</b><i>_</i><b>delivery</b><i>_</i><b>lock</b> + What file locking method(s) to use when delivering + to a UNIX-style mailbox. The default setting is + system dependent. For a list of available file + locking methods, use the <b>postconf</b> <b>-l</b> command. + <b>Resource</b> <b>controls</b> <b>fork</b><i>_</i><b>attempts</b> - Number of attempts to <b>fork</b>() a process before giv- + Number of attempts to <b>fork</b>() a process before giv- ing up. <b>fork</b><i>_</i><b>delay</b> - Delay in seconds between successive <b>fork</b>() + Delay in seconds between successive <b>fork</b>() attempts. <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -116,18 +128,6 @@ POSTLOCK(1) POSTLOCK(1) - - - - - - - - - - - - 2 diff --git a/gnu/dist/postfix/html/postlog.1.html b/gnu/dist/postfix/html/postlog.1.html index e6464549aa8..c6d6247a839 100644 --- a/gnu/dist/postfix/html/postlog.1.html +++ b/gnu/dist/postfix/html/postlog.1.html @@ -9,42 +9,48 @@ POSTLOG(1) POSTLOG(1) postlog - Postfix-compatible logging utility <b>SYNOPSIS</b> - <b>postlog</b> [<b>-i</b>] [<b>-p</b> <i>priority</i><b>]</b> <b>[-t</b> <i>tag</i>] [<b>-v</b>] [<i>text...</i>] + <b>postlog</b> [<b>-iv</b>] [<b>-c</b> <i>config_dir</i>] [<b>-p</b> <i>priority</i><b>]</b> <b>[-t</b> <i>tag</i>] + [<i>text...</i>] <b>DESCRIPTION</b> - The <b>postlog</b> command implements a Postfix-compatible log- + The <b>postlog</b> command implements a Postfix-compatible log- ging interface for use in, for example, shell scripts. - By default, <b>postlog</b> logs the <i>text</i> given on the command + By default, <b>postlog</b> logs the <i>text</i> given on the command line as one record. If no <i>text</i> is specified on the command - line, <b>postlog</b> reads from standard input and logs each + line, <b>postlog</b> reads from standard input and logs each input line as one record. - Logging is sent to <b>syslogd</b>(8); when the standard error - stream is connected to a terminal, logging is sent there + Logging is sent to <b>syslogd</b>(8); when the standard error + stream is connected to a terminal, logging is sent there as well. The following options are implemented: + <b>-c</b> <i>config_dir</i> + Read the <b>main.cf</b> configuration file in the named + directory instead of the default configuration + directory. + <b>-i</b> Include the process ID in the logging tag. <b>-p</b> <i>priority</i> - Specifies the logging severity: <b>info</b> (default), + Specifies the logging severity: <b>info</b> (default), <b>warn</b>, <b>error</b>, <b>fatal</b>, or <b>panic</b>. <b>-t</b> <i>tag</i> Specifies the logging tag, that is, the identifying - name that appears at the beginning of each logging + name that appears at the beginning of each logging record. <b>-v</b> Enable verbose logging for debugging purposes. Mul- - tiple <b>-v</b> options make the software increasingly + tiple <b>-v</b> options make the software increasingly verbose. <b>SEE</b> <b>ALSO</b> syslogd(8) syslog daemon. <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -56,12 +62,6 @@ POSTLOG(1) POSTLOG(1) - - - - - - 1 diff --git a/gnu/dist/postfix/html/postmap.1.html b/gnu/dist/postfix/html/postmap.1.html index c818e43e0f7..77833681c9d 100644 --- a/gnu/dist/postfix/html/postmap.1.html +++ b/gnu/dist/postfix/html/postmap.1.html @@ -9,7 +9,7 @@ POSTMAP(1) POSTMAP(1) postmap - Postfix lookup table management <b>SYNOPSIS</b> - <b>postmap</b> [<b>-Ninvw</b>] [<b>-c</b> <i>config_dir</i>] [<b>-q</b> <i>key</i>] + <b>postmap</b> [<b>-Ninrvw</b>] [<b>-c</b> <i>config_dir</i>] [<b>-d</b> <i>key</i>] [<b>-q</b> <i>key</i>] [<i>file_type</i>:]<i>file_name</i> ... <b>DESCRIPTION</b> @@ -52,12 +52,12 @@ POSTMAP(1) POSTMAP(1) <b>-c</b> <i>config_dir</i> Read the <b>main.cf</b> configuration file in the named + directory instead of the default configuration directory. - <b>-i</b> Incremental mode. Read entries from standard input - and do not truncate an existing database. By - default, <b>postmap</b> creates a new database from the - entries in <b>file</b><i>_</i><b>name</b>. + <b>-d</b> <i>key</i> Search the specified maps for <i>key</i> and remove one + entry per map. The exit status is non-zero if the + requested information was not found. @@ -71,22 +71,30 @@ POSTMAP(1) POSTMAP(1) POSTMAP(1) POSTMAP(1) - <b>-n</b> Don't include the terminating null character that - terminates lookup keys and values. By default, - Postfix does whatever is the default for the host + <b>-i</b> Incremental mode. Read entries from standard input + and do not truncate an existing database. By + default, <b>postmap</b> creates a new database from the + entries in <b>file</b><i>_</i><b>name</b>. + + <b>-n</b> Don't include the terminating null character that + terminates lookup keys and values. By default, + Postfix does whatever is the default for the host operating system. - <b>-q</b> <i>key</i> Search the specified maps for <i>key</i> and print the - first value found on the standard output stream. + <b>-q</b> <i>key</i> Search the specified maps for <i>key</i> and print the + first value found on the standard output stream. The exit status is non-zero if the requested infor- mation was not found. + <b>-r</b> When updating a table, do not warn about duplicate + entries; silently replace them. + <b>-v</b> Enable verbose logging for debugging purposes. Mul- tiple <b>-v</b> options make the software increasingly verbose. - <b>-w</b> Do not warn about duplicate entries; silently - ignore them. + <b>-w</b> When updating a table, do not warn about duplicate + entries; silently ignore them. Arguments: @@ -117,14 +125,6 @@ POSTMAP(1) POSTMAP(1) <b>DIAGNOSTICS</b> Problems and transactions are logged to the standard error stream. No output means no problems. Duplicate entries are - skipped and are flagged with a warning. - -<b>ENVIRONMENT</b> - <b>MAIL</b><i>_</i><b>CONFIG</b> - Directory with Postfix configuration files. - - <b>MAIL</b><i>_</i><b>VERBOSE</b> - Enable verbose logging for debugging purposes. @@ -137,14 +137,31 @@ POSTMAP(1) POSTMAP(1) POSTMAP(1) POSTMAP(1) + skipped and are flagged with a warning. + + <b>postmap</b> terminates with zero exit status in case of suc- + cess (including successful <b>postmap</b> <b>-q</b> lookup) and termi- + nates with non-zero exit status in case of failure. + +<b>BUGS</b> + The "delete key" support is limited to one delete opera- + tion per command invocation. + +<b>ENVIRONMENT</b> + <b>MAIL</b><i>_</i><b>CONFIG</b> + Directory with Postfix configuration files. + + <b>MAIL</b><i>_</i><b>VERBOSE</b> + Enable verbose logging for debugging purposes. + <b>CONFIGURATION</b> <b>PARAMETERS</b> <b>database</b><i>_</i><b>type</b> - Default output database type. On many UNIX sys- - tems, the default database type is either <b>hash</b> or + Default output database type. On many UNIX sys- + tems, the default database type is either <b>hash</b> or <b>dbm</b>. <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -177,23 +194,6 @@ POSTMAP(1) POSTMAP(1) - - - - - - - - - - - - - - - - - 3 diff --git a/gnu/dist/postfix/html/qmgr.8.html b/gnu/dist/postfix/html/qmgr.8.html index 213a35b04f6..032e6dfdbc6 100644 --- a/gnu/dist/postfix/html/qmgr.8.html +++ b/gnu/dist/postfix/html/qmgr.8.html @@ -14,8 +14,8 @@ QMGR(8) QMGR(8) <b>DESCRIPTION</b> The <b>qmgr</b> 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>triv-</b> - <b>ial-rewrite</b>(8)</a> daemon. This program expects to be run + The actual mail routing strategy is delegated to the <a href="trivial-rewrite.8.html"><b>triv-</b></a> + <a href="trivial-rewrite.8.html"><b>ial-rewrite</b>(8)</a> daemon. This program expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager. Mail addressed to the local <b>double-bounce</b> address is diff --git a/gnu/dist/postfix/html/regexp_table.5.html b/gnu/dist/postfix/html/regexp_table.5.html new file mode 100644 index 00000000000..ad38289d12f --- /dev/null +++ b/gnu/dist/postfix/html/regexp_table.5.html @@ -0,0 +1,134 @@ +<html> <head> </head> <body> <pre> + + + +REGEXP_TABLE(5) REGEXP_TABLE(5) + + +<b>NAME</b> + regexp_table - format of Postfix regular expression tables + +<b>SYNOPSIS</b> + regexp:/etc/postfix/filename + +<b>DESCRIPTION</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. Alternatively, lookup tables can be speci- + fied in POSIX regular expression form. + + To find out what types of lookup tables your Postfix sys- + tem supports use the <b>postconf</b> <b>-m</b> command. + + The general form of a Postfix regular expression table is: + + blanks and comments + Blank lines are ignored, as are lines beginning + with `#'. + + leading whitespace + Lines that begin with whitespace continue the pre- + vious line. + + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches a search string, use the cor- + responding <i>result</i>. A line that starts with white + space continues the preceding line. + + <i>pattern1!pattern2</i> <i>result</i> + Matches <i>pattern1</i> but not <i>pattern2</i>. + + Each pattern is a regular expression enclosed by a pair of + delimiters. The regular expression syntax is described in + <i>re_format</i>(7). The expression delimiter can be any charac- + ter, except whitespace or characters that have special + meaning (traditionally the forward slash is used). The + regular expression can contain whitespace. + + By default, matching is case-insensitive, although follow- + ing the second slash with an `i' flag will reverse this. + Other flags are `x' (disable extended expression syntax), + and `m' (enable multi-line mode). + + Each pattern is applied to the entire string being looked + up. Depending on the application, that string is an + entire client hostname, an entire client IP address, or an + entire mail address. Thus, no parent domain or parent + network search is done, and <i>user@domain</i> mail addresses are + not broken 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>. + + Patterns are applied in the order as specified in the + + + + 1 + + + + + +REGEXP_TABLE(5) REGEXP_TABLE(5) + + + table, until a pattern is found that matches the search + string. + + Substitution of sub-strings from the matched expression is + possible using $1, $2, etc.. The macros in the replacement + string may need to be written as ${n} or $(n) if they + aren't followed by whitespace. + +<b>EXAMPLES</b> + # Disallow sender-specified routing. This is a must if you relay mail + # for other domains. + /[%!@].*[%!@]/ 550 Sender-specified routing rejected + + # Postmaster is OK, that way they can talk to us about how to fix + # their problem. + /^postmaster@.*$/ OK + + # Protect your outgoing majordomo exploders + /^(.*)-outgoing@(.*)$/!/^owner-.*/ 550 Use ${1}@${2} instead + +<b>SEE</b> <b>ALSO</b> + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + +<b>AUTHOR(S)</b> + The regexp table lookup code was originally written by: + LaMont Jones + lamont@hp.com + + That code was based on the PCRE dictionary contributed by: + Andrew McNamara + andrewm@connect.com.au + connect.com.au Pty. Ltd. + Level 3, 213 Miller St + North Sydney, NSW, Australia + + Adopted and adapted by: + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA + + + + + + + + + + + + + + + + + + 2 + + +</pre> </body> </html> diff --git a/gnu/dist/postfix/html/relocated.5.html b/gnu/dist/postfix/html/relocated.5.html index a7788b8a499..d25a045978e 100644 --- a/gnu/dist/postfix/html/relocated.5.html +++ b/gnu/dist/postfix/html/relocated.5.html @@ -12,29 +12,46 @@ RELOCATED(5) RELOCATED(5) <b>postmap</b> <b>/etc/postfix/relocated</b> <b>DESCRIPTION</b> - The optional <b>relocated</b> file provides the information that + The optional <b>relocated</b> table provides the information that is used in "user has moved to <i>new_location</i>" bounce mes- sages. - The file 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. After an update issue a - <b>postfix</b> <b>reload</b> command to make the change visible. + Normally, the <b>relocated</b> 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. Execute the command + <b>postmap</b> <b>/etc/postfix/relocated</b> in order to rebuild the + indexed file after changing the relocated table. + + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. + + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. Table lookups are case insensitive. +<b>TABLE</b> <b>FORMAT</b> The format of the table is as follows: - <b>o</b> Blank lines are ignored, as are lines beginning + <b>o</b> Blank lines are ignored, as are lines beginning with `#'. + <b>o</b> Lines that begin with whitespace continue the pre- + vious line. + <b>o</b> An entry has one of the following form: <i>key</i> <i>new_location</i> Where <i>new_location</i> specifies contact information such as an email address, or perhaps a street address or telephone number. - The <i>key</i> field is one of the following: + With lookups from indexed files such as DB or DBM, or from + networked tables such as NIS, LDAP or SQL, the <i>key</i> field + is one of the following: <i>user</i>@<i>domain</i> Matches <i>user</i>@<i>domain</i>. This form has precedence over @@ -42,6 +59,18 @@ RELOCATED(5) RELOCATED(5) <i>user</i> Matches <i>user</i>@<i>site</i> when <i>site</i> is $<b>myorigin</b>, when <i>site</i> is listed in $<b>mydestination</b>, or when <i>site</i> is listed + + + + 1 + + + + + +RELOCATED(5) RELOCATED(5) + + in $<b>inet</b><i>_</i><b>interfaces</b>. @<i>domain</i> @@ -54,23 +83,31 @@ RELOCATED(5) RELOCATED(5) the search is repeated for the unextended address (e.g. <i>user</i>@<i>domain</i>). -<b>BUGS</b> - The table format does not understand quoting conventions. - -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - +<b>REGULAR</b> <b>EXPRESSION</b> <b>TABLES</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</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + Each pattern is a regular expression that is applied to + the entire address being looked up. Thus, <i>user@domain</i> mail + addresses are not broken 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>. - 1 - + Patterns are applied in the order as specified in the + table, until a pattern is found that matches the search + string. + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. +<b>BUGS</b> + The table format does not understand quoting conventions. - -RELOCATED(5) RELOCATED(5) - - +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant to this topic. See the Postfix <b>main.cf</b> file for syntax details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. @@ -88,11 +125,25 @@ RELOCATED(5) RELOCATED(5) List of domains that this mail system considers local. + + + + 2 + + + + + +RELOCATED(5) RELOCATED(5) + + <b>myorigin</b> The domain that is appended to locally-posted mail. <b>SEE</b> <b>ALSO</b> <a href="postmap.1.html">postmap(1)</a> create lookup table + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables <b>LICENSE</b> The Secure Mailer license must be distributed with this @@ -128,7 +179,22 @@ RELOCATED(5) RELOCATED(5) - 2 + + + + + + + + + + + + + + + + 3 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/resource.html b/gnu/dist/postfix/html/resource.html index cabadc1503a..4c24021b317 100644 --- a/gnu/dist/postfix/html/resource.html +++ b/gnu/dist/postfix/html/resource.html @@ -80,6 +80,14 @@ Header text that does not fit in <b>$header_size_limit</b> bytes overflows into the message body. This limit is enforced by the <a href="cleanup.8.html"> cleanup</a> header rewriting code. +<p> + +<dt> <b>extract_recipient_limit</b> (default: 10240 recipients) + +<dd> How many recipients Postfix will extract from message headers +before it gives up. This limits the damage that a run-away program +can do with "sendmail -t". + </dl> <p> @@ -90,8 +98,8 @@ The following parameters restrict the use of file system storage: <dt> <b>message_size_limit</b> (default: 10240000 bytes) -<dd> The maximal size of a Postfix queue file for inbound mail, -including envelope information (sender, recipient, etc.). +<dd> The maximal size of a Postfix queue file, including envelope +information (sender, recipient, etc.). <p> diff --git a/gnu/dist/postfix/html/sendmail.1.html b/gnu/dist/postfix/html/sendmail.1.html index 8c037cbe021..43b48ba1426 100644 --- a/gnu/dist/postfix/html/sendmail.1.html +++ b/gnu/dist/postfix/html/sendmail.1.html @@ -87,44 +87,44 @@ SENDMAIL(1) SENDMAIL(1) Set the sender full name. This is used only with messages that have no <b>From:</b> message header. - <b>-I</b> Initialize alias database. See the <b>newaliases</b> com- + <b>-G</b> (ignored) + Gateway (relay) submission, as opposed to initial + user submission. + + <b>-I</b> Initialize alias database. See the <b>newaliases</b> com- mand above. <b>-N</b> <i>dsn</i> (ignored) - Delivery status notification control. Currently, + Delivery status notification control. Currently, Postfix does not implement <b>DSN</b>. <b>-R</b> <i>return_limit</i> (ignored) - Limit the size of bounced mail. Use the - <b>bounce</b><i>_</i><b>size</b><i>_</i><b>limit</b> configuration parameter instead. + Limit the size of bounced mail. Use the + <b>bounce</b><i>_</i><b>size</b><i>_</i><b>limit</b> configuration parameter instead. <b>-X</b> <i>log_file</i> (ignored) - Log mailer traffic. Use the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> and - <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> configuration parameters instead. + Log mailer traffic. Use the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> and + <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> configuration parameters instead. <b>-U</b> (ignored) Initial user submission. - <b>-bd</b> Go into daemon mode. This mode of operation is + <b>-bd</b> Go into daemon mode. This mode of operation is implemented by executing the <b>postfix</b> <b>start</b> command. - <b>-bi</b> Initialize alias database. See the <b>newaliases</b> com- + <b>-bi</b> Initialize alias database. See the <b>newaliases</b> com- mand above. - <b>-bm</b> Read mail from standard input and arrange for + <b>-bm</b> Read mail from standard input and arrange for delivery. This is the default mode of operation. <b>-bp</b> List the mail queue. See the <b>mailq</b> command above. - <b>-bs</b> Stand-alone SMTP server mode. Read SMTP commands - from standard input, and write responses to stan- + <b>-bs</b> Stand-alone SMTP server mode. Read SMTP commands + from standard input, and write responses to stan- dard output. This mode of operation is implemented by running the <a href="smtpd.8.html"><b>smtpd</b>(8)</a> daemon. - <b>-f</b> <i>sender</i> - Set the envelope sender address. This is the - address where delivery problems are sent to, unless - the message contains an <b>Errors-To:</b> message header. @@ -137,12 +137,17 @@ SENDMAIL(1) SENDMAIL(1) SENDMAIL(1) SENDMAIL(1) + <b>-f</b> <i>sender</i> + Set the envelope sender address. This is the + address where delivery problems are sent to, unless + the message contains an <b>Errors-To:</b> message header. + <b>-h</b> <i>hop_count</i> (ignored) - Hop count limit. Use the <b>hopcount</b><i>_</i><b>limit</b> configura- + Hop count limit. Use the <b>hopcount</b><i>_</i><b>limit</b> configura- tion parameter instead. - <b>-i</b> When reading a message from standard input, don't - treat a line with only a <b>.</b> character as the end of + <b>-i</b> When reading a message from standard input, don't + treat a line with only a <b>.</b> character as the end of input. <b>-m</b> (ignored) @@ -152,45 +157,40 @@ SENDMAIL(1) SENDMAIL(1) Backwards compatibility. <b>-oA</b><i>alias_database</i> - Non-default alias database. Specify <i>pathname</i> or + Non-default alias database. Specify <i>pathname</i> or <i>type</i>:<i>pathname</i>. See <a href="postalias.1.html"><b>postalias</b>(1)</a> for details. <b>-o7</b> (ignored) <b>-o8</b> (ignored) - The message body type. Currently, Postfix imple- + The message body type. Currently, Postfix imple- ments <b>just-send-eight</b>. - <b>-oi</b> When reading a message from standard input, don't - treat a line with only a <b>.</b> character as the end of + <b>-oi</b> When reading a message from standard input, don't + treat a line with only a <b>.</b> character as the end of input. <b>-om</b> (ignored) - The sender is never eliminated from alias etc. + The sender is never eliminated from alias etc. expansions. <b>-o</b> <i>x</i> <i>value</i> (ignored) - Set option <i>x</i> to <i>value</i>. Use the equivalent configu- + Set option <i>x</i> to <i>value</i>. Use the equivalent configu- ration parameter in <b>main.cf</b> instead. <b>-r</b> <i>sender</i> Set the envelope sender address. This is the address where delivery problems are sent to, unless - the message contains an <b>Errors-To:</b> message header. + the message contains an <b>Errors-To:</b> message header. - <b>-q</b> Flush the mail queue. This is implemented by kick- - ing the <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon. + <b>-q</b> Attempt to deliver all queued mail. This is imple- + mented by kicking the <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon. <b>-q</b><i>interval</i> (ignored) - The interval between queue runs. Use the + The interval between queue runs. Use the <b>queue</b><i>_</i><b>run</b><i>_</i><b>delay</b> configuration parameter instead. - <b>-t</b> Extract recipients from message headers. This - requires that no recipients be specified on the - command line. - <b>-v</b> Enable verbose logging for debugging purposes. Mul- - tiple <b>-v</b> options make the software increasingly @@ -203,6 +203,25 @@ SENDMAIL(1) SENDMAIL(1) SENDMAIL(1) SENDMAIL(1) + <b>-qR</b><i>site</i> + Schedule immediate delivery of all mail that is + queued for the named <i>site</i>. Depending on the desti- + nation, this uses "fast flush" service, or it has + the same effect as <b>sendmail</b> <b>-q</b>. This is imple- + mented by connecting to the local SMTP server. See + <a href="smtpd.8.html"><b>smtpd</b>(8)</a> for more information about the "fast + flush" service. + + <b>-qS</b><i>site</i> + This command is not implemented. Use the slower + <b>sendmail</b> <b>-q</b> command instead. + + <b>-t</b> Extract recipients from message headers. This + requires that no recipients be specified on the + command line. + + <b>-v</b> Enable verbose logging for debugging purposes. Mul- + tiple <b>-v</b> options make the software increasingly verbose. <b>SECURITY</b> @@ -238,6 +257,18 @@ SENDMAIL(1) SENDMAIL(1) <b>alias</b><i>_</i><b>database</b> Default alias database(s) for <b>newaliases</b>. The + + + + 4 + + + + + +SENDMAIL(1) SENDMAIL(1) + + default value for this parameter is system-spe- cific. @@ -258,23 +289,21 @@ SENDMAIL(1) SENDMAIL(1) host matches a pattern in the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> parameter. - - - 4 - - - - - -SENDMAIL(1) SENDMAIL(1) - - <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> List of domain or network patterns. When a remote host matches a pattern, increase the verbose log- ging level by the amount specified in the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> parameter. + <b>fast</b><i>_</i><b>flush</b><i>_</i><b>domains</b> + List of domains that will receive "fast flush" ser- + vice (default: all domains that this system is + willing to relay mail to). This greatly improves + the performance of the SMTP <b>ETRN</b> request, and of + the <b>sendmail</b> <b>-qR</b> command. For domains not in the + list, Postfix simply attempts to deliver all queued + mail. + <b>fork</b><i>_</i><b>attempts</b> Number of attempts to <b>fork</b>() a process before giv- ing up. @@ -294,6 +323,18 @@ SENDMAIL(1) SENDMAIL(1) Directory with Postfix support commands (default: <b>$program</b><i>_</i><b>directory</b>). + + + + 5 + + + + + +SENDMAIL(1) SENDMAIL(1) + + <b>daemon</b><i>_</i><b>directory</b> Directory with Postfix daemon programs (default: <b>$program</b><i>_</i><b>directory</b>). @@ -316,25 +357,13 @@ SENDMAIL(1) SENDMAIL(1) <a href="qmgr.8.html">qmgr(8)</a> queue manager <a href="showq.8.html">showq(8)</a> list mail queue <a href="smtpd.8.html">smtpd(8)</a> SMTP server + flushd(8) fast flush service syslogd(8) system logging <b>LICENSE</b> The Secure Mailer license must be distributed with this software. - - - - - 5 - - - - - -SENDMAIL(1) SENDMAIL(1) - - <b>AUTHOR(S)</b> Wietse Venema IBM T.J. Watson Research @@ -363,35 +392,6 @@ SENDMAIL(1) SENDMAIL(1) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6 diff --git a/gnu/dist/postfix/html/smtp.8.html b/gnu/dist/postfix/html/smtp.8.html index 4dfcdfd0e83..b493e7090e4 100644 --- a/gnu/dist/postfix/html/smtp.8.html +++ b/gnu/dist/postfix/html/smtp.8.html @@ -29,6 +29,11 @@ SMTP(8) SMTP(8) preference, and connects to each listed address until it finds a server that responds. + When the domain or host is specified as a comma/whitespace + separated list, the SMTP client repeats the above process + for all destinations until it finds a server that + responds. + Once the SMTP client has received the server greeting ban- ner, no error will cause it to proceed to the next address on the mail exchanger list. Instead, the message is either @@ -36,30 +41,25 @@ SMTP(8) SMTP(8) <b>SECURITY</b> The SMTP client is moderately security-sensitive. It talks - to SMTP servers and to DNS servers on the network. The + to SMTP servers and to DNS servers on the network. The SMTP client can be run chrooted at fixed low privilege. <b>STANDARDS</b> - RFC 821 (SMTP protocol) - RFC 1651 (SMTP service extensions) - RFC 1870 (Message Size Declaration) - RFC 2197 (Pipelining) + <a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a> (SMTP protocol) + <a href="http://www.faqs.org/rfcs/rfc1651.html">RFC 1651</a> (SMTP service extensions) + <a href="http://www.faqs.org/rfcs/rfc1870.html">RFC 1870</a> (Message Size Declaration) + <a href="http://www.faqs.org/rfcs/rfc2197.html">RFC 2197</a> (Pipelining) + <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> (AUTH command) <b>DIAGNOSTICS</b> - Problems and transactions are logged to <b>syslogd</b>(8). Cor- - rupted message files are marked so that the queue manager + Problems and transactions are logged to <b>syslogd</b>(8). Cor- + rupted message files are marked so that the queue manager can move them to the <b>corrupt</b> queue for further inspection. - Depending on the setting of the <b>notify</b><i>_</i><b>classes</b> parameter, - the postmaster is notified of bounces, protocol problems, + Depending on the setting of the <b>notify</b><i>_</i><b>classes</b> parameter, + the postmaster is notified of bounces, protocol problems, and of other trouble. -<b>BUGS</b> -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> - 1 @@ -71,130 +71,196 @@ SMTP(8) SMTP(8) SMTP(8) SMTP(8) +<b>BUGS</b> +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. <b>Miscellaneous</b> <b>best</b><i>_</i><b>mx</b><i>_</i><b>transport</b> - Name of the delivery transport to use when the - local machine is the most-preferred mail exchanger - (by default, a mailer loop is reported, and the + Name of the delivery transport to use when the + local machine is the most-preferred mail exchanger + (by default, a mailer loop is reported, and the message is bounced). <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> - Verbose logging level increment for hosts that + Verbose logging level increment for hosts that match a pattern in the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> parameter. <b>debug</b><i>_</i><b>peer</b><i>_</i><b>list</b> - List of domain or network patterns. When a remote - host matches a pattern, increase the verbose log- - ging level by the amount specified in the + List of domain or network patterns. When a remote + host matches a pattern, increase the verbose log- + ging level by the amount specified in the <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> parameter. <b>disable</b><i>_</i><b>dns</b><i>_</i><b>lookups</b> - Disable DNS lookups. This means that mail must be + Disable DNS lookups. This means that mail must be forwarded via a smart relay host. <b>error</b><i>_</i><b>notice</b><i>_</i><b>recipient</b> - Recipient of protocol/policy/resource/software + Recipient of protocol/policy/resource/software error notices. <b>fallback</b><i>_</i><b>relay</b> - Hosts to hand off mail to if a message destination + Hosts to hand off mail to if a message destination is not found or if a destination is unreachable. <b>ignore</b><i>_</i><b>mx</b><i>_</i><b>lookup</b><i>_</i><b>error</b> When a name server fails to respond to an MX query, - search for an A record instead of assuming that the - name server will recover. + search for an A record instead deferring mail + delivery. <b>inet</b><i>_</i><b>interfaces</b> The network interface addresses that this mail sys- - tem receives mail on. When any of those addresses + tem receives mail on. When any of those addresses appears in the list of mail exchangers for a remote - destination, the list is truncated to avoid mail + destination, the list is truncated to avoid mail delivery loops. <b>notify</b><i>_</i><b>classes</b> - When this parameter includes the <b>protocol</b> class, - send mail to the postmaster with transcripts of + When this parameter includes the <b>protocol</b> class, + send mail to the postmaster with transcripts of SMTP sessions with protocol errors. + + + + + 2 + + + + + +SMTP(8) SMTP(8) + + + <b>smtp</b><i>_</i><b>always</b><i>_</i><b>send</b><i>_</i><b>ehlo</b> + Always send EHLO at the start of a connection. + + <b>smtp</b><i>_</i><b>never</b><i>_</i><b>send</b><i>_</i><b>ehlo</b> + Never send EHLO at the start of a connection. + <b>smtp</b><i>_</i><b>skip</b><i>_</i><b>4xx</b><i>_</i><b>greeting</b> - Skip servers that greet us with a 4xx status code. + Skip servers that greet us with a 4xx status code. + + <b>smtp</b><i>_</i><b>skip</b><i>_</i><b>5xx</b><i>_</i><b>greeting</b> + Skip servers that greet us with a 5xx status code. <b>smtp</b><i>_</i><b>skip</b><i>_</i><b>quit</b><i>_</i><b>response</b> Do not wait for the server response after sending QUIT. + <b>smtp</b><i>_</i><b>bind</b><i>_</i><b>address</b> + Numerical network address to bind to when making a + connection. +<b>Authentication</b> <b>controls</b> + <b>smtp</b><i>_</i><b>enable</b><i>_</i><b>sasl</b><i>_</i><b>auth</b> + Enable per-session authentication as per <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> + (SASL). By default, Postfix is built without SASL + support. - 2 - + <b>smtp</b><i>_</i><b>sasl</b><i>_</i><b>password</b><i>_</i><b>maps</b> + Lookup tables with per-host or domain <i>name</i>:<i>password</i> + entries. No entry for a host means no attempt to + authenticate. + <b>smtp</b><i>_</i><b>sasl</b><i>_</i><b>security</b><i>_</i><b>options</b> + Zero or more of the following. + <b>noplaintext</b> + Disallow authentication methods that use + plaintext passwords. + <b>noactive</b> + Disallow authentication methods that are + vulnerable to non-dictionary active attacks. -SMTP(8) SMTP(8) + <b>nodictionary</b> + Disallow authentication methods that are + vulnerable to passive dictionary attack. + <b>noanonymous</b> + Disallow anonymous logins. <b>Resource</b> <b>controls</b> <b>smtp</b><i>_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> Limit the number of parallel deliveries to the same - destination. The default limit is taken from the + destination. The default limit is taken from the <b>default</b><i>_</i><b>destination</b><i>_</i><b>concurrency</b><i>_</i><b>limit</b> parameter. + + + 3 + + + + + +SMTP(8) SMTP(8) + + <b>smtp</b><i>_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> - Limit the number of recipients per message deliv- - ery. The default limit is taken from the + Limit the number of recipients per message deliv- + ery. The default limit is taken from the <b>default</b><i>_</i><b>destination</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> parameter. <b>Timeout</b> <b>controls</b> + The default time unit is seconds; an explicit time unit + can be specified by appending a one-letter suffix to the + value: s (seconds), m (minutes), h (hours), d (days) or w + (weeks). + <b>smtp</b><i>_</i><b>connect</b><i>_</i><b>timeout</b> - Timeout in seconds for completing a TCP connection. - When no connection can be made within the deadline, - the SMTP client tries the next address on the mail + Timeout for completing a TCP connection. When no + connection can be made within the deadline, the + SMTP client tries the next address on the mail exchanger list. <b>smtp</b><i>_</i><b>helo</b><i>_</i><b>timeout</b> - Timeout in seconds for receiving the SMTP greeting - banner. When the server drops the connection with- - out sending a greeting banner, or when it sends no - greeting banner within the deadline, the SMTP - client tries the next address on the mail exchanger - list. + Timeout for receiving the SMTP greeting banner. + When the server drops the connection without send- + ing a greeting banner, or when it sends no greeting + banner within the deadline, the SMTP client tries + the next address on the mail exchanger list. <b>smtp</b><i>_</i><b>helo</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the <b>HELO</b> command, - and for receiving the server response. + Timeout for sending the <b>HELO</b> command, and for + receiving the server response. <b>smtp</b><i>_</i><b>mail</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the <b>MAIL</b> <b>FROM</b> com- - mand, and for receiving the server response. + Timeout for sending the <b>MAIL</b> <b>FROM</b> command, and for + receiving the server response. <b>smtp</b><i>_</i><b>rcpt</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the <b>RCPT</b> <b>TO</b> command, - and for receiving the server response. + Timeout for sending the <b>RCPT</b> <b>TO</b> command, and for + receiving the server response. <b>smtp</b><i>_</i><b>data</b><i>_</i><b>init</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the <b>DATA</b> command, - and for receiving the server response. + Timeout for sending the <b>DATA</b> command, and for + receiving the server response. <b>smtp</b><i>_</i><b>data</b><i>_</i><b>xfer</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the message content. + Timeout for sending the message content. <b>smtp</b><i>_</i><b>data</b><i>_</i><b>done</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the "<b>.</b>" command, and - for receiving the server response. When no response - is received, a warning is logged that the mail may - be delivered multiple times. + Timeout for sending the "<b>.</b>" command, and for + receiving the server response. When no response is + received, a warning is logged that the mail may be + delivered multiple times. <b>smtp</b><i>_</i><b>quit</b><i>_</i><b>timeout</b> - Timeout in seconds for sending the <b>QUIT</b> command, - and for receiving the server response. + Timeout for sending the <b>QUIT</b> command, and for + receiving the server response. + - 3 + + 4 @@ -260,7 +326,7 @@ SMTP(8) SMTP(8) - 4 + 5 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/smtpd.8.html b/gnu/dist/postfix/html/smtpd.8.html index f5bbf286674..97ae6d8377b 100644 --- a/gnu/dist/postfix/html/smtpd.8.html +++ b/gnu/dist/postfix/html/smtpd.8.html @@ -26,9 +26,9 @@ SMTPD(8) SMTPD(8) system is not running. The SMTP server implements a variety of policies for con- - nection requests, and for parameters given to <b>HELO,</b> <b>MAIL</b> - <b>FROM,</b> <b>VRFY</b> and <b>RCPT</b> <b>TO</b> commands. They are detailed below - and in the <b>main.cf</b> configuration file. + nection requests, and for parameters given to <b>HELO,</b> <b>ETRN,</b> + <b>MAIL</b> <b>FROM,</b> <b>VRFY</b> and <b>RCPT</b> <b>TO</b> commands. They are detailed + below and in the <b>main.cf</b> configuration file. <b>SECURITY</b> The SMTP server is moderately security-sensitive. It talks @@ -42,7 +42,8 @@ SMTPD(8) SMTPD(8) <a href="http://www.faqs.org/rfcs/rfc1652.html">RFC 1652</a> (8bit-MIME transport) <a href="http://www.faqs.org/rfcs/rfc1854.html">RFC 1854</a> (SMTP Pipelining) <a href="http://www.faqs.org/rfcs/rfc1870.html">RFC 1870</a> (Message Size Declaration) - <a href="http://www.faqs.org/rfcs/rfc1985.html">RFC 1985</a> (ETRN command) (partial) + <a href="http://www.faqs.org/rfcs/rfc1985.html">RFC 1985</a> (ETRN command) + <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> (AUTH command) <b>DIAGNOSTICS</b> Problems and transactions are logged to <b>syslogd</b>(8). @@ -51,14 +52,13 @@ SMTPD(8) SMTPD(8) the postmaster is notified of bounces, protocol problems, policy violations, and of other trouble. -<b>BUGS</b> - <a href="http://www.faqs.org/rfcs/rfc1985.html">RFC 1985</a> is implemented by forcing delivery of all - deferred mail. - <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this program. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> + command after a configuration change. + + @@ -71,14 +71,53 @@ SMTPD(8) SMTPD(8) SMTPD(8) SMTPD(8) - command after a configuration change. - <b>Compatibility</b> <b>controls</b> <b>strict</b><i>_</i><b>rfc821</b><i>_</i><b>envelopes</b> - Disallow non-<a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a> style addresses in envelopes. - For example, allow <a href="http://www.faqs.org/rfcs/rfc822.html">RFC822</a>-style address forms with + Disallow non-<a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a> style addresses in envelopes. + For example, allow <a href="http://www.faqs.org/rfcs/rfc822.html">RFC822</a>-style address forms with comments, like Sendmail does. + <b>broken</b><i>_</i><b>sasl</b><i>_</i><b>auth</b><i>_</i><b>clients</b> + Support older Microsoft clients that mis-implement + the AUTH protocol, and that expect an EHLO response + of "250 AUTH=list" instead of "250 AUTH list". + +<b>Content</b> <b>inspection</b> <b>controls</b> + <b>content</b><i>_</i><b>filter</b> + The name of a mail delivery transport that filters + mail and that either bounces mail or re-injects the + result back into Postfix. This parameter uses the + same syntax as the right-hand side of a Postfix + transport table. + +<b>Authentication</b> <b>controls</b> + <b>enable</b><i>_</i><b>sasl</b><i>_</i><b>authentication</b> + Enable per-session authentication as per <a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> + (SASL). This functionality is available only when + explicitly selected at program build time and + explicitly enabled at runtime. + + <b>smtpd</b><i>_</i><b>sasl</b><i>_</i><b>local</b><i>_</i><b>domain</b> + The name of the local authentication realm. + + <b>smtpd</b><i>_</i><b>sasl</b><i>_</i><b>security</b><i>_</i><b>options</b> + Zero or more of the following. + + <b>noplaintext</b> + Disallow authentication methods that use + plaintext passwords. + + <b>noactive</b> + Disallow authentication methods that are + vulnerable to non-dictionary active attacks. + + <b>nodictionary</b> + Disallow authentication methods that are + vulnerable to passive dictionary attack. + + <b>noanonymous</b> + Disallow anonymous logins. + <b>Miscellaneous</b> <b>always</b><i>_</i><b>bcc</b> Address to send a copy of each message that enters @@ -86,6 +125,18 @@ SMTPD(8) SMTPD(8) <b>command</b><i>_</i><b>directory</b> Location of Postfix support commands (default: + + + + 2 + + + + + +SMTPD(8) SMTPD(8) + + <b>$program</b><i>_</i><b>directory</b>). <b>debug</b><i>_</i><b>peer</b><i>_</i><b>level</b> @@ -106,15 +157,15 @@ SMTPD(8) SMTPD(8) <b>hopcount</b><i>_</i><b>limit</b> Limit the number of <b>Received:</b> message headers. - <b>notify</b><i>_</i><b>classes</b> - List of error classes. Of special interest are: - <b>local</b><i>_</i><b>recipient</b><i>_</i><b>maps</b> List of maps with user names that are local to <b>$myorigin</b> or <b>$inet</b><i>_</i><b>interfaces</b>. If this parameter is defined, then the SMTP server rejects mail for unknown local users. + <b>notify</b><i>_</i><b>classes</b> + List of error classes. Of special interest are: + <b>policy</b> When a client violates any policy, mail a transcript of the entire SMTP session to the postmaster. @@ -125,29 +176,34 @@ SMTPD(8) SMTPD(8) transcript of the entire SMTP session to the postmaster. + <b>smtpd</b><i>_</i><b>banner</b> + Text that follows the <b>220</b> status code in the SMTP + greeting banner. + <b>smtpd</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> + Restrict the number of recipients that the SMTP + server accepts per message delivery. + <b>smtpd</b><i>_</i><b>timeout</b> + Limit the time to send a server response and to + receive a client request. - 2 + <b>soft</b><i>_</i><b>bounce</b> + Change hard (5xx) reject responses into soft (4xx) + reject responses. This can be useful for testing + 3 -SMTPD(8) SMTPD(8) - <b>smtpd</b><i>_</i><b>banner</b> - Text that follows the <b>220</b> status code in the SMTP - greeting banner. - <b>smtpd</b><i>_</i><b>recipient</b><i>_</i><b>limit</b> - Restrict the number of recipients that the SMTP - server accepts per message delivery. +SMTPD(8) SMTPD(8) - <b>smtpd</b><i>_</i><b>timeout</b> - Limit the time to send a server response and to - receive a client request. + + purposes. <b>Resource</b> <b>controls</b> <b>line</b><i>_</i><b>length</b><i>_</i><b>limit</b> @@ -192,24 +248,26 @@ SMTPD(8) SMTPD(8) Require that clients introduce themselves at the beginning of an SMTP session. + <b>smtpd</b><i>_</i><b>helo</b><i>_</i><b>restrictions</b> + Restrict what client hostnames are allowed in <b>HELO</b> + and <b>EHLO</b> commands. + <b>smtpd</b><i>_</i><b>sender</b><i>_</i><b>restrictions</b> + Restrict what sender addresses are allowed in <b>MAIL</b> + <b>FROM</b> commands. - 3 + 4 -SMTPD(8) SMTPD(8) - <b>smtpd</b><i>_</i><b>helo</b><i>_</i><b>restrictions</b> - Restrict what client hostnames are allowed in <b>HELO</b> - and <b>EHLO</b> commands. - <b>smtpd</b><i>_</i><b>sender</b><i>_</i><b>restrictions</b> - Restrict what sender addresses are allowed in <b>MAIL</b> - <b>FROM</b> commands. + +SMTPD(8) SMTPD(8) + <b>smtpd</b><i>_</i><b>recipient</b><i>_</i><b>restrictions</b> Restrict what recipient addresses are allowed in @@ -256,26 +314,26 @@ SMTPD(8) SMTPD(8) Response code when the client matches a <b>reject</b> restriction. + <b>relay</b><i>_</i><b>domains</b><i>_</i><b>reject</b><i>_</i><b>code</b> + Server response when a client attempts to violate + the mail relay policy. + <b>unknown</b><i>_</i><b>address</b><i>_</i><b>reject</b><i>_</i><b>code</b> + Server response when a client violates the + <b>reject</b><i>_</i><b>unknown</b><i>_</i><b>address</b> restriction. - 4 + 5 -SMTPD(8) SMTPD(8) - <b>relay</b><i>_</i><b>domains</b><i>_</i><b>reject</b><i>_</i><b>code</b> - Server response when a client attempts to violate - the mail relay policy. +SMTPD(8) SMTPD(8) - <b>unknown</b><i>_</i><b>address</b><i>_</i><b>reject</b><i>_</i><b>code</b> - Server response when a client violates the - <b>reject</b><i>_</i><b>unknown</b><i>_</i><b>address</b> restriction. <b>unknown</b><i>_</i><b>client</b><i>_</i><b>reject</b><i>_</i><b>code</b> Server response when a client without address to @@ -326,7 +384,15 @@ SMTPD(8) SMTPD(8) - 5 + + + + + + + + + 6 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/spawn.8.html b/gnu/dist/postfix/html/spawn.8.html new file mode 100644 index 00000000000..b844abf3ac3 --- /dev/null +++ b/gnu/dist/postfix/html/spawn.8.html @@ -0,0 +1,134 @@ +<html> <head> </head> <body> <pre> + + + +SPAWN(8) SPAWN(8) + + +<b>NAME</b> + spawn - Postfix external command spawner + +<b>SYNOPSIS</b> + <b>spawn</b> [generic Postfix daemon options] command_attributes... + +<b>DESCRIPTION</b> + The <b>spawn</b> daemon provides the Postfix equivalent of <b>inetd</b>. + It listens on a port as specified in the Postfix <b>master.cf</b> + file and spawns an external command whenever a connection + is established. The connection can be made over local IPC + (such as UNIX-domain sockets) or over non-local IPC (such + as TCP sockets). The command's standard input, output and + error streams are connected directly to the communication + endpoint. + + This daemon expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process + manager. + +<b>COMMAND</b> <b>ATTRIBUTE</b> <b>SYNTAX</b> + The external command attributes are given in the <b>master.cf</b> + file at the end of a service definition. The syntax is as + follows: + + <b>user</b>=<i>username</i> (required) + + <b>user</b>=<i>username</i>:<i>groupname</i> + The external command is executed with the rights of + the specified <i>username</i>. The software refuses to + execute commands with root privileges, or with the + privileges of the mail system owner. If <i>groupname</i> + is specified, the corresponding group ID is used + instead of the group ID of of <i>username</i>. + + <b>argv</b>=<i>command</i>... (required) + The command to be executed. This must be specified + as the last command attribute. The command is exe- + cuted directly, i.e. without interpretation of + shell meta characters by a shell command inter- + preter. + +<b>BUGS</b> + In order to enforce standard Postfix process resource con- + trols, the <b>spawn</b> daemon runs only one external command at + a time. As such, it presents a noticeable overhead by + wasting precious process resources. The <b>spawn</b> daemon is + expected to be replaced by a more structural solution. + +<b>DIAGNOSTICS</b> + The <b>spawn</b> daemon reports abnormal child exits. Problems + are logged to <b>syslogd</b>(8). + +<b>SECURITY</b> + This program needs root privilege in order to execute + + + + 1 + + + + + +SPAWN(8) SPAWN(8) + + + external commands as the specified user. It is therefore + security sensitive. However the <b>spawn</b> daemon does not + talk to the external command and thus is not vulnerable to + data-driven attacks. + +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this program. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> + command after a configuration change. + +<b>Miscellaneous</b> + <b>export</b><i>_</i><b>environment</b> + List of names of environment parameters that can be + exported to non-Postfix processes. + + <b>mail</b><i>_</i><b>owner</b> + The process privileges used while not running an + external command. + +<b>Resource</b> <b>control</b> + <i>service_</i><b>command</b><i>_</i><b>time</b><i>_</i><b>limit</b> + The amount of time the command is allowed to run + before it is killed with force. The <i>service</i> name is + the name of the entry in the <b>master.cf</b> file. The + default time limit is given by the global <b>com-</b> + <b>mand</b><i>_</i><b>time</b><i>_</i><b>limit</b> configuration parameter. + +<b>SEE</b> <b>ALSO</b> + <a href="master.8.html">master(8)</a> process manager + syslogd(8) system logging + +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. + +<b>AUTHOR(S)</b> + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA + + + + + + + + + + + + + + + + + 2 + + +</pre> </body> </html> diff --git a/gnu/dist/postfix/html/transport.5.html b/gnu/dist/postfix/html/transport.5.html index bace70fa91d..c384739dde4 100644 --- a/gnu/dist/postfix/html/transport.5.html +++ b/gnu/dist/postfix/html/transport.5.html @@ -12,23 +12,46 @@ TRANSPORT(5) TRANSPORT(5) <b>postmap</b> <b>/etc/postfix/transport</b> <b>DESCRIPTION</b> - The optional <b>transport</b> file specifies a mapping from + The optional <b>transport</b> table specifies a mapping from domain hierarchies to message delivery transports and/or relay hosts. The mapping is used by the <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon. - The file 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. After updating this - table, issue the <b>postfix</b> <b>reload</b> command to make the change - visible. + Normally, the <b>transport</b> 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. Execute the command + <b>postmap</b> <b>/etc/postfix/transport</b> in order to rebuild the + indexed file after changing the transport table. + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. + + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. + +<b>TABLE</b> <b>FORMAT</b> The format of the transport table is as follows: blanks and comments Blank lines are ignored, as are lines beginning with `#'. + leading whitespace + Lines that begin with whitespace continue the pre- + vious line. + + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches the domain, use the corre- + sponding <i>result</i>. + + 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: + <i>domain</i> <i>transport</i>:<i>nexthop</i> Mail for <i>domain</i> is delivered through <i>transport</i> to <i>nexthop</i>. @@ -37,79 +60,113 @@ TRANSPORT(5) TRANSPORT(5) Mail for any subdomain of <i>domain</i> is delivered through <i>transport</i> to <i>nexthop</i>. + + + 1 + + + + + +TRANSPORT(5) TRANSPORT(5) + + Note: transport map entries take precedence over domains specified in the <b>mydestination</b> parameter. If you use the optional transport map, it may be safer to specify explicit entries for all domains specified in <b>mydestina-</b> <b>tion</b>, for example: - <b>hostname.my.domain</b> <b>local:</b> + <b>hostname.my.domain</b> <b>local:</b> <b>localhost.my.domain</b> <b>local:</b> The interpretation of the <i>nexthop</i> field is transport dependent. In the case of SMTP, specify <i>host</i>:<i>service</i> for a - non-default server port, and use [<i>host</i>] or [<i>host</i>:<i>port</i>] in + non-default server port, and use [<i>host</i>] or [<i>host</i>]:<i>port</i> in order to disable MX (mail exchanger) DNS lookups. The [] form can also be used with IP addresses instead of host- names. <b>EXAMPLES</b> - In order to send mail for <b>foo.org</b> and its subdomains - via the <b>uucp</b> transport to the UUCP host named <b>foo</b>: + In order to send mail for <b>foo.org</b> and its subdomains via + the <b>uucp</b> transport to the UUCP host named <b>foo</b>: <b>foo.org</b> <b>uucp:foo</b> <b>.foo.org</b> <b>uucp:foo</b> + When no <i>nexthop</i> host name is specified, the destination + domain name is used instead. For example, the following + directs mail for <i>user</i>@<b>foo.org</b> via the <b>slow</b> transport to a + mail exchanger for <b>foo.org</b>. The <b>slow</b> transport could be + something that runs at most one delivery process at a + time: + <b>foo.org</b> <b>slow:</b> - 1 + When no <i>transport</i> is specified, the default transport is + used, as specified via the <b>default</b><i>_</i><b>transport</b> configuration + parameter. The following sends all mail for <b>foo.org</b> and + its subdomains to host <b>gateway.foo.org</b>: + <b>foo.org</b> <b>:[gateway.foo.org]</b> + <b>.foo.org</b> <b>:[gateway.foo.org]</b> + In the above example, the [] are used to suppress MX + lookups. The result would likely point to your local + machine. + In the case of delivery via SMTP, one may specify <i>host-</i> + <i>name</i>:<i>service</i> instead of just a host: + <b>foo.org</b> <b>smtp:bar.org:2025</b> -TRANSPORT(5) TRANSPORT(5) + This directs mail for <i>user</i>@<b>foo.org</b> to host <b>bar.org</b> port + <b>2025</b>. Instead of a numerical port a symbolic name may be + used. Specify [] around the hostname in order to disable + MX lookups. - When no <i>nexthop</i> host name is specified, the destination domain - name is used instead. For example, the following directs mail for - <i>user</i>@<b>foo.org</b> via the <b>slow</b> transport to a mail - exchanger for <b>foo.org</b>. The <b>slow</b> transport could be - something that runs at most one delivery process at a time: - <b>foo.org</b> <b>slow:</b> - When no <i>transport</i> is specified, the default transport is - used, as specified via the <b>default</b><i>_</i><b>transport</b> configuration - parameter. The following sends all mail for <b>foo.org</b> and its - subdomains to host <b>gateway.foo.org</b>: + 2 - <b>foo.org</b> <b>:[gateway.foo.org]</b> - <b>.foo.org</b> <b>:[gateway.foo.org]</b> - In the above example, the [] are used to suppress MX lookups. - The result would likely point to your local machine. - In the case of delivery via SMTP, one may specify - <i>hostname</i>:<i>service</i> instead of just a host: - <b>foo.org</b> <b>smtp:bar.org:2025</b> - This directs mail for <i>user</i>@<b>foo.org</b> to host <b>bar.org</b> - port <b>2025</b>. Instead of a numerical port a symbolic name may be - used. Specify [] around the destination in order to disable MX lookups. +TRANSPORT(5) TRANSPORT(5) + The error mailer can be used to bounce mail: - <b>.foo.org</b> <b>error:mail</b> <b>for</b> <b>*.foo.org</b> <b>is</b> <b>not</b> <b>deliverable</b> + <b>.foo.org</b> <b>error:mail</b> <b>for</b> <b>*.foo.org</b> <b>is</b> <b>not</b> <b>deliv-</b> + <b>erable</b> + + This causes all mail for <i>user</i>@<i>anything</i><b>.foo.org</b> to be + bounced. + +<b>REGULAR</b> <b>EXPRESSION</b> <b>TABLES</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</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + + Each pattern is a regular expression that is applied to + the entire domain being looked up. Thus, <i>some.domain.hier-</i> + <i>archy</i> is not broken up into parent domains. - This causes all mail for <i>user</i>@<i>anything</i><b>foo.org</b> - to be bounced. + Patterns are applied in the order as specified in the + table, until a pattern is found that matches the search + string. + + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. <b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this topic. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> + The following <b>main.cf</b> parameters are especially relevant + to this topic. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> command after a configuration change. <b>transport</b><i>_</i><b>maps</b> @@ -118,32 +175,33 @@ TRANSPORT(5) TRANSPORT(5) Other parameters of interest: <b>default</b><i>_</i><b>transport</b> - The transport to use when no transport is explic- + The transport to use when no transport is explic- itly specified. <b>relayhost</b> The default host to send to when no transport table entry matches. +<b>SEE</b> <b>ALSO</b> + <a href="postmap.1.html">postmap(1)</a> create mapping table + <a href="trivial-rewrite.8.html">trivial-rewrite(8)</a> rewrite and resolve addresses + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. - 2 - + 3 -TRANSPORT(5) TRANSPORT(5) -<b>SEE</b> <b>ALSO</b> - <a href="postmap.1.html">postmap(1)</a> create mapping table - <a href="trivial-rewrite.8.html">trivial-rewrite(8)</a> rewrite and resolve addresses +TRANSPORT(5) TRANSPORT(5) -<b>LICENSE</b> - The Secure Mailer license must be distributed with this - software. <b>AUTHOR(S)</b> Wietse Venema @@ -194,7 +252,15 @@ TRANSPORT(5) TRANSPORT(5) - 3 + + + + + + + + + 4 </pre> </body> </html> diff --git a/gnu/dist/postfix/html/trivial-rewrite.8.html b/gnu/dist/postfix/html/trivial-rewrite.8.html index 08ff75d86be..f2412581479 100644 --- a/gnu/dist/postfix/html/trivial-rewrite.8.html +++ b/gnu/dist/postfix/html/trivial-rewrite.8.html @@ -43,8 +43,8 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) The <b>trivial-rewrite</b> daemon by default only distin- guishes between local and non-local mail. For finer - control over mail routing, use the optional <a href="transport.5.html"><b>trans-</b> - <b>port</b>(5)</a> lookup table. + control over mail routing, use the optional <a href="transport.5.html"><b>trans-</b></a> + <a href="transport.5.html"><b>port</b>(5)</a> lookup table. This program expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager. @@ -109,21 +109,21 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) Rewrite <i>site</i>!<i>user</i> to <i>user</i>@<i>site</i>. <b>Routing</b> - <b>default</b><i>_</i><b>transport</b> - The default transport to use when no transport is - explicitly given in the <a href="transport.5.html"><b>transport</b>(5)</a> table. - - <b>relayhost</b> - The default host to send mail to when no entry is - matched in the <a href="transport.5.html"><b>transport</b>(5)</a> table. + <b>local</b><i>_</i><b>transport</b> + Where to deliver mail for destinations that match + $<b>mydestination</b> or $<b>inet</b><i>_</i><b>interfaces</b>. The default + transport is <b>local</b>. - When no <b>relayhost</b> is specified, mail is routed - directly to the destination's mail exchanger. + Syntax is <i>transport</i>:<i>nexthop</i>; see <a href="transport.5.html"><b>transport</b>(5)</a> for + details. The :<i>nexthop</i> part is optional. - <b>transport</b><i>_</i><b>maps</b> - List of tables with <i>domain</i> to (<i>transport,</i> <i>nexthop</i>) - mappings. + <b>default</b><i>_</i><b>transport</b> + Where to deliver non-local mail when no information + is explicitly given in the <a href="transport.5.html"><b>transport</b>(5)</a> table. The + default transport is <b>smtp</b>. + Syntax is <i>transport</i>:<i>nexthop</i>; see <a href="transport.5.html"><b>transport</b>(5)</a> for + details. The :<i>nexthop</i> part is optional. @@ -137,13 +137,24 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) + <b>relayhost</b> + The default host to send non-local mail to when no + entry is matched in the <a href="transport.5.html"><b>transport</b>(5)</a> table. + + When no <b>relayhost</b> is specified, mail is routed + directly to the destination's mail exchanger. + + <b>transport</b><i>_</i><b>maps</b> + List of tables with <i>domain</i> to (<i>transport,</i> <i>nexthop</i>) + mappings. + <b>SEE</b> <b>ALSO</b> <a href="master.8.html">master(8)</a> process manager syslogd(8) system logging <a href="transport.5.html">transport(5)</a> transport table format <b>LICENSE</b> - The Secure Mailer license must be distributed with this + The Secure Mailer license must be distributed with this software. <b>AUTHOR(S)</b> @@ -183,17 +194,6 @@ TRIVIAL-REWRITE(8) TRIVIAL-REWRITE(8) - - - - - - - - - - - 3 diff --git a/gnu/dist/postfix/html/uce.html b/gnu/dist/postfix/html/uce.html index ce35418fba4..6333a381cfa 100644 --- a/gnu/dist/postfix/html/uce.html +++ b/gnu/dist/postfix/html/uce.html @@ -109,7 +109,8 @@ is allowed in message headers. <dt>Syntax: <dd>Specify a list of zero or more lookup tables. Whenever a header -matches a table, a REJECT result means reject the message. +matches a table, a REJECT result means reject the message, and a +SKIP result means delete the header from the message. <p> @@ -216,9 +217,9 @@ result as another list of UCE restrictions. The <a name="reject_maps_rbl"> -<dt> <b>reject_maps_rbl</b> <dd> Reject the request when the client -network address is listed under any of the domains listed in <a -href="#maps_rbl_domains">$maps_rbl_domains</a>. The <b> +<dt> <b>reject_maps_rbl</b> <dd> Reject the request when the reversed +client network address is listed under any of the domains listed +in <a href="#maps_rbl_domains">$maps_rbl_domains</a>. The <b> maps_rbl_reject_code</b> parameter specifies the response code for rejected requests (default: <b>554</b>). @@ -979,7 +980,7 @@ appear as part of a client hostname/address restriction list. <dt>Default: -<dd><b>maps_rbl_domains = rbl.maps.vix.com, dul.maps.vix.com</b> +<dd><b>maps_rbl_domains = blackholes.mail-abuse.org</b> <p> diff --git a/gnu/dist/postfix/html/virtual.5.html b/gnu/dist/postfix/html/virtual.5.html index 91f57e9b7bd..720d763b6ae 100644 --- a/gnu/dist/postfix/html/virtual.5.html +++ b/gnu/dist/postfix/html/virtual.5.html @@ -12,53 +12,53 @@ VIRTUAL(5) VIRTUAL(5) <b>postmap</b> <b>/etc/postfix/virtual</b> <b>DESCRIPTION</b> - The optional <b>virtual</b> table specifies redirections for - local and non-local recipients or domains. The redirec- - tions are used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon. The redirections - are recursive. + The optional <b>virtual</b> table specifies address redirections + for local and non-local recipients or domains. The redi- + rections are used by the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> daemon. The redirec- + tions are recursive. - The <b>virtual</b> redirection is applied only to the recipient - envelope address, and does not affect message headers. + The <b>virtual</b> redirection is applied only to recipient enve- + lope addresses, and does not affect message headers. Think Sendmail rule set <b>S0</b>, if you like. Use <a href="canonical.5.html"><b>canonical</b>(5)</a> mapping to rewrite header and envelope addresses in gen- eral. - The file 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. After an update it may - take a minute or so before the change becomes visible. - Issue a <b>postfix</b> <b>reload</b> command to eliminate the delay. + Normally, the <b>virtual</b> 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. Execute the command + <b>postmap</b> <b>/etc/postfix/virtual</b> in order to rebuild the + indexed file after changing the text file. - Typical support for a virtual domain looks like the fol- - lowing: + When the table is provided via other means such as NIS, + LDAP or SQL, the same lookups are done as for ordinary + indexed files. - <i>virtual.domain</i> <i>anything</i> (right-hand content does not matter) - <i>user1@virtual.domain</i> <i>address1</i> - <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> + Alternatively, the table can be provided as a regular- + expression map where patterns are given as regular expres- + sions. In that case, the lookups are done in a slightly + different way as described below. - With this, the SMTP server accepts mail for <i>virtual.domain</i> - and rejects mail for <i>unknown</i>@<i>virtual.domain</i> as undeliver- - able. +<b>POSTFIX-STYLE</b> <b>VIRTUAL</b> <b>DOMAINS</b> + With a Postfix-style virtual domain, the virtual domain + has its own user name space. Local (i.e. non-virtual) + usernames are not visible in a Postfix-style virtual + domain. In particular, local <a href="aliases.5.html"><b>aliases</b>(5)</a> and mailing lists + are not visible as <i>localname@virtual.domain</i>. - The format of the virtual table is as follows, mappings - being tried in the order as listed in this manual page: - - blanks and comments - Blank lines are ignored, as are lines beginning - with `#'. + Use a Sendmail-style virtual domain (see below) if local + usernames, <a href="aliases.5.html"><b>aliases</b>(5)</a> or mailing lists should be visible + as <i>localname@virtual.domain</i>. - <i>user</i>@<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for <i>user</i>@<i>domain</i> is redirected to <i>address</i>. - This form has the highest precedence. + Support for a Postfix-style virtual domain looks like: - <i>user</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for <i>user</i>@<i>site</i> is redirected to <i>address</i> when - <i>site</i> is equal to $<b>myorigin</b>, when <i>site</i> is listed in - $mydestination, or when it is listed in - $<i>inet_interfaces</i>. + /etc/postfix/virtual: + <i>virtual.domain</i> <i>anything</i> (right-hand content does not matter) + <i>postmaster@virtual.domain</i> <i>postmaster</i> + <i>user1@virtual.domain</i> <i>address1</i> + <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> - This functionality overlaps with functionality of - the local <i>alias</i>(5) database. The difference is that + The <i>virtual.domain</i> <i>anything</i> entry is required for a @@ -71,60 +71,60 @@ VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) - <b>virtual</b> mapping can be applied to non-local - addresses. + Postfix-style virtual domain. - @<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> - Mail for any user in <i>domain</i> is redirected to - <i>address</i>. This form has the lowest precedence. + Do not list a Postfix-style virtual domain in the <b>main.cf</b> + <b>mydestination</b> configuration parameter. Such an entry is + required only for a Sendmail-style virtual domain. - In all the above forms, when <i>address</i> has the form @<i>other-</i> - <i>domain</i>, the result is the same user in <i>otherdomain</i>. This - works for the first address in the expansion only. + With a Postfix-style virtual domain, the Postfix SMTP + server accepts mail for <i>known-user@virtual.domain</i> and + rejects mail for <i>unknown-user</i>@<i>virtual.domain</i> as undeliver- + able. -<b>ADDRESS</b> <b>EXTENSION</b> - When the search fails, and the address localpart contains - the optional recipient delimiter (e.g., <i>user+foo</i>@<i>domain</i>), - the search is repeated for the unextended address (e.g. - <i>user</i>@<i>domain</i>), and the unmatched address extension is prop- - agated to the result of expansion. The matching order is: - <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>SENDMAIL-STYLE</b> <b>VIRTUAL</b> <b>DOMAINS</b> + With a Sendmail-style virtual domain, every local (i.e. + non-virtual) username is visible in the virtual domain. In + particular, every local alias and mailing list is visible + as <i>localname@virtual.domain</i>. -<b>BUGS</b> - The table format does not understand quoting conventions. + Use a Postfix-style virtual domain (see above) if local + usernames, <a href="aliases.5.html"><b>aliases</b>(5)</a> or mailing lists should not be visi- + ble as <i>localname@virtual.domain</i>. -<b>CONFIGURATION</b> <b>PARAMETERS</b> - The following <b>main.cf</b> parameters are especially relevant - to this topic. See the Postfix <b>main.cf</b> file for syntax - details and for default values. Use the <b>postfix</b> <b>reload</b> - command after a configuration change. + Support for a Sendmail-style virtual domain looks like: - <b>virtual</b><i>_</i><b>maps</b> - List of virtual mapping tables. + /etc/postfix/main.cf: + mydestination = $myhostname localhost.$mydomain $mydomain + <i>virtual.domain</i> - Other parameters of interest: + /etc/postfix/virtual: + <i>user1@virtual.domain</i> <i>address1</i> + <i>user2@virtual.domain</i> <i>address2,</i> <i>address3</i> - <b>inet</b><i>_</i><b>interfaces</b> - The network interface addresses that this system - receives mail on. + The <b>main.cf</b> <b>mydestination</b> entry is required for a Send- + mail-style virtual domain. - <b>mydestination</b> - List of domains that this mail system considers - local. + Do not specify a <i>virtual.domain</i> <i>whatever</i> virtual map entry + for a Sendmail-style virtual domain. Such an entry is + required only with a Postfix-style virtual domain. - <b>myorigin</b> - The domain that is appended to locally-posted mail. + With a Sendmail-style virtual domain, the Postfix local + delivery agent delivers mail for an unknown <i>user</i>@<i>vir-</i> + <i>tual.domain</i> to a local (i.e. non-virtual) user that has + the same name; if no such recipient exists, the Postfix + local delivery agent bounces the mail to the sender. - <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> - Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> - addresses. +<b>TABLE</b> <b>FORMAT</b> + The format of the virtual table is as follows, mappings + being tried in the order as listed in this manual page: -<b>SEE</b> <b>ALSO</b> - <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail - <a href="postmap.1.html">postmap(1)</a> create mapping table + blanks and comments + Blank lines are ignored, as are lines beginning + with `#'. -<b>LICENSE</b> - The Secure Mailer license must be distributed with this + leading whitespace + Lines that begin with whitespace continue the @@ -137,64 +137,130 @@ VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) VIRTUAL(5) - software. - -<b>AUTHOR(S)</b> - Wietse Venema - IBM T.J. Watson Research - P.O. Box 704 - Yorktown Heights, NY 10598, USA - - - - - - - - - - - + previous line. + <i>pattern</i> <i>result</i> + When <i>pattern</i> matches a mail address, replace it by + the corresponding <i>result</i>. + 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: + <i>user</i>@<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for <i>user</i>@<i>domain</i> is redirected to <i>address</i>. + This form has the highest precedence. + <i>user</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for <i>user</i>@<i>site</i> is redirected to <i>address</i> when + <i>site</i> is equal to $<b>myorigin</b>, when <i>site</i> is listed in + $mydestination, or when it is listed in + $<i>inet_interfaces</i>. + This functionality overlaps with functionality of + the local <i>alias</i>(5) database. The difference is that + <b>virtual</b> mapping can be applied to non-local + addresses. + @<i>domain</i> <i>address,</i> <i>address,</i> <i>...</i> + Mail for any user in <i>domain</i> is redirected to + <i>address</i>. This form has the lowest precedence. + In all the above forms, when <i>address</i> has the form @<i>other-</i> + <i>domain</i>, the result is the same user in <i>otherdomain</i>. This + works for the first address in the expansion only. +<b>ADDRESS</b> <b>EXTENSION</b> + When the search fails, and the address localpart contains + the optional recipient delimiter (e.g., <i>user+foo</i>@<i>domain</i>), + the search is repeated for the unextended address (e.g. + <i>user</i>@<i>domain</i>), and the unmatched address extension is prop- + agated to the result of expansion. The matching order is: + <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</b> <b>EXPRESSION</b> <b>TABLES</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</b><i>_</i><b>table</b>(5)</a> or <a href="pcre_table.5.html"><b>pcre</b><i>_</i><b>table</b>(5)</a>. + Each pattern is a regular expression that is applied to + the entire address being looked up. Thus, <i>user@domain</i> mail + addresses are not broken 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>. + Patterns are applied in the order as specified in the + 3 +VIRTUAL(5) VIRTUAL(5) + table, until a pattern is found that matches the search + string. + Results are the same as with normal indexed file lookups, + with the additional feature that parenthesized substrings + from the pattern can be interpolated as <b>$1</b>, <b>$2</b> and so on. +<b>BUGS</b> + The table format does not understand quoting conventions. +<b>CONFIGURATION</b> <b>PARAMETERS</b> + The following <b>main.cf</b> parameters are especially relevant + to this topic. See the Postfix <b>main.cf</b> file for syntax + details and for default values. Use the <b>postfix</b> <b>reload</b> + command after a configuration change. + <b>virtual</b><i>_</i><b>maps</b> + List of virtual mapping tables. + Other parameters of interest: + <b>inet</b><i>_</i><b>interfaces</b> + The network interface addresses that this system + receives mail on. + <b>mydestination</b> + List of domains that this mail system considers + local. + <b>myorigin</b> + The domain that is appended to locally-posted mail. + <b>owner</b><i>_</i><b>request</b><i>_</i><b>special</b> + Give special treatment to <b>owner-</b><i>xxx</i> and <i>xxx</i><b>-request</b> + addresses. +<b>SEE</b> <b>ALSO</b> + <a href="cleanup.8.html">cleanup(8)</a> canonicalize and enqueue mail + <a href="postmap.1.html">postmap(1)</a> create mapping table + <a href="pcre_table.5.html">pcre_table(5)</a> format of PCRE tables + <a href="regexp_table.5.html">regexp_table(5)</a> format of POSIX regular expression tables +<b>LICENSE</b> + The Secure Mailer license must be distributed with this + software. +<b>AUTHOR(S)</b> + Wietse Venema + IBM T.J. Watson Research + P.O. Box 704 + Yorktown Heights, NY 10598, USA - 3 + 4 </pre> </body> </html> |
