1<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN" 2 "http://www.w3.org/TR/html4/loose.dtd"> 3<html> <head> 4<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> 5<title> Postfix manual - oqmgr(8) </title> 6</head> <body> <pre> 7OQMGR(8) OQMGR(8) 8 9<b>NAME</b> 10 oqmgr - old Postfix queue manager 11 12<b>SYNOPSIS</b> 13 <b>oqmgr</b> [generic Postfix daemon options] 14 15<b>DESCRIPTION</b> 16 The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon awaits the arrival of incoming mail and arranges 17 for its delivery via Postfix delivery processes. The actual mail rout- 18 ing strategy is delegated to the <a href="trivial-rewrite.8.html"><b>trivial-rewrite</b>(8)</a> daemon. This pro- 19 gram expects to be run from the <a href="master.8.html"><b>master</b>(8)</a> process manager. 20 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 23 notifications. 24 25<b>MAIL QUEUES</b> 26 The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon maintains the following queues: 27 28 <b>incoming</b> 29 Inbound mail from the network, or mail picked up by the local 30 <a href="pickup.8.html"><b>pickup</b>(8)</a> agent from the <b>maildrop</b> directory. 31 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). 35 36 <b>deferred</b> 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. 40 41 <b>corrupt</b> 42 Unreadable or damaged queue files are moved here for inspection. 43 44 <b>hold</b> Messages that are kept "on hold" are kept here until someone 45 sets them free. 46 47<b>DELIVERY STATUS REPORTS</b> 48 The <a href="qmgr.8.html"><b>oqmgr</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: 51 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. 54 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. 57 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. 61 62 The <a href="qmgr.8.html"><b>oqmgr</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> 63 or <a href="trace.8.html"><b>trace</b>(8)</a> daemons to send delivery reports. 64 65<b>STRATEGIES</b> 66 The queue manager implements a variety of strategies for either opening 67 queue files (input) or for message delivery (output). 68 69 <b>leaky bucket</b> 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 72 heavy load. 73 74 <b>fairness</b> 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 78 new mail. 79 80 <b>slow start</b> 81 This strategy eliminates "thundering herd" problems by slowly 82 adjusting the number of parallel deliveries to the same destina- 83 tion. 84 85 <b>round robin</b> 86 The queue manager sorts delivery requests by destination. 87 Round-robin selection prevents one destination from dominating 88 deliveries to other destinations. 89 90 <b>exponential backoff</b> 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. 94 95 <b>destination status cache</b> 96 The queue manager avoids unnecessary delivery attempts by main- 97 taining a short-term, in-memory list of unreachable destina- 98 tions. 99 100<b>TRIGGERS</b> 101 On an idle system, the queue manager waits for the arrival of trigger 102 events, or it waits for a timer to go off. A trigger is a one-byte mes- 103 sage. Depending on the message received, the queue manager performs 104 one of the following actions (the message is followed by the symbolic 105 constant used internally by the software): 106 107 <b>D (QMGR_REQ_SCAN_DEFERRED)</b> 108 Start a <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan. If a deferred queue scan is 109 already in progress, that scan will be restarted as soon as it 110 finishes. 111 112 <b>I (QMGR_REQ_SCAN_INCOMING)</b> 113 Start an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> scan. If an incoming queue scan is 114 already in progress, that scan will be restarted as soon as it 115 finishes. 116 117 <b>A (QMGR_REQ_SCAN_ALL)</b> 118 Ignore <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> file time stamps. The request affects the 119 next <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scan. 120 121 <b>F (QMGR_REQ_FLUSH_DEAD)</b> 122 Purge all information about dead transports and destinations. 123 124 <b>W (TRIGGER_REQ_WAKEUP)</b> 125 Wakeup call, This is used by the master server to instantiate 126 servers that should not go away forever. The action is to start 127 an <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> scan. 128 129 The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon reads an entire buffer worth of triggers. Multiple 130 identical trigger requests are collapsed into one, and trigger requests 131 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 132 <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> run, one would request <b>A F D</b>; in order to notify the 133 queue manager of the arrival of new mail one would request <b>I</b>. 134 135<b>STANDARDS</b> 136 <a href="http://tools.ietf.org/html/rfc3463">RFC 3463</a> (Enhanced status codes) 137 <a href="http://tools.ietf.org/html/rfc3464">RFC 3464</a> (Delivery status notifications) 138 139<b>SECURITY</b> 140 The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon is not security sensitive. It reads single-charac- 141 ter messages from untrusted local users, and thus may be susceptible to 142 denial of service attacks. The <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> daemon does not talk to the 143 outside world, and it can be run at fixed low privilege in a chrooted 144 environment. 145 146<b>DIAGNOSTICS</b> 147 Problems and transactions are logged to the <b>syslog</b>(8) daemon. Cor- 148 rupted message files are saved to the <b>corrupt</b> queue for further inspec- 149 tion. 150 151 Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter, the postmas- 152 ter is notified of bounces and of other trouble. 153 154<b>BUGS</b> 155 A single queue manager process has to compete for disk access with mul- 156 tiple front-end processes such as <a href="cleanup.8.html"><b>cleanup</b>(8)</a>. A sudden burst of inbound 157 mail can negatively impact outbound delivery rates. 158 159<b>CONFIGURATION PARAMETERS</b> 160 Changes to <a href="postconf.5.html"><b>main.cf</b></a> are not picked up automatically, as <a href="qmgr.8.html"><b>oqmgr</b>(8)</a> is a 161 persistent process. Use the command "<b>postfix reload</b>" after a configura- 162 tion change. 163 164 The text below provides only a parameter summary. See <a href="postconf.5.html"><b>postconf</b>(5)</a> for 165 more details including examples. 166 167 In the text below, <i>transport</i> is the first field in a <a href="master.5.html"><b>master.cf</b></a> entry. 168 169<b>COMPATIBILITY CONTROLS</b> 170 Available before Postfix version 2.5: 171 172 <b><a href="postconf.5.html#allow_min_user">allow_min_user</a> (no)</b> 173 Allow a sender or recipient address to have `-' as the first 174 character. 175 176 Available with Postfix version 2.7 and later: 177 178 <b><a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> (empty)</b> 179 When a <a href="postconf.5.html#content_filter">content_filter</a> or FILTER request specifies no explicit 180 next-hop destination, use $<a href="postconf.5.html#default_filter_nexthop">default_filter_nexthop</a> instead; when 181 that value is empty, use the domain in the recipient address. 182 183<b>ACTIVE QUEUE CONTROLS</b> 184 <b><a href="postconf.5.html#qmgr_clog_warn_time">qmgr_clog_warn_time</a> (300s)</b> 185 The minimal delay between warnings that a specific destination 186 is clogging up the Postfix <a href="QSHAPE_README.html#active_queue">active queue</a>. 187 188 <b><a href="postconf.5.html#qmgr_message_active_limit">qmgr_message_active_limit</a> (20000)</b> 189 The maximal number of messages in the <a href="QSHAPE_README.html#active_queue">active queue</a>. 190 191 <b><a href="postconf.5.html#qmgr_message_recipient_limit">qmgr_message_recipient_limit</a> (20000)</b> 192 The maximal number of recipients held in memory by the Postfix 193 queue manager, and the maximal size of the short-term, in-memory 194 "dead" destination status cache. 195 196<b>DELIVERY CONCURRENCY CONTROLS</b> 197 <b><a href="postconf.5.html#qmgr_fudge_factor">qmgr_fudge_factor</a> (100)</b> 198 Obsolete feature: the percentage of delivery resources that a 199 busy mail system will use up for delivery of a large mailing 200 list message. 201 202 <b><a href="postconf.5.html#initial_destination_concurrency">initial_destination_concurrency</a> (5)</b> 203 The initial per-destination concurrency level for parallel 204 delivery to the same destination. 205 206 <b><a href="postconf.5.html#default_destination_concurrency_limit">default_destination_concurrency_limit</a> (20)</b> 207 The default maximal number of parallel deliveries to the same 208 destination. 209 210 <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> 211 <b><a href="postconf.5.html#default_destination_concurrency_limit">rency_limit</a>)</b> 212 Idem, for delivery via the named message <i>transport</i>. 213 214 Available in Postfix version 2.5 and later: 215 216 <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> 217 <b><a href="postconf.5.html#initial_destination_concurrency">rency</a>)</b> 218 Initial concurrency for delivery via the named message <i>trans-</i> 219 <i>port</i>. 220 221 <b><a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">default_destination_concurrency_failed_cohort_limit</a> (1)</b> 222 How many pseudo-cohorts must suffer connection or handshake 223 failure before a specific destination is considered unavailable 224 (and further delivery is suspended). 225 226 <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> 227 <b><a href="postconf.5.html#default_destination_concurrency_failed_cohort_limit">nation_concurrency_failed_cohort_limit</a>)</b> 228 Idem, for delivery via the named message <i>transport</i>. 229 230 <b><a href="postconf.5.html#default_destination_concurrency_negative_feedback">default_destination_concurrency_negative_feedback</a> (1)</b> 231 The per-destination amount of delivery concurrency negative 232 feedback, after a delivery completes with a connection or hand- 233 shake failure. 234 235 <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> 236 <b><a href="postconf.5.html#default_destination_concurrency_negative_feedback">tion_concurrency_negative_feedback</a>)</b> 237 Idem, for delivery via the named message <i>transport</i>. 238 239 <b><a href="postconf.5.html#default_destination_concurrency_positive_feedback">default_destination_concurrency_positive_feedback</a> (1)</b> 240 The per-destination amount of delivery concurrency positive 241 feedback, after a delivery completes without connection or hand- 242 shake failure. 243 244 <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> 245 <b><a href="postconf.5.html#default_destination_concurrency_positive_feedback">tion_concurrency_positive_feedback</a>)</b> 246 Idem, for delivery via the named message <i>transport</i>. 247 248 <b><a href="postconf.5.html#destination_concurrency_feedback_debug">destination_concurrency_feedback_debug</a> (no)</b> 249 Make the queue manager's feedback algorithm verbose for perfor- 250 mance analysis purposes. 251 252<b>RECIPIENT SCHEDULING CONTROLS</b> 253 <b><a href="postconf.5.html#default_destination_recipient_limit">default_destination_recipient_limit</a> (50)</b> 254 The default maximal number of recipients per message delivery. 255 256 <b><a href="postconf.5.html#transport_destination_recipient_limit"><i>transport</i>_destination_recipient_limit</a></b> 257 Idem, for delivery via the named message <i>transport</i>. 258 259<b>OTHER RESOURCE AND RATE CONTROLS</b> 260 <b><a href="postconf.5.html#minimal_backoff_time">minimal_backoff_time</a> (300s)</b> 261 The minimal time between attempts to deliver a deferred message; 262 prior to Postfix 2.4 the default value was 1000s. 263 264 <b><a href="postconf.5.html#maximal_backoff_time">maximal_backoff_time</a> (4000s)</b> 265 The maximal time between attempts to deliver a deferred message. 266 267 <b><a href="postconf.5.html#maximal_queue_lifetime">maximal_queue_lifetime</a> (5d)</b> 268 Consider a message as undeliverable, when delivery fails with a 269 temporary error, and the time in the queue has reached the <a href="postconf.5.html#maximal_queue_lifetime">maxi</a>- 270 <a href="postconf.5.html#maximal_queue_lifetime">mal_queue_lifetime</a> limit. 271 272 <b><a href="postconf.5.html#queue_run_delay">queue_run_delay</a> (300s)</b> 273 The time between <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> scans by the queue manager; 274 prior to Postfix 2.4 the default value was 1000s. 275 276 <b><a href="postconf.5.html#transport_retry_time">transport_retry_time</a> (60s)</b> 277 The time between attempts by the Postfix queue manager to con- 278 tact a malfunctioning message delivery transport. 279 280 Available in Postfix version 2.1 and later: 281 282 <b><a href="postconf.5.html#bounce_queue_lifetime">bounce_queue_lifetime</a> (5d)</b> 283 Consider a bounce message as undeliverable, when delivery fails 284 with a temporary error, and the time in the queue has reached 285 the <a href="postconf.5.html#bounce_queue_lifetime">bounce_queue_lifetime</a> limit. 286 287 Available in Postfix version 2.5 and later: 288 289 <b><a href="postconf.5.html#default_destination_rate_delay">default_destination_rate_delay</a> (0s)</b> 290 The default amount of delay that is inserted between individual 291 deliveries to the same destination; the resulting behavior 292 depends on the value of the corresponding per-destination recip- 293 ient limit. 294 295 <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> 296 Idem, for delivery via the named message <i>transport</i>. 297 298<b>SAFETY CONTROLS</b> 299 <b><a href="postconf.5.html#qmgr_daemon_timeout">qmgr_daemon_timeout</a> (1000s)</b> 300 How much time a Postfix queue manager process may take to handle 301 a request before it is terminated by a built-in watchdog timer. 302 303 <b><a href="postconf.5.html#qmgr_ipc_timeout">qmgr_ipc_timeout</a> (60s)</b> 304 The time limit for the queue manager to send or receive informa- 305 tion over an internal communication channel. 306 307<b>MISCELLANEOUS CONTROLS</b> 308 <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b> 309 The default location of the Postfix <a href="postconf.5.html">main.cf</a> and <a href="master.5.html">master.cf</a> con- 310 figuration files. 311 312 <b><a href="postconf.5.html#defer_transports">defer_transports</a> (empty)</b> 313 The names of message delivery transports that should not deliver 314 mail unless someone issues "<b>sendmail -q</b>" or equivalent. 315 316 <b><a href="postconf.5.html#delay_logging_resolution_limit">delay_logging_resolution_limit</a> (2)</b> 317 The maximal number of digits after the decimal point when log- 318 ging sub-second delay values. 319 320 <b><a href="postconf.5.html#helpful_warnings">helpful_warnings</a> (yes)</b> 321 Log warnings about problematic configuration settings, and pro- 322 vide helpful suggestions. 323 324 <b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b> 325 The process ID of a Postfix command or daemon process. 326 327 <b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b> 328 The process name of a Postfix command or daemon process. 329 330 <b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b> 331 The location of the Postfix top-level queue directory. 332 333 <b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b> 334 The syslog facility of Postfix logging. 335 336 <b><a href="postconf.5.html#syslog_name">syslog_name</a> (see 'postconf -d' output)</b> 337 The mail system name that is prepended to the process name in 338 syslog records, so that "smtpd" becomes, for example, "post- 339 fix/smtpd". 340 341<b>FILES</b> 342 /var/spool/postfix/incoming, <a href="QSHAPE_README.html#incoming_queue">incoming queue</a> 343 /var/spool/postfix/active, <a href="QSHAPE_README.html#active_queue">active queue</a> 344 /var/spool/postfix/deferred, <a href="QSHAPE_README.html#deferred_queue">deferred queue</a> 345 /var/spool/postfix/bounce, non-delivery status 346 /var/spool/postfix/defer, non-delivery status 347 /var/spool/postfix/trace, delivery status 348 349<b>SEE ALSO</b> 350 <a href="trivial-rewrite.8.html">trivial-rewrite(8)</a>, address routing 351 <a href="bounce.8.html">bounce(8)</a>, delivery status reports 352 <a href="postconf.5.html">postconf(5)</a>, configuration parameters 353 <a href="master.5.html">master(5)</a>, generic daemon options 354 <a href="master.8.html">master(8)</a>, process manager 355 syslogd(8), system logging 356 357<b>README FILES</b> 358 <a href="QSHAPE_README.html">QSHAPE_README</a>, Postfix queue analysis 359 360<b>LICENSE</b> 361 The Secure Mailer license must be distributed with this software. 362 363<b>AUTHOR(S)</b> 364 Wietse Venema 365 IBM T.J. Watson Research 366 P.O. Box 704 367 Yorktown Heights, NY 10598, USA 368 369 OQMGR(8) 370</pre> </body> </html> 371