Zum Inhalt springen

/etc/postfix/master.cf: Unterschied zwischen den Versionen

Aus Foxwiki
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 1: Zeile 1:
{{DISPLAYTITLE:master.cf}}
{{DISPLAYTITLE:master.cf}}
'''topic''' kurze Beschreibung
 
'''master.cf''' - Postfix master process configuration file format


== Beschreibung ==
== Beschreibung ==
== Installation ==
The Postfix mail system is implemented by small number of (mostly)    client commands that are invoked by users, and by a larger number of    services that run in the background.
 
Postfix services are implemented by daemon processes. These run in    the background, started on-demand by the master(8) process. The    master.cf configuration file defines how a client program connects to a    service, and what daemon program runs when a service is requested. Most    daemon processes are short-lived and terminate voluntarily after serving    '''max_use''' clients, or after inactivity for '''max_idle''' or more    units of time.
 
All daemons specified here must speak a Postfix-internal protocol.    In order to execute non-Postfix software use the local(8),    pipe(8) or spawn(8) services, or execute the software with    inetd(8) or equivalent.
 
After changing master.cf you must execute "'''postfix    reload'''" to reload the configuration.
 
== Syntax ==
== Syntax ==
The general format of the master.cf file is as follows:
* Empty lines and whitespace-only lines are ignored, as are lines whose      first non-whitespace character is a `#'.
* A logical line starts with non-whitespace text. A line that starts with      whitespace continues a logical line.
* Each logical line defines a single Postfix service. Each service is      identified by its name and type as described below. When multiple lines      specify the same service name and type, only the last one is remembered.      Otherwise, the order of master.cf service definitions does not    matter.
Each logical line consists of eight fields separated by    whitespace. These are described below in the order as they appear in the    master.cf file.
Where applicable a field of "-" requests that the    built-in default value be used. For boolean fields specify "y" or    "n" to override the default value.
=== Parameter ===
=== Parameter ===
=== Optionen ===
=== Optionen ===

Version vom 6. Juli 2022, 10:23 Uhr


master.cf - Postfix master process configuration file format

Beschreibung

The Postfix mail system is implemented by small number of (mostly) client commands that are invoked by users, and by a larger number of services that run in the background.

Postfix services are implemented by daemon processes. These run in the background, started on-demand by the master(8) process. The master.cf configuration file defines how a client program connects to a service, and what daemon program runs when a service is requested. Most daemon processes are short-lived and terminate voluntarily after serving max_use clients, or after inactivity for max_idle or more units of time.

All daemons specified here must speak a Postfix-internal protocol. In order to execute non-Postfix software use the local(8), pipe(8) or spawn(8) services, or execute the software with inetd(8) or equivalent.

After changing master.cf you must execute "postfix reload" to reload the configuration.

Syntax

The general format of the master.cf file is as follows:

  • Empty lines and whitespace-only lines are ignored, as are lines whose first non-whitespace character is a `#'.
  • A logical line starts with non-whitespace text. A line that starts with whitespace continues a logical line.
  • Each logical line defines a single Postfix service. Each service is identified by its name and type as described below. When multiple lines specify the same service name and type, only the last one is remembered. Otherwise, the order of master.cf service definitions does not matter.

Each logical line consists of eight fields separated by whitespace. These are described below in the order as they appear in the master.cf file.

Where applicable a field of "-" requests that the built-in default value be used. For boolean fields specify "y" or "n" to override the default value.

Parameter

Optionen

Umgebungsvariablen

Exit-Status

Konfiguration

Dateien

Anwendungen

Sicherheit

Dokumentation

RFC

Man-Pages

Info-Pages

Siehe auch

Links

Projekt-Homepage

Weblinks

Einzelnachweise


Testfragen

Testfrage 1

Antwort1

Testfrage 2

Antwort2

Testfrage 3

Antwort3

Testfrage 4

Antwort4

Testfrage 5

Antwort5