1QMQPD(8) System Manager's Manual QMQPD(8)
2
3
4
6 qmqpd - Postfix QMQP server
7
9 qmqpd [generic Postfix daemon options]
10
12 The Postfix QMQP server receives one message per connection. Each mes‐
13 sage is piped through the cleanup(8) daemon, and is placed into the
14 incoming queue as one single queue file. The program expects to be run
15 from the master(8) process manager.
16
17 The QMQP server implements one access policy: only explicitly autho‐
18 rized client hosts are allowed to use the service.
19
21 The QMQP server is moderately security-sensitive. It talks to QMQP
22 clients and to DNS servers on the network. The QMQP server can be run
23 chrooted at fixed low privilege.
24
26 Problems and transactions are logged to syslogd(8) or postlogd(8).
27
29 The QMQP protocol provides only one server reply per message delivery.
30 It is therefore not possible to reject individual recipients.
31
32 The QMQP protocol requires the server to receive the entire message
33 before replying. If a message is malformed, or if any netstring compo‐
34 nent is longer than acceptable, Postfix replies immediately and closes
35 the connection. It is left up to the client to handle the situation.
36
38 Changes to main.cf are picked up automatically, as qmqpd(8) processes
39 run for only a limited amount of time. Use the command "postfix reload"
40 to speed up a change.
41
42 The text below provides only a parameter summary. See postconf(5) for
43 more details including examples.
44
46 content_filter (empty)
47 After the message is queued, send the entire message to the
48 specified transport:destination.
49
50 receive_override_options (empty)
51 Enable or disable recipient validation, built-in content filter‐
52 ing, or address mapping.
53
55 Preliminary SMTPUTF8 support is introduced with Postfix 3.0.
56
57 smtputf8_enable (yes)
58 Enable preliminary SMTPUTF8 support for the protocols described
59 in RFC 6531..6533.
60
61 smtputf8_autodetect_classes (sendmail, verify)
62 Detect that a message requires SMTPUTF8 support for the speci‐
63 fied mail origin classes.
64
65 Available in Postfix version 3.2 and later:
66
67 enable_idna2003_compatibility (no)
68 Enable 'transitional' compatibility between IDNA2003 and
69 IDNA2008, when converting UTF-8 domain names to/from the ASCII
70 form that is used for DNS lookups.
71
73 line_length_limit (2048)
74 Upon input, long lines are chopped up into pieces of at most
75 this length; upon delivery, long lines are reconstructed.
76
77 hopcount_limit (50)
78 The maximal number of Received: message headers that is allowed
79 in the primary message headers.
80
81 message_size_limit (10240000)
82 The maximal size in bytes of a message, including envelope
83 information.
84
85 qmqpd_timeout (300s)
86 The time limit for sending or receiving information over the
87 network.
88
90 debug_peer_level (2)
91 The increment in verbose logging level when a remote client or
92 server matches a pattern in the debug_peer_list parameter.
93
94 debug_peer_list (empty)
95 Optional list of remote client or server hostname or network
96 address patterns that cause the verbose logging level to
97 increase by the amount specified in $debug_peer_level.
98
99 soft_bounce (no)
100 Safety net to keep mail queued that would otherwise be returned
101 to the sender.
102
104 qmqpd_error_delay (1s)
105 How long the Postfix QMQP server will pause before sending a
106 negative reply to the remote QMQP client.
107
109 config_directory (see 'postconf -d' output)
110 The default location of the Postfix main.cf and master.cf con‐
111 figuration files.
112
113 daemon_timeout (18000s)
114 How much time a Postfix daemon process may take to handle a
115 request before it is terminated by a built-in watchdog timer.
116
117 ipc_timeout (3600s)
118 The time limit for sending or receiving information over an
119 internal communication channel.
120
121 max_idle (100s)
122 The maximum amount of time that an idle Postfix daemon process
123 waits for an incoming connection before terminating voluntarily.
124
125 max_use (100)
126 The maximal number of incoming connections that a Postfix daemon
127 process will service before terminating voluntarily.
128
129 process_id (read-only)
130 The process ID of a Postfix command or daemon process.
131
132 process_name (read-only)
133 The process name of a Postfix command or daemon process.
134
135 qmqpd_authorized_clients (empty)
136 What remote QMQP clients are allowed to connect to the Postfix
137 QMQP server port.
138
139 queue_directory (see 'postconf -d' output)
140 The location of the Postfix top-level queue directory.
141
142 syslog_facility (mail)
143 The syslog facility of Postfix logging.
144
145 syslog_name (see 'postconf -d' output)
146 A prefix that is prepended to the process name in syslog
147 records, so that, for example, "smtpd" becomes "prefix/smtpd".
148
149 verp_delimiter_filter (-=+)
150 The characters Postfix accepts as VERP delimiter characters on
151 the Postfix sendmail(1) command line and in SMTP commands.
152
153 Available in Postfix version 2.5 and later:
154
155 qmqpd_client_port_logging (no)
156 Enable logging of the remote QMQP client port in addition to the
157 hostname and IP address.
158
159 Available in Postfix 3.3 and later:
160
161 service_name (read-only)
162 The master.cf service name of a Postfix daemon process.
163
165 http://cr.yp.to/proto/qmqp.html, QMQP protocol
166 cleanup(8), message canonicalization
167 master(8), process manager
168 postlogd(8), Postfix logging
169 syslogd(8), system logging
170
172 Use "postconf readme_directory" or "postconf html_directory" to locate
173 this information.
174 QMQP_README, Postfix ezmlm-idx howto.
175
177 The Secure Mailer license must be distributed with this software.
178
180 The qmqpd service was introduced with Postfix version 1.1.
181
183 Wietse Venema
184 IBM T.J. Watson Research
185 P.O. Box 704
186 Yorktown Heights, NY 10598, USA
187
188 Wietse Venema
189 Google, Inc.
190 111 8th Avenue
191 New York, NY 10011, USA
192
193
194
195 QMQPD(8)