summaryrefslogtreecommitdiff
path: root/gnu/dist/postfix/html/basic.html
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/dist/postfix/html/basic.html')
-rw-r--r--gnu/dist/postfix/html/basic.html96
1 files changed, 85 insertions, 11 deletions
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>