Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
centos:mail_c7:spam_5 [05.11.2014 21:34. ] – angelegt django | centos:mail_c7:spam_5 [22.07.2019 15:02. ] (aktuell) – Externe Bearbeitung 127.0.0.1 | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | ====== | + | ====== |
- | FIXME //... comming soon!// | + | {{: |
+ | |||
+ | Ob die Filterung von // | ||
+ | |||
+ | ===== main.cf ===== | ||
+ | Damit wir später die einfache Möglichkeiten haben, basierend auf bestimmte Inhalte im Mailheader bzw. Mailbody, Nachrichten zu bewerten oder gar zu manipulieren, | ||
+ | |||
+ | Wir legen uns in unserer Konfigurationsdatei // | ||
+ | # vim / | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | ################################################################################ | ||
+ | ## SPAM ABWEHRMECHANISMEN - INTERNER POSTFIX CONTENT-FILTER | ||
+ | # | ||
+ | # Django : 2014-10-15 - Lookup-Tabelle zum Verwalten der Routinen zur | ||
+ | # inhaltliche Prüfung der eMail-Header. Nach dem Ändern der Tabelle | ||
+ | # header_check_maps ist ein " | ||
+ | # durchzuführen, | ||
+ | # default: header_checks = | ||
+ | header_checks = pcre:/ | ||
+ | |||
+ | # Django : 2014-10-15 - Lookup-Tabelle zum Verwalten der Routinen zur | ||
+ | # inhaltliche Prüfung der eMail-Bodies. Nach dem Ändern der Tabelle | ||
+ | # body_check_maps ist ein " | ||
+ | # durchzuführen, | ||
+ | # default: body_checks = | ||
+ | body_checks = pcre:/ | ||
+ | </ | ||
+ | |||
+ | Voraussetzung hierzu (Perl Compatible Regular Expressions) ist natürlich die Unterstützung des installierten Postfix. Mit folgender Abfrage können wir überprüfen, | ||
+ | # postconf -m | grep pcre | ||
+ | |||
+ | | ||
+ | |||
+ | Die pcre-Unterstützung bei Postfix 2.11.3 | ||
+ | |||
+ | Trifft das gewählte Suchmuster bei unseren **PRCE**((**P**erl **C**ompatible **R**egular **E**xpressions)) zu, so haben wir unter anderem folgene Möglichkeiten: | ||
+ | |||
+ | * **REJECT** Nachricht mit einem fatalen Fehler 5xx ablehnen | ||
+ | * **REJECT MSG** Nachricht mit dem Text MSG ablehnen | ||
+ | * **DISCARD** Die Nachricht wird verworfen und zwar an alle Empfänger, sobald einer der Empfänger via DISCARD abgelehnt wird. Dem Einliefernden client wir eine erfolgreiche Zustellung mittels 250 OK vorgegaukelt. | ||
+ | |||
+ | Im Konfigurationsverzeichnis von Postfix finden wir für weitere Beschreibungen die Manpage für den Einsatz und die Verwendung der body- und header-checks. Dort finden sich jede Menge hilfreicher Tips zur **//Postfix built-in Content Inspection// | ||
+ | # less / | ||
+ | <file bash / | ||
+ | # | ||
+ | # NAME | ||
+ | # header_checks - Postfix built-in content inspection | ||
+ | # | ||
+ | # SYNOPSIS | ||
+ | # header_checks | ||
+ | # mime_header_checks | ||
+ | # nested_header_checks | ||
+ | # body_checks | ||
+ | # | ||
+ | # postmap -q " | ||
+ | # postmap -q - pcre:/ | ||
+ | # | ||
+ | # DESCRIPTION | ||
+ | # This document | ||
+ | # message headers and message body lines; it is implemented | ||
+ | # by the Postfix | ||
+ | # See access(5) for access control | ||
+ | # information. | ||
+ | # | ||
+ | # Each message | ||
+ | # against a list of patterns. | ||
+ | # corresponding action is executed, and the matching process | ||
+ | # is repeated for the next message header | ||
+ | # line. | ||
+ | # | ||
+ | # For examples, see the EXAMPLES section at the end of this | ||
+ | # manual page. | ||
+ | # | ||
+ | # Postfix header or body_checks are designed to stop a flood | ||
+ | # of mail from worms or viruses; they do not decode attach- | ||
+ | # ments, and they do not unzip archives. See the documents | ||
+ | # referenced | ||
+ | # more sophisticated content analysis. | ||
+ | # | ||
+ | # Postfix supports four built-in content inspection classes: | ||
+ | # | ||
+ | # header_checks | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # mime_header_checks (default: $header_checks) | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # This feature is available in Postfix 2.0 and later. | ||
+ | # | ||
+ | # nested_header_checks (default: $header_checks) | ||
+ | # | ||
+ | # email messages (except for the headers | ||
+ | # | ||
+ | # | ||
+ | # This feature is available in Postfix 2.0 and later. | ||
+ | # | ||
+ | # body_checks | ||
+ | # These are applied to all other content, | ||
+ | # | ||
+ | # | ||
+ | # With Postfix versions before 2.0, all content after | ||
+ | # the initial message headers is treated as body con- | ||
+ | # | ||
+ | # | ||
+ | # Note: message headers are examined one logical header at a | ||
+ | # time, even when a message | ||
+ | # Body lines are always examined one line at a time. | ||
+ | # | ||
+ | # COMPATIBILITY | ||
+ | # With Postfix version 2.2 and earlier specify " | ||
+ | # to query a table that contains case sensitive patterns. By | ||
+ | # default, | ||
+ | # | ||
+ | # TABLE FORMAT | ||
+ | # This document assumes that header | ||
+ | # are specified | ||
+ | # lookup tables. Usually the best performance | ||
+ | # with pcre (Perl Compatible Regular Expression) tables, but | ||
+ | # the slower regexp (POSIX regular expressions) | ||
+ | # more widely | ||
+ | # find out what lookup table types your Postfix system | ||
+ | # ports. | ||
+ | # | ||
+ | # The general format of Postfix regular expression tables is | ||
+ | # given below. | ||
+ | # flags | ||
+ | # respectively. | ||
+ | # | ||
+ | # / | ||
+ | # When /pattern/ matches the input string, | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # !/ | ||
+ | # When /pattern/ does not match the input string, | ||
+ | # | ||
+ | # | ||
+ | # if / | ||
+ | # | ||
+ | # endif Match the input string against the patterns between | ||
+ | # if and endif, if and only if the same input string | ||
+ | # also matches /pattern/. The if..endif can nest. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # if !/ | ||
+ | # | ||
+ | # endif Match the input string against the patterns between | ||
+ | # | ||
+ | # does not match /pattern/. The if..endif can nest. | ||
+ | # | ||
+ | # blank lines and comments | ||
+ | # Empty lines and whitespace-only lines are ignored, | ||
+ | # | ||
+ | # is a `#'. | ||
+ | # | ||
+ | # multi-line text | ||
+ | # A pattern/ | ||
+ | # | ||
+ | # a logical line. | ||
+ | # | ||
+ | # TABLE SEARCH ORDER | ||
+ | # For each line of message input, the patterns | ||
+ | # in the order as specified in the table. When a pattern is | ||
+ | # found that matches | ||
+ | # action | ||
+ | # inspected. | ||
+ | # | ||
+ | # TEXT SUBSTITUTION | ||
+ | # Substitution of substrings | ||
+ | # into the action string is possible using the conventional | ||
+ | # Perl syntax ($1, $2, etc.). | ||
+ | # string | ||
+ | # aren't followed by whitespace. | ||
+ | # | ||
+ | # Note: since negated patterns (those preceded by !) return | ||
+ | # a result when the expression does not match, substitutions | ||
+ | # are not available for negated patterns. | ||
+ | # | ||
+ | # ACTIONS | ||
+ | # Action names are case insensitive. They are shown in upper | ||
+ | # case for consistency with other Postfix documentation. | ||
+ | # | ||
+ | # DISCARD optional text... | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # ient without discarding the entire message, use the | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # This feature is available in Postfix 2.0 and later. | ||
+ | # | ||
+ | # DUNNO Pretend | ||
+ | # tern, and inspect the next input line. This action | ||
+ | # can be used to shorten the table search. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # as DUNNO. | ||
+ | # | ||
+ | # This feature is available in Postfix 2.1 and later. | ||
+ | # | ||
+ | # FILTER transport: | ||
+ | # Write a content filter request to the queue file, | ||
+ | # | ||
+ | # plete message is received it will be sent through | ||
+ | # the specified external content filter. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Note: this action overrides the content_filter set- | ||
+ | # ting, and affects all recipients of the message. In | ||
+ | # | ||
+ | # the last one is executed. | ||
+ | # | ||
+ | # This feature is available in Postfix 2.0 and later. | ||
+ | # | ||
+ | # HOLD optional text... | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # it or releases it for delivery. | ||
+ | # text if specified, otherwise log a generic message. | ||
+ | # | ||
+ | # Mail that is placed on hold can be examined | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Note: use " | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # not expire within a few delivery attempts. | ||
+ | # | ||
+ | # Note: this action affects | ||
+ | # | ||
+ | # | ||
+ | # This feature is available in Postfix 2.0 and later. | ||
+ | # | ||
+ | # IGNORE Delete the current line from the input, and inspect | ||
+ | # the next input line. | ||
+ | # | ||
+ | # PREPEND text... | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # line, immediately | ||
+ | # triggered the PREPEND action. | ||
+ | # | ||
+ | # | ||
+ | # the input stream: | ||
+ | # header/body checks or address rewriting, and | ||
+ | # it does not affect the way that Postfix adds | ||
+ | # missing message headers. | ||
+ | # | ||
+ | # | ||
+ | # line, the prepended text must begin with a | ||
+ | # valid message header label. | ||
+ | # | ||
+ | # | ||
+ | # line text. | ||
+ | # | ||
+ | # This feature is available in Postfix 2.1 and later. | ||
+ | # | ||
+ | # REDIRECT user@domain | ||
+ | # Write a message redirection request | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # This feature is available in Postfix 2.1 and later. | ||
+ | # | ||
+ | # REPLACE text... | ||
+ | # | ||
+ | # and inspect the next input line. | ||
+ | # | ||
+ | # This feature is available in Postfix 2.2 and later. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # replacement | ||
+ | # header label. | ||
+ | # | ||
+ | # | ||
+ | # stream. | ||
+ | # action, a replaced | ||
+ | # subject | ||
+ | # the way that Postfix | ||
+ | # headers. | ||
+ | # | ||
+ | # REJECT optional text... | ||
+ | # | ||
+ | # | ||
+ | # wise reply with a generic error message. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # tus codes. | ||
+ | # ning of optional text..., Postfix inserts a default | ||
+ | # | ||
+ | # | ||
+ | # WARN optional text... | ||
+ | # Log a warning with the optional text... (or log a | ||
+ | # | ||
+ | # This action is useful for debugging and for testing | ||
+ | # a pattern before applying more drastic actions. | ||
+ | # | ||
+ | # BUGS | ||
+ | # Empty lines never match, because some map types mis-behave | ||
+ | # when given a zero-length search string. | ||
+ | # may be removed for regular expression tables in a future | ||
+ | # release. | ||
+ | # | ||
+ | # Many people overlook the main limitations | ||
+ | # body_checks rules. | ||
+ | # | ||
+ | # o These rules operate on one logical message header | ||
+ | # or one body line at a time. A decision made for one | ||
+ | # line is not carried over to the next line. | ||
+ | # | ||
+ | # o If text in the message body is encoded (RFC 2045) | ||
+ | # then the rules need to be specified for the encoded | ||
+ | # | ||
+ | # | ||
+ | # o Likewise, | ||
+ | # 2047) then the rules need to be specified | ||
+ | # | ||
+ | # | ||
+ | # Message | ||
+ | # excluded from inspection. Examples of such message headers | ||
+ | # are From:, To:, Message-ID:, | ||
+ | # | ||
+ | # Message | ||
+ | # examined before they are deleted. Examples are: Bcc:, Con- | ||
+ | # tent-Length:, | ||
+ | # | ||
+ | # CONFIGURATION PARAMETERS | ||
+ | # body_checks | ||
+ | # | ||
+ | # body lines. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # body_checks_size_limit | ||
+ | # The amount of content | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # header_checks | ||
+ | # | ||
+ | # mime_header_checks (default: $header_checks) | ||
+ | # | ||
+ | # nested_header_checks (default: $header_checks) | ||
+ | # | ||
+ | # | ||
+ | # the initial message | ||
+ | # | ||
+ | # sage, and to the initial headers of attached | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # at a time, even when a message header spans multi- | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # disable_mime_input_processing | ||
+ | # While receiving mail, give no special treatment | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # that body_checks is applied to the remainder of the | ||
+ | # | ||
+ | # | ||
+ | # Note: when used in this manner, | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # EXAMPLES | ||
+ | # Header pattern to block attachments | ||
+ | # extensions. | ||
+ | # fied, so that there is no need to collapse | ||
+ | # into | ||
+ | # [[: | ||
+ | # strings. | ||
+ | # | ||
+ | # / | ||
+ | # header_checks | ||
+ | # | ||
+ | # / | ||
+ | # / | ||
+ | # ade|adp|asp|bas|bat|chm|cmd|com|cpl|crt|dll|exe| | ||
+ | # hlp|ht[at]| | ||
+ | # inf|ins|isp|jse? | ||
+ | # \{[[: | ||
+ | # ops|pcd|pif|prf|reg|sc[frt]|sh[bsm]|swf| | ||
+ | # vb[esx]? | ||
+ | # REJECT Attachment name " | ||
+ | # | ||
+ | # Body pattern to stop a specific HTML browser vulnerability | ||
+ | # exploit. | ||
+ | # | ||
+ | # /etc/postfix/main.cf: | ||
+ | # body_checks = regexp:/ | ||
+ | # | ||
+ | # / | ||
+ | # / | ||
+ | # REJECT IFRAME vulnerability exploit | ||
+ | # | ||
+ | # SEE ALSO | ||
+ | # cleanup(8), canonicalize and enqueue Postfix message | ||
+ | # pcre_table(5), | ||
+ | # regexp_table(5), | ||
+ | # postconf(1), | ||
+ | # postmap(1), Postfix lookup table management | ||
+ | # postsuper(1), | ||
+ | # postcat(1), show Postfix queue file contents | ||
+ | # RFC 2045, base64 and quoted-printable encoding rules | ||
+ | # RFC 2047, message header encoding for non-ASCII text | ||
+ | # | ||
+ | # README FILES | ||
+ | # Use " | ||
+ | # tory" to locate this information. | ||
+ | # DATABASE_README, | ||
+ | # CONTENT_INSPECTION_README, | ||
+ | # BUILTIN_FILTER_README, | ||
+ | # BACKSCATTER_README, | ||
+ | # | ||
+ | # LICENSE | ||
+ | # The Secure | ||
+ | # software. | ||
+ | # | ||
+ | # AUTHOR(S) | ||
+ | # Wietse Venema | ||
+ | # IBM T.J. Watson Research | ||
+ | # P.O. Box 704 | ||
+ | # Yorktown Heights, NY 10598, USA | ||
+ | # | ||
+ | # | ||
+ | </ | ||
+ | |||
+ | ===== header_checks_map ===== | ||
+ | Wollen wir nun Nachrichten von bestimmten Absendern oder anderen Einträgen in den Headerzeilen generell blocken, so legen wir uns folgende Konfigurationsdatei // | ||
+ | # vim / | ||
+ | <file bash / | ||
+ | # Kapitel 13.5 Filtern von eMails nach Inhalt | ||
+ | # Kapitel 12.3 Überprüfen von Headern | ||
+ | # In der Postfix-Konfigurationsdatei / | ||
+ | # body_checks = pcre:/ | ||
+ | # | ||
+ | # Nach dem Ändern der Datei ist ein " | ||
+ | # | ||
+ | # Die Nummern hinter dem REJECT tauchen später als SMTP-Error und auch im Mailserver-Log auf. | ||
+ | # Die auslösende Filter-Regel, | ||
+ | # | ||
+ | |||
+ | # Ausnahmeregelung für den sicheren IT-/Mailbetrieb im heimischen Netzwerk | ||
+ | # | ||
+ | # Domeus hat bis heute nicht den Unterschied zwischen Mailheader-To und | ||
+ | # SMTP-Envelope-To verstanden und fabriziert seit nunmehr über sieben Jahren in | ||
+ | # schöner Regelmäßigkeit Mailschleifen im vier/fünfstelligen Bereich. | ||
+ | # | ||
+ | / | ||
+ | # | ||
+ | # Dauerhaft genutzte Regelungen: | ||
+ | # =============================================== | ||
+ | # [Immer mit aufsteiger Nummer sauber eintragen!] | ||
+ | # | ||
+ | If / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | Endif | ||
+ | # | ||
+ | # und das Ganze nach Header-From | ||
+ | # ============================== | ||
+ | # | ||
+ | #If / | ||
+ | #/^From: .*Online Spiele.*/ | ||
+ | #/^From: .*Apotheken-News.*/ | ||
+ | #/^From: .*Kasino.*/ | ||
+ | #/^From: .*Pharmacy.*/ | ||
+ | #/^From: .*Royal Club Casino.*/ | ||
+ | #/^From: .*Euro Dice Casino.*/ | ||
+ | #/ | ||
+ | #Endif | ||
+ | |||
+ | |||
+ | # Django : 2014-10-10 | ||
+ | ##If /^To:/i | ||
+ | ##/^To: .*dj4n90@piraten-it.guru.*/ | ||
+ | ##Endif | ||
+ | # | ||
+ | # generelle Filerregelungen nach den üblichen Verdächtigen | ||
+ | # ======================================================== | ||
+ | # | ||
+ | /^Date: .* 200[0-7]/ | ||
+ | /^Date: .* 19[0-9][0-9]/ | ||
+ | If / | ||
+ | /^X-Mailer: 0001/ | ||
+ | /^X-Mailer: Avalanche/ | ||
+ | /^X-Mailer: Crescent Internet Tool/ | ||
+ | /^X-Mailer: DiffondiCool/ | ||
+ | /^X-Mailer: E-Mail Delivery Agent/ | ||
+ | /^X-Mailer: Emailer Platinum/ | ||
+ | /^X-Mailer: Entity/ | ||
+ | /^X-Mailer: Extractor/ | ||
+ | /^X-Mailer: Floodgate/ | ||
+ | /^X-Mailer: GOTO Software Sarbacane/ | ||
+ | /^X-Mailer: MailWorkz/ | ||
+ | /^X-Mailer: MassE-Mail/ | ||
+ | /^X-Mailer: MaxBulk.Mailer/ | ||
+ | /^X-Mailer: News Breaker Pro/ | ||
+ | /^X-Mailer: SmartMailer/ | ||
+ | /^X-Mailer: StormPort/ | ||
+ | /^X-Mailer: SuperMail-2/ | ||
+ | Endif | ||
+ | </ | ||
+ | |||
+ | ===== body_checks_map ===== | ||
+ | Wollen wir nun Nachrichten von bestimmten Absendern oder anderen Einträgen in den Headerzeilen generell blocken, so legen wir uns folgende Konfigurationsdatei // | ||
+ | # / | ||
+ | <file bash / | ||
+ | # Django : 2012-02-06 | ||
+ | # Kapitel 13.5 Filtern von eMails nach Inhalt | ||
+ | # Kapitel 12.6 Body prüfen | ||
+ | # In der Postfix-Konfigurationsdatei / | ||
+ | # body_checks = pcre:/ | ||
+ | # | ||
+ | # Nach dem Ändern der Datei ist ein " | ||
+ | # | ||
+ | # Die Nummern hinter dem REJECT tauchen später als SMTP-Error und auch im Mailserver-Log auf. | ||
+ | # Die auslösende Filter-Regel, | ||
+ | # | ||
+ | |||
+ | #/ | ||
+ | #/ | ||
+ | </ | ||
+ | |||
+ | ===== Aktivierung ===== | ||
+ | Zum Aktivieren unserer Konfigurationsänderungen führen wir nun einen //Reload// unseres Postfix-Servers durch. | ||
+ | # systemctl reload postfix.service | ||
+ | |||
+ | Bei Bedarf können wir uns noch vergewissern und prüfen welchen Status unser MX nun hat. | ||
+ | # systemctl status postfix.service | ||
+ | |||
+ | < | ||
+ | | ||
+ | | ||
+ | Process: 15133 ExecStop=/ | ||
+ | Process: 17334 ExecReload=/ | ||
+ | Process: 15148 ExecStart=/ | ||
+ | Process: 15146 ExecStartPre=/ | ||
+ | Process: 15143 ExecStartPre=/ | ||
+ | Main PID: 15221 (master) | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | Nov 12 14:02:04 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:02:04 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:02:04 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:02:05 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:02:05 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:35:39 vml000087.dmz.nausch.org systemd[1]: Reloading Postfix Mail Transport Agent. | ||
+ | Nov 12 14:35:39 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:35:39 vml000087.dmz.nausch.org systemd[1]: Reloaded Postfix Mail Transport Agent. | ||
+ | Nov 12 14:35:47 vml000087.dmz.nausch.org systemd[1]: Reloading Postfix Mail Transport Agent. | ||
+ | Nov 12 14:35:47 vml000087.dmz.nausch.org postfix/ | ||
+ | Nov 12 14:35:47 vml000087.dmz.nausch.org systemd[1]: Reloaded Postfix Mail Transport Agent. | ||
+ | Hint: Some lines were ellipsized, use -l to show in full. | ||
+ | </ | ||
+ | |||
+ | ====== Links ====== | ||
+ | * **⇐ [[centos: | ||
+ | * **⇒ [[centos: | ||
+ | * **[[centos: | ||
+ | * **[[wiki: | ||
+ | * **[[http:// | ||
+ | |||
+ |