13
13
<b>qmgr</b> [generic Postfix daemon options]
16
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon awaits the arrival of incoming mail and
17
arranges for its delivery via Postfix delivery processes.
18
The actual mail routing strategy is delegated to the <a href="trivial-rewrite.8.html"><b>triv-</b></a>
19
<a href="trivial-rewrite.8.html"><b>ial-rewrite</b>(8)</a> daemon. This program expects to be run
20
from the <a href="master.8.html"><b>master</b>(8)</a> process manager.
16
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon awaits the arrival of incoming mail and arranges for
17
its delivery via Postfix delivery processes. The actual mail routing
18
strategy is delegated to the <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon. This program
19
expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager.
22
Mail addressed to the local <b>double-bounce</b> address is
23
logged and discarded. This stops potential loops caused
24
by undeliverable bounce notifications.
21
Mail addressed to the local <b>double-bounce</b> address is logged and dis-
22
carded. This stops potential loops caused by undeliverable bounce
27
26
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon maintains the following queues:
30
Inbound mail from the network, or mail picked up by
31
the local <a href="pickup.8.html"><b>pickup</b>(8)</a> daemon from the <b>maildrop</b> direc-
29
Inbound mail from the network, or mail picked up by the local
30
<a href="pickup.8.html"><b>pickup</b>(8)</a> daemon from the <b>maildrop</b> directory.
34
<b>active</b> Messages that the queue manager has opened for
35
delivery. Only a limited number of messages is
36
allowed to enter the <b>active</b> queue (leaky bucket
37
strategy, for a fixed delivery rate).
32
<b>active</b> Messages that the queue manager has opened for delivery. Only a
33
limited number of messages is allowed to enter the <b>active</b> queue
34
(leaky bucket strategy, for a fixed delivery rate).
40
Mail that could not be delivered upon the first
41
attempt. The queue manager implements exponential
42
backoff by doubling the time between delivery
37
Mail that could not be delivered upon the first attempt. The
38
queue manager implements exponential backoff by doubling the
39
time between delivery attempts.
46
Unreadable or damaged queue files are moved here
42
Unreadable or damaged queue files are moved here for inspection.
49
<b>hold</b> Messages that are kept "on hold" are kept here
50
until someone sets them free.
44
<b>hold</b> Messages that are kept "on hold" are kept here until someone
52
47
<b>DELIVERY STATUS REPORTS</b>
53
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon keeps an eye on per-message delivery
54
status reports in the following directories. Each status
55
report file has the same name as the corresponding message
58
<b>bounce</b> Per-recipient status information about why mail is
59
bounced. These files are maintained by the
60
<a href="bounce.8.html"><b>bounce</b>(8)</a> daemon.
62
<b>defer</b> Per-recipient status information about why mail is
63
delayed. These files are maintained by the
64
<a href="defer.8.html"><b>defer</b>(8)</a> daemon.
66
<b>trace</b> Per-recipient status information as requested with
67
the Postfix "<b>sendmail -v</b>" or "<b>sendmail -bv</b>" com-
68
mand. These files are maintained by the <a href="trace.8.html"><b>trace</b>(8)</a>
71
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is responsible for asking the
72
<a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or <a href="trace.8.html"><b>trace</b>(8)</a> daemons to send delivery
48
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon keeps an eye on per-message delivery status reports
49
in the following directories. Each status report file has the same name
50
as the corresponding message file:
52
<b>bounce</b> Per-recipient status information about why mail is bounced.
53
These files are maintained by the <a href="bounce.8.html"><b>bounce</b>(8)</a> daemon.
55
<b>defer</b> Per-recipient status information about why mail is delayed.
56
These files are maintained by the <a href="defer.8.html"><b>defer</b>(8)</a> daemon.
58
<b>trace</b> Per-recipient status information as requested with the Postfix
59
"<b>sendmail -v</b>" or "<b>sendmail -bv</b>" command. These files are main-
60
tained by the <a href="trace.8.html"><b>trace</b>(8)</a> daemon.
62
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is responsible for asking the <a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or
63
<a href="trace.8.html"><b>trace</b>(8)</a> daemons to send delivery reports.
76
The queue manager implements a variety of strategies for
77
either opening queue files (input) or for message delivery
66
The queue manager implements a variety of strategies for either opening
67
queue files (input) or for message delivery (output).
80
69
<b>leaky bucket</b>
81
This strategy limits the number of messages in the
82
<b>active</b> queue and prevents the queue manager from
83
running out of memory under heavy load.
70
This strategy limits the number of messages in the <b>active</b> queue
71
and prevents the queue manager from running out of memory under
86
When the <b>active</b> queue has room, the queue manager
87
takes one message from the <a href="QSHAPE_README.html#incoming_queue"><b>incoming</b> queue</a> and one
88
from the <b>deferred</b> queue. This prevents a large mail
89
backlog from blocking the delivery of new mail.
75
When the <b>active</b> queue has room, the queue manager takes one mes-
76
sage from the <a href="QSHAPE_README.html#incoming_queue"><b>incoming</b> queue</a> and one from the <b>deferred</b> queue.
77
This prevents a large mail backlog from blocking the delivery of
92
This strategy eliminates "thundering herd" problems
93
by slowly adjusting the number of parallel deliver-
94
ies to the same destination.
81
This strategy eliminates "thundering herd" problems by slowly
82
adjusting the number of parallel deliveries to the same destina-
97
The queue manager sorts delivery requests by desti-
98
nation. Round-robin selection prevents one desti-
99
nation from dominating deliveries to other destina-
86
The queue manager sorts delivery requests by destination.
87
Round-robin selection prevents one destination from dominating
88
deliveries to other destinations.
102
90
<b>exponential backoff</b>
103
Mail that cannot be delivered upon the first
104
attempt is deferred. The time interval between
105
delivery attempts is doubled after each attempt.
91
Mail that cannot be delivered upon the first attempt is
92
deferred. The time interval between delivery attempts is dou-
93
bled after each attempt.
107
95
<b>destination status cache</b>
108
The queue manager avoids unnecessary delivery
109
attempts by maintaining a short-term, in-memory
110
list of unreachable destinations.
96
The queue manager avoids unnecessary delivery attempts by main-
97
taining a short-term, in-memory list of unreachable destina-
112
100
<b>preemptive message scheduling</b>
113
The queue manager attempts to minimize the average
114
per-recipient delay while still preserving the cor-
115
rect per-message delays, using a sophisticated pre-
116
emptive message scheduling.
101
The queue manager attempts to minimize the average per-recipient
102
delay while still preserving the correct per-message delays,
103
using a sophisticated preemptive message scheduling.
119
On an idle system, the queue manager waits for the arrival
120
of trigger events, or it waits for a timer to go off. A
121
trigger is a one-byte message. Depending on the message
122
received, the queue manager performs one of the following
123
actions (the message is followed by the symbolic constant
124
used internally by the software):
106
On an idle system, the queue manager waits for the arrival of trigger
107
events, or it waits for a timer to go off. A trigger is a one-byte mes-
108
sage. Depending on the message received, the queue manager performs
109
one of the following actions (the message is followed by the symbolic
110
constant used internally by the software):
126
112
<b>D (QMGR_REQ_SCAN_DEFERRED)</b>
127
Start a <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan. If a deferred queue
128
scan is already in progress, that scan will be
129
restarted as soon as it finishes.
113
Start a <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan. If a deferred queue scan is
114
already in progress, that scan will be restarted as soon as it
131
117
<b>I (QMGR_REQ_SCAN_INCOMING)</b>
132
Start an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> scan. If an incoming queue
133
scan is already in progress, that scan will be
134
restarted as soon as it finishes.
118
Start an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> scan. If an incoming queue scan is
119
already in progress, that scan will be restarted as soon as it
136
122
<b>A (QMGR_REQ_SCAN_ALL)</b>
137
Ignore <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> file time stamps. The request
138
affects the next <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan.
123
Ignore <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> file time stamps. The request affects the
124
next <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan.
140
126
<b>F (QMGR_REQ_FLUSH_DEAD)</b>
141
Purge all information about dead transports and
127
Purge all information about dead transports and destinations.
144
129
<b>W (TRIGGER_REQ_WAKEUP)</b>
145
Wakeup call, This is used by the master server to
146
instantiate servers that should not go away for-
147
ever. The action is to start an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a>
130
Wakeup call, This is used by the master server to instantiate
131
servers that should not go away forever. The action is to start
132
an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> scan.
150
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon reads an entire buffer worth of trig-
151
gers. Multiple identical trigger requests are collapsed
152
into one, and trigger requests are sorted so that <b>A</b> and <b>F</b>
153
precede <b>D</b> and <b>I</b>. Thus, in order to force a <a href="QSHAPE_README.html#deferred_queue">deferred queue</a>
154
run, one would request <b>A F D</b>; in order to notify the queue
155
manager of the arrival of new mail one would request <b>I</b>.
134
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon reads an entire buffer worth of triggers. Multiple
135
identical trigger requests are collapsed into one, and trigger requests
136
are sorted so that <b>A</b> and <b>F</b> precede <b>D</b> and <b>I</b>. Thus, in order to force a
137
<a href="QSHAPE_README.html#deferred_queue">deferred queue</a> run, one would request <b>A F D</b>; in order to notify the
138
queue manager of the arrival of new mail one would request <b>I</b>.
158
141
<a href="http://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced status codes)
159
142
<a href="http://tools.ietf.org/html/rfc3464">RFC 3464</a> (Delivery status notifications)
162
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is not security sensitive. It reads
163
single-character messages from untrusted local users, and
164
thus may be susceptible to denial of service attacks. The
165
<a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon does not talk to the outside world, and it
166
can be run at fixed low privilege in a chrooted environ-
145
The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon is not security sensitive. It reads single-character
146
messages from untrusted local users, and thus may be susceptible to
147
denial of service attacks. The <a href="qmgr.8.html"><b>qmgr</b>(8)</a> daemon does not talk to the out-
148
side world, and it can be run at fixed low privilege in a chrooted
169
151
<b>DIAGNOSTICS</b>
170
Problems and transactions are logged to the syslog daemon.
171
Corrupted message files are saved to the <b>corrupt</b> queue for
152
Problems and transactions are logged to the syslog daemon. Corrupted
153
message files are saved to the <b>corrupt</b> queue for further inspection.
174
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter,
175
the postmaster is notified of bounces and of other trou-
155
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas-
156
ter is notified of bounces and of other trouble.
179
A single queue manager process has to compete for disk
180
access with multiple front-end processes such as
181
<a href="cleanup.8.html"><b>cleanup</b>(8)</a>. A sudden burst of inbound mail can negatively
182
impact outbound delivery rates.
159
A single queue manager process has to compete for disk access with mul-
160
tiple front-end processes such as <a href="cleanup.8.html"><b>cleanup</b>(8)</a>. A sudden burst of inbound
161
mail can negatively impact outbound delivery rates.
184
163
<b>CONFIGURATION PARAMETERS</b>
185
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically as
186
<a href="qmgr.8.html"><b>qmgr</b>(8)</a> is a persistent process. Use the "<b>postfix reload</b>"
187
command after a configuration change.
189
The text below provides only a parameter summary. See
190
<a href="postconf.5.html"><b>postconf</b>(5)</a> for more details including examples.
192
In the text below, <i>transport</i> is the first field in a <b>mas-</b>
164
Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically as <a href="qmgr.8.html"><b>qmgr</b>(8)</a> is a per-
165
sistent process. Use the "<b>postfix reload</b>" command after a configuration
168
The text below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for
169
more details including examples.
171
In the text below, <i>transport</i> is the first field in a <a href="master.5.html"><b>master.cf</b></a> entry.
195
173
<b>COMPATIBILITY CONTROLS</b>
196
174
Available before Postfix version 2.5:
198
176
<b><a href="postconf.5.html#allow_min_user">allow_min_user</a> (no)</b>
199
Allow a sender or recipient address to have `-' as
177
Allow a sender or recipient address to have `-' as the first
202
180
Available with Postfix version 2.7 and later:
204
182
<b><a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> (empty)</b>
205
When a <a href="postconf.5.html#content_filter">content_filter</a> or FILTER request specifies
206
no explicit next-hop destination, use $default_fil-
207
ter_nexthop instead; when that value is empty, use
208
the domain in the recipient address.
183
When a <a href="postconf.5.html#content_filter">content_filter</a> or FILTER request specifies no explicit
184
next-hop destination, use $<a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> instead; when
185
that value is empty, use the domain in the recipient address.
210
187
<b>ACTIVE QUEUE CONTROLS</b>
211
188
<b><a href="postconf.5.html#qmgr_clog_warn_time">qmgr_clog_warn_time</a> (300s)</b>
212
The minimal delay between warnings that a specific
213
destination is clogging up the Postfix active
189
The minimal delay between warnings that a specific destination
190
is clogging up the Postfix <a href="QSHAPE_README.html#active_queue">active queue</a>.
216
192
<b><a href="postconf.5.html#qmgr_message_active_limit">qmgr_message_active_limit</a> (20000)</b>
217
193
The maximal number of messages in the <a href="QSHAPE_README.html#active_queue">active queue</a>.
219
195
<b><a href="postconf.5.html#qmgr_message_recipient_limit">qmgr_message_recipient_limit</a> (20000)</b>
220
The maximal number of recipients held in memory by
221
the Postfix queue manager, and the maximal size of
222
the short-term, in-memory "dead" destination status
196
The maximal number of recipients held in memory by the Postfix
197
queue manager, and the maximal size of the short-term, in-memory
198
"dead" destination status cache.
225
200
<b><a href="postconf.5.html#qmgr_message_recipient_minimum">qmgr_message_recipient_minimum</a> (10)</b>
226
The minimal number of in-memory recipients for any
201
The minimal number of in-memory recipients for any message.
229
203
<b><a href="postconf.5.html#default_recipient_limit">default_recipient_limit</a> (20000)</b>
230
The default per-transport upper limit on the number
231
of in-memory recipients.
204
The default per-transport upper limit on the number of in-memory
233
207
<b><a href="postconf.5.html#transport_recipient_limit"><i>transport</i>_recipient_limit</a> ($<a href="postconf.5.html#default_recipient_limit">default_recipient_limit</a>)</b>
234
208
Idem, for delivery via the named message <i>transport</i>.
236
210
<b><a href="postconf.5.html#default_extra_recipient_limit">default_extra_recipient_limit</a> (1000)</b>
237
The default value for the extra per-transport limit
238
imposed on the number of in-memory recipients.
211
The default value for the extra per-transport limit imposed on
212
the number of in-memory recipients.
240
<b><a href="postconf.5.html#transport_extra_recipient_limit"><i>transport</i>_extra_recipient_limit</a> ($<a href="postconf.5.html#default_extra_recipient_limit">default_extra_recipi</a>-</b>
241
<b><a href="postconf.5.html#default_extra_recipient_limit">ent_limit</a>)</b>
214
<b><a href="postconf.5.html#transport_extra_recipient_limit"><i>transport</i>_extra_recipient_limit</a> ($<a href="postconf.5.html#default_extra_recipient_limit">default_extra_recipient_limit</a>)</b>
242
215
Idem, for delivery via the named message <i>transport</i>.
244
217
Available in Postfix version 2.4 and later:
246
219
<b><a href="postconf.5.html#default_recipient_refill_limit">default_recipient_refill_limit</a> (100)</b>
247
The default per-transport limit on the number of
248
recipients refilled at once.
220
The default per-transport limit on the number of recipients
250
<b><a href="postconf.5.html#transport_recipient_refill_limit"><i>transport</i>_recipient_refill_limit</a> ($<a href="postconf.5.html#default_recipient_refill_limit">default_recipi</a>-</b>
251
<b><a href="postconf.5.html#default_recipient_refill_limit">ent_refill_limit</a>)</b>
223
<b><a href="postconf.5.html#transport_recipient_refill_limit"><i>transport</i>_recipient_refill_limit</a> ($<a href="postconf.5.html#default_recipient_refill_limit">default_recipient_refill_limit</a>)</b>
252
224
Idem, for delivery via the named message <i>transport</i>.
254
226
<b><a href="postconf.5.html#default_recipient_refill_delay">default_recipient_refill_delay</a> (5s)</b>
255
The default per-transport maximum delay between
227
The default per-transport maximum delay between recipients
258
<b><a href="postconf.5.html#transport_recipient_refill_delay"><i>transport</i>_recipient_refill_delay</a> ($<a href="postconf.5.html#default_recipient_refill_delay">default_recipi</a>-</b>
259
<b><a href="postconf.5.html#default_recipient_refill_delay">ent_refill_delay</a>)</b>
230
<b><a href="postconf.5.html#transport_recipient_refill_delay"><i>transport</i>_recipient_refill_delay</a> ($<a href="postconf.5.html#default_recipient_refill_delay">default_recipient_refill_delay</a>)</b>
260
231
Idem, for delivery via the named message <i>transport</i>.
262
233
<b>DELIVERY CONCURRENCY CONTROLS</b>
263
234
<b><a href="postconf.5.html#initial_destination_concurrency">initial_destination_concurrency</a> (5)</b>
264
The initial per-destination concurrency level for
265
parallel delivery to the same destination.
235
The initial per-destination concurrency level for parallel
236
delivery to the same destination.
267
238
<b><a href="postconf.5.html#default_destination_concurrency_limit">default_destination_concurrency_limit</a> (20)</b>
268
The default maximal number of parallel deliveries
269
to the same destination.
239
The default maximal number of parallel deliveries to the same
271
<b><a href="postconf.5.html#transport_destination_concurrency_limit"><i>transport</i>_destination_concurrency_limit</a> ($<a href="postconf.5.html#default_destination_concurrency_limit">default_destina</a>-</b>
272
<b><a href="postconf.5.html#default_destination_concurrency_limit">tion_concurrency_limit</a>)</b>
242
<b><a href="postconf.5.html#transport_destination_concurrency_limit"><i>transport</i>_destination_concurrency_limit</a> ($<a href="postconf.5.html#default_destination_concurrency_limit">default_destination_concur</a>-</b>
243
<b><a href="postconf.5.html#default_destination_concurrency_limit">rency_limit</a>)</b>
273
244
Idem, for delivery via the named message <i>transport</i>.
275
246
Available in Postfix version 2.5 and later:
277
<b><a href="postconf.5.html#transport_initial_destination_concurrency"><i>transport</i>_initial_destination_concurrency</a> ($<a href="postconf.5.html#initial_destination_concurrency">initial_desti</a>-</b>
278
<b><a href="postconf.5.html#initial_destination_concurrency">nation_concurrency</a>)</b>
279
Initial concurrency for delivery via the named mes-
280
sage <i>transport</i>.
248
<b><a href="postconf.5.html#transport_initial_destination_concurrency"><i>transport</i>_initial_destination_concurrency</a> ($<a href="postconf.5.html#initial_destination_concurrency">initial_destination_concur</a>-</b>
249
<b><a href="postconf.5.html#initial_destination_concurrency">rency</a>)</b>
250
Initial concurrency for delivery via the named message <i>trans-</i>
282
253
<b><a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">default_destination_concurrency_failed_cohort_limit</a> (1)</b>
283
How many pseudo-cohorts must suffer connection or
284
handshake failure before a specific destination is
285
considered unavailable (and further delivery is
254
How many pseudo-cohorts must suffer connection or handshake
255
failure before a specific destination is considered unavailable
256
(and further delivery is suspended).
288
<b><a href="postconf.5.html#transport_destination_concurrency_failed_cohort_limit"><i>transport</i>_destination_concurrency_failed_cohort_limit</a></b>
289
<b>($<a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">default_destination_concurrency_failed_cohort_limit</a>)</b>
258
<b><a href="postconf.5.html#transport_destination_concurrency_failed_cohort_limit"><i>transport</i>_destination_concurrency_failed_cohort_limit</a> ($<a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">default_desti</a>-</b>
259
<b><a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">nation_concurrency_failed_cohort_limit</a>)</b>
290
260
Idem, for delivery via the named message <i>transport</i>.
292
262
<b><a href="postconf.5.html#default_destination_concurrency_negative_feedback">default_destination_concurrency_negative_feedback</a> (1)</b>
293
The per-destination amount of delivery concurrency
294
negative feedback, after a delivery completes with
295
a connection or handshake failure.
263
The per-destination amount of delivery concurrency negative
264
feedback, after a delivery completes with a connection or hand-
297
<b><a href="postconf.5.html#transport_destination_concurrency_negative_feedback"><i>transport</i>_destination_concurrency_negative_feedback</a></b>
298
<b>($<a href="postconf.5.html#default_destination_concurrency_negative_feedback">default_destination_concurrency_negative_feedback</a>)</b>
267
<b><a href="postconf.5.html#transport_destination_concurrency_negative_feedback"><i>transport</i>_destination_concurrency_negative_feedback</a> ($<a href="postconf.5.html#default_destination_concurrency_negative_feedback">default_destina</a>-</b>
268
<b><a href="postconf.5.html#default_destination_concurrency_negative_feedback">tion_concurrency_negative_feedback</a>)</b>
299
269
Idem, for delivery via the named message <i>transport</i>.
301
271
<b><a href="postconf.5.html#default_destination_concurrency_positive_feedback">default_destination_concurrency_positive_feedback</a> (1)</b>
302
The per-destination amount of delivery concurrency
303
positive feedback, after a delivery completes with-
304
out connection or handshake failure.
272
The per-destination amount of delivery concurrency positive
273
feedback, after a delivery completes without connection or hand-
306
<b><a href="postconf.5.html#transport_destination_concurrency_positive_feedback"><i>transport</i>_destination_concurrency_positive_feedback</a></b>
307
<b>($<a href="postconf.5.html#default_destination_concurrency_positive_feedback">default_destination_concurrency_positive_feedback</a>)</b>
276
<b><a href="postconf.5.html#transport_destination_concurrency_positive_feedback"><i>transport</i>_destination_concurrency_positive_feedback</a> ($<a href="postconf.5.html#default_destination_concurrency_positive_feedback">default_destina</a>-</b>
277
<b><a href="postconf.5.html#default_destination_concurrency_positive_feedback">tion_concurrency_positive_feedback</a>)</b>
308
278
Idem, for delivery via the named message <i>transport</i>.
310
280
<b><a href="postconf.5.html#destination_concurrency_feedback_debug">destination_concurrency_feedback_debug</a> (no)</b>
311
Make the queue manager's feedback algorithm verbose
312
for performance analysis purposes.
281
Make the queue manager's feedback algorithm verbose for perfor-
282
mance analysis purposes.
314
284
<b>RECIPIENT SCHEDULING CONTROLS</b>
315
285
<b><a href="postconf.5.html#default_destination_recipient_limit">default_destination_recipient_limit</a> (50)</b>
316
The default maximal number of recipients per mes-
286
The default maximal number of recipients per message delivery.
319
<b><a href="postconf.5.html#transport_destination_recipient_limit"><i>transport</i>_destination_recipient_limit</a> ($<a href="postconf.5.html#default_destination_recipient_limit">default_destina</a>-</b>
320
<b><a href="postconf.5.html#default_destination_recipient_limit">tion_recipient_limit</a>)</b>
288
<b><a href="postconf.5.html#transport_destination_recipient_limit"><i>transport</i>_destination_recipient_limit</a> ($<a href="postconf.5.html#default_destination_recipient_limit">default_destination_recipi</a>-</b>
289
<b><a href="postconf.5.html#default_destination_recipient_limit">ent_limit</a>)</b>
321
290
Idem, for delivery via the named message <i>transport</i>.
323
292
<b>MESSAGE SCHEDULING CONTROLS</b>
324
293
<b><a href="postconf.5.html#default_delivery_slot_cost">default_delivery_slot_cost</a> (5)</b>
325
How often the Postfix queue manager's scheduler is
326
allowed to preempt delivery of one message with
294
How often the Postfix queue manager's scheduler is allowed to
295
preempt delivery of one message with another.
329
297
<b><a href="postconf.5.html#transport_delivery_slot_cost"><i>transport</i>_delivery_slot_cost</a> ($<a href="postconf.5.html#default_delivery_slot_cost">default_delivery_slot_cost</a>)</b>
330
298
Idem, for delivery via the named message <i>transport</i>.
332
300
<b><a href="postconf.5.html#default_minimum_delivery_slots">default_minimum_delivery_slots</a> (3)</b>
333
How many recipients a message must have in order to
334
invoke the Postfix queue manager's scheduling algo-
301
How many recipients a message must have in order to invoke the
302
Postfix queue manager's scheduling algorithm at all.
337
<b><a href="postconf.5.html#transport_minimum_delivery_slots"><i>transport</i>_minimum_delivery_slots</a> ($<a href="postconf.5.html#default_minimum_delivery_slots">default_minimum_deliv</a>-</b>
338
<b><a href="postconf.5.html#default_minimum_delivery_slots">ery_slots</a>)</b>
304
<b><a href="postconf.5.html#transport_minimum_delivery_slots"><i>transport</i>_minimum_delivery_slots</a> ($<a href="postconf.5.html#default_minimum_delivery_slots">default_minimum_delivery_slots</a>)</b>
339
305
Idem, for delivery via the named message <i>transport</i>.
341
307
<b><a href="postconf.5.html#default_delivery_slot_discount">default_delivery_slot_discount</a> (50)</b>
342
The default value for transport-specific _deliv-
343
ery_slot_discount settings.
308
The default value for transport-specific _delivery_slot_discount
345
<b><a href="postconf.5.html#transport_delivery_slot_discount"><i>transport</i>_delivery_slot_discount</a> ($<a href="postconf.5.html#default_delivery_slot_discount">default_deliv</a>-</b>
346
<b><a href="postconf.5.html#default_delivery_slot_discount">ery_slot_discount</a>)</b>
311
<b><a href="postconf.5.html#transport_delivery_slot_discount"><i>transport</i>_delivery_slot_discount</a> ($<a href="postconf.5.html#default_delivery_slot_discount">default_delivery_slot_discount</a>)</b>
347
312
Idem, for delivery via the named message <i>transport</i>.
349
314
<b><a href="postconf.5.html#default_delivery_slot_loan">default_delivery_slot_loan</a> (3)</b>
350
The default value for transport-specific _deliv-
351
ery_slot_loan settings.
315
The default value for transport-specific _delivery_slot_loan
353
318
<b><a href="postconf.5.html#transport_delivery_slot_loan"><i>transport</i>_delivery_slot_loan</a> ($<a href="postconf.5.html#default_delivery_slot_loan">default_delivery_slot_loan</a>)</b>
354
319
Idem, for delivery via the named message <i>transport</i>.
356
321
<b>OTHER RESOURCE AND RATE CONTROLS</b>
357
322
<b><a href="postconf.5.html#minimal_backoff_time">minimal_backoff_time</a> (300s)</b>
358
The minimal time between attempts to deliver a
359
deferred message; prior to Postfix 2.4 the default
323
The minimal time between attempts to deliver a deferred message;
324
prior to Postfix 2.4 the default value was 1000s.
362
326
<b><a href="postconf.5.html#maximal_backoff_time">maximal_backoff_time</a> (4000s)</b>
363
The maximal time between attempts to deliver a
327
The maximal time between attempts to deliver a deferred message.
366
329
<b><a href="postconf.5.html#maximal_queue_lifetime">maximal_queue_lifetime</a> (5d)</b>
367
The maximal time a message is queued before it is
368
sent back as undeliverable.
330
Consider a message as undeliverable, when delivery fails with a
331
temporary error, and the time in the queue has reached the <a href="postconf.5.html#maximal_queue_lifetime">maxi</a>-
332
<a href="postconf.5.html#maximal_queue_lifetime">mal_queue_lifetime</a> limit.
370
334
<b><a href="postconf.5.html#queue_run_delay">queue_run_delay</a> (300s)</b>
371
The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue
372
manager; prior to Postfix 2.4 the default value was
335
The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue manager;
336
prior to Postfix 2.4 the default value was 1000s.
375
338
<b><a href="postconf.5.html#transport_retry_time">transport_retry_time</a> (60s)</b>
376
The time between attempts by the Postfix queue man-
377
ager to contact a malfunctioning message delivery
339
The time between attempts by the Postfix queue manager to con-
340
tact a malfunctioning message delivery transport.
380
342
Available in Postfix version 2.1 and later:
382
344
<b><a href="postconf.5.html#bounce_queue_lifetime">bounce_queue_lifetime</a> (5d)</b>
383
The maximal time a bounce message is queued before
384
it is considered undeliverable.
345
Consider a bounce message as undeliverable, when delivery fails
346
with a temporary error, and the time in the queue has reached
347
the <a href="postconf.5.html#bounce_queue_lifetime">bounce_queue_lifetime</a> limit.
386
349
Available in Postfix version 2.5 and later:
388
351
<b><a href="postconf.5.html#default_destination_rate_delay">default_destination_rate_delay</a> (0s)</b>
389
The default amount of delay that is inserted
390
between individual deliveries to the same destina-
391
tion; the resulting behavior depends on the value
392
of the corresponding per-destination recipient
352
The default amount of delay that is inserted between individual
353
deliveries to the same destination; the resulting behavior
354
depends on the value of the corresponding per-destination recip-
395
<b><a href="postconf.5.html#transport_destination_rate_delay"><i>transport</i>_destination_rate_delay</a> $<a href="postconf.5.html#default_destination_rate_delay">default_destina</a>-</b>
396
<b><a href="postconf.5.html#default_destination_rate_delay">tion_rate_delay</a></b>
357
<b><a href="postconf.5.html#transport_destination_rate_delay"><i>transport</i>_destination_rate_delay</a> $<a href="postconf.5.html#default_destination_rate_delay">default_destination_rate_delay</a></b>
397
358
Idem, for delivery via the named message <i>transport</i>.
399
360
<b>SAFETY CONTROLS</b>
400
361
<b><a href="postconf.5.html#qmgr_daemon_timeout">qmgr_daemon_timeout</a> (1000s)</b>
401
How much time a Postfix queue manager process may
402
take to handle a request before it is terminated by
403
a built-in watchdog timer.
362
How much time a Postfix queue manager process may take to handle
363
a request before it is terminated by a built-in watchdog timer.
405
365
<b><a href="postconf.5.html#qmgr_ipc_timeout">qmgr_ipc_timeout</a> (60s)</b>
406
The time limit for the queue manager to send or
407
receive information over an internal communication
366
The time limit for the queue manager to send or receive informa-
367
tion over an internal communication channel.
410
369
<b>MISCELLANEOUS CONTROLS</b>
411
370
<b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
412
The default location of the Postfix <a href="postconf.5.html">main.cf</a> and
413
<a href="master.5.html">master.cf</a> configuration files.
371
The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con-
415
374
<b><a href="postconf.5.html#defer_transports">defer_transports</a> (empty)</b>
416
The names of message delivery transports that
417
should not deliver mail unless someone issues
418
"<b>sendmail -q</b>" or equivalent.
375
The names of message delivery transports that should not deliver
376
mail unless someone issues "<b>sendmail -q</b>" or equivalent.
420
378
<b><a href="postconf.5.html#delay_logging_resolution_limit">delay_logging_resolution_limit</a> (2)</b>
421
The maximal number of digits after the decimal
422
point when logging sub-second delay values.
379
The maximal number of digits after the decimal point when log-
380
ging sub-second delay values.
424
382
<b><a href="postconf.5.html#helpful_warnings">helpful_warnings</a> (yes)</b>
425
Log warnings about problematic configuration set-
426
tings, and provide helpful suggestions.
383
Log warnings about problematic configuration settings, and pro-
384
vide helpful suggestions.
428
386
<b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b>
429
The process ID of a Postfix command or daemon
387
The process ID of a Postfix command or daemon process.
432
389
<b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b>
433
The process name of a Postfix command or daemon
390
The process name of a Postfix command or daemon process.
436
392
<b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
437
The location of the Postfix top-level queue direc-
393
The location of the Postfix top-level queue directory.
440
395
<b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b>
441
396
The syslog facility of Postfix logging.
443
398
<b><a href="postconf.5.html#syslog_name">syslog_name</a> (see 'postconf -d' output)</b>
444
The mail system name that is prepended to the
445
process name in syslog records, so that "smtpd"
446
becomes, for example, "postfix/smtpd".
399
The mail system name that is prepended to the process name in
400
syslog records, so that "smtpd" becomes, for example, "post-
449
404
/var/spool/postfix/incoming, <a href="QSHAPE_README.html#incoming_queue">incoming queue</a>
added
removed
html/qmgr.8.html
