centos:mail_c7:postfix3_1

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung		 Vorhergehende Überarbeitung
centos:mail_c7:postfix3_1 [26.01.2019 20:26. ] – [Lockup-Tables] djangocentos:mail_c7:postfix3_1 [22.07.2019 15:11. ] (aktuell) – Externe Bearbeitung 127.0.0.1
Zeile 2306: Zeile 2306:
   * **[[centos:mail_c7:mta_4?&#virtual|virtual]]**    * **[[centos:mail_c7:mta_4?&#virtual|virtual]]** 
  
-\\ \\ \\ 
-<WRAP center round todo 30%> 
-FIXME FIXME FIXME  
-  * //**do geds weida!**//   
-FIXME FIXME FIXME  
-</WRAP> 
-\\ \\ \\ 
 ===== Header-Checks ===== ===== Header-Checks =====
 Möchte man Informationen im Mailheader zum Bewerten verwenden, um so z.B. eine Nachricht zu blocken, kann man dies mit Hilfe der Konfigurationsdatei **header_checks** realisieren. Möchte man Informationen im Mailheader zum Bewerten verwenden, um so z.B. eine Nachricht zu blocken, kann man dies mit Hilfe der Konfigurationsdatei **header_checks** realisieren.
    # less /etc/postfix/header_checks    # less /etc/postfix/header_checks
 <file bash /etc/postfix/header_checks># HEADER_CHECKS(5)                                              HEADER_CHECKS(5) <file bash /etc/postfix/header_checks># HEADER_CHECKS(5)                                              HEADER_CHECKS(5)
-#                                                                          +#  
-# NAME                                                                     +# NAME 
-#        header_checks - Postfix built-in content inspection               +#        header_checks - Postfix built-in content inspection 
-#                                                                            +#  
-# SYNOPSIS                                                                      +# SYNOPSIS 
-#        header_checks = pcre:/etc/postfix/header_checks                               +#        header_checks = pcre:/etc/postfix/header_checks 
-#        mime_header_checks = pcre:/etc/postfix/mime_header_checks                       +#        mime_header_checks = pcre:/etc/postfix/mime_header_checks 
-#        nested_header_checks = pcre:/etc/postfix/nested_header_checks                    +#        nested_header_checks = pcre:/etc/postfix/nested_header_checks 
-#        body_checks = pcre:/etc/postfix/body_checks                                         +#        body_checks = pcre:/etc/postfix/body_checks
 #  # 
 #        milter_header_checks = pcre:/etc/postfix/milter_header_checks #        milter_header_checks = pcre:/etc/postfix/milter_header_checks
Zeile 2448: Zeile 2441:
 #        if /pattern/flags #        if /pattern/flags
 #  # 
-#        endif  Match the input string against the patterns between +#        endif  If the input string matches /pattern/,  then  match 
-#               if  and endif, if and only if the same input string +#               that  input  string against the patterns between if 
-#               also matches /pattern/. The if..endif can nest.+#               and endif.  The if..endif can nest.
 #  # 
 #               Note: do not prepend whitespace to patterns  inside #               Note: do not prepend whitespace to patterns  inside
Zeile 2457: Zeile 2450:
 #        if !/pattern/flags #        if !/pattern/flags
 #  # 
-#        endif  Match the input string against the patterns between +#        endif  If  the input string does not match /pattern/, then 
-#               if and endif, if and only if the same input  string +#               match  that  input  string  against  the   patterns 
-#               does not match /pattern/. The if..endif can nest.+#               between if and endif. The if..endif can nest.
 #  # 
 #        blank lines and comments #        blank lines and comments
Zeile 2492: Zeile 2485:
 #        Action names are case insensitive. They are shown in upper #        Action names are case insensitive. They are shown in upper
 #        case for consistency with other Postfix documentation. #        case for consistency with other Postfix documentation.
 +# 
 +#        BCC user@domain
 +#               Add the specified address as a BCC  recipient,  and
 +#               inspect  the next input line. The address must have
 +#               a local part and domain part.  The  number  of  BCC
 +#               addresses  that can be added is limited only by the
 +#               amount of available storage space.
 +# 
 +#               Note 1: the BCC address is added as if it was spec-
 +#               ified  with  NOTIFY=NONE.  The  sender  will not be
 +#               notified when the BCC address is undeliverable,  as
 +#               long  as  all  down-stream  software implements RFC
 +#               3461.
 +# 
 +#               Note 2: this ignores duplicate addresses (with  the
 +#               same delivery status notification options).
 +# 
 +#               This feature is available in Postfix 3.0 and later.
 +# 
 +#               This feature is not supported with smtp header/body
 +#               checks.
 #  # 
 #        DISCARD optional text... #        DISCARD optional text...
-#               Claim successful delivery and silently discard  the+#               Claim  successful delivery and silently discard the 
 +#               message.  Do not inspect the remainder of the input
 #               message.   Log the optional text if specified, oth- #               message.   Log the optional text if specified, oth-
 #               erwise log a generic message. #               erwise log a generic message.
Zeile 2521: Zeile 2536:
 #  # 
 #        FILTER transport:destination #        FILTER transport:destination
-#               After the message is queued, send the  entire  mes- +#               Override the content_filter parameter setting,  and 
-#               sage through the specified external content filter. +#               inspect  the next input line.  After the message is 
-#               The transport name specifies the first field  of  a +#               queued, send the entire message through the  speci- 
-#               mail  delivery  agent  definition in master.cf; the +#               fied  external  content  filter. The transport name 
-#               syntax of the next-hop destination is described  in +#               specifies the first field of a mail delivery  agent 
-#               the  manual  page  of  the  corresponding  delivery +#               definition in master.cf; the syntax of the next-hop 
-#               agent.  More  information  about  external  content +#               destination is described in the manual page of  the 
-#               filters is in the Postfix FILTER_README file.+#               corresponding  delivery  agent.   More  information 
 +#               about external content filters is  in  the  Postfix 
 +#               FILTER_README file.
 #  # 
 #               Note  1: do not use $number regular expression sub- #               Note  1: do not use $number regular expression sub-
Zeile 2581: Zeile 2598:
 #  # 
 #        IGNORE Delete the current line from the input, and inspect #        IGNORE Delete the current line from the input, and inspect
-#               the next input line.+#               the next input line. See STRIP for  an  alternative 
 +#               that logs the action.
 #  # 
 #        INFO optional text... #        INFO optional text...
 #               Log an "info:" record with the optional text... (or #               Log an "info:" record with the optional text... (or
-#               log  a  generic  text),  and inspect the next input +#               log a generic text), and  inspect  the  next  input 
-#               line. This action is useful for routine logging  or+#               line.  This action is useful for routine logging or
 #               for debugging. #               for debugging.
 #  # 
 #               This feature is available in Postfix 2.8 and later. #               This feature is available in Postfix 2.8 and later.
 +# 
 +#        PASS optional text...
 +#               Log  a "pass:" record with the optional text... (or
 +#               log a generic text), and turn off header, body, and
 +#               Milter  inspection  for  the remainder of this mes-
 +#               sage.
 +# 
 +#               Note: this feature relies on trust  in  information
 +#               that is easy to forge.
 +# 
 +#               This feature is available in Postfix 3.2 and later.
 +# 
 +#               This feature is not supported with smtp header/body
 +#               checks.
 #  # 
 #        PREPEND text... #        PREPEND text...
-#               Prepend one  line  with  the  specified  text,  and+#               Prepend  one  line  with  the  specified  text, and
 #               inspect the next input line. #               inspect the next input line.
 #  # 
 #               Notes: #               Notes:
 #  # 
-#               o      The  prepended  text is output on a separate+#               o      The prepended text is output on  a  separate
 #                      line,  immediately  before  the  input  that #                      line,  immediately  before  the  input  that
 #                      triggered the PREPEND action. #                      triggered the PREPEND action.
 #  # 
 #               o      The prepended text is not considered part of #               o      The prepended text is not considered part of
-#                      the input  stream:  it  is  not  subject  to+#                      the  input  stream:  it  is  not  subject to
 #                      header/body checks or address rewriting, and #                      header/body checks or address rewriting, and
 #                      it does not affect the way that Postfix adds #                      it does not affect the way that Postfix adds
Zeile 2608: Zeile 2640:
 #  # 
 #               o      When prepending text before a message header #               o      When prepending text before a message header
-#                      line, the prepended text must begin  with  a+#                      line,  the  prepended text must begin with a
 #                      valid message header label. #                      valid message header label.
 #  # 
-#               o      This action cannot be used to prepend multi- +#               o      This  action  cannot  be  used  to   prepend 
-#                      line text.+#                      multi-line text.
 #  # 
 #               This feature is available in Postfix 2.1 and later. #               This feature is available in Postfix 2.1 and later.
Zeile 2620: Zeile 2652:
 #  # 
 #        REDIRECT user@domain #        REDIRECT user@domain
-#               Write a message redirection request  to  the  queue +#               Write  a  message  redirection request to the queue 
-#               file,  and  inspect  the next input line. After the+#               file, and inspect the next input  line.  After  the
 #               message is queued, it will be sent to the specified #               message is queued, it will be sent to the specified
 #               address instead of the intended recipient(s). #               address instead of the intended recipient(s).
 #  # 
-#               Note:  this action overrides the FILTER action, and +#               Note: this action overrides the FILTER action,  and 
-#               affects all recipients of the message. If  multiple +#               affects  all recipients of the message. If multiple 
-#               REDIRECT  actions  fire,  only the last one is exe-+#               REDIRECT actions fire, only the last  one  is  exe-
 #               cuted. #               cuted.
 #  # 
Zeile 2636: Zeile 2668:
 #  # 
 #        REPLACE text... #        REPLACE text...
-#               Replace the current line with the  specified  text,+#               Replace  the  current line with the specified text,
 #               and inspect the next input line. #               and inspect the next input line.
 #  # 
 #               This feature is available in Postfix 2.2 and later. #               This feature is available in Postfix 2.2 and later.
-#               The description below applies to Postfix 2.2.2  and+#               The  description below applies to Postfix 2.2.2 and
 #               later. #               later.
 #  # 
 #               Notes: #               Notes:
 #  # 
-#               o      When  replacing  a  message header line, the +#               o      When replacing a message  header  line,  the 
-#                      replacement text must  begin  with  a  valid+#                      replacement  text  must  begin  with a valid
 #                      header label. #                      header label.
 #  # 
-#               o      The  replaced text remains part of the input +#               o      The replaced text remains part of the  input 
-#                      stream. Unlike the result from  the  PREPEND +#                      stream.  Unlike  the result from the PREPEND 
-#                      action,  a  replaced  message  header may be +#                      action, a replaced  message  header  may  be 
-#                      subject to address rewriting and may  affect +#                      subject  to address rewriting and may affect 
-#                      the  way  that  Postfix adds missing message+#                      the way that Postfix  adds  missing  message
 #                      headers. #                      headers.
 #  # 
 #        REJECT optional text... #        REJECT optional text...
-#               Reject the  entire  message.  Reply  with  optional +#               Reject  the  entire  message.  Do  not  inspect the 
-#               text... when the optional text is specified, other- +#               remainder  of  the  input  message.    Reply   with 
-#               wise reply with a generic error message.+#               optional  text...  when the optional text is speci- 
 +#               fied, otherwise reply with a generic error message.
 #  # 
-#               Note:  this  action  disables  further  header   or +#               Note:   this  action  disables  further  header  or 
-#               body_checks  inspection  of the current message and+#               body_checks inspection of the current  message  and
 #               affects all recipients. #               affects all recipients.
 #  # 
Zeile 2672: Zeile 2705:
 #               This feature is not supported with smtp header/body #               This feature is not supported with smtp header/body
 #               checks. #               checks.
 +# 
 +#        STRIP optional text...
 +#               Log a "strip:" record with the optional text... (or
 +#               log a generic text), delete the input line from the
 +#               input,  and inspect the next input line. See IGNORE
 +#               for a silent alternative.
 +# 
 +#               This feature is available in Postfix 3.2 and later.
 #  # 
 #        WARN optional text... #        WARN optional text...
-#               Log a "warning:" record with the  optional  text...+#               Log  a  "warning:" record with the optional text...
 #               (or log a generic text), and inspect the next input #               (or log a generic text), and inspect the next input
-#               line. This action is useful for debugging  and  for +#               line.  This  action is useful for debugging and for 
-#               testing  a  pattern  before  applying  more drastic+#               testing a  pattern  before  applying  more  drastic
 #               actions. #               actions.
 #  # 
 # BUGS # BUGS
 #        Empty lines never match, because some map types mis-behave #        Empty lines never match, because some map types mis-behave
-#        when  given  a zero-length search string.  This limitation +#        when given a zero-length search string.   This  limitation 
-#        may be removed for regular expression tables in  a  future+#        may  be  removed for regular expression tables in a future
 #        release. #        release.
 #  # 
-#        Many  people  overlook  the main limitations of header and+#        Many people overlook the main limitations  of  header  and
 #        body_checks rules. #        body_checks rules.
 #  # 
-#        o      These rules operate on one logical  message  header+#        o      These  rules  operate on one logical message header
 #               or one body line at a time. A decision made for one #               or one body line at a time. A decision made for one
 #               line is not carried over to the next line. #               line is not carried over to the next line.
 #  # 
-#        o      If text in the message body is encoded  (RFC  2045)+#        o      If  text  in the message body is encoded (RFC 2045)
 #               then the rules need to be specified for the encoded #               then the rules need to be specified for the encoded
 #               form. #               form.
 #  # 
-#        o      Likewise, when message  headers  are  encoded  (RFC +#        o      Likewise,  when  message  headers  are encoded (RFC 
-#               2047)  then  the rules need to be specified for the+#               2047) then the rules need to be specified  for  the
 #               encoded form. #               encoded form.
 #  # 
-#        Message headers added by the cleanup(8) daemon itself  are+#        Message  headers added by the cleanup(8) daemon itself are
 #        excluded from inspection. Examples of such message headers #        excluded from inspection. Examples of such message headers
 #        are From:, To:, Message-ID:, Date:. #        are From:, To:, Message-ID:, Date:.
 #  # 
-#        Message headers deleted by the cleanup(8) daemon  will  be+#        Message  headers  deleted by the cleanup(8) daemon will be
 #        examined before they are deleted. Examples are: Bcc:, Con- #        examined before they are deleted. Examples are: Bcc:, Con-
 #        tent-Length:, Return-Path:. #        tent-Length:, Return-Path:.
Zeile 2713: Zeile 2754:
 #               Lookup tables with content filter rules for message #               Lookup tables with content filter rules for message
 #               body lines.  These filters see one physical line at #               body lines.  These filters see one physical line at
-#               a time, in chunks  of  at  most  $line_length_limit+#               a  time,  in  chunks  of at most $line_length_limit
 #               bytes. #               bytes.
 #  # 
 #        body_checks_size_limit #        body_checks_size_limit
-#               The  amount  of  content  per  message body segment+#               The amount of  content  per  message  body  segment
 #               (attachment) that is subjected to $body_checks fil- #               (attachment) that is subjected to $body_checks fil-
 #               tering. #               tering.
Zeile 2727: Zeile 2768:
 #        nested_header_checks (default: $header_checks) #        nested_header_checks (default: $header_checks)
 #               Lookup tables with content filter rules for message #               Lookup tables with content filter rules for message
-#               header lines: respectively, these  are  applied  to +#               header  lines:  respectively,  these are applied to 
-#               the  initial  message  headers  (not including MIME +#               the initial message  headers  (not  including  MIME 
-#               headers), to the MIME headers anywhere in the  mes- +#               headers),  to the MIME headers anywhere in the mes- 
-#               sage,  and  to the initial headers of attached mes-+#               sage, and to the initial headers of  attached  mes-
 #               sages. #               sages.
 #  # 
-#               Note: these filters see one logical message  header +#               Note:  these filters see one logical message header 
-#               at  a time, even when a message header spans multi- +#               at a time, even when a message header spans  multi- 
-#               ple lines. Message headers  that  are  longer  than+#               ple  lines.  Message  headers  that are longer than
 #               $header_size_limit characters are truncated. #               $header_size_limit characters are truncated.
 #  # 
 #        disable_mime_input_processing #        disable_mime_input_processing
-#               While  receiving mail, give no special treatment to +#               While receiving mail, give no special treatment  to 
-#               MIME related message headers; all  text  after  the+#               MIME  related  message  headers; all text after the
 #               initial message headers is considered to be part of #               initial message headers is considered to be part of
-#               the message body. This means that header_checks  is +#               the  message body. This means that header_checks is 
-#               applied  to  all  the  initial message headers, and+#               applied to all the  initial  message  headers,  and
 #               that body_checks is applied to the remainder of the #               that body_checks is applied to the remainder of the
 #               message. #               message.
 #  # 
-#               Note:  when  used  in this manner, body_checks will +#               Note: when used in this  manner,  body_checks  will 
-#               process a multi-line message header one line  at  a+#               process  a  multi-line message header one line at a
 #               time. #               time.
 #  # 
 # EXAMPLES # EXAMPLES
-#        Header  pattern  to  block  attachments with bad file name +#        Header pattern to block attachments  with  bad  file  name 
-#        extensions.  For convenience, the PCRE /x flag  is  speci- +#        extensions.   For  convenience, the PCRE /x flag is speci- 
-#        fied,  so  that  there  is no need to collapse the pattern +#        fied, so that there is no need  to  collapse  the  pattern 
-#        into  a  single  line  of  text.   The  purpose   of   the+#        into   a   single  line  of  text.   The  purpose  of  the
 #        [[:xdigit:]] sub-expressions is to recognize Windows CLSID #        [[:xdigit:]] sub-expressions is to recognize Windows CLSID
 #        strings. #        strings.
Zeile 2763: Zeile 2804:
 #  # 
 #        /etc/postfix/header_checks.pcre: #        /etc/postfix/header_checks.pcre:
-#            /^Content-(Disposition|Type).*name\s*=\s*"?(.*(\.|=2E)(+#            /^Content-(Disposition|Type).*name\s*=\s*"?([^;]*(\.|=2E)(
 #              ade|adp|asp|bas|bat|chm|cmd|com|cpl|crt|dll|exe| #              ade|adp|asp|bas|bat|chm|cmd|com|cpl|crt|dll|exe|
 #              hlp|ht[at]| #              hlp|ht[at]|
Zeile 2794: Zeile 2835:
 #  # 
 # README FILES # README FILES
-#        Use  "postconf  readme_directory" or "postconf html_direc-+#        Use "postconf readme_directory" or  "postconf  html_direc-
 #        tory" to locate this information. #        tory" to locate this information.
 #        DATABASE_README, Postfix lookup table overview #        DATABASE_README, Postfix lookup table overview
Zeile 2802: Zeile 2843:
 #  # 
 # LICENSE # LICENSE
-#        The Secure Mailer license must be  distributed  with  this+#        The  Secure  Mailer  license must be distributed with this
 #        software. #        software.
 #  # 
Zeile 2811: Zeile 2852:
 #        Yorktown Heights, NY 10598, USA #        Yorktown Heights, NY 10598, USA
 #  # 
-# +#        Wietse Venema 
-</file> +#        Google, Inc. 
- +#        111 8th Avenue 
-Wie dies im Detail von Statten geht werden wir uns in einem separaten Schritt [[centos:mail_c7:mta_3?&#inhaltliche_pruefungen|Grundabsicherung von Postfix]] noch genauer ansehen. FIXME+#        New York, NY 10011, USA 
 +#  
 +#                                                               HEADER_CHECKS(5)</file>
  
 +Wie dies im Detail von Statten geht werden wir uns in einem separaten Schritt [[centos:mail_c7:mta_3?&#inhaltliche_pruefungen|Grundabsicherung von Postfix]] noch genauer ansehen.
 ===== Paketfilter / Firewall ===== ===== Paketfilter / Firewall =====
 Damit fremde **MTA**s((**M**ail **T**ransfer **A**gent)) auf **[[centos:mail_c7:mta_1#smtpd|SMTP]]**-Port **25** und unsere Kunden mit deren **MUA**s((**M**ail **U**ser **A**gent)) auf dem **[[centos:mail_c7:mta_1#submission|Submission]]**-Port **587** ihre Nachrichten bei unserem Postfix-Mailserver einliefern können, müssen wir für diese noch Änderungen am Paketfilter **firewalld** vornehmen. Damit fremde **MTA**s((**M**ail **T**ransfer **A**gent)) auf **[[centos:mail_c7:mta_1#smtpd|SMTP]]**-Port **25** und unsere Kunden mit deren **MUA**s((**M**ail **U**ser **A**gent)) auf dem **[[centos:mail_c7:mta_1#submission|Submission]]**-Port **587** ihre Nachrichten bei unserem Postfix-Mailserver einliefern können, müssen wir für diese noch Änderungen am Paketfilter **firewalld** vornehmen.
Zeile 2840: Zeile 2884:
     0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:587 ctstate NEW     0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:587 ctstate NEW
 </code> </code>
- 
- 
  
 ===== Systemstart ===== ===== Systemstart =====
 ==== erster manueller Start ==== ==== erster manueller Start ====
 +
    # systemctl start postfix.service    # systemctl start postfix.service
  
Zeile 2855: Zeile 2898:
  
    # systemctl status postfix.service    # systemctl status postfix.service
-<code>postfix.service - Postfix Mail Transport Agent + 
-   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled) +<html><pre class="code"> 
-   Active: active (running) since Fri 2014-10-10 22:41:26 CEST; 1min 11s ago +<font style="color: rgb(0, 255, 0)"><b>● </b></font>postfix.service - Postfix Mail Transport Agent 
-  Process: 30501 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS) +   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled) 
-  Process: 30517 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS) +   Active: <font style="color: rgb(0, 255, 0)"><b>active (running)</b></font> since Sat 2019-01-26 21:41:21 CET; 12s ago 
-  Process: 30515 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS) +  Process: 14349 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS) 
-  Process: 30513 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS) +  Process: 14346 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS) 
- Main PID: 30590 (master)+  Process: 14341 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS) 
 + Main PID: 14423 (master)
    CGroup: /system.slice/postfix.service    CGroup: /system.slice/postfix.service
-           ├─30590 /usr/libexec/postfix/master -w +           ├─14423 /usr/libexec/postfix/master -w 
-           ├─30591 pickup -l -t unix -u +           ├─14424 pickup -l -t unix -u 
-           └─30592 qmgr -l -t unix -u+           └─14425 qmgr -l -t unix -u 
 + 
 +Jan 26 21:41:20 vml000080.dmz.nausch.org systemd[1]: Starting Postfix Mail Transport Agent... 
 +Jan 26 21:41:21 vml000080.dmz.nausch.org postfix/postfix-script[14421]: starting the Postfix mail system 
 +Jan 26 21:41:21 vml000080.dmz.nausch.org postfix/master[14423]: daemon started -- version 3.3.2, configuration /etc/postfix 
 +Jan 26 21:41:21 vml000080.dmz.nausch.org systemd[1]: Started Postfix Mail Transport Agent.</font> 
 +</pre> 
 +</html> 
 + 
 +Fragen wir nun mit Hilfe des Befehls ''**netstat -tulpen**'' die offenen Ports ab, sehen wir, dass der Port **25** auf beiden zur Verfügung stehenden Netzwerkinterfaces geöffnet wurden. 
 +   # netstat -tulpen 
 + 
 +<code>Active Internet connections (only servers) 
 +Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name     
 +tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          48472      14423/master         
 +tcp6       0      0 ::1:25                  :::*                    LISTEN      0          48473      14423/master</code> 
 + 
 +Alternativ dazu können wr auch den Befehl ''**lsof**'' verwenden. 
 +   # lsof -i :25 
 + 
 +  COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME 
 +  master  14423 root   13u  IPv4  48472      0t0  TCP localhost:smtp (LISTEN) 
 +  master  14423 root   14u  IPv6  48473      0t0  TCP localhost:smtp (LISTEN)
  
-Oct 10 22:41:25 vml000087.dmz.nausch.org systemd[1]: Starting Postfix Mail Transport Agent... 
-Oct 10 22:41:26 vml000087.dmz.nausch.org postfix/master[30590]: daemon started -- version 2.11.1, configuration /etc/postfix 
-Oct 10 22:41:26 vml000087.dmz.nausch.org systemd[1]: Started Postfix Mail Transport Agent. 
-</code> 
  
 ==== automatischer Start beim Systemstart ==== ==== automatischer Start beim Systemstart ====
Zeile 2885: Zeile 2947:
  
 ===== Systemtest ===== ===== Systemtest =====
-Mit der minimalen Konfiguration unseres Postfix haben wir bereits einen lauffähigen **MTA**. Zum Testen  verwenden wir das programm **telnet**. + 
 +Mit der minimalen Konfiguration unseres Postfix haben wir bereits einen lauffähigen **MTA**. Zum Testen verwenden wir das Programm **telnet**. 
 Die Eingaben am testenden Client sind in der Farbe <html><font style="color: rgb(0, 0, 255)"><b>blau</b></font></html> und die Rückmeldungen unseres Dovecot-Servers in der Farbe <html><font style="color: rgb(66, 66, 66)"><b>hellgrau</b></font></html> gekennzeichnet. Die Ausgaben des Befehls **telnet** sind in der Farbe <html><font style="color: rgb(0, 0, 0)"><b>schwarz</b></font></html> eingefärbt. Die Eingaben am testenden Client sind in der Farbe <html><font style="color: rgb(0, 0, 255)"><b>blau</b></font></html> und die Rückmeldungen unseres Dovecot-Servers in der Farbe <html><font style="color: rgb(66, 66, 66)"><b>hellgrau</b></font></html> gekennzeichnet. Die Ausgaben des Befehls **telnet** sind in der Farbe <html><font style="color: rgb(0, 0, 0)"><b>schwarz</b></font></html> eingefärbt.
  
Zeile 2898: Zeile 2961:
 <font style="color: rgb(0, 0, 255)">mail from:&lt;&gt;</font> <font style="color: rgb(0, 0, 255)">mail from:&lt;&gt;</font>
 <font style="color: rgb(66, 66, 66)">250 2.1.0 OK</font> <font style="color: rgb(66, 66, 66)">250 2.1.0 OK</font>
-<font style="color: rgb(0, 0, 255)">rcpt to:&lt;django@vml000087.dmz.nausch.org>&gt;</font>+<font style="color: rgb(0, 0, 255)">rcpt to:&lt;django@vml000080.dmz.nausch.org>&gt;</font>
 <font style="color: rgb(66, 66, 66)">250 2.1.0 OK</font> <font style="color: rgb(66, 66, 66)">250 2.1.0 OK</font>
 <font style="color: rgb(0, 0, 255)">DATA</font> <font style="color: rgb(0, 0, 255)">DATA</font>
Zeile 2909: Zeile 2972:
 test test
 .</font> .</font>
-<font style="color: rgb(66, 66, 66)">250 2.0.0 Ok: queued as 5F251C00088</font>+<font style="color: rgb(66, 66, 66)">250 2.0.0 Ok: queued as 5FFA5600088</font>
 <font style="color: rgb(0, 0, 255)">quit</font> <font style="color: rgb(0, 0, 255)">quit</font>
 <font style="color: rgb(66, 66, 66)">221 2.0.0 Bye</font> <font style="color: rgb(66, 66, 66)">221 2.0.0 Bye</font>
Zeile 2915: Zeile 2978:
 </pre></html> </pre></html>
  
-Die Message-ID **5F251C00088** finden wir dann auch im Maillog wieder.+Die Message-ID **5FFA5600088** finden wir dann auch im Maillog wieder.
  
    # tail -n7 /var/log/maillog     # tail -n7 /var/log/maillog 
  
-   Oct 13 22:15:55 vml000087 postfix/smtpd[4304]: connect from localhost[::1] +<code>Jan 26 22:03:03 vml000080.dmz.nausch.org postfix/smtpd[14470]: connect from localhost[::1] 
-   Oct 13 22:16:34 vml000087 postfix/smtpd[4304]: 5F251C00088: client=localhost[::1] +Jan 26 22:03:46 vml000080.dmz.nausch.org postfix/smtpd[14470]: 5FFA5600088: client=localhost[::1] 
-   Oct 13 22:17:13 vml000087 postfix/cleanup[4308]: 5F251C00088: message-id=<20141013201634.5F251C00088@vml000087.dmz.nausch.org> +Jan 26 22:04:20 vml000080.dmz.nausch.org postfix/cleanup[14474]: 5FFA5600088: message-id=<20190126210346.5FFA5600088@vml000080.dmz.nausch.org> 
-   Oct 13 22:17:13 vml000087 postfix/qmgr[2202]: 5F251C00088: from=<>, size=364, nrcpt=1 (queue active) +Jan 26 22:04:20 vml000080.dmz.nausch.org postfix/qmgr[14425]: 5FFA5600088: from=<>, size=363, nrcpt=1 (queue active) 
-   Oct 13 22:17:13 vml000087 postfix/local[4309]: 5F251C00088: to=<django@vml000087.dmz.nausch.org>, relay=local, delay=63, delays=63/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to mailbox) +Jan 26 22:04:20 vml000080.dmz.nausch.org postfix/local[14475]: 5FFA5600088: to=<django@vml000080.dmz.nausch.org>, relay=local, delay=61, delays=60/0.02/0/0, dsn=2.0.0, status=sent (delivered to mailbox) 
-   Oct 13 22:17:13 vml000087 postfix/qmgr[2202]: 5F251C00088: removed +Jan 26 22:04:20 vml000080.dmz.nausch.org postfix/qmgr[14425]: 5FFA5600088: removed 
-   Oct 13 22:17:16 vml000087 postfix/smtpd[4304]: disconnect from localhost[::1]+Jan 26 22:04:23 vml000080.dmz.nausch.org postfix/smtpd[14470]: disconnect from localhost[::1] helo=1 mail=1 rcpt=1 data=1 quit=1 commands=5</code>
  
 Auf unserem Festplatten wurde die eMail auch entsprechend abgespeichert. Auf unserem Festplatten wurde die eMail auch entsprechend abgespeichert.
Zeile 2935: Zeile 2998:
    # cat /var/spool/mail/django    # cat /var/spool/mail/django
  
-<code>From MAILER-DAEMON  Mon Oct 13 22:17:13 2014+<code>From MAILER-DAEMON  Sat Jan 26 22:04:20 2019
 Return-Path: <> Return-Path: <>
-X-Original-To: django@vml000087.dmz.nausch.org +X-Original-To: django@vml000080.dmz.nausch.org 
-Delivered-To: django@vml000087.dmz.nausch.org+Delivered-To: django@vml000080.dmz.nausch.org
 Received: from foo (localhost [IPv6:::1]) Received: from foo (localhost [IPv6:::1])
-        by vml000087.dmz.nausch.org (Postfix) with SMTP id 5F251C00088 + by vml000080.dmz.nausch.org (Postfix) with SMTP id 5FFA5600088 
-        for <django@vml000087.dmz.nausch.org>; Mon, 13 Oct 2014 22:16:10 +0200 (CEST)+ for <django@vml000080.dmz.nausch.org>; Sat, 26 Jan 2019 22:03:19 +0100 (CET)
 From: michael@nausch.org From: michael@nausch.org
 To: django@vml000087.dmz.nausch.org To: django@vml000087.dmz.nausch.org
 Subject: erste testmail Subject: erste testmail
 Date: heute Date: heute
-Message-Id: <20141013201634.5F251C00088@vml000087.dmz.nausch.org>+Message-Id: <20190126210346.5FFA5600088@vml000080.dmz.nausch.org>
  
 test test
Zeile 2959: Zeile 3022:
   * **[[http://dokuwiki.nausch.org/doku.php/|Zurück zur Startseite]]**   * **[[http://dokuwiki.nausch.org/doku.php/|Zurück zur Startseite]]**
  
-/* ~~AUTOTWEET:~~ */ 
  
  • centos/mail_c7/postfix3_1.1548534375.txt.gz
  • Zuletzt geändert: 26.01.2019 20:26.
  • von django