Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- centos:mail_c7:postfix3_4 [27.01.2019 20:02. ] – [manpage] django
+++ centos:mail_c7:postfix3_4 [22.07.2020 20:09. ] (aktuell) – [Reject-Regeln] django
@@ Zeile 18: / Zeile 18: @@
   - Anschließend wechseln wir in das Konfigurationsverzeichnis //**/etc/postfix/**//. <code> # cd /etc/postfix</code>
   - Nun löschen __oder__ verschieben wir die nicht benötigten Dateien:
-    - **löschen** <code> # rm access canonical generic header_checks relocated virtual transport \
+    - **löschen** <code> # rm canonical generic header_checks relocated virtual transport \
       main.cf main.cf.proto master.cf.proto -f</code>
-    - **verschieben** <code> # mkdir -p /etc/postfix/.orig/</code><code> # mv access canonical generic header_checks relocated virtual transport \
+    - **verschieben** <code> # mkdir -p /etc/postfix/.orig/</code><code> # mv canonical generic header_checks relocated virtual transport \
       main.cf main.cf.proto master.cf.proto /etc/postfix/.orig/ -f</code>
   - Anlegen einer leeren **main.cf**. <code> # touch main.cf</code>
@@ Zeile 26: / Zeile 26: @@
 Somit befinden sich nun nur noch zwei Dateien im Verzeichnis //**/etc/postfix**//.
 <code>/etc/postfix/
+├── access
 ├── dynamicmaps.cf
 ├── dynamicmaps.cf.d
@@ Zeile 343: / Zeile 344: @@
 virtual_transport = lmtp:[imap.dmz.nausch.org]:24
 </code>
+=== relay_domains ===
+  * **relay_domains** Lookup-Tabelle zur Definition der Domänen für die unser Mailserver Nachricht annehmen soll. \\ **relay_domains.db** Datenbankfile zur //relay_domains//-Datei. <code> # vim /etc/postfix/relay_domains</code> <file bash /etc/postfix/relay_domains># Django : 2019-01-27
+# Kapitel 12.1 Postfix als eingehendes Mailrelay vor einem anderen Server
+# Lookup-Tabelle zur Definition der Domänen für die unser Mailserver Nachricht annehmen soll.
+# Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
+#
+#                  $ postmap /etc/postfix/relay_domains
+#
+# die zugehörige Datenbank erzeugt werden.
+#
+# Relevant ist erst eimal nur die erste Spalte. Die zweite Spalte dient nur zum Erhalten der Tabellenstruktur und
+# kann daher z.B. als Hinweisfeld zum Dokumentieren verwendet werden.
+# Beispiel:
+# omni128.de                    meine eigene Domäne
+#
+# Da für jede Domäne auch ein Transportweg definiert werden muss, erledigen wir die Definition des selbigen gleich
+# hier in dieser Tabelle, in dem wir die Spalte zwei hierzu verwenden.
+#nausch.org                     lmtp:[10.0.0.70]:24</file>
+=== transport_maps ===
+  * **transport_maps** Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der Zustellung an einen weiteren Mailserver. \\ **transport_maps.db** Datenbankfile zur //transport_maps//-Datei. <code> # vim /etc/postfix/transport_maps</code> <file bash /etc/postfix/transport_maps># Django : 2019-01-27
+# Kapitel 5.2.5 transport-Tabelle: Abweichende Zustellung
+# Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der
+# Zustellung an einen weiteren Mailserver. Nach dem Ändern und/oder
+# Erweitern der Tabelle, muß noch mittels:
+#
+#               $ postmap /etc/postfix/transport_maps
+#
+# die zugehörige Datenbank erzeugt werden.
+#
+# Alle eMails, die an Subdomains von nausch.org gerichtet sind
+# ("." am Anfang der Zeile!) werden an den/die Mailserver von
+# intra.nausch.org (MX-Records) weitergeleitet. (keine "["-Klammern!)
+#.nausch.org                            smtp:intra.nausch.org
+# Alle eMails, die an die Domain tachtler.net gerichtet sind, werden an
+# den bzw. die Mailserver der Mail-Domäne t-offline.de (MX-Records)
+# weitergeleitet. (keine "["-Klammern!)
+# tachtler.net                          smtp:t-offline.de
+# Mails an backup.nausch.org werden an den Mailserver (A-Record) auf Port 25
+# mit Namen mail.intra.nausch.org geschickt.
+#backup.nausch.org                      smtp:[mail.intra.nausch.org]:25</file>
 ==== Queueing ====
@@ Zeile 497: / Zeile 542: @@
    # wget http://postfix.state-of-mind.de/bounce-templates/bounce.de-DE.cf
-\\ \\ \\
-<WRAP center round todo 30%>
-FIXME FIXME FIXME
-  * //**do geds weida!**//
-FIXME FIXME FIXME
-</WRAP>
-\\ \\ \\
 ===== Lookup-Tabellen =====
@@ Zeile 1070: / Zeile 1101: @@
 === Access-Dateien ===
 == check_client_access ==
-  * **access_client** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Basis ihrer IP-Adresse. Damit wir auch Netzbereiche in der Form **10.0.10.1/28**, also mit IP-Adressen mit einer Netzmaske versehen, nutzen können, dürfen wir hier nicht **btree** als Datenbankformat verwenden! Wir greifen hier auf **cidr**-//Maps// zurück! <code> # vim /etc/postfix/access_client</code> <file bash /etc/postfix/access_client># Django : 2012-02-06
+  * **access_client** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Basis ihrer IP-Adresse. Damit wir auch Netzbereiche in der Form **10.0.10.1/28**, also mit IP-Adressen mit einer Netzmaske versehen, nutzen können, dürfen wir hier nicht **btree** als Datenbankformat verwenden! Wir greifen hier auf **cidr**-//Maps// zurück! <code> # vim /etc/postfix/access_client</code> <file bash /etc/postfix/access_client># Django : 2019-01-27
 # Kapitel 5.2.7 access-Tabelle: Wer darf, wer darf nicht?
 # Tabelle zum black- und whitelisten einzelner Hosts auf Basis ihrer
@@ Zeile 1086: / Zeile 1117: @@
 == check_helo_access ==
-  * **access_helo** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Grund seines HELO-Namens. \\  **access_helo.db** Datenbankfile zur //access_helo//-Datei. <code> # vim /etc/postfix/access_helo</code> <file bash /etc/postfix/access_helo># Django : 2012-02-06
+  * **access_helo** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Grund seines HELO-Namens. \\  **access_helo.db** Datenbankfile zur //access_helo//-Datei. <code> # vim /etc/postfix/access_helo</code> <file bash /etc/postfix/access_helo># Django : 2019-01-27
 # Kapitel 5.2.7 access-Tabelle: Wer darf, wer darf nicht?
 # Tabelle zum black- und whitelisten einzelner Hosts auf Grund seines
@@ Zeile 1098: / Zeile 1129: @@
 == check_recipient_access-rfc ==
-  * **access_recipient-rfc** Access-Tabelle zum Black- und Whitelisten einzelner aufgaben- oder funktionsgebundener E-Mail-Adressen (Role-Accounts). \\ **access_recipient-rfc.db** Datenbankfile zur //access_recipient-rfc//-Datei. <code> # vim /etc/postfix/access_recipient-rfc</code> <file bash /etc/postfix/access_recipient-rfc># Django : 2012-02-06
+  * **access_recipient-rfc** Access-Tabelle zum Black- und Whitelisten einzelner aufgaben- oder funktionsgebundener E-Mail-Adressen (Role-Accounts). \\ **access_recipient-rfc.db** Datenbankfile zur //access_recipient-rfc//-Datei. <code> # vim /etc/postfix/access_recipient-rfc</code> <file bash /etc/postfix/access_recipient-rfc># Django : 2019-01-27
 # Postmaster, abuse und andere aufgaben- oder funktionsgebundene eMail-Adressen
 # (Role-Accounts) whitelisten. Nach dem Ändern und/oder Erweiterrn der Tabelle,
@@ Zeile 1107: / Zeile 1138: @@
 abuse@          OK
 postmaster@     OK
+webmaster@      OK
 </file>
 == check_recipient_access ==
-  * **access_recipient** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Grund der Empfänger-eMailadresse. \\ **access_recipient.db** Datenbankfile zur //access_recipient//-Datei. <code> # vim /etc/postfix/access_recipient</code> <file bash /etc/postfix/access_recipient># Django : 2012-02-06
+  * **access_recipient** Access-Tabelle zum Black- und Whitelisten einzelner Hosts auf Grund der Empfänger-eMailadresse. \\ **access_recipient.db** Datenbankfile zur //access_recipient//-Datei. <code> # vim /etc/postfix/access_recipient</code> <file bash /etc/postfix/access_recipient># Django : 2019-01-27
 # Kapitel 5.2.7 access-Tabelle: Wer darf, wer darf nicht?
 # Tabelle zum black- und whitelisten einzelne Empfänger auf Basis ihrer
@@ Zeile 1123: / Zeile 1155: @@
 == check_sender_access ==
-  * **access_sender** Access-Tabelle zum Black- und Whitelisten einzelner Absender auf Grund der Absender-eMailadresse. \\ **access_sender.db** Datenbankfile zur //access_sender//-Datei. <code> # vim /etc/postfix/access_sender</code> <file bash /etc/postfix/access_sender># Django : 2012-02-06
+  * **access_sender** Access-Tabelle zum Black- und Whitelisten einzelner Absender auf Grund der Absender-eMailadresse. \\ **access_sender.db** Datenbankfile zur //access_sender//-Datei. <code> # vim /etc/postfix/access_sender</code> <file bash /etc/postfix/access_sender># Django : 2019-01-27
 # Kapitel 5.2.7 access-Tabelle: Wer darf, wer darf nicht?
 # Tabelle zum black- und whitelisten einzelner Absender auf Basis ihrer
@@ Zeile 1145: / Zeile 1177: @@
 In der Manpage zu **canonical** bzw. in der Datei //**/etc/postfix/canonical**// finden wir detaillierte Informationen zur **canonical - Postfix canonical table format**.
    # man 5 canonical
-<code>CANONICAL(5)                         File Formats Manual                        CANONICAL(5)
+<code>CANONICAL(5)                                   File Formats Manual                                   CANONICAL(5)
 NAME
@@ Zeile 1158: / Zeile 1190: @@
 DESCRIPTION
-       The  optional canonical(5) table specifies an address mapping for local and non-local
+       The  optional  canonical(5) table specifies an address mapping for local and non-local addresses. The map‐
-       addresses. The mapping is used by the cleanup(8) daemon, before mail is  stored  into
+       ping is used by the cleanup(8) daemon, before mail is stored into  the  queue.   The  address  mapping  is
-       the queue.  The address mapping is recursive.
+       recursive.
-       Normally,  the canonical(5) table is specified as a text file that serves as input to
+       Normally,  the  canonical(5) table is specified as a text file that serves as input to the postmap(1) com‐
-       the postmap(1) command.  The result, an indexed file in dbm or db format, is used for
+       mand.  The result, an indexed file in dbm or db format, is used for fast searching  by  the  mail  system.
-       fast  searching by the mail system. Execute the command "postmap /etc/postfix/canoni‐
+       Execute  the command "postmap /etc/postfix/canonical" to rebuild an indexed file after changing the corre‐
-       cal" to rebuild an indexed file after changing the corresponding text file.
+       sponding text file.
-       When the table is provided via other means such as NIS, LDAP or SQL, the same lookups
+       When the table is provided via other means such as NIS, LDAP or SQL, the same  lookups  are  done  as  for
-       are done as for ordinary indexed files.
+       ordinary indexed files.
-       Alternatively,  the  table can be provided as a regular-expression map where patterns
+       Alternatively,  the  table can be provided as a regular-expression map where patterns are given as regular
-       are given as regular expressions, or lookups can be directed to TCP-based server.  In
+       expressions, or lookups can be directed to TCP-based server. In those cases, the lookups  are  done  in  a
-       those  cases,  the  lookups  are  done in a slightly different way as described below
+       slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       By default the canonical(5) mapping  affects  both  message  header  addresses  (i.e.
+       By  default  the  canonical(5)  mapping  affects both message header addresses (i.e. addresses that appear
-       addresses  that  appear inside messages) and message envelope addresses (for example,
+       inside messages) and message envelope addresses (for example, the addresses that are used in SMTP protocol
-       the addresses that are used in SMTP protocol commands). This is controlled  with  the
+       commands). This is controlled with the canonical_classes parameter.
-       canonical_classes parameter.
-       NOTE: Postfix versions 2.2 and later rewrite message headers from remote SMTP clients
+       NOTE:  Postfix  versions 2.2 and later rewrite message headers from remote SMTP clients only if the client
-       only if the client matches the  local_header_rewrite_clients  parameter,  or  if  the
+       matches the local_header_rewrite_clients parameter, or if the  remote_header_rewrite_domain  configuration
-       remote_header_rewrite_domain  configuration parameter specifies a non-empty value. To
+       parameter  specifies  a non-empty value. To get the behavior before Postfix 2.2, specify "local_header_re‐
-       get  the  behavior  before  Postfix  2.2,  specify  "local_header_rewrite_clients   =
+       write_clients = static:all".
-       static:all".
-       Typically,  one  would  use  the  canonical(5) table to replace login names by First‐
+       Typically, one would use the canonical(5) table to replace login names by Firstname.Lastname, or to  clean
-       name.Lastname, or to clean up addresses produced by legacy mail systems.
+       up addresses produced by legacy mail systems.
-       The canonical(5) mapping is not to be confused with virtual  alias  support  or  with
+       The  canonical(5)  mapping  is  not  to  be confused with virtual alias support or with local aliasing. To
-       local  aliasing. To change the destination but not the headers, use the virtual(5) or
+       change the destination but not the headers, use the virtual(5) or aliases(5) map instead.
-       aliases(5) map instead.
 CASE FOLDING
-       The search string is folded to lowercase before database lookup. As of  Postfix  2.3,
+       The search string is folded to lowercase before database lookup. As of Postfix 2.3, the search  string  is
-       the  search  string  is  not case folded with database types such as regexp: or pcre:
+       not  case folded with database types such as regexp: or pcre: whose lookup fields can match both upper and
-       whose lookup fields can match both upper and lower case.
+       lower case.
 TABLE FORMAT
@@ Zeile 1205: / Zeile 1233: @@
        blank lines and comments
-              Empty lines and whitespace-only lines are ignored, as are  lines  whose  first
+              Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace  charac‐
-              non-whitespace character is a `#'.
+              ter is a `#'.
        multi-line text
-              A logical line starts with non-whitespace text. A line that starts with white‐
+              A logical line starts with non-whitespace text. A line that starts with whitespace continues a log‐
-              space continues a logical line.
+              ical line.
 TABLE SEARCH ORDER
-       With lookups from indexed files such as DB or DBM, or from networked tables  such  as
+       With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, each
-       NIS, LDAP or SQL, patterns are tried in the order as listed below:
+       user@domain query produces a sequence of query patterns as described below.
+       Each  query  pattern  is sent to each specified lookup table before trying the next query pattern, until a
+       match is found.
        user@domain address
               Replace user@domain by address. This form has the highest precedence.
-              This  is useful to clean up addresses produced by legacy mail systems.  It can
+              This is useful to clean up addresses produced by legacy mail systems.  It can also be used to  pro‐
-              also be used to produce Firstname.Lastname style addresses, but see below  for
+              duce Firstname.Lastname style addresses, but see below for a simpler solution.
-              a simpler solution.
        user address
-              Replace  user@site  by  address  when site is equal to $myorigin, when site is
+              Replace  user@site  by  address when site is equal to $myorigin, when site is listed in $mydestina‐
-              listed in  $mydestination,  or  when  it  is  listed  in  $inet_interfaces  or
+              tion, or when it is listed in $inet_interfaces or $proxy_interfaces.
-              $proxy_interfaces.
               This form is useful for replacing login names by Firstname.Lastname.
        @domain address
-              Replace other addresses in domain by address.  This form has the lowest prece‐
+              Replace other addresses in domain by address.  This form has the lowest precedence.
-              dence.
-              Note: @domain  is  a  wild-card.  When  this  form  is  applied  to  recipient
+              Note: @domain is a wild-card. When this form is applied to recipient addresses,  the  Postfix  SMTP
-              addresses,  the  Postfix SMTP server accepts mail for any recipient in domain,
+              server accepts mail for any recipient in domain, regardless of whether that recipient exists.  This
-              regardless of whether that recipient exists.  This may turn your  mail  system
+              may turn your mail system into a backscatter source: Postfix first accepts  mail  for  non-existent
-              into a backscatter source: Postfix first accepts mail for non-existent recipi‐
+              recipients  and  then  tries  to  return  that  mail  as "undeliverable" to the often forged sender
-              ents and then tries to return that mail as "undeliverable" to the often forged
+              address.
-              sender address.
 RESULT ADDRESS REWRITING
        The lookup result is subject to address rewriting:
-       ·      When the result has the form @otherdomain, the result becomes the same user in
+       ·      When the result has the form @otherdomain, the result becomes the same user in otherdomain.
-              otherdomain.
-       ·      When  "append_at_myorigin=yes",  append  "@$myorigin"  to  addresses   without
+       ·      When "append_at_myorigin=yes", append "@$myorigin" to addresses without "@domain".
-              "@domain".
-       ·      When  "append_dot_mydomain=yes",  append  ".$mydomain"  to  addresses  without
+       ·      When "append_dot_mydomain=yes", append ".$mydomain" to addresses without ".domain".
-              ".domain".
 ADDRESS EXTENSION
-       When a mail address  localpart  contains  the  optional  recipient  delimiter  (e.g.,
+       When a mail address localpart contains the  optional  recipient  delimiter  (e.g.,  user+foo@domain),  the
-       user+foo@domain),  the  lookup order becomes: user+foo@domain, user@domain, user+foo,
+       lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.
-       user, and @domain.
-       The propagate_unmatched_extensions parameter controls whether  an  unmatched  address
+       The  propagate_unmatched_extensions  parameter  controls  whether an unmatched address extension (+foo) is
-       extension (+foo) is propagated to the result of table lookup.
+       propagated to the result of table lookup.
 REGULAR EXPRESSION TABLES
-       This  section  describes  how the table lookups change when the table is given in the
+       This section describes how the table lookups change when the table is given in the form of regular expres‐
-       form of regular expressions. For a description of  regular  expression  lookup  table
+       sions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5).
-       syntax, see regexp_table(5) or pcre_table(5).
-       Each  pattern  is  a  regular  expression that is applied to the entire address being
+       Each  pattern  is  a  regular  expression  that  is  applied  to the entire address being looked up. Thus,
-       looked up. Thus, user@domain mail addresses are not broken up  into  their  user  and
+       user@domain mail addresses are not broken up into  their  user  and  @domain  constituent  parts,  nor  is
-       @domain constituent parts, nor is user+foo broken up into user and foo.
+       user+foo broken up into user and foo.
-       Patterns are applied in the order as specified in the table, until a pattern is found
+       Patterns  are  applied  in  the order as specified in the table, until a pattern is found that matches the
-       that matches the search string.
+       search string.
-       Results are the same as with indexed file lookups, with the additional  feature  that
+       Results are the same as with indexed file lookups, with the additional  feature  that  parenthesized  sub‐
-       parenthesized substrings from the pattern can be interpolated as $1, $2 and so on.
+       strings from the pattern can be interpolated as $1, $2 and so on.
 TCP-BASED TABLES
-       This  section  describes  how the table lookups change when lookups are directed to a
+       This section describes how the table lookups change when lookups are directed to a TCP-based server. For a
-       TCP-based server. For a description of the TCP  client/server  lookup  protocol,  see
+       description of the TCP client/server lookup protocol, see tcp_table(5).  This feature is not available  up
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
+       to and including Postfix version 2.4.
-       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses
+       Each  lookup  operation  uses the entire address once.  Thus, user@domain mail addresses are not broken up
-       are not broken up into their user and @domain constituent parts, nor is user+foo bro‐
+       into their user and @domain constituent parts, nor is user+foo broken up into user and foo.
-       ken up into user and foo.
        Results are the same as with indexed file lookups.
@@ Zeile 1291: / Zeile 1312: @@
 CONFIGURATION PARAMETERS
-       The  following  main.cf  parameters are especially relevant.  The text below provides
+       The following main.cf parameters are especially relevant.  The text below provides only a  parameter  sum‐
-       only a parameter summary. See postconf(5) for more details including examples.
+       mary. See postconf(5) for more details including examples.
        canonical_classes
@@ Zeile 1307: / Zeile 1328: @@
        propagate_unmatched_extensions
-              A list of address rewriting or forwarding mechanisms that propagate an address
+              A  list  of address rewriting or forwarding mechanisms that propagate an address extension from the
-              extension  from  the  original address to the result.  Specify zero or more of
+              original address to the result.  Specify zero  or  more  of  canonical,  virtual,  alias,  forward,
-              canonical, virtual, alias, forward, include, or generic.
+              include, or generic.
        Other parameters of interest:
        inet_interfaces
-              The network interface addresses that this system receives mail on.   You  need
+              The  network  interface  addresses  that  this system receives mail on.  You need to stop and start
-              to stop and start Postfix when this parameter changes.
+              Postfix when this parameter changes.
        local_header_rewrite_clients
-              Rewrite  message header addresses in mail from these clients and update incom‐
+              Rewrite message header addresses in mail from these clients and update  incomplete  addresses  with
-              plete addresses with the domain name in $myorigin or $mydomain;  either  don't
+              the  domain name in $myorigin or $mydomain; either don't rewrite message headers from other clients
-              rewrite  message headers from other clients at all, or rewrite message headers
+              at all, or rewrite message headers and update incomplete addresses with the domain specified in the
-              and  update  incomplete  addresses  with   the   domain   specified   in   the
               remote_header_rewrite_domain parameter.
        proxy_interfaces
-              Other interfaces that this machine receives mail on by way of a proxy agent or
+              Other  interfaces  that  this  machine  receives mail on by way of a proxy agent or network address
-              network address translator.
+              translator.
        masquerade_classes
-              List of address classes  subject  to  masquerading:  zero  or  more  of  enve‐
+              List of address classes subject to masquerading: zero or more of envelope_sender,  envelope_recipi‐
-              lope_sender, envelope_recipient, header_sender, header_recipient.
+              ent, header_sender, header_recipient.
        masquerade_domains
@@ Zeile 1348: / Zeile 1368: @@
        remote_header_rewrite_domain
-              Don't  rewrite  message headers from remote clients at all when this parameter
+              Don't  rewrite  message headers from remote clients at all when this parameter is empty; otherwise,
-              is empty; otherwise, rewrite message headers and append the  specified  domain
+              rewrite message headers and append the specified domain name to incomplete addresses.
-              name to incomplete addresses.
 SEE ALSO
@@ Zeile 1359: / Zeile 1378: @@
 README FILES
-       Use  "postconf readme_directory" or "postconf html_directory" to locate this informa‐
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
-       tion.
        DATABASE_README, Postfix lookup table overview
        ADDRESS_REWRITING_README, address rewriting guide
@@ Zeile 1373: / Zeile 1391: @@
        Yorktown Heights, NY 10598, USA
-                                                                                CANONICAL(5)
+       Wietse Venema
+       Google, Inc.
+8th Avenue
+       New York, NY 10011, USA
+                                                                                                     CANONICAL(5)
 </code>
 Auch hier editieren wir nicht die Vorlage- und Musterdatei //**/etc/postfix/canonical**//, sondern legen uns für die einzelnen Anwendungsfälle eigene Dateien an, auch wenn diese eventuell erst einmal ohne Inhalt sind. Wir haben so später kein Problem mehr, wenn wir ad hoc auf eine Anforderung schnell reagieren müssen.
@@ Zeile 1379: / Zeile 1402: @@
 === Canonical-Dateien ===
 == sender_canonical_maps ==
-  * **sender_canonical_maps** Lookup-Tabelle zum Umschreibungen von Absender eMail-Adressen im SMTP-Envelop und im Header der eMail. \\ **sender_canonical_maps.db** Datenbankfile zur //sender_canonical_maps//-Datei. <code> # vim /etc/postfix/sender_canonical_maps</code> <file bash /etc/postfix/sender_canonical_maps># Django : 2012-02-06
+  * **sender_canonical_maps** Lookup-Tabelle zum Umschreibungen von Absender eMail-Adressen im SMTP-Envelop und im Header der eMail. \\ **sender_canonical_maps.db** Datenbankfile zur //sender_canonical_maps//-Datei. <code> # vim /etc/postfix/sender_canonical_maps</code> <file bash /etc/postfix/sender_canonical_maps># Django : 2019-01-27
 # Kapitel 5.2.3 canonical-Tabelle: Ich versteck' mich
 # Lookup-Tabelle zum Umschreibungen von Absender eMail-Adressen im
 # SMTP-Envelop und im Header der eMail.
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/sender_canonical_maps
+#
+#          $ postmap /etc/postfix/sender_canonical_maps
+#
 # die zugehörige Datenbank erzeugt werden.
 #
@@ Zeile 1398: / Zeile 1423: @@
 </file>
 == recipient_canonical_maps ==
-  * **recipient_canonical_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. \\ **recipient_canonical_maps.db** Datenbankfile zur //recipient_canonical_maps//-Datei. <code> # vim /etc/postfix/recipient_canonical_maps</code> <file bash /etc/postfix/recipient_canonical_maps># Django : 2012-02-06
+  * **recipient_canonical_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. \\ **recipient_canonical_maps.db** Datenbankfile zur //recipient_canonical_maps//-Datei. <code> # vim /etc/postfix/recipient_canonical_maps</code> <file bash /etc/postfix/recipient_canonical_maps># Django : 2019-01-27
 # Kapitel 5.2.3 canonical-Tabelle: Ich versteck' mich
 # Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen
 # im SMTP-Envelop und im Header der eMail.
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/recipient_canonical_maps
+#
+#       $ postmap /etc/postfix/recipient_canonical_maps
+#
 # die zugehörige Datenbank erzeugt werden.
 #
@@ Zeile 1410: / Zeile 1437: @@
 #
 # genau eine Adresse umschreiben
-#swat@nausch.org        abuse@nausch.org
+swat@nausch.org        abuse@nausch.org
-#
-# Django : 2012-12-29
-# FaxMaster für hylafax definiert
-FaxMaster@nausch.org            django@nausch.org
-root@vml000020.dmz.nausch.org   django@nausch.org
-sks@keyserver.nausch.org        sks@vml000030.dmz.nausch.org
-# Django : 2014-05-09
-# test für dmarc.nausch.org
-#huhu@dmarc.nausch.org          dmarc-reports@vml000030.dmz.nausch.org
-huhu@dmarc.nausch.org           huhu@dmarc.nausch.org
-# Django : 2014-06-07
-# rewrite
-root@vml000080.dmz.nausch.org   django@nausch.org
 </file>
@@ Zeile 1441: / Zeile 1452: @@
 In der Manpage zu **generic** bzw. in der Datei //**/etc/postfix/generic**// finden wir detaillierte Informationen zur **generic - Postfix generic table format**.
    # man 5 generic
-<code>GENERIC(5)                           File Formats Manual                          GENERIC(5)
+<code>GENERIC(5)                                     File Formats Manual                                     GENERIC(5)
 NAME
@@ Zeile 1454: / Zeile 1465: @@
 DESCRIPTION
-       The  optional generic(5) table specifies an address mapping that applies when mail is
+       The  optional  generic(5)  table specifies an address mapping that applies when mail is delivered. This is
-       delivered. This is the opposite of canonical(5) mapping, which applies when  mail  is
+       the opposite of canonical(5) mapping, which applies when mail is received.
-       received.
-       Typically,  one would use the generic(5) table on a system that does not have a valid
+       Typically, one would use the generic(5) table on a system that does not have a valid Internet domain  name
-       Internet domain name and that uses something  like  localdomain.local  instead.   The
+       and  that uses something like localdomain.local instead.  The generic(5) table is then used by the smtp(8)
-       generic(5) table is then used by the smtp(8) client to transform local mail addresses
+       client to transform local mail addresses into valid Internet mail addresses  when  mail  has  to  be  sent
-       into valid Internet mail addresses when mail has to be sent across the Internet.  See
+       across the Internet.  See the EXAMPLE section at the end of this document.
-       the EXAMPLE section at the end of this document.
-       The  generic(5)  mapping  affects  both message header addresses (i.e. addresses that
+       The  generic(5) mapping affects both message header addresses (i.e. addresses that appear inside messages)
-       appear inside messages) and message envelope addresses (for  example,  the  addresses
+       and message envelope addresses (for example, the addresses that are used in SMTP protocol commands).
-       that are used in SMTP protocol commands).
-       Normally,  the  generic(5)  table is specified as a text file that serves as input to
+       Normally, the generic(5) table is specified as a text file that serves as input to the postmap(1) command.
-       the postmap(1) command.  The result, an indexed file in dbm or db format, is used for
+       The  result,  an  indexed file in dbm or db format, is used for fast searching by the mail system. Execute
-       fast searching by the mail system. Execute the command "postmap /etc/postfix/generic"
+       the command "postmap /etc/postfix/generic" to rebuild an indexed file  after  changing  the  corresponding
-       to rebuild an indexed file after changing the corresponding text file.
+       text file.
-       When the table is provided via other means such as NIS, LDAP or SQL, the same lookups
+       When  the  table  is  provided  via other means such as NIS, LDAP or SQL, the same lookups are done as for
-       are done as for ordinary indexed files.
+       ordinary indexed files.
-       Alternatively,  the  table can be provided as a regular-expression map where patterns
+       Alternatively, the table can be provided as a regular-expression map where patterns are given  as  regular
-       are given as regular expressions, or lookups can be directed to TCP-based server.  In
+       expressions,  or  lookups  can  be  directed to TCP-based server. In those case, the lookups are done in a
-       those case, the lookups are done in a slightly different way as described below under
+       slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
 CASE FOLDING
-       The search string is folded to lowercase before database lookup. As of  Postfix  2.3,
+       The search string is folded to lowercase before database lookup. As of Postfix 2.3, the search  string  is
-       the  search  string  is  not case folded with database types such as regexp: or pcre:
+       not  case folded with database types such as regexp: or pcre: whose lookup fields can match both upper and
-       whose lookup fields can match both upper and lower case.
+       lower case.
 TABLE FORMAT
@@ Zeile 1493: / Zeile 1500: @@
        blank lines and comments
-              Empty lines and whitespace-only lines are ignored, as are  lines  whose  first
+              Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace  charac‐
-              non-whitespace character is a `#'.
+              ter is a `#'.
        multi-line text
-              A logical line starts with non-whitespace text. A line that starts with white‐
+              A logical line starts with non-whitespace text. A line that starts with whitespace continues a log‐
-              space continues a logical line.
+              ical line.
 TABLE SEARCH ORDER
-       With lookups from indexed files such as DB or DBM, or from networked tables  such  as
+       With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, each
-       NIS, LDAP or SQL, patterns are tried in the order as listed below:
+       user@domain query produces a sequence of query patterns as described below.
+       Each  query  pattern  is sent to each specified lookup table before trying the next query pattern, until a
+       match is found.
        user@domain address
@@ Zeile 1508: / Zeile 1518: @@
        user address
-              Replace  user@site  by  address  when site is equal to $myorigin, when site is
+              Replace user@site by address when site is equal to $myorigin, when site is  listed  in  $mydestina‐
-              listed in  $mydestination,  or  when  it  is  listed  in  $inet_interfaces  or
+              tion, or when it is listed in $inet_interfaces or $proxy_interfaces.
-              $proxy_interfaces.
        @domain address
-              Replace other addresses in domain by address.  This form has the lowest prece‐
+              Replace other addresses in domain by address.  This form has the lowest precedence.
-              dence.
 RESULT ADDRESS REWRITING
        The lookup result is subject to address rewriting:
-       ·      When the result has the form @otherdomain, the result becomes the same user in
+       ·      When the result has the form @otherdomain, the result becomes the same user in otherdomain.
-              otherdomain.
-       ·      When   "append_at_myorigin=yes",  append  "@$myorigin"  to  addresses  without
+       ·      When "append_at_myorigin=yes", append "@$myorigin" to addresses without "@domain".
-              "@domain".
-       ·      When  "append_dot_mydomain=yes",  append  ".$mydomain"  to  addresses  without
+       ·      When "append_dot_mydomain=yes", append ".$mydomain" to addresses without ".domain".
-              ".domain".
 ADDRESS EXTENSION
-       When  a  mail  address  localpart  contains  the  optional recipient delimiter (e.g.,
+       When  a  mail  address  localpart  contains  the optional recipient delimiter (e.g., user+foo@domain), the
-       user+foo@domain), the lookup order becomes: user+foo@domain,  user@domain,  user+foo,
+       lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.
-       user, and @domain.
-       The  propagate_unmatched_extensions  parameter  controls whether an unmatched address
+       The propagate_unmatched_extensions parameter controls whether an unmatched  address  extension  (+foo)  is
-       extension (+foo) is propagated to the result of table lookup.
+       propagated to the result of table lookup.
 REGULAR EXPRESSION TABLES
-       This section describes how the table lookups change when the table is  given  in  the
+       This section describes how the table lookups change when the table is given in the form of regular expres‐
-       form  of  regular  expressions.  For a description of regular expression lookup table
+       sions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5).
-       syntax, see regexp_table(5) or pcre_table(5).
-       Each pattern is a regular expression that is applied  to  the  entire  address  being
+       Each pattern is a regular expression that is  applied  to  the  entire  address  being  looked  up.  Thus,
-       looked  up.  Thus,  user@domain  mail addresses are not broken up into their user and
+       user@domain  mail  addresses  are  not  broken  up  into  their user and @domain constituent parts, nor is
-       @domain constituent parts, nor is user+foo broken up into user and foo.
+       user+foo broken up into user and foo.
-       Patterns are applied in the order as specified in the table, until a pattern is found
+       Patterns are applied in the order as specified in the table, until a pattern is  found  that  matches  the
-       that matches the search string.
+       search string.
-       Results  are  the same as with indexed file lookups, with the additional feature that
+       Results  are  the  same  as with indexed file lookups, with the additional feature that parenthesized sub‐
-       parenthesized substrings from the pattern can be interpolated as $1, $2 and so on.
+       strings from the pattern can be interpolated as $1, $2 and so on.
 TCP-BASED TABLES
-       This section describes how the table lookups change when lookups are  directed  to  a
+       This section describes how the table lookups change when lookups are directed to a TCP-based server. For a
-       TCP-based  server.  For  a  description of the TCP client/server lookup protocol, see
+       description  of the TCP client/server lookup protocol, see tcp_table(5).  This feature is not available up
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
+       to and including Postfix version 2.4.
-       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses
+       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses are  not  broken  up
-       are not broken up into their user and @domain constituent parts, nor is user+foo bro‐
+       into their user and @domain constituent parts, nor is user+foo broken up into user and foo.
-       ken up into user and foo.
        Results are the same as with indexed file lookups.
 EXAMPLE
-       The following shows a generic mapping with an indexed file.  When mail is sent  to  a
+       The  following shows a generic mapping with an indexed file.  When mail is sent to a remote host via SMTP,
-       remote  host  via  SMTP, this replaces his@localdomain.local by his ISP mail address,
+       this replaces his@localdomain.local by his ISP mail address, replaces  her@localdomain.local  by  her  ISP
-       replaces her@localdomain.local by her ISP mail  address,  and  replaces  other  local
+       mail  address,  and replaces other local addresses by his ISP account, with an address extension of +local
-       addresses  by  his  ISP  account,  with  an address extension of +local (this example
+       (this example assumes that the ISP supports "+" style address extensions).
-       assumes that the ISP supports "+" style address extensions).
        /etc/postfix/main.cf:
@@ Zeile 1577: / Zeile 1578: @@
            @localdomain.local      hisaccount+local@hisisp.example
-       Execute the command "postmap /etc/postfix/generic" whenever  the  table  is  changed.
+       Execute the command "postmap /etc/postfix/generic" whenever the table is changed.  Instead of  hash,  some
-       Instead  of  hash,  some systems use dbm database files. To find out what tables your
+       systems  use  dbm  database  files. To find out what tables your system supports use the command "postconf
-       system supports use the command "postconf -m".
+       -m".
 BUGS
@@ Zeile 1585: / Zeile 1587: @@
 CONFIGURATION PARAMETERS
-       The following main.cf parameters are especially relevant.  The  text  below  provides
+       The following main.cf parameters are especially relevant.  The text below provides only a  parameter  sum‐
-       only a parameter summary. See postconf(5) for more details including examples.
+       mary. See postconf(5) for more details including examples.
        smtp_generic_maps
-              Address  mapping  lookup  table  for  envelope and header sender and recipient
+              Address  mapping lookup table for envelope and header sender and recipient addresses while deliver‐
-              addresses while delivering mail via SMTP.
+              ing mail via SMTP.
        propagate_unmatched_extensions
-              A list of address rewriting or forwarding mechanisms that propagate an address
+              A list of address rewriting or forwarding mechanisms that propagate an address extension  from  the
-              extension  from  the  original address to the result.  Specify zero or more of
+              original  address  to  the  result.   Specify  zero  or more of canonical, virtual, alias, forward,
-              canonical, virtual, alias, forward, include, or generic.
+              include, or generic.
        Other parameters of interest:
        inet_interfaces
-              The network interface addresses that this system receives mail on.   You  need
+              The network interface addresses that this system receives mail on.  You  need  to  stop  and  start
-              to stop and start Postfix when this parameter changes.
+              Postfix when this parameter changes.
        proxy_interfaces
-              Other interfaces that this machine receives mail on by way of a proxy agent or
+              Other  interfaces  that  this  machine  receives mail on by way of a proxy agent or network address
-              network address translator.
+              translator.
        mydestination
@@ Zeile 1622: / Zeile 1624: @@
 README FILES
-       Use "postconf readme_directory" or "postconf html_directory" to locate this  informa‐
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
-       tion.
        ADDRESS_REWRITING_README, address rewriting guide
        DATABASE_README, Postfix lookup table overview
@@ Zeile 1642: / Zeile 1643: @@
        Yorktown Heights, NY 10598, USA
-                                                                                  GENERIC(5)
+       Wietse Venema
-</code>
+       Google, Inc.
+8th Avenue
+       New York, NY 10011, USA
-Auch hier editieren wir nicht diese Vorlage- und Musterdatei //**/etc/postfix/genericaccess**//, sondern legen uns für die einzelnen Anwendungsfälle eigene Dateien an, auch wenn diese eventuell erst einmal ohne Inhalt sind. Wir haben so später kein Problem mehr, wenn wir ad hoc auf eine Anforderung schnell reagieren müssen.
+                                                                                                       GENERIC(5)</code>
+Auch hier editieren wir nicht diese Vorlage- und Musterdatei //**/etc/postfix/generic**//, sondern legen uns für die einzelnen Anwendungsfälle eigene Dateien an, auch wenn diese eventuell erst einmal ohne Inhalt sind. Wir haben so später kein Problem mehr, wenn wir ad hoc auf eine Anforderung schnell reagieren müssen.
 === generic-Dateien ===
 == lmtp_generic_maps ==
-  * **lmtp_generic_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. Das Umschreiben erfolgt beim Verlassen des Systems via LMTP. \\ **lmtp_generic_maps.db** Datenbankfile zur //lmtp_generic_maps//-Datei. <code> # vim /etc/postfix/lmtp_generic_maps</code> <file bash /etc/postfix/lmtp_generic_maps># Kapitel 5.2.4 generic-Tabelle: Umschreiben bei ausgehenden eMails
+  * **lmtp_generic_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. Das Umschreiben erfolgt beim Verlassen des Systems via LMTP. \\ **lmtp_generic_maps.db** Datenbankfile zur //lmtp_generic_maps//-Datei. <code> # vim /etc/postfix/lmtp_generic_maps</code> <file bash /etc/postfix/lmtp_generic_maps># Django : 2019-01-27
+# Kapitel 5.2.4 generic-Tabelle: Umschreiben bei ausgehenden eMails
 # Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im
 # SMTP-Envelop und im Header der eMail.
 #
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/lmtp_generic_maps die zugehörige Datenbank
+#
-# erzeugt werden.
+#          $ postmap /etc/postfix/lmtp_generic_maps
+#
+# die zugehörige Datenbank erzeugt werden.
 #
 # catch all
@@ Zeile 1664: / Zeile 1672: @@
 </file>
 == smtp_generic_maps ==
-  * **smtp_generic_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. Das Umschreiben erfolgt beim Verlassen des Systems via SMTP. \\ **smtp_generic_maps.db** Datenbankfile zur //smtp_generic_maps//-Datei. <code> # vim /etc/postfix/smtp_generic_maps</code> <file bash /etc/postfix/smtp_generic_maps># Kapitel 5.2.4 generic-Tabelle: Umschreiben bei ausgehenden eMails
+  * **smtp_generic_maps** Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im SMTP-Envelop und im Header der eMail. Das Umschreiben erfolgt beim Verlassen des Systems via SMTP. \\ **smtp_generic_maps.db** Datenbankfile zur //smtp_generic_maps//-Datei. <code> # vim /etc/postfix/smtp_generic_maps</code> <file bash /etc/postfix/smtp_generic_maps># Django : 2019-01-27
+# Kapitel 5.2.4 generic-Tabelle: Umschreiben bei ausgehenden eMails
 # Lookup-Tabelle zum Umschreibungen von Empfänger eMail-Adressen im
 # SMTP-Envelop und im Header der eMail.
 #
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/smtp_generic_maps die zugehörige Datenbank
+#
-# erzeugt werden.
+#          $ postmap /etc/postfix/lmtp_generic_maps
+#
+# die zugehörige Datenbank erzeugt werden.
 #
 # catch all
@@ Zeile 1684: / Zeile 1695: @@
 In der Manpage zu **relocated** bzw. in der Datei //**/etc/postfix/relocated**// finden wir detaillierte Informationen zur **relocated - Postfix relocated table format**.
    # man 5 relocated
-<code>RELOCATED(5)                         File Formats Manual                        RELOCATED(5)
+<code>RELOCATED(5)                                   File Formats Manual                                   RELOCATED(5)
 NAME
@@ Zeile 1693: / Zeile 1704: @@
 DESCRIPTION
-       The  optional  relocated(5)  table provides the information that is used in "user has
+       The  optional relocated(5) table provides the information that is used in "user has moved to new_location"
-       moved to new_location" bounce messages.
+       bounce messages.
-       Normally, the relocated(5) table is specified as a text file that serves as input  to
+       Normally, the relocated(5) table is specified as a text file that serves as input to the  postmap(1)  com‐
-       the postmap(1) command.  The result, an indexed file in dbm or db format, is used for
+       mand.   The  result,  an  indexed file in dbm or db format, is used for fast searching by the mail system.
-       fast searching by the mail system. Execute the  command  "postmap  /etc/postfix/relo‐
+       Execute the command "postmap /etc/postfix/relocated" to rebuild an indexed file after changing the  corre‐
-       cated" to rebuild an indexed file after changing the corresponding relocated table.
+       sponding relocated table.
-       When the table is provided via other means such as NIS, LDAP or SQL, the same lookups
+       When  the  table  is  provided  via other means such as NIS, LDAP or SQL, the same lookups are done as for
-       are done as for ordinary indexed files.
+       ordinary indexed files.
-       Alternatively, the table can be provided as a regular-expression map  where  patterns
+       Alternatively, the table can be provided as a regular-expression map where patterns are given  as  regular
-       are  given as regular expressions, or lookups can be directed to TCP-based server. In
+       expressions,  or  lookups  can  be  directed to TCP-based server. In those case, the lookups are done in a
-       those case, the lookups are done in a slightly different way as described below under
+       slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
        Table lookups are case insensitive.
 CASE FOLDING
-       The  search  string is folded to lowercase before database lookup. As of Postfix 2.3,
+       The search string is folded to lowercase before database lookup. As of Postfix 2.3, the search  string  is
-       the search string is not case folded with database types such  as  regexp:  or  pcre:
+       not  case folded with database types such as regexp: or pcre: whose lookup fields can match both upper and
-       whose lookup fields can match both upper and lower case.
+       lower case.
 TABLE FORMAT
@@ Zeile 1723: / Zeile 1733: @@
                    pattern      new_location
-              Where  new_location specifies contact information such as an email address, or
+              Where new_location specifies contact information such as an email  address,  or  perhaps  a  street
-              perhaps a street address or telephone number.
+              address or telephone number.
-       ·      Empty lines and whitespace-only lines are ignored, as are  lines  whose  first
+       ·      Empty  lines and whitespace-only lines are ignored, as are lines whose first non-whitespace charac‐
-              non-whitespace character is a `#'.
+              ter is a `#'.
-       ·      A logical line starts with non-whitespace text. A line that starts with white‐
+       ·      A logical line starts with non-whitespace text. A line that starts with whitespace continues a log‐
-              space continues a logical line.
+              ical line.
 TABLE SEARCH ORDER
-       With lookups from indexed files such as DB or DBM, or from networked tables  such  as
+       With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, pat‐
-       NIS, LDAP or SQL, patterns are tried in the order as listed below:
+       terns are tried in the order as listed below:
        user@domain
               Matches user@domain. This form has precedence over all other forms.
-       user   Matches  user@site  when site is $myorigin, when site is listed in $mydestina‐
+       user   Matches user@site when site is $myorigin, when site is listed in $mydestination, or  when  site  is
-              tion, or when site is listed in $inet_interfaces or $proxy_interfaces.
+              listed in $inet_interfaces or $proxy_interfaces.
        @domain
@@ Zeile 1746: / Zeile 1756: @@
 ADDRESS EXTENSION
-       When a mail address  localpart  contains  the  optional  recipient  delimiter  (e.g.,
+       When  a  mail  address  localpart  contains  the optional recipient delimiter (e.g., user+foo@domain), the
-       user+foo@domain),  the  lookup order becomes: user+foo@domain, user@domain, user+foo,
+       lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.
-       user, and @domain.
 REGULAR EXPRESSION TABLES
-       This section describes how the table lookups change when the table is  given  in  the
+       This section describes how the table lookups change when the table is given in the form of regular expres‐
-       form of regular expressions or when lookups are directed to a TCP-based server. For a
+       sions  or  when lookups are directed to a TCP-based server. For a description of regular expression lookup
-       description of  regular  expression  lookup  table  syntax,  see  regexp_table(5)  or
+       table syntax, see regexp_table(5) or pcre_table(5). For a  description  of  the  TCP  client/server  table
-       pcre_table(5).  For a description of the TCP client/server table lookup protocol, see
+       lookup protocol, see tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
-       Each pattern is a regular expression that is applied  to  the  entire  address  being
+       Each  pattern  is  a  regular  expression  that  is  applied  to the entire address being looked up. Thus,
-       looked  up.  Thus,  user@domain  mail addresses are not broken up into their user and
+       user@domain mail addresses are not broken up into  their  user  and  @domain  constituent  parts,  nor  is
-       @domain constituent parts, nor is user+foo broken up into user and foo.
+       user+foo broken up into user and foo.
-       Patterns are applied in the order as specified in the table, until a pattern is found
+       Patterns  are  applied  in  the order as specified in the table, until a pattern is found that matches the
-       that matches the search string.
+       search string.
-       Results  are  the same as with indexed file lookups, with the additional feature that
+       Results are the same as with indexed file lookups, with the additional  feature  that  parenthesized  sub‐
-       parenthesized substrings from the pattern can be interpolated as $1, $2 and so on.
+       strings from the pattern can be interpolated as $1, $2 and so on.
 TCP-BASED TABLES
-       This section describes how the table lookups change when lookups are  directed  to  a
+       This section describes how the table lookups change when lookups are directed to a TCP-based server. For a
-       TCP-based  server.  For  a  description of the TCP client/server lookup protocol, see
+       description of the TCP client/server lookup protocol, see tcp_table(5).  This feature is not available  up
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
+       to and including Postfix version 2.4.
-       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses
+       Each  lookup  operation  uses the entire address once.  Thus, user@domain mail addresses are not broken up
-       are not broken up into their user and @domain constituent parts, nor is user+foo bro‐
+       into their user and @domain constituent parts, nor is user+foo broken up into user and foo.
-       ken up into user and foo.
        Results are the same as with indexed file lookups.
@@ Zeile 1782: / Zeile 1789: @@
 CONFIGURATION PARAMETERS
-       The following main.cf parameters are especially relevant.  The  text  below  provides
+       The following main.cf parameters are especially relevant.  The text below provides only a  parameter  sum‐
-       only a parameter summary. See postconf(5) for more details including examples.
+       mary. See postconf(5) for more details including examples.
        relocated_maps
@@ Zeile 1791: / Zeile 1798: @@
        inet_interfaces
-              The  network  interface addresses that this system receives mail on.  You need
+              The  network  interface  addresses  that  this system receives mail on.  You need to stop and start
-              to stop and start Postfix when this parameter changes.
+              Postfix when this parameter changes.
        mydestination
@@ Zeile 1801: / Zeile 1808: @@
        proxy_interfaces
-              Other interfaces that this machine receives mail on by way of a proxy agent or
+              Other interfaces that this machine receives mail on by way of a  proxy  agent  or  network  address
-              network address translator.
+              translator.
 SEE ALSO
@@ Zeile 1810: / Zeile 1817: @@
 README FILES
-       Use  "postconf readme_directory" or "postconf html_directory" to locate this informa‐
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
-       tion.
+       DATABASE_README, Postfix lookup table overview
+       ADDRESS_REWRITING_README, address rewriting guide
+LICENSE
+       The Secure Mailer license must be distributed with this software.
+              List of lookup tables for relocated users or sites.
+       Other parameters of interest:
+       inet_interfaces
+              The  network  interface  addresses  that  this system receives mail on.  You need to stop and start
+              Postfix when this parameter changes.
+       mydestination
+              List of domains that this mail system considers local.
+       myorigin
+              The domain that is appended to locally-posted mail.
+       proxy_interfaces
+              Other interfaces that this machine receives mail on by way of a  proxy  agent  or  network  address
+              translator.
+SEE ALSO
+       trivial-rewrite(8), address resolver
+       postmap(1), Postfix lookup table manager
+       postconf(5), configuration parameters
+README FILES
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
        DATABASE_README, Postfix lookup table overview
        ADDRESS_REWRITING_README, address rewriting guide
@@ Zeile 1824: / Zeile 1861: @@
        Yorktown Heights, NY 10598, USA
-                                                                                RELOCATED(5)
+       Wietse Venema
-</code>
+       Google, Inc.
+8th Avenue
+       New York, NY 10011, USA
+                                                                                                     RELOCATED(5)</code>
 Wir editieren nun aber nicht diese Vorlage- und Musterdatei //**/etc/postfix/relocated**//, sondern legen uns eine eigene Dateien an, auch wenn diese eventuell erst einmal ohne Inhalt sind. Wir haben so später kein Problem mehr, wenn wir ad hoc auf eine Anforderung schnell reagieren müssen.
 === relocated-Datei ===
-  * **relocated_maps** Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten" an den Absender einer eMail über nicht existierende eMailadressen mit Angabe der neu zu nutzenden eMailadresse des Empfängers. \\ **relocated_maps.db** Datenbankfile zur //relocated_maps//-Datei. <code> # vim /etc/postfix/relocated_maps</code> <file bash /etc/postfix/relocated_maps># Kapitel 5.2.6 relocated-Tabelle: Empfängrt verzogen
+  * **relocated_maps** Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten" an den Absender einer eMail über nicht existierende eMailadressen mit Angabe der neu zu nutzenden eMailadresse des Empfängers. \\ **relocated_maps.db** Datenbankfile zur //relocated_maps//-Datei. <code> # vim /etc/postfix/relocated_maps</code> <file bash /etc/postfix/relocated_maps># Django : 2019-01-27
+# Kapitel 5.2.6 relocated-Tabelle: Empfängrt verzogen
 # Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten" an den Absender
 # einer eMail über nicht existierende eMailadressen mit Angabe der neu zu
@@ Zeile 1835: / Zeile 1878: @@
 #
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/relocated_maps
+#
+#             $ postmap /etc/postfix/relocated_maps
+#
 # die zugehörige Datenbank erzeugt werden.
 #
-michael.nausch@omni128.de      django@nausch.org
+michael.nausch@omni128.de               django@nausch.org</file>
-</file>
 ==== transport ====
 Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der Zustellung an einen weiteren Mailserver.
@@ Zeile 1845: / Zeile 1889: @@
 In der Manpage zu **transport** bzw. in der Datei //**/etc/postfix/transport**// finden wir detaillierte Informationen zur **transport - Postfix transport table format**.
    # man 5 transport
-<code>TRANSPORT(5)                         File Formats Manual                        TRANSPORT(5)
+<code>TRANSPORT(5)                                   File Formats Manual                                   TRANSPORT(5)
 NAME
@@ Zeile 1858: / Zeile 1902: @@
 DESCRIPTION
-       The  optional  transport(5) table specifies a mapping from email addresses to message
+       The  optional  transport(5)  table specifies a mapping from email addresses to message delivery transports
-       delivery transports and next-hop destinations.  Message delivery transports  such  as
+       and next-hop destinations.  Message delivery transports such as local or smtp are defined in the master.cf
-       local  or smtp are defined in the master.cf file, and next-hop destinations are typi‐
+       file,  and  next-hop  destinations are typically hosts or domain names. The table is searched by the triv‐
-       cally hosts or domain names. The table is searched by the trivial-rewrite(8) daemon.
+       ial-rewrite(8) daemon.
-       This mapping overrides the default transport:nexthop selection  that  is  built  into
+       This mapping overrides the default transport:nexthop selection that is built into Postfix:
-       Postfix:
        local_transport (default: local:$myhostname)
-              This  is  the default for final delivery to domains listed with mydestination,
+              This is the default for final delivery to domains listed with mydestination,  and  for  [ipaddress]
-              and for [ipaddress] destinations that match $inet_interfaces or  $proxy_inter‐
+              destinations  that  match $inet_interfaces or $proxy_interfaces. The default nexthop destination is
-              faces. The default nexthop destination is the MTA hostname.
+              the MTA hostname.
        virtual_transport (default: virtual:)
-              This  is  the  default for final delivery to domains listed with virtual_mail‐
+              This is the default for final delivery to domains listed with virtual_mailbox_domains. The  default
-              box_domains. The default nexthop destination is the recipient domain.
+              nexthop destination is the recipient domain.
        relay_transport (default: relay:)
-              This is the default for remote delivery to domains listed with  relay_domains.
+              This  is the default for remote delivery to domains listed with relay_domains. In order of decreas‐
-              In  order  of  decreasing  precedence,  the  nexthop destination is taken from
+              ing precedence, the nexthop destination  is  taken  from  relay_transport,  sender_dependent_relay‐
-              relay_transport,  sender_dependent_relayhost_maps,  relayhost,  or  from   the
+              host_maps, relayhost, or from the recipient domain.
-              recipient domain.
        default_transport (default: smtp:)
-              This  is  the  default for remote delivery to other destinations.  In order of
+              This  is the default for remote delivery to other destinations.  In order of decreasing precedence,
-              decreasing precedence, the nexthop destination  is  taken  from  sender_depen‐
+              the nexthop destination is taken from  sender_dependent_default_transport_maps,  default_transport,
-              dent_default_transport_maps,     default_transport,    sender_dependent_relay‐
+              sender_dependent_relayhost_maps, relayhost, or from the recipient domain.
-              host_maps, relayhost, or from the recipient domain.
-       Normally, the transport(5) table is specified as a text file that serves as input  to
+       Normally,  the  transport(5) table is specified as a text file that serves as input to the postmap(1) com‐
-       the postmap(1) command.  The result, an indexed file in dbm or db format, is used for
+       mand.  The result, an indexed file in dbm or db format, is used for fast searching  by  the  mail  system.
-       fast searching by the mail system. Execute the command  "postmap  /etc/postfix/trans‐
+       Execute  the command "postmap /etc/postfix/transport" to rebuild an indexed file after changing the corre‐
-       port" to rebuild an indexed file after changing the corresponding transport table.
+       sponding transport table.
-       When the table is provided via other means such as NIS, LDAP or SQL, the same lookups
+       When the table is provided via other means such as NIS, LDAP or SQL, the same  lookups  are  done  as  for
-       are done as for ordinary indexed files.
+       ordinary indexed files.
-       Alternatively, the table can be provided as a regular-expression map  where  patterns
+       Alternatively,  the  table can be provided as a regular-expression map where patterns are given as regular
-       are  given as regular expressions, or lookups can be directed to TCP-based server. In
+       expressions, or lookups can be directed to TCP-based server. In those case, the  lookups  are  done  in  a
-       those case, the lookups are done in a slightly different way as described below under
+       slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
 CASE FOLDING
-       The  search  string is folded to lowercase before database lookup. As of Postfix 2.3,
+       The  search  string is folded to lowercase before database lookup. As of Postfix 2.3, the search string is
-       the search string is not case folded with database types such  as  regexp:  or  pcre:
+       not case folded with database types such as regexp: or pcre: whose lookup fields can match both upper  and
-       whose lookup fields can match both upper and lower case.
+       lower case.
 TABLE FORMAT
@@ Zeile 1909: / Zeile 1949: @@
        pattern result
-              When  pattern  matches  the recipient address or domain, use the corresponding
+              When pattern matches the recipient address or domain, use the corresponding result.
-              result.
        blank lines and comments
-              Empty lines and whitespace-only lines are ignored, as are  lines  whose  first
+              Empty  lines and whitespace-only lines are ignored, as are lines whose first non-whitespace charac‐
-              non-whitespace character is a `#'.
+              ter is a `#'.
        multi-line text
-              A logical line starts with non-whitespace text. A line that starts with white‐
+              A logical line starts with non-whitespace text. A line that starts with whitespace continues a log‐
-              space continues a logical line.
+              ical line.
-       The pattern specifies an email address, a domain name, or a domain name hierarchy, as
+       The pattern specifies an email address, a domain name, or a domain name hierarchy, as described in section
-       described in section "TABLE LOOKUP".
+       "TABLE LOOKUP".
-       The  result  is  of  the form transport:nexthop and specifies how or where to deliver
+       The result is of the form transport:nexthop and specifies how or where to deliver mail. This is  described
-       mail. This is described in section "RESULT FORMAT".
+       in section "RESULT FORMAT".
 TABLE SEARCH ORDER
-       With lookups from indexed files such as DB or DBM, or from networked tables  such  as
+       With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, pat‐
-       NIS, LDAP or SQL, patterns are tried in the order as listed below:
+       terns are tried in the order as listed below:
        user+extension@domain transport:nexthop
@@ Zeile 1940: / Zeile 1979: @@
        .domain transport:nexthop
-              Deliver  mail  for  any subdomain of domain through transport to nexthop. This
+              Deliver mail for any subdomain of domain through transport to nexthop. This applies only  when  the
-              applies only when  the  string  transport_maps  is  not  listed  in  the  par‐
+              string  transport_maps is not listed in the parent_domain_matches_subdomains configuration setting.
-              ent_domain_matches_subdomains configuration setting.  Otherwise, a domain name
+              Otherwise, a domain name matches itself and its subdomains.
-              matches itself and its subdomains.
        * transport:nexthop
-              The special pattern * represents any address (i.e. it functions as  the  wild-
+              The special pattern * represents any address (i.e. it functions as the wild-card  pattern,  and  is
-              card pattern, and is unique to Postfix transport tables).
+              unique to Postfix transport tables).
-       Note  1: the null recipient address is looked up as $empty_address_recipient@$myhost‐
+       Note  1:  the  null  recipient  address  is  looked  up  as $empty_address_recipient@$myhostname (default:
-       name (default: mailer-daemon@hostname).
+       mailer-daemon@hostname).
-       Note 2: user@domain or user+extension@domain lookup is available in Postfix  2.0  and
+       Note 2: user@domain or user+extension@domain lookup is available in Postfix 2.0 and later.
-       later.
 RESULT FORMAT
-       The  lookup result is of the form transport:nexthop.  The transport field specifies a
+       The lookup result is of the form transport:nexthop.  The transport field specifies a mail delivery  trans‐
-       mail delivery transport such as smtp or local. The nexthop field specifies where  and
+       port such as smtp or local. The nexthop field specifies where and how to deliver mail.
-       how to deliver mail.
-       The  transport  field specifies the name of a mail delivery transport (the first name
+       The  transport  field  specifies  the name of a mail delivery transport (the first name of a mail delivery
-       of a mail delivery service entry in the Postfix master.cf file).
+       service entry in the Postfix master.cf file).
-       The interpretation of the nexthop field is transport dependent. In the case of  SMTP,
+       The interpretation of the nexthop field is transport dependent. In the case of SMTP, specify a service  on
-       specify  a  service  on  a  non-default  port  as  host:service, and disable MX (mail
+       a  non-default  port  as  host:service,  and  disable  MX  (mail  exchanger)  DNS  lookups  with [host] or
-       exchanger) DNS lookups with [host] or [host]:port. The [] form is required  when  you
+       [host]:port. The [] form is required when you specify an IP address instead of a hostname.
-       specify an IP address instead of a hostname.
-       A  null  transport  and  null  nexthop result means "do not change": use the delivery
+       A null transport and null nexthop result means "do not change": use the  delivery  transport  and  nexthop
-       transport and nexthop information that would be used when the entire transport  table
+       information that would be used when the entire transport table did not exist.
-       did not exist.
-       A  non-null  transport field with a null nexthop field resets the nexthop information
+       A  non-null  transport  field  with  a  null nexthop field resets the nexthop information to the recipient
-       to the recipient domain.
+       domain.
-       A null transport field with non-null nexthop field  does  not  modify  the  transport
+       A null transport field with non-null nexthop field does not modify the transport information.
-       information.
 EXAMPLES
-       In  order  to  deliver internal mail directly, while using a mail relay for all other
+       In order to deliver internal mail directly, while using a mail relay for all other mail,  specify  a  null
-       mail, specify a null entry for internal destinations  (do  not  change  the  delivery
+       entry  for  internal  destinations  (do  not change the delivery transport or the nexthop information) and
-       transport  or  the nexthop information) and specify a wildcard for all other destina‐
+       specify a wildcard for all other destinations.
-       tions.
             my.domain    :
@@ Zeile 1988: / Zeile 2020: @@
             *            smtp:outbound-relay.my.domain
-       In order to send mail for example.com and its subdomains via the  uucp  transport  to
+       In order to send mail for example.com and its subdomains via the uucp transport to  the  UUCP  host  named
-       the UUCP host named example:
+       example:
             example.com      uucp:example
             .example.com     uucp:example
-       When  no nexthop host name is specified, the destination domain name is used instead.
+       When no nexthop host name is specified, the destination domain name is used instead. For example, the fol‐
-       For example, the following directs mail for user@example.com via the  slow  transport
+       lowing directs mail for user@example.com via the slow transport to a mail exchanger for example.com.   The
-       to  a  mail exchanger for example.com.  The slow transport could be configured to run
+       slow transport could be configured to run at most one delivery process at a time:
-       at most one delivery process at a time:
             example.com      slow:
-       When no transport is specified, Postfix uses the transport that matches  the  address
+       When  no  transport  is  specified,  Postfix uses the transport that matches the address domain class (see
-       domain  class  (see DESCRIPTION above).  The following sends all mail for example.com
+       DESCRIPTION above).  The following sends all mail for example.com and its subdomains to host gateway.exam‐
-       and its subdomains to host gateway.example.com:
+       ple.com:
             example.com      :[gateway.example.com]
             .example.com     :[gateway.example.com]
-       In the above example, the [] suppress MX lookups.  This prevents mail  routing  loops
+       In  the  above example, the [] suppress MX lookups.  This prevents mail routing loops when your machine is
-       when your machine is primary MX host for example.com.
+       primary MX host for example.com.
-       In  the case of delivery via SMTP, one may specify hostname:service instead of just a
+       In the case of delivery via SMTP, one may specify hostname:service instead of just a host:
-       host:
             example.com      smtp:bar.example:2025
-       This directs mail for user@example.com to host bar.example port 2025.  Instead  of  a
+       This directs mail for user@example.com to host bar.example port 2025. Instead of a numerical port  a  sym‐
-       numerical  port  a  symbolic  name  may be used. Specify [] around the hostname if MX
+       bolic name may be used. Specify [] around the hostname if MX lookups must be disabled.
-       lookups must be disabled.
        The error mailer can be used to bounce mail:
@@ Zeile 2027: / Zeile 2056: @@
 REGULAR EXPRESSION TABLES
-       This section describes how the table lookups change when the table is  given  in  the
+       This section describes how the table lookups change when the table is given in the form of regular expres‐
-       form  of  regular  expressions.  For a description of regular expression lookup table
+       sions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5).
-       syntax, see regexp_table(5) or pcre_table(5).
-       Each pattern is a regular expression that is applied  to  the  entire  address  being
+       Each pattern is a regular expression that is  applied  to  the  entire  address  being  looked  up.  Thus,
-       looked  up.  Thus, some.domain.hierarchy is not looked up via its parent domains, nor
+       some.domain.hierarchy  is  not  looked  up  via  its  parent  domains, nor is user+foo@domain looked up as
-       is user+foo@domain looked up as user@domain.
+       user@domain.
-       Patterns are applied in the order as specified in the table, until a pattern is found
+       Patterns are applied in the order as specified in the table, until a pattern is  found  that  matches  the
-       that matches the search string.
+       search string.
-       The trivial-rewrite(8) server disallows regular expression substitution of $1 etc. in
+       The  trivial-rewrite(8)  server disallows regular expression substitution of $1 etc. in regular expression
-       regular expression lookup tables, because that could open a  security  hole  (Postfix
+       lookup tables, because that could open a security hole (Postfix version 2.3 and later).
-       version 2.3 and later).
 TCP-BASED TABLES
-       This  section  describes  how the table lookups change when lookups are directed to a
+       This section describes how the table lookups change when lookups are directed to a TCP-based server. For a
-       TCP-based server. For a description of the TCP  client/server  lookup  protocol,  see
+       description  of the TCP client/server lookup protocol, see tcp_table(5).  This feature is not available up
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
+       to and including Postfix version 2.4.
-       Each   lookup   operation   uses   the   entire   recipient   address   once.   Thus,
+       Each lookup operation uses the entire recipient address once.  Thus, some.domain.hierarchy is  not  looked
-       some.domain.hierarchy is not looked up via its parent domains, nor is user+foo@domain
+       up via its parent domains, nor is user+foo@domain looked up as user@domain.
-       looked up as user@domain.
        Results are the same as with indexed file lookups.
 CONFIGURATION PARAMETERS
-       The  following  main.cf  parameters are especially relevant.  The text below provides
+       The  following  main.cf parameters are especially relevant.  The text below provides only a parameter sum‐
-       only a parameter summary. See postconf(5) for more details including examples.
+       mary. See postconf(5) for more details including examples.
        empty_address_recipient
@@ Zeile 2061: / Zeile 2087: @@
        parent_domain_matches_subdomains
-              List of Postfix features that use domain.tld patterns to match  sub.domain.tld
+              List of Postfix features that use domain.tld  patterns  to  match  sub.domain.tld  (as  opposed  to
-              (as opposed to requiring .domain.tld patterns).
+              requiring .domain.tld patterns).
        transport_maps
@@ Zeile 2074: / Zeile 2100: @@
 README FILES
-       Use  "postconf readme_directory" or "postconf html_directory" to locate this informa‐
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
-       tion.
        ADDRESS_REWRITING_README, address rewriting guide
        DATABASE_README, Postfix lookup table overview
@@ Zeile 2089: / Zeile 2114: @@
        Yorktown Heights, NY 10598, USA
-                                                                                TRANSPORT(5)
+       Wietse Venema
-</code>
+       Google, Inc.
+8th Avenue
+       New York, NY 10011, USA
+                                                                                                     TRANSPORT(5)</code>
 === transport-Datei ===
-  * **transport_maps** Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der Zustellung an einen weiteren Mailserver. \\ **transport_maps.db** Datenbankfile zur //transport_maps//-Datei. <code> # vim /etc/postfix/transport_maps</code> <file bash /etc/postfix/transport_maps># Kapitel 5.2.5 transport-Tabelle: Abweichende Zustellung
+  * **transport_maps** Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der Zustellung an einen weiteren Mailserver. \\ **transport_maps.db** Datenbankfile zur //transport_maps//-Datei. <code> # vim /etc/postfix/transport_maps</code> <file bash /etc/postfix/transport_maps># Django : 2019-01-27
+# Kapitel 5.2.5 transport-Tabelle: Abweichende Zustellung
 # Lookup-Tabelle zum Aktivieren einer alternativen Mailrouting bei der
 # Zustellung an einen weiteren Mailserver. Nach dem Ändern und/oder
 # Erweitern der Tabelle, muß noch mittels:
-#               $ postmap /etc/postfix/transport_map
+#
+#               $ postmap /etc/postfix/transport_maps
 #
 # die zugehörige Datenbank erzeugt werden.
@@ Zeile 2114: / Zeile 2145: @@
 # mit Namen mail.intra.nausch.org geschickt.
 #backup.nausch.org                      smtp:[mail.intra.nausch.org]:25
-# Django : 2013-02-21
-# eMails an den Fax-Server an den Host vml000020 weiterleiten
-fax.nausch.org                          smtp:[10.0.0.20]:25
-# eMails an den Key-Server sollen an den Host vml000030 weitergeleitet
-# werden.
-keyserver.nausch.org                    smtp:[10.0.0.30]:25
-# Django : 2013-02-22
-# eMails an den Mailinglisten-Server an das Programm mailman weiterreichen
-#lists.nausch.org                       mailman:
 </file>
@@ Zeile 2133: / Zeile 2153: @@
 In der Manpage zu **virtual** bzw. in der Datei //**/etc/postfix/virtual**// finden wir detaillierte Informationen zur **virtual - Postfix virtual alias table format**.
    # man 5 transport
-<code>VIRTUAL(5)                           File Formats Manual                          VIRTUAL(5)
+<code>VIRTUAL(5)                                     File Formats Manual                                     VIRTUAL(5)
 NAME
@@ Zeile 2146: / Zeile 2166: @@
 DESCRIPTION
-       The  optional  virtual(5) alias table rewrites recipient addresses for all local, all
+       The  optional  virtual(5)  alias  table  rewrites  recipient addresses for all local, all virtual, and all
-       virtual, and all remote mail destinations.  This is unlike the aliases(5) table which
+       remote mail destinations.  This is unlike the aliases(5) table which is used only for  local(8)  delivery.
-       is  used  only  for  local(8) delivery.  Virtual aliasing is recursive, and is imple‐
+       Virtual aliasing is recursive, and is implemented by the Postfix cleanup(8) daemon before mail is queued.
-       mented by the Postfix cleanup(8) daemon before mail is queued.
        The main applications of virtual aliasing are:
@@ Zeile 2155: / Zeile 2174: @@
        ·      To redirect mail for one address to one or more addresses.
-       ·      To implement  virtual  alias  domains  where  all  addresses  are  aliased  to
+       ·      To implement virtual alias domains where all addresses are aliased to addresses in other domains.
-              addresses in other domains.
-              Virtual  alias domains are not to be confused with the virtual mailbox domains
+              Virtual  alias domains are not to be confused with the virtual mailbox domains that are implemented
-              that are implemented with the Postfix virtual(8)  mail  delivery  agent.  With
+              with the Postfix virtual(8) mail delivery agent.  With  virtual  mailbox  domains,  each  recipient
-              virtual mailbox domains, each recipient address can have its own mailbox.
+              address can have its own mailbox.
-       Virtual aliasing is applied only to recipient envelope addresses, and does not affect
+       Virtual  aliasing  is  applied  only to recipient envelope addresses, and does not affect message headers.
-       message headers.  Use canonical(5) mapping to rewrite header and  envelope  addresses
+       Use canonical(5) mapping to rewrite header and envelope addresses in general.
-       in general.
-       Normally, the virtual(5) alias table is specified as a text file that serves as input
+       Normally, the virtual(5) alias table is specified as a text file that serves as input  to  the  postmap(1)
-       to the postmap(1) command.  The result, an indexed file in dbm or db format, is  used
+       command.   The result, an indexed file in dbm or db format, is used for fast searching by the mail system.
-       for fast searching by the mail system. Execute the command "postmap /etc/postfix/vir‐
+       Execute the command "postmap /etc/postfix/virtual" to rebuild an indexed file after  changing  the  corre‐
-       tual" to rebuild an indexed file after changing the corresponding text file.
+       sponding text file.
-       When the table is provided via other means such as NIS, LDAP or SQL, the same lookups
+       When  the  table  is  provided  via other means such as NIS, LDAP or SQL, the same lookups are done as for
-       are done as for ordinary indexed files.
+       ordinary indexed files.
-       Alternatively,  the  table can be provided as a regular-expression map where patterns
+       Alternatively, the table can be provided as a regular-expression map where patterns are given  as  regular
-       are given as regular expressions, or lookups can be directed to TCP-based server.  In
+       expressions,  or  lookups  can  be  directed to TCP-based server. In those case, the lookups are done in a
-       those case, the lookups are done in a slightly different way as described below under
+       slightly different way as described below under "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
-       "REGULAR EXPRESSION TABLES" or "TCP-BASED TABLES".
 CASE FOLDING
-       The search string is folded to lowercase before database lookup. As of  Postfix  2.3,
+       The search string is folded to lowercase before database lookup. As of Postfix 2.3, the search  string  is
-       the  search  string  is  not case folded with database types such as regexp: or pcre:
+       not  case folded with database types such as regexp: or pcre: whose lookup fields can match both upper and
-       whose lookup fields can match both upper and lower case.
+       lower case.
 TABLE FORMAT
@@ Zeile 2191: / Zeile 2207: @@
        blank lines and comments
-              Empty lines and whitespace-only lines are ignored, as are  lines  whose  first
+              Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace  charac‐
-              non-whitespace character is a `#'.
+              ter is a `#'.
        multi-line text
-              A logical line starts with non-whitespace text. A line that starts with white‐
+              A logical line starts with non-whitespace text. A line that starts with whitespace continues a log‐
-              space continues a logical line.
+              ical line.
 TABLE SEARCH ORDER
-       With lookups from indexed files such as DB or DBM, or from networked tables  such  as
+       With lookups from indexed files such as DB or DBM, or from networked tables such as NIS, LDAP or SQL, each
-       NIS, LDAP or SQL, patterns are tried in the order as listed below:
+       user@domain query produces a sequence of query patterns as described below.
+       Each  query  pattern  is sent to each specified lookup table before trying the next query pattern, until a
+       match is found.
        user@domain address, address, ...
-              Redirect  mail  for  user@domain to address.  This form has the highest prece‐
+              Redirect mail for user@domain to address.  This form has the highest precedence.
-              dence.
        user address, address, ...
-              Redirect mail for user@site to address when site is equal to  $myorigin,  when
+              Redirect mail for user@site to address when site is equal to $myorigin,  when  site  is  listed  in
-              site  is listed in $mydestination, or when it is listed in $inet_interfaces or
+              $mydestination, or when it is listed in $inet_interfaces or $proxy_interfaces.
-              $proxy_interfaces.
-              This functionality overlaps with functionality of the local  aliases(5)  data‐
+              This  functionality overlaps with functionality of the local aliases(5) database. The difference is
-              base.  The  difference  is that virtual(5) mapping can be applied to non-local
+              that virtual(5) mapping can be applied to non-local addresses.
-              addresses.
        @domain address, address, ...
-              Redirect mail for other users in domain to address.  This form has the  lowest
+              Redirect mail for other users in domain to address.  This form has the lowest precedence.
-              precedence.
-              Note:  @domain is a wild-card. With this form, the Postfix SMTP server accepts
+              Note: @domain is a wild-card. With this form, the Postfix SMTP server accepts mail for any  recipi‐
-              mail for any recipient in domain, regardless of whether that recipient exists.
+              ent  in domain, regardless of whether that recipient exists.  This may turn your mail system into a
-              This  may  turn  your  mail  system  into  a backscatter source: Postfix first
+              backscatter source: Postfix first accepts mail for non-existent recipients and then tries to return
-              accepts mail for non-existent recipients and then tries to return that mail as
+              that mail as "undeliverable" to the often forged sender address.
-              "undeliverable" to the often forged sender address.
 RESULT ADDRESS REWRITING
        The lookup result is subject to address rewriting:
-       ·      When the result has the form @otherdomain, the result becomes the same user in
+       ·      When  the  result has the form @otherdomain, the result becomes the same user in otherdomain.  This
-              otherdomain.  This works only for the first address in a multi-address  lookup
+              works only for the first address in a multi-address lookup result.
-              result.
-       ·      When   "append_at_myorigin=yes",  append  "@$myorigin"  to  addresses  without
+       ·      When "append_at_myorigin=yes", append "@$myorigin" to addresses without "@domain".
-              "@domain".
-       ·      When  "append_dot_mydomain=yes",  append  ".$mydomain"  to  addresses  without
+       ·      When "append_dot_mydomain=yes", append ".$mydomain" to addresses without ".domain".
-              ".domain".
 ADDRESS EXTENSION
-       When  a  mail  address  localpart  contains  the  optional recipient delimiter (e.g.,
+       When a mail address localpart contains the  optional  recipient  delimiter  (e.g.,  user+foo@domain),  the
-       user+foo@domain), the lookup order becomes: user+foo@domain,  user@domain,  user+foo,
+       lookup order becomes: user+foo@domain, user@domain, user+foo, user, and @domain.
-       user, and @domain.
-       The  propagate_unmatched_extensions  parameter  controls whether an unmatched address
+       The  propagate_unmatched_extensions  parameter  controls  whether an unmatched address extension (+foo) is
-       extension (+foo) is propagated to the result of table lookup.
+       propagated to the result of table lookup.
 VIRTUAL ALIAS DOMAINS
-       Besides virtual aliases, the virtual alias table can also be used to  implement  vir‐
+       Besides virtual aliases, the virtual alias table can also be used to implement virtual alias domains. With
-       tual  alias domains. With a virtual alias domain, all recipient addresses are aliased
+       a virtual alias domain, all recipient addresses are aliased to addresses in other domains.
-       to addresses in other domains.
-       Virtual alias domains are not to be confused with the virtual  mailbox  domains  that
+       Virtual  alias  domains  are not to be confused with the virtual mailbox domains that are implemented with
-       are implemented with the Postfix virtual(8) mail delivery agent. With virtual mailbox
+       the Postfix virtual(8) mail delivery agent. With virtual mailbox domains, each recipient address can  have
-       domains, each recipient address can have its own mailbox.
+       its own mailbox.
-       With a virtual alias domain, the virtual domain has its own user  name  space.  Local
+       With  a  virtual  alias  domain,  the virtual domain has its own user name space. Local (i.e. non-virtual)
-       (i.e.  non-virtual)  usernames are not visible in a virtual alias domain. In particu‐
+       usernames are not visible in a virtual alias domain. In particular, local  aliases(5)  and  local  mailing
-       lar, local aliases(5) and local mailing lists are not visible  as  localname@virtual-
+       lists are not visible as localname@virtual-alias.domain.
-       alias.domain.
        Support for a virtual alias domain looks like:
@@ Zeile 2265: / Zeile 2273: @@
            virtual_alias_maps = hash:/etc/postfix/virtual
-       Note:  some systems use dbm databases instead of hash.  See the output from "postconf
+       Note:  some  systems  use  dbm databases instead of hash.  See the output from "postconf -m" for available
-       -m" for available database types.
+       database types.
        /etc/postfix/virtual:
-           virtual-alias.domain     anything (right-hand content does not matter)
+           virtual-alias.domain    anything (right-hand content does not matter)
-           postmaster@virtual-alias.domain  postmaster
+           postmaster@virtual-alias.domain postmaster
-           user1@virtual-alias.domain       address1
+           user1@virtual-alias.domain      address1
-           user2@virtual-alias.domain       address2, address3
+           user2@virtual-alias.domain      address2, address3
-       The virtual-alias.domain anything entry is required for a virtual alias domain. With‐
+       The virtual-alias.domain anything entry is required for a virtual alias domain. Without this  entry,  mail
-       out  this  entry,  mail is rejected with "relay access denied", or bounces with "mail
+       is rejected with "relay access denied", or bounces with "mail loops back to myself".
-       loops back to myself".
-       Do  not  specify  virtual  alias  domain  names  in  the  main.cf  mydestination   or
+       Do  not  specify  virtual  alias  domain names in the main.cf mydestination or relay_domains configuration
-       relay_domains configuration parameters.
+       parameters.
-       With a virtual alias domain, the Postfix SMTP server accepts mail for known-user@vir‐
+       With a virtual alias domain, the Postfix SMTP server accepts mail for known-user@virtual-alias.domain, and
-       tual-alias.domain, and rejects mail for unknown-user@virtual-alias.domain as undeliv‐
+       rejects mail for unknown-user@virtual-alias.domain as undeliverable.
-       erable.
-       Instead of specifying the virtual alias domain name via the virtual_alias_maps table,
+       Instead of specifying the virtual alias domain name via the virtual_alias_maps table, you may also specify
-       you may also specify it via the main.cf virtual_alias_domains  configuration  parame‐
+       it via the main.cf virtual_alias_domains configuration parameter.  This latter  parameter  uses  the  same
-       ter.  This latter parameter uses the same syntax as the main.cf mydestination config‐
+       syntax as the main.cf mydestination configuration parameter.
-       uration parameter.
 REGULAR EXPRESSION TABLES
-       This section describes how the table lookups change when the table is  given  in  the
+       This section describes how the table lookups change when the table is given in the form of regular expres‐
-       form  of  regular  expressions.  For a description of regular expression lookup table
+       sions. For a description of regular expression lookup table syntax, see regexp_table(5) or pcre_table(5).
-       syntax, see regexp_table(5) or pcre_table(5).
-       Each pattern is a regular expression that is applied  to  the  entire  address  being
+       Each pattern is a regular expression that is  applied  to  the  entire  address  being  looked  up.  Thus,
-       looked  up.  Thus,  user@domain  mail addresses are not broken up into their user and
+       user@domain  mail  addresses  are  not  broken  up  into  their user and @domain constituent parts, nor is
-       @domain constituent parts, nor is user+foo broken up into user and foo.
+       user+foo broken up into user and foo.
-       Patterns are applied in the order as specified in the table, until a pattern is found
+       Patterns are applied in the order as specified in the table, until a pattern is  found  that  matches  the
-       that matches the search string.
+       search string.
-       Results  are  the same as with indexed file lookups, with the additional feature that
+       Results  are  the  same  as with indexed file lookups, with the additional feature that parenthesized sub‐
-       parenthesized substrings from the pattern can be interpolated as $1, $2 and so on.
+       strings from the pattern can be interpolated as $1, $2 and so on.
 TCP-BASED TABLES
-       This section describes how the table lookups change when lookups are  directed  to  a
+       This section describes how the table lookups change when lookups are directed to a TCP-based server. For a
-       TCP-based  server.  For  a  description of the TCP client/server lookup protocol, see
+       description  of the TCP client/server lookup protocol, see tcp_table(5).  This feature is not available up
-       tcp_table(5).  This feature is not available up to and including Postfix version 2.4.
+       to and including Postfix version 2.4.
-       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses
+       Each lookup operation uses the entire address once.  Thus, user@domain mail addresses are  not  broken  up
-       are not broken up into their user and @domain constituent parts, nor is user+foo bro‐
+       into their user and @domain constituent parts, nor is user+foo broken up into user and foo.
-       ken up into user and foo.
        Results are the same as with indexed file lookups.
@@ Zeile 2320: / Zeile 2323: @@
 CONFIGURATION PARAMETERS
-       The following main.cf parameters are especially relevant to this topic. See the Post‐
+       The  following  main.cf parameters are especially relevant to this topic. See the Postfix main.cf file for
-       fix  main.cf file for syntax details and for default values. Use the "postfix reload"
+       syntax details and for default values. Use the "postfix reload" command after a configuration change.
-       command after a configuration change.
        virtual_alias_maps
@@ Zeile 2328: / Zeile 2330: @@
        virtual_alias_domains
-              List of virtual alias domains. This uses the same syntax as the  mydestination
+              List of virtual alias domains. This uses the same syntax as the mydestination parameter.
-              parameter.
        propagate_unmatched_extensions
-              A list of address rewriting or forwarding mechanisms that propagate an address
+              A list of address rewriting or forwarding mechanisms that propagate an address extension  from  the
-              extension from the original address to the result.  Specify zero  or  more  of
+              original  address  to  the  result.   Specify  zero  or more of canonical, virtual, alias, forward,
-              canonical, virtual, alias, forward, include, or generic.
+              include, or generic.
        Other parameters of interest:
        inet_interfaces
-              The  network  interface addresses that this system receives mail on.  You need
+              The network interface addresses that this system receives mail on.  You  need  to  stop  and  start
-              to stop and start Postfix when this parameter changes.
+              Postfix when this parameter changes.
        mydestination
@@ Zeile 2352: / Zeile 2353: @@
        proxy_interfaces
-              Other interfaces that this machine receives mail on by way of a proxy agent or
+              Other  interfaces  that  this  machine  receives mail on by way of a proxy agent or network address
-              network address translator.
+              translator.
 SEE ALSO
@@ Zeile 2362: / Zeile 2363: @@
 README FILES
-       Use  "postconf readme_directory" or "postconf html_directory" to locate this informa‐
+       Use "postconf readme_directory" or "postconf html_directory" to locate this information.
-       tion.
        ADDRESS_REWRITING_README, address rewriting guide
        DATABASE_README, Postfix lookup table overview
@@ Zeile 2377: / Zeile 2377: @@
        Yorktown Heights, NY 10598, USA
-                                                                                  VIRTUAL(5)
+       Wietse Venema
-</code>
+       Google, Inc.
+8th Avenue
+       New York, NY 10011, USA
+                                                                                                       VIRTUAL(5)</code>
 === virtual-Dateien ===
 == virtual_alias_domains ==
-  * **virtual_alias_domains** Lookup-Tabelle zum Verwalten der virtuellen Domains. \\ **virtual_alias_domains.db**  Datenbankfile zur //virtual_alias_domains//-Datei. <code> # vim /etc/postfix/virtual_alias_domains</code> <file bash /etc/postfix/virtual_alias_domains># Kapitel 5.2.2 virtual: Weiterleitung und virtuelle Mailadressen
+  * **virtual_alias_domains** Lookup-Tabelle zum Verwalten der virtuellen Domains. \\ **virtual_alias_domains.db**  Datenbankfile zur //virtual_alias_domains//-Datei. <code> # vim /etc/postfix/virtual_alias_domains</code> <file bash /etc/postfix/virtual_alias_domains># Django : 2019-01-27
+# Kapitel 5.2.2 virtual: Weiterleitung und virtuelle Mailadressen
 # Lookup-Tabelle zum Verwalten der virtuellen Domains.
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
@@ Zeile 2396: / Zeile 2401: @@
 #lists.nausch.org                Mailman
 </file>
-  * **virtual_alias_maps** Lookup-Tabelle zum Verwalten der virtuellen eMail-Adressen. \\ **virtual_alias_maps.db**  Datenbankfile zur //virtual_alias_maps//-Datei. <code> # vim /etc/postfix/virtual_alias_maps</code> <file bash /etc/postfix/virtual_alias_maps># Kapitel 5.2.2 virtual: Weiterleitung und virtuelle Mailadressen
+  * **virtual_alias_maps** Lookup-Tabelle zum Verwalten der virtuellen eMail-Adressen. \\ **virtual_alias_maps.db**  Datenbankfile zur //virtual_alias_maps//-Datei. <code> # vim /etc/postfix/virtual_alias_maps</code> <file bash /etc/postfix/virtual_alias_maps># Django : 2019-01-27
+# Kapitel 5.2.2 virtual: Weiterleitung und virtuelle Mailadressen
 # Lookup-Tabelle zum Verwalten der virtuellen eMailadressen.
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
@@ Zeile 2437: / Zeile 2443: @@
 == mysql_virtual_domains_maps.cf ==
    # vim /etc/postfix/mysql_virtual_domains_maps.cf
-<file bash /etc/postfix/mysql_virtual_domains_maps.cf># Django : 2013-02-07
+<file bash /etc/postfix/mysql_virtual_domains_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtuellen Domaenen
 #
@@ Zeile 2449: / Zeile 2455: @@
 == mysql_virtual_alias_maps.cf ==
    # vim /etc/postfix/mysql_virtual_alias_maps.cf
-<file bash /etc/postfix/mysql_virtual_alias_maps.cf># Django : 2012-02-07
+<file bash /etc/postfix/mysql_virtual_alias_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtual Alias Maps
 #
@@ Zeile 2461: / Zeile 2467: @@
 == mysql_virtual_alias_domain_maps.cf ==
    # vim /etc/postfix/mysql_virtual_alias_domain_maps.cf
-<file bash /etc/postfix/mysql_virtual_alias_domain_maps.cf># Django : 2013-02-07
+<file bash /etc/postfix/mysql_virtual_alias_domain_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtual Alias Domain Maps
 #
@@ Zeile 2475: / Zeile 2481: @@
 == mysql_virtual_alias_domain_catchall_maps.cf ==
    # vim /etc/postfix/mysql_virtual_alias_domain_catchall_maps.cf
-<file bash /etc/postfix/mysql_virtual_alias_domain_catchall_maps.cf># Django : 2013-02-07
+<file bash /etc/postfix/mysql_virtual_alias_domain_catchall_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtual Alias Domain Catchall Maps
 #
@@ Zeile 2489: / Zeile 2495: @@
 == mysql_virtual_mailbox_maps.cf ==
    # vim /etc/postfix/mysql_virtual_mailbox_maps.cf
-<file bash /etc/postfix/mysql_virtual_mailbox_maps.cf># Django : 2013-02-07
+<file bash /etc/postfix/mysql_virtual_mailbox_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtual Mailbox Maps
 #
@@ Zeile 2501: / Zeile 2507: @@
 == mysql_virtual_alias_domain_mailbox_maps.cf ==
    # vim /etc/postfix/mysql_virtual_alias_domain_mailbox_maps.cf
-<file bash /etc/postfix/mysql_virtual_alias_domain_mailbox_maps.cf># Django : 2012-10-09
+<file bash /etc/postfix/mysql_virtual_alias_domain_mailbox_maps.cf># Django : 2019-01-27
 # Definition der Datenbankanbindung zur Abfrage der virtual Alias Domain Mailbox Maps
 #
@@ Zeile 2517: / Zeile 2523: @@
 === bcc-Dateien ===
 == recipient_bcc_maps ==
-  * **recipient_bcc_maps** Lookup-Tabelle für Blindcopies einer oder mehrerer Empfangsadressen zu einem oder mehrer Zieladressen. \\ **recipient_bcc_maps.db**  Datenbankfile zur //recipient_bcc_maps//-Datei. <code> # vim /etc/postfix/recipient_bcc_maps</code> <file bash /etc/postfix/recipient_bcc_maps># Django : 2014-06-11
+  * **recipient_bcc_maps** Lookup-Tabelle für Blindcopies einer oder mehrerer Empfangsadressen zu einem oder mehrer Zieladressen. \\ **recipient_bcc_maps.db**  Datenbankfile zur //recipient_bcc_maps//-Datei. <code> # vim /etc/postfix/recipient_bcc_maps</code> <file bash /etc/postfix/recipient_bcc_maps># Django : 2019-01-27
 # Kapitel 5.2.3 bcc-Tabelle: Blindcopy einer oder mehrerer Empfangsadressen.
 #
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/recipient_bcc_maps
+#
+#            $ postmap /etc/postfix/recipient_bcc_maps
+#
 # die zugehörige Datenbank erzeugt werden.
 #
@@ Zeile 2529: / Zeile 2537: @@
 # alle Nachrichten eines einzelnen Empfängers kopieren
 #weather@nausch.org                     mailsave@nausch.org
-#
-#f2b-reports@nausch.org                 michi@mail.sskm.de
 </file>
-  * **sender_bcc_maps** Lookup-Tabelle für Blindcopies einer oder mehrerer Absenderadressen zu einem oder mehrer Zieladressen. \\ **sender_bcc_maps.db**  Datenbankfile zur //sender_bcc_maps//-Datei. <code> # vim /etc/postfix/sender_bcc_maps</code> <file bash /etc/postfix/sender_bcc_maps># Django : 2014-06-11
+  * **sender_bcc_maps** Lookup-Tabelle für Blindcopies einer oder mehrerer Absenderadressen zu einem oder mehrer Zieladressen. \\ **sender_bcc_maps.db**  Datenbankfile zur //sender_bcc_maps//-Datei. <code> # vim /etc/postfix/sender_bcc_maps</code> <file bash /etc/postfix/sender_bcc_maps># Django : 2019-01-27
 # Kapitel 5.2.3 bcc-Tabelle: Blindcopy einer oder mehrerer Sendeadressen.
 #
 # Nach dem Ändern und/oder Erweitern der Tabelle, muß noch mittels
-# $ postmap /etc/postfix/sender_bcc_maps
+#
+#           $ postmap /etc/postfix/sender_bcc_maps
+#
 # die zugehörige Datenbank erzeugt werden.
 #
@@ Zeile 2543: / Zeile 2551: @@
 #
 # alle Nachrichten eines einzelnen Absenders kopieren
-#weather@nausch.org                     mailsave@nausch.org
+#weather@nausch.org                     mailsave@nausch.org</file>
-#
-#fail2ban@vml000080.dmz.nausch.org      michi@mail.sskm.de</file>
+==== main.cf ====
 In der Sektion **LOOKUP-TABELLEN** definieren wir nun die zuvor vorgestellten Lookup-Tabellen in der Hauptkonfigurationsdatei **main.cf**.
    # vim /etc/postfix/main.cf
-<code bash>...
+<code bash>################################################################################
-################################################################################
 ## LOOKUP-TABELLEN
 #
-# Django : 2014-10-15 - default Datenbank Typ für die Befehle newaliases,
+# Django : 2019-01-27 - default Datenbank Typ für die Befehle newaliases,
 #          postalias und postmap auf das performantere btree umgestellt.
 # default default_database_type = hash
 default_database_type = btree
-# Django : 2014-10-15 - Trennzeichen zwischen Usernamen und Adresserweiterung
+# Django : 2019-01-27 - Trennzeichen zwischen Usernamen und Adresserweiterung
 # default: recipient_delimiter =
 recipient_delimiter = +
-# Django : 2014-10-15 - Alias-Tabelle für die Zustellung von lokalen Nachrichten
+# Django : 2019-01-27 - Alias-Tabelle für die Zustellung von lokalen Nachrichten
 #          durch den MDA (Mail Delivery Agent) "local". Nach Änderungen an der
 #          Tabelle /etc/aliases ist "newaliases" zum Neubau des Datenbankfiles
@@ Zeile 2569: / Zeile 2574: @@
 # default: alias_maps = hash:/etc/aliases, nis:mail.aliase
 alias_maps = hash:/etc/aliases
-#            btree:/etc/mailman/aliases
 alias_database = hash:/etc/aliases
-# Django : 2014-10-15 - Optionale Lookup Tabelle mit allen gültigen Empfängern
+# Django : 2019-01-27 - Optionale Lookup Tabelle mit allen gültigen Empfängern
 #          der in $relay_domains aufgeführten Domains
 # default: relay_recipient_maps =
@@ Zeile 2579: / Zeile 2583: @@
 #                         btree:/etc/mailman/roleaccounts
-# Django : 2014-10-15 - virtuelle Mail-Domains und Mailboxen mit Anbindung an
+# Django : 2019-01-27 - virtuelle Mail-Domains und Mailboxen mit Anbindung an
 #          das mySQL-Datenbankbackend (Verwaltung mit Hilfe von postfixadmin)
 # default: virtual_mailbox_domains = $virtual_mailbox_maps
@@ Zeile 2593: / Zeile 2597: @@
                           proxy:mysql:/etc/postfix/mysql_virtual_alias_domain_mailbox_maps.cf
-# Django : 2014-10-15 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
+# Django : 2019-01-27 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
 #          einzelner oder mehrerer Empfänger automatisch an einen weiteren
 #          Empfänger geschickt werden.
@@ Zeile 2599: / Zeile 2603: @@
 recipient_bcc_maps = btree:/etc/postfix/recipient_bcc_maps
-# Django : 2014-10-15 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
+# Django : 2019-01-27 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
 #          einzelner oder mehrerer Absender automatisch an einen weiteren
 #          Empfänger geschickt werden.
 sender_bcc_maps = btree:/etc/postfix/sender_bcc_maps
-# Django : 2014-10-16 - SMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
+# Django : 2019-01-27 - SMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
 #          Empfänger im SMTP-Envelope und im Header der eMail beim Verlassen
 #          des MTA via SMTP umgeschrieben werden können.
@@ Zeile 2610: / Zeile 2614: @@
 smtp_generic_maps = btree:/etc/postfix/smtp_generic_maps
-# Django : 2014-10-16 - LMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
+# Django : 2019-01-27 - LMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
 #          Empfänger im SMTP-Envelope und im Header der eMail beim Verlassen
 #          des MTA zum MDA via LMTP umgeschrieben werden können.
@@ Zeile 2616: / Zeile 2620: @@
 lmtp_generic_maps = btree:/etc/postfix/lmtp_generic_maps
-# Django : 2014-10-16 - Lookup-Tabelle zum Umschreibungen von Absender-eMail-
+# Django : 2019-01-27 - Lookup-Tabelle zum Umschreibungen von Absender-eMail-
 #          -Adressen im SMTP-Envelop und/oder im Header der eMail.
 # default: sender_canonical_maps =
@@ Zeile 2626: / Zeile 2630: @@
 sender_canonical_classes = envelope_sender
-# Django : 2014-10-16 - Lookup-Tabelle zum Umschreibungen von Empfänger-eMail-
+# Django : 2019-01-27 - Lookup-Tabelle zum Umschreibungen von Empfänger-eMail-
 #          -Adressen im SMTP-Envelop und/oder im Header der eMail.
 # default: recipient_canonical_maps =
@@ Zeile 2636: / Zeile 2640: @@
 recipient_canonical_classes = envelope_recipient
-# Django : 2014-10-16 - Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten"
+# Django : 2019-01-27 - Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten"
 #          an den Absender einer eMail über nicht existierende eMail-Adressen
 #          mit Angabe der neu zu nutzenden eMailadresse des Empfängers.
@@ Zeile 2642: / Zeile 2646: @@
 relocated_maps = btree:/etc/postfix/relocated_maps
-# Django : 2015-10-15 - Ergebnisse der Adress-Verification cachen
+# Django : 2019-01-27 - Ergebnisse der Adress-Verification cachen
 #          Kapitel 12.2.2 Dynamische Empfänger-Verifizierung
 #          Kapitel 9.5.5 envelope sender überprüfen
 # default: address_verify_map = btree:$data_directory/verify_cache
 </code>
+Die Installation und Konfiguration des in diesem Codeabschnitt enthaltenen SRS-Daemon findest sich im Kapitel **[[centos:mail_c7:spam_11#postfix|SRS - Sender Rewriting Scheme unter CentOS 7.x]]**.
@@ Zeile 2682: / Zeile 2685: @@
     * **reject_rbl_client ix.dnsbl.manitu.net** Blockiert die eMail, wenn die Client-IP-Adresse bei **ix.dnsbl.manitu.net** geblacklistet ist.
     * **reject_rbl_client bl.spamcop.net** Blockiert die eMail, wenn die Client-IP-Adresse bei **bl.spamcop.net** geblacklistet ist.
-    * **reject_rbl_client dnsbl.njabl.org** Blockiert die eMail, wenn die Client-IP-Adresse bei **dnsbl.njabl.org** geblacklistet ist.
   * **reject_rhsbl_client multi.uribl.com** \\ Blockiert die eMail, sofern der Client-Hostname in der verwendeten **rhsbl_domain**(**RHSBL**)((**R**ight-**H**and **S**ided **B**lacklist)) gelistet ist.
   * **reject_plaintext_session** \\ Liefert einen **REJECT**, wenn die Verbindung nicht TLS transportverschlüsselt ist.
@@ Zeile 2688: / Zeile 2690: @@
 Nachfolgende Definitionen fügen wir nun am Ende der //**/etc/postfix/main.cf**// ein. Hierzu benutzen wir wie immer den Editor unserer Wahl.
    # vim /etc/postfix/main.cf
-<code>...
+<code>################################################################################
-################################################################################
 ## SMTP RECIPIENT RESTRICTIONS
 #
-# Django : 2014-10-29 - Schutz unserer Empfänger mit Hilfe der Recipient
+# Django : 2019-01-27 - Schutz unserer Empfänger mit Hilfe der Recipient
 #          Restrictions
 # default: smtpd_recipient_restrictions =
@@ Zeile 2751: / Zeile 2751: @@
 Nachfolgende Definitionen fügen wir nun am Ende der //**/etc/postfix/main.cf**// ein.
    # vim /etc/postfix/main.cf
-<code>...
+<code>################################################################################
-################################################################################
 ## SMTP RELAY RESTRICTIONS
 #
-# Django : 2014-10-27 - Definition, wer über unseren MX relayen darf oder nicht.
+# Django : 2019-01-27 - Definition, wer über unseren MX relayen darf oder nicht.
 #          http://www.postfix.org/postconf.5.html#smtpd_relay_restrictions
 # default: smtpd_relay_restrictions = permit_mynetworks,
@@ Zeile 2776: / Zeile 2774: @@
 <file bash /etc/postfix/main.cf>################################################################################
 #                                                                              #
-#    Django : 2014-10-15 - Musterkonfiguration Postfix 2.11 unter CentOS 7     #
+#    Django : 2019-01-27 - Musterkonfiguration Postfix 3.x unter CentOS 7      #
 #                                                                              #
 ################################################################################
@@ Zeile 2783: / Zeile 2781: @@
 ## INSTALLATIONS-KONFIGURATIONS INFORMATIONEN
 #
+# Der Kopatibilitäts Level definiert, welche Standardeinstellungen Postfix für
+# die Einstellungen main.cf und master.cf verwendet. Diese Standardeinstellungen
+# werden sich im Laufe der Zeit voraussichtlich ändern!
+#
+# Damit die Lauffähigkeit des Postfix-Daemon nicht gefährdet wird der Daemon
+# rückwärtskompatible Standardeinstellungen verwenden und dies auch entsprechend
+# protokollieren. So kann bei einer Migration definiert werden,  ob rückwärts-
+# kompatible Standardeinstellungen in main.cf oder master.cf dauerhaft
+# vorgenommen werden müssen.
+#
+# Nach erfolgter Überprüfung ist der compatibility_level, wie in der Datei
+# /usr/share/doc/postfix-3.*/README_FILES/RELEASE_NOTES
+# empfohlen, entsprechend anzupassen.
+#
+# Django : 2019-01-27 - Kompatibilitäts-Level der Postfix 3 Installation
+#          Standardwert 2 definiert eine Neuinstalltion und kein (!) Upgrade.
+# default: compatibility_level = 2
+compatibility_level = 2
 # Folgende Default-Parameter werden benutzt, sobald eine neue Postfix-Version
 # installiert wird.
 #
-# Django : 2014-10-31 - Vollständiger Pfad zum Postfix sendmail Programm, dem
+# Django : 2019-01-27 - Vollständiger Pfad zum Postfix sendmail Programm, dem
 #          zu senmail kompatiblen sendmail Befehl.
 # default: sendmail_path = /usr/sbin/sendmail
 sendmail_path = /usr/sbin/sendmail.postfix
-# Django : 2014-10-31 - Vollständiger Pfad zum Postfix newaliases Programm, dem
+# Django : 2019-01-27 - Vollständiger Pfad zum Postfix newaliases Programm, dem
 #          zu sendmail kompatiblen Programm zum Anlegen der Alias Datenbanken.
 # default: newaliases_path = /usr/bin/newaliases
 newaliases_path = /usr/bin/newaliases.postfix
-# Django : 2014-10-31 - Vollständiger Pfad zum Postfix qmail-Programm, dem zu
+# Django : 2019-01-27 - Vollständiger Pfad zum Postfix qmail-Programm, dem zu
 #          sendmail kompatiblen Programm zum Anzeigen der Maile-Queues
 # default: mailq_path = /usr/bin/mailq
 mailq_path = /usr/bin/mailq.postfix
-# Django : 2014-10-31 - Gruppe für die Befehle mail submission und queue
+# Django : 2019-01-27 - Gruppe für die Befehle mail submission und queue
 #          management. Die Gruppe muss eine numerische eigene ID haben
 #          und darf nicht mit anderen Benutzeraccounts geteilt werden,
@@ Zeile 2807: / Zeile 2824: @@
 # default: setgid_group = postdrop
 setgid_group = postdrop
-# Django : 2014-10-31 - Pfad für die Postfix Postfix HTML Dokumentation.
+# Django : 2019-01-27 - Pfad für die Postfix Postfix HTML Dokumentation.
 # default: html_directory
 html_directory = no
-# Django : 2014-10-31 - Pfad für die Postfix online man-pages.
+# Django : 2019-01-27 - Pfad für die Postfix online man-pages.
 # default: manpage_directory = /usr/local/man
 manpage_directory = /usr/share/man
-# Django : 2014-10-31 - Pfadangabe für die Postfix Beispielkonfigurationsdateien.
+# Django : 2019-01-27 - Pfadangabe für die Postfix Beispielkonfigurationsdateien.
 #          Dieser Parameter ist obsolete seit Postfix 2.1.
 # default: sample_directory = /etc/postfix
-sample_directory = /usr/share/doc/postfix-2.11.3/samples
+sample_directory = /usr/share/doc/postfix-3.3.2/samples
-# Django : 2014-10-31 - Pfadangabe für die Postfix README Dateien.
+# Django : 2019-01-27 - Pfadangabe für die Postfix README Dateien.
 # default: readme_directory = no
-readme_directory = /usr/share/doc/postfix-2.11.3/README_FILES
+readme_directory = /usr/share/doc/postfix-3.3.2/README_FILES
+# Django : 2019-01-27 - Pfadangabe für das Postfix Metadirectory
+# default: meta_directory = /etc/postfix
+meta_directory = /etc/postfix
+# Django : 2019-01-27 - Pfadangabe für das SHLIB-Verzeichnis
+# default: shlib_directory = /usr/lib/postfix
+shlib_directory = /usr/lib/postfix
 ################################################################################
 ## PFADANGABEN DER LOKALEN INSTALLATION
 #
-# Django : 2014-10-31 - Definition des Speicherortes für die Queue-Dateien von
+# Django : 2019-01-27 - Definition des Speicherortes für die Queue-Dateien von
 #          Postfix. Dies ist auch der root-Pfad, falls Postfix in einer
 #          chroot-Umgebung laufen sollte. In der Datei examples/chroot-setup
@@ Zeile 2837: / Zeile 2862: @@
 # default: queue_directory = /var/spool/postfix
 queue_directory = /var/spool/postfix
-# Django : 2014-10-31 - Vollständiger Pfad zu allen postXXX-Programmen.
+# Django : 2019-01-27 - Vollständiger Pfad zu allen postXXX-Programmen.
 # default: command_directory = /usr/sbin
 command_directory = /usr/sbin
-# Django : 2014-10-31 Vollständiger Pfad zum Verzeichnis, in dem sich alle
+# Django : 2019-01-27 Vollständiger Pfad zum Verzeichnis, in dem sich alle
 #          postfix Daemon Programme (die z.B. auch in der master.cf
 #          aufgeführt sind) befinden. Das Verzeichnis muss root gehören!
 # default: daemon_directory = /usr/libexec/postfix
 daemon_directory = /usr/libexec/postfix
-# Django : 2014-10-31 - Datenverzeichnis, in dem Postfix alle variablen Daten
+# Django : 2019-01-27 - Datenverzeichnis, in dem Postfix alle variablen Daten
 #          ablegt, wie z.B. Caches, Zufallszahlen ect. pp. Das Verzeichnis
 #          muss dem nachfolgendem "mail_owner" gehören!
@@ Zeile 2858: / Zeile 2883: @@
 ## RECHTE BEI QUEUES UND PROZESSEN
 #
-# Django : 2014-10-31 - Definition des Nutzers, unter dem die meisten Postfix
+# Django : 2019-01-27 - Definition des Nutzers, unter dem die meisten Postfix
 #          Daemons laufen und mit dem die Queue-Dateien geschrieben werden.
 #          Die User muss unique sein, d.h. er darf weder einer anderen Gruppe
@@ Zeile 2867: / Zeile 2892: @@
 mail_owner = postfix
-# Django : 2014-10-31 - Festlegung der Defaultrechte, die vom LDA (Local
+# Django : 2019-01-27 - Festlegung der Defaultrechte, die vom LDA (Local
 #          Delivery Agent) verwendet werden, wenn dieser Nachrichten in eine
 #          externe Datei schreibt, oder einem anderen Befehl übergibt.
@@ Zeile 2876: / Zeile 2901: @@
 # default: default_privs = nobody
 default_privs = nobody
 ################################################################################
 ## DEBUGGING
 #
-# Django : 2014-10-31 - Mit dem Parameter "debug_peer_level" wird festgelegt
+# Django : 2019-01-27 - Mit dem Parameter "debug_peer_level" wird festgelegt
 #          um welchen Faktor der Logging-Level erhöht wird, wenn ein SMTP
 #          Client, ein Hostname oder eine IP-Adresse zu den Definitionen des
@@ Zeile 2887: / Zeile 2913: @@
 debug_peer_level = 2
-# Django : 2014-10-31 : Definition einer Liste aus Netzwerk-Adressen,
+# Django : 2019-01-27 : Definition einer Liste aus Netzwerk-Adressen,
 #          Namen, IP-Adressen oder entsprechender Postfix-Listen
 #          "type:name", für die der Loglevel gemäß dem obigen Loglevelwert
@@ Zeile 2896: / Zeile 2922: @@
 # default: debug_peer_list =
-# Django : 2014-10-13 - Debugger-Befehlszeile
+# Django : 2019-01-27 - Debugger-Befehlszeile
 #          Die Option "debugger_command" definiert den kompletten Debug-Aufruf,
 #          das ausgeführt werden soll, sofern der Postfix Daemon mit der
@@ Zeile 2918: / Zeile 2944: @@
 ## ZUSTÄNDIGKEITEN, VERTRAUENSWÜRDIGE NETZE UND NETZWERKK-DEFINITIONEN
 #
-# Django : 2014-10-15 - Hostname auf "offiziellen" DNS-MX-Record Namen gesetzt
+# Django : 2019-01-27 - Hostname auf "offiziellen" DNS-MX-Record Namen gesetzt
 # default: myhostname = FQDN
-myhostname = mx01.nausch.org
+myhostname = mx1.nausch.org
-# Django : 2014-10-15 - Domainpart der lokal generierten Nachrichten gesetzt
+# Django : 2019-01-27 - Domainpart der lokal generierten Nachrichten gesetzt
 # default: myorigin = $myhostname
 myorigin = $mydomain
-# Django : 2014-10-15 - Für welche Domains ist unser Mailserver zuständig,
+# Django : 2019-01-27 - Für welche Domains ist unser Mailserver zuständig,
 #          also final destination? Zusätzlich zu den Defaultwerten soll der MTA
 #          auch noch Nachrichten für die beiden Sub-Domains lists.nausch.org
 #          (Mailman) und dmarc.nausch.org (DMARC-Reportmails) annehmen.
 # default: mydestination = $myhostname, localhost.$mydomain, localhost
 mydestination =
                 $myhostname
                 localhost.$mydomain
@@ Zeile 2938: / Zeile 2964: @@
                 dmarc.nausch.org
-# default: unbekannte Empfänger sollen abgewiesen und nicht mit einem
+# Django : 2019-01-27 - Ablehnung unbekannter Empfänger sollen abgewiesen und
-#          temporären Fehler 450 abgewiesen werden.
+#          nicht mit einem temporären Fehler 450 abgewiesen werden.
-unknown_local_recipient_reject_code = 550
+# default: unknown_local_recipient_reject_code = 550
+#          unverified_recipient_reject_code = 450
+unverified_recipient_reject_code = 577
-# Django : 2014-10-15 - Soll bei einem unbekanntem Ziel der genaue Tabellenname
+# Django : 2019-01-27 - Soll bei einem unbekanntem Ziel der genaue Tabellenname
 #          bei der Ablehnung genannt werden?
 # default: show_user_unknown_table_name = yes
 show_user_unknown_table_name = no
-# Django : 2014-10-15 - auf allen Interfaces und Protokollen (IPv4 und IPv6)
+# Django : 2019-01-27 - auf allen Interfaces und Protokollen (IPv4 und IPv6)
 #          soll gelauscht werden
 # default: inet_interfaces = all
 # default: inet_protocols = all
-# Django : 2014-10-15 - Grundsätzlich soll erst einmal unser Mailserver nur dem
+# Django : 2019-01-27 - Grundsätzlich soll erst einmal unser Mailserver nur dem
 #          eigenen Host trauen, sonst niemanden!
 # default: mynetworks_style = subnet
@@ Zeile 2961: / Zeile 2989: @@
                 [::1]/128
 .0.0.0/24
-.0.10.0/26
+.0.10.0/25
-.185.109.34/32
-.185.109.87/32
-# Django : 2015-10-15 - Backup-Mailserver explizit erlauben
+# Django : 2019-01-27 - Backup-Mailserver explizit erlauben
 # default: permit_mx_backup_networks =
 permit_mx_backup_networks = 88.217.171.167/32
-################################################################################
+###############################################################################
-## ROUTING _ WEITERLEITEN VON NACHRICHTEN AN DAS EIGENTLICHE ZIEL
+## ROUTING - WEITERLEITEN VON NACHRICHTEN AN DAS EIGENTLICHE ZIEL
 #
-# Django : 2014-10-15 - Relayhost: Alle Nachrichten werden an den Relayhost
+# Django : 2019-01-27 - Relayhost: Alle Nachrichten werden an den Relayhost
 #          smtp-out.dmz.nausch.org gesendet.
 # default: relayhost =
 # relayhost = [smtp-out.dmz.nausch.org]
-# Django : 2014-10-15 - Backup-Relayhost: Sollte der $relayhost nicht erreichbar
+# Django : 2019-01-27 - Backup-Relayhost: Sollte der $relayhost nicht erreichbar
 #          sein, soll sich unser MTA an den backup-relayhost
 #          smtp-backup.dmz.nausch.org senden
@@ Zeile 2984: / Zeile 3010: @@
 # smtp_fallback_relay = [smtp-backup.dmz.nausch.org]
-# Django : 2014-10-15 - Relay Domains: Postfix als eingehendes Mailrelay vor
+# Django : 2019-01-27 - Relay Domains: Postfix als eingehendes Mailrelay vor
 #          einem anderen Server
 # default: relay_domains = $mydestination
 relay_domains = btree:/etc/postfix/relay_domains
-# Django : 2014-10-15 - Nachrichten für eine bestimmte Richtung sollen
+# Django : 2019-01-27 - Nachrichten für eine bestimmte Richtung sollen
 #          abweichend von den MX-Definitionen im DNS an dedizierte Ziele
 #          geroutet/weitergeleitet werden.
@@ Zeile 2995: / Zeile 3021: @@
 transport_maps = btree:/etc/postfix/transport_maps
-# Django : 2014-10-15 - Definition zur Erreichbarkeit unseres MDA-Servers
+# Django : 2019-01-27 - Definition zur Erreichbarkeit unseres MDA-Servers
 #          Dovecot-IMAP
 # default: virtual_transport = virtual
-virtual_transport = lmtp:[10.0.0.77]:24
+virtual_transport = lmtp:[imap.dmz.nausch.org]:24
@@ Zeile 3004: / Zeile 3030: @@
 ## QUEUEING-VERHALTEN
 #
-# Django : 2014-10-18 - Queue-Lifetime auf 3 Tage heruntersetzen, defininiert
+# Django : 2019-01-27 - Queue-Lifetime auf 3 Tage heruntersetzen, defininiert
 #          die maximale Zeit, die der MX versuchen darf, eine Nachricht zuzu-
 #          stellen
 # default: maximal_queue_lifetime = 5d
 maximal_queue_lifetime = 3d
-# Django : 2014-03-17- Bounce-Queue-Lifetime auf 3 Tage heruntersetzen, die
+# Django : 2019-01-27- Bounce-Queue-Lifetime auf 3 Tage heruntersetzen, die
 #          der MTA versuchen soll eine Bouncenachricht zuzustellen.
 # default: bounce_queue_lifetime = 5d
@@ Zeile 3019: / Zeile 3045: @@
 ## NACHRICHTENGROESSE UND ZUSTELLVERSUCHE/-MENGEN
 #
-# Django : 2014-10-18 Maximale Nachrichtengröße festlegen. Maximale Nachrichten-
+# Django : 2019-01-27 Maximale Nachrichtengröße festlegen. Maximale Nachrichten-
 #          größe einer Nachricht incl. der Headerinformationen darf maximal
 #          50 MB ( 52428800 = 50*1024*1024 ) betragen, darüber verweigert
@@ Zeile 3026: / Zeile 3052: @@
 message_size_limit = 52428800
-# Django : 2014-10-18 Maximale Mailboxgröße einer einzelnen Mailbox bzw.
+# Django : 2019-01-27 Maximale Mailboxgröße einer einzelnen Mailbox bzw.
-#          Maildir-Fiels. Der Wert darf nicht kleiner als die maximale
+#          Maildir-Files. Der Wert darf nicht kleiner als die maximale
 #          Nachrichtengröße (message_size_limit) sein.
 # default: mailbox_size_limit = 10240000
 mailbox_size_limit = 52428800
-# Django : 2010-10-28 - Rate Limiting (DOS-Attacken verhindern) maximale
+# Django : 2019-01-27 - Rate Limiting (DOS-Attacken verhindern) maximale
 #          Zustellung limitieren (Kapitel 24 des Buches Postfix)
 #          (Kapitel 13.14 Rate-Limiting gegenüber Clients durchsetzen)
@@ Zeile 3054: / Zeile 3080: @@
 #          Maximale Anzahl von erlaubten Anzahl von eMails je definierter Zeit-
 #          einheit (anvil_rate_time_unit) pro einliefernden Host
-# deafault: smtpd_client_message_rate_limit = 0
+# default: smtpd_client_message_rate_limit = 0
 smtpd_client_message_rate_limit = 50
 #
-#          Welche Cleints sollen vom Rate-Limeting ausgenommen werden? Per
+#          Welche Clients sollen vom Rate-Limeting ausgenommen werden? Per
 #          Default sind dies alle Clients aus dem eigenen Netzwerk $mynetworks
 # default: smtpd_client_event_limit_exceptions =
@@ Zeile 3078: / Zeile 3104: @@
 #          Ausgehende Nachrichten des MAilinglistenservers auf 2,5 Minuten
 #          setzen
-smtp_destination_rate_delay = 150s
+#smtp_destination_rate_delay = 150s
@@ Zeile 3084: / Zeile 3110: @@
 ## RÜCKMELDUNGEN BEEINFLUSSEN UND INDIVIDUALISIEREN
 #
-# Django : 2014-10-18 - Greeting Banner bei der 220er Begrüßung des MTA
+# Django : 2019-01-27 - Greeting Banner bei der 220er Begrüßung des MTA
 smtpd_banner = $myhostname ESMTP $mail_name
-# Django : 2014-10-16 - Extra-Footer bls zweite Zeiler jeder Fehlermeldungen
+# Django : 2019-01-27 - Extra-Footer als zweite Zeiler jeder Fehlermeldungen
 #          anfügen
 smtpd_reject_footer = \c. Contact your postmaster/admin for technical assistance. He can achieve our postmaster via email: postmaster@nausch.org or via fax: +49 8121 883179. In any case, please provide the following information in your problem report: This error message, time ($localtime), client ($client_address) and server ($server_name).
-# Django : 2014-10-16 - Anzeige des Tabellen-Namens, in der der Empfänger
+# Django : 2019-01-27 - Anzeige des Tabellen-Namens, in der der Empfänger
 #          nicht gefunden wurde. Das unterdrücken macht unter Umständen die
 #          Fehlersuche etwas aufwändiger, aber Externen geht diese Detailinfo
@@ Zeile 3098: / Zeile 3124: @@
 show_user_unknown_table_name = no
-# Django : 2014-10-24 - Adressverifikationsdetails unterdrücken
+# Django : 2019-01-27 - Adressverifikationsdetails unterdrücken
 #          Weder den numerischen SMTP-reply-Code, noch den enhanced status code
 #          zurückgeben. Lediglich "Recipient address lookup failed" zurückmelden.
@@ Zeile 3104: / Zeile 3130: @@
 unverified_recipient_reject_reason = Recipient address lookup failed
-# Django : 2014-10-24 - Adressverifikationsdetails unterdrücken
+# Django : 2019-01-27 - Adressverifikationsdetails unterdrücken
 #          Weder den numerischen SMTP-reply-Code, noch den enhanced status code
 #          zurückgeben. Lediglich "Recipient address lookup failed" zurückmelden.
@@ Zeile 3110: / Zeile 3136: @@
 unverified_sender_reject_reason = Sender address lookup failed
-# Django : 2014-10-18 Definition der benutzerspezifischen und individualisierten
+# Django : 2019-01-27 Definition der benutzerspezifischen und individualisierten
 #          Bounce-Nachrichten mit deutsch- und englischsprachigen Texten aktiviert
 # default: bounce_template_file =
 bounce_template_file = /etc/postfix/bounce.de-DE.cf
-# Django : 2014-10-18 - Delivery Status Notification (DSN) selectiv sperren
+# Django : 2019-01-27 - Delivery Status Notification (DSN) selectiv sperren
 #          oder freigeben
 # default: smtpd_discard_ehlo_keyword_address_maps =
 smtpd_discard_ehlo_keyword_address_maps = cidr:/etc/postfix/esmtp_access
-# Django : 2014-10-18 - SMTP-Kommando VRFY sperren, mit dem eine einfache und
+# Django : 2019-01-27 - SMTP-Kommando VRFY sperren, mit dem eine einfache und
 #          schnelle Addressverifizierung möglich ist.
 # default: disable_vrfy_command = no
 disable_vrfy_command = yes
-# Django : 2015-10-08 - Fehlercode bei Verwendung der Option
+# Django : 2019-01-27 - Fehlercode bei Verwendung der Option
 #          reject_plaintext_session beim Einsatz von verpflichtender
 #          TLS-Transportverschlüsselung.
 #          https://tools.ietf.org/html/rfc3463#section-3.8
 # default: plaintext_reject_code = 450
-# plaintext_reject_code = 573
+plaintext_reject_code = 571
@@ Zeile 3136: / Zeile 3162: @@
 ## LOOKUP-TABELLEN
 #
-# Django : 2014-10-15 - default Datenbank Typ für die Befehle newaliases,
+# Django : 2019-01-27 - default Datenbank Typ für die Befehle newaliases,
 #          postalias und postmap auf das performantere btree umgestellt.
 # default default_database_type = hash
-default_database_type = btree
+default_database_type =   btree
-# Django : 2014-10-15 - Trennzeichen zwischen Usernamen und Adresserweiterung
+# Django : 2019-01-27 - Trennzeichen zwischen Usernamen und Adresserweiterung
 # default: recipient_delimiter =
 recipient_delimiter = +
-# Django : 2014-10-15 - Alias-Tabelle für die Zustellung von lokalen Nachrichten
+# Django : 2019-01-27 - Alias-Tabelle für die Zustellung von lokalen Nachrichten
 #          durch den MDA (Mail Delivery Agent) "local". Nach Änderungen an der
 #          Tabelle /etc/aliases ist "newaliases" zum Neubau des Datenbankfiles
 #          notwendig!
 # default: alias_maps = hash:/etc/aliases, nis:mail.aliase
-alias_maps = hash:/etc/aliases
+alias_maps =              hash:/etc/aliases
-#            btree:/etc/mailman/aliases
+                          #btree:/etc/mailman/aliases
-alias_database = hash:/etc/aliases
+alias_database =          hash:/etc/aliases
-# Django : 2014-10-15 - Optionale Lookup Tabelle mit allen gültigen Empfängern
+# Django : 2019-01-27 - Optionale Lookup Tabelle mit allen gültigen Empfängern
 #          der in $relay_domains aufgeführten Domains
 # default: relay_recipient_maps =
 relay_recipient_maps =
-#                         btree:/etc/mailman/virtual-mailman
+                          #btree:/etc/mailman/virtual-mailman
-#                         btree:/etc/mailman/roleaccounts
+                          #btree:/etc/mailman/roleaccounts
-# Django : 2014-10-15 - virtuelle Mail-Domains und Mailboxen mit Anbindung an
+# Django : 2019-01-27 - virtuelle Mail-Domains und Mailboxen mit Anbindung an
 #          das mySQL-Datenbankbackend (Verwaltung mit Hilfe von postfixadmin)
 # default: virtual_mailbox_domains = $virtual_mailbox_maps
@@ Zeile 3175: / Zeile 3201: @@
                           proxy:mysql:/etc/postfix/mysql_virtual_alias_domain_mailbox_maps.cf
-# Django : 2014-10-15 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
+# Django : 2019-01-27 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
 #          einzelner oder mehrerer Empfänger automatisch an einen weiteren
 #          Empfänger geschickt werden.
@@ Zeile 3181: / Zeile 3207: @@
 recipient_bcc_maps = btree:/etc/postfix/recipient_bcc_maps
-# Django : 2014-10-15 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
+# Django : 2019-01-27 - BCC-Adress Lookup Tabelle mit deren Hilfe Nachrichten
 #          einzelner oder mehrerer Absender automatisch an einen weiteren
 #          Empfänger geschickt werden.
 sender_bcc_maps = btree:/etc/postfix/sender_bcc_maps
-# Django : 2014-10-16 - SMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
+# Django : 2019-01-27 - SMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
 #          Empfänger im SMTP-Envelope und im Header der eMail beim Verlassen
 #          des MTA via SMTP umgeschrieben werden können.
@@ Zeile 3192: / Zeile 3218: @@
 smtp_generic_maps = btree:/etc/postfix/smtp_generic_maps
-# Django : 2014-10-16 - LMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
+# Django : 2019-01-27 - LMTP Lookup Tabelle mit deren Hilfe eMail-Adressen der
 #          Empfänger im SMTP-Envelope und im Header der eMail beim Verlassen
 #          des MTA zum MDA via LMTP umgeschrieben werden können.
@@ Zeile 3198: / Zeile 3224: @@
 lmtp_generic_maps = btree:/etc/postfix/lmtp_generic_maps
-# Django : 2014-10-16 - Lookup-Tabelle zum Umschreibungen von Absender-eMail-
+# Django : 2019-01-27 - Lookup-Tabelle zum Umschreibungen von Absender-eMail-
 #          -Adressen im SMTP-Envelop und/oder im Header der eMail.
 # default: sender_canonical_maps =
 sender_canonical_maps = btree:/etc/postfix/sender_canonical_maps
 #                       SRS - Sender Rewriting Scheme mit postsrsd
-#                       tcp:127.0.0.1:10001
+                        tcp:127.0.0.1:10001
 #          Definition welche Adressen umgeschrieben werden sollen
 # default: sender_canonical_classes = envelope_sender, header_sender
 sender_canonical_classes = envelope_sender
+			   #header_sender
-# Django : 2014-10-16 - Lookup-Tabelle zum Umschreibungen von Empfänger-eMail-
+# Django : 2019-01-27 - Lookup-Tabelle zum Umschreibungen von Empfänger-eMail-
 #          -Adressen im SMTP-Envelop und/oder im Header der eMail.
 # default: recipient_canonical_maps =
 recipient_canonical_maps = btree:/etc/postfix/recipient_canonical_maps
-#                       SRS - Sender Rewriting Scheme mit postsrsd
+#                          SRS - Sender Rewriting Scheme mit postsrsd
-#                       tcp:127.0.0.1:10002
+                           tcp:127.0.0.1:10002
 #          Definition welche Adressen umgeschrieben werden sollen
 # default: recipient_canonical_classes = envelope_recipient, header_recipient
 recipient_canonical_classes = envelope_recipient
+			      #header_recipient
-# Django : 2014-10-16 - Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten"
+# Django : 2019-01-27 - Lookup-Tabelle zum Aktivieren von "Bounce-Nachrichten"
 #          an den Absender einer eMail über nicht existierende eMail-Adressen
 #          mit Angabe der neu zu nutzenden eMailadresse des Empfängers.
@@ Zeile 3224: / Zeile 3252: @@
 relocated_maps = btree:/etc/postfix/relocated_maps
-# Django : 2015-10-15 - Ergebnisse der Adress-Verification cachen
+# Django : 2019-01-27 - Ergebnisse der Adress-Verification cachen
 #          Kapitel 12.2.2 Dynamische Empfänger-Verifizierung
 #          Kapitel 9.5.5 envelope sender überprüfen
 # default: address_verify_map = btree:$data_directory/verify_cache
+#address_verify_map = btree:/var/spool/postfix/data/verify
 ################################################################################
 ## SMTP RECIPIENT RESTRICTIONS
 #
-# Django : 2014-10-29 - Schutz unserer Empfänger mit Hilfe der Recipient
+# Django : 2019-01-27 - Schutz unserer Empfänger mit Hilfe der Recipient
 #          Restrictions
 # default: smtpd_recipient_restrictions =
@@ Zeile 3260: / Zeile 3288: @@
 #          Greylisting via postgrey checken via Unix-Socket
 #                                          (Kapitel 9.2.5 postgrey installieren)
-#          check_policy_service unix:postgrey/socket,
+          #check_policy_service unix:postgrey/socket,
 #          Policyd-Weight check over TCP-Connection
@@ Zeile 3291: / Zeile 3319: @@
 ## SMTP RELAY RESTRICTIONS
 #
-# Django : 2014-10-27 - Definition, wer über unseren MX relayen darf oder nicht.
+# Django : 2019-01-27 - Definition, wer über unseren MX relayen darf oder nicht.
 #          http://www.postfix.org/postconf.5.html#smtpd_relay_restrictions
 # default: smtpd_relay_restrictions = permit_mynetworks,
@@ Zeile 3304: / Zeile 3332: @@
 # alles andere an relaying verbieten, d.h. mit einem finalen error 550 abweisen
            reject_unauth_destination
 </file>
 ===== Konfiguration aktivieren =====
@@ Zeile 3313: / Zeile 3342: @@
 Wir können aber auch den Status unseres Mailservers abfragen.
    # systemctl status postfix
-<code>postfix.service - Postfix Mail Transport Agent
-   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled)
+<html><pre class="code">
-   Active: active (running) since Mon 2014-11-03 22:35:18 CET; 3s ago
+<font style="color: rgb(0, 255, 0)"><b>● </b></font>postfix.service - Postfix Mail Transport Agent
-  Process: 3222 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
+   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled)
-  Process: 3206 ExecReload=/usr/sbin/postfix reload (code=exited, status=0/SUCCESS)
+   Active: <font style="color: rgb(0, 255, 0)"><b>active (running)</b></font> since Sun 2019-01-27 22:53:52 CET; 2min 20s ago
-  Process: 3236 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
+  Process: 5671 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
-  Process: 3234 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS)
+  Process: 5687 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
-  Process: 3231 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS)
+  Process: 5684 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS)
- Main PID: 3309 (master)
+  Process: 5681 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS)
+ Main PID: 5761 (master)
    CGroup: /system.slice/postfix.service
-           ├─3309 /usr/libexec/postfix/master -w
+           ├─5761 /usr/libexec/postfix/master -w
-           ├─3310 pickup -l -t unix -u
+           ├─5762 pickup -l -t unix -u
-           └─3311 qmgr -l -t unix -u
+           └─5763 qmgr -l -t unix -u
-Nov 03 22:35:17 vml000087.dmz.nausch.org systemd[1]: Starting Postfix Mail Transport Agent...
+Jan 27 22:53:51 vml000080.dmz.nausch.org systemd[1]: Stopped Postfix Mail Transport Agent.
-Nov 03 22:35:18 vml000087.dmz.nausch.org postfix/master[3309]: daemon started -- version 2.11.3, configuration /etc/postfix
+Jan 27 22:53:51 vml000080.dmz.nausch.org systemd[1]: Starting Postfix Mail Transport Agent...
-Nov 03 22:35:18 vml000087.dmz.nausch.org systemd[1]: Started Postfix Mail Transport Agent.
+Jan 27 22:53:52 vml000080.dmz.nausch.org postfix/postfix-script[5759]: starting the Postfix mail system
-</code>
+Jan 27 22:53:52 vml000080.dmz.nausch.org postfix/master[5761]: daemon started -- version 3.3.2, configuration /etc/postfix
+Jan 27 22:53:52 vml000080.dmz.nausch.org systemd[1]: Started Postfix Mail Transport Agent.</font>
+</pre>
+</html>
+\\ \\ \\
+<WRAP center round todo 30%>
+FIXME FIXME FIXME
+  * //**do geds weida!**//
+FIXME FIXME FIXME
+</WRAP>
+\\ \\ \\
 ====== Links ======
@@ Zeile 3339: / Zeile 3380: @@
   * **[[http://dokuwiki.nausch.org/doku.php/|Zurück zur Startseite]]**
-/* ~~AUTOTWEET:~~ */