Seth Woolley's Man Viewer

qmgr(8) - qmgr - Postfix queue manager - man 8 qmgr

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

QMGR(8)                                                                QMGR(8)

       qmgr - Postfix queue(1,3) manager

       qmgr [generic Postfix daemon options]

       The qmgr(8) daemon awaits the arrival of incoming mail(1,8) and arranges for
       its delivery via Postfix delivery processes.  The actual  mail(1,8)  routing
       strategy  is  delegated to the trivial-rewrite(8) daemon.  This program
       expects to be run from the master(5,8)(8) process manager.

       Mail addressed to the local double-bounce address is  logged  and  dis-
       carded.   This  stops  potential  loops  caused by undeliverable bounce

       The qmgr(8) daemon maintains the following queues:

              Inbound mail(1,8) from the network, or mail(1,8) picked up  by  the  local
              pickup(8) daemon from the maildrop directory.

       active Messages  that the queue(1,3) manager has opened for delivery. Only a
              limited number of messages is allowed to enter the active  queue(1,3)
              (leaky bucket strategy, for a fixed delivery rate).

              Mail  that  could  not  be delivered upon the first attempt. The
              queue(1,3) manager implements exponential  backoff  by  doubling  the
              time(1,2,n) between delivery attempts.

              Unreadable or damaged queue(1,3) files are moved here for inspection.

       hold   Messages that are kept "on hold" are  kept  here  until  someone
              sets them free.

       The  qmgr(8) daemon keeps an eye on per-message delivery status reports
       in(1,8) the following directories. Each status report file(1,n) has the same name
       as the corresponding message file:

       bounce Per-recipient  status  information  about  why  mail(1,8) is bounced.
              These files are maintained by the bounce(8) daemon.

       defer  Per-recipient status information  about  why  mail(1,8)  is  delayed.
              These files are maintained by the defer(8) daemon.

       trace(3x,n,3x _nc_tracebits)  Per-recipient  status  information as requested with the Postfix
              "sendmail(1,8) -v" or "sendmail(1,8) -bv" command.  These files are  main-
              tained by the trace(3x,n,3x _nc_tracebits)(8) daemon.

       The qmgr(8) daemon is responsible for asking the bounce(8), defer(8) or
       trace(3x,n,3x _nc_tracebits)(8) daemons to send(2,n) delivery reports.

       The queue(1,3) manager implements a variety of strategies for either opening
       queue(1,3) files (input) or for message delivery (output).

       leaky bucket
              This  strategy limits the number of messages in(1,8) the active queue(1,3)
              and prevents the queue(1,3) manager from running out of memory  under
              heavy load.

              When the active queue(1,3) has room, the queue(1,3) manager takes one mes-
              sage from the incoming queue(1,3) and one from  the  deferred  queue.
              This prevents a large mail(1,8) backlog from blocking the delivery of
              new mail.

       slow start
              This strategy eliminates "thundering herd"  problems  by  slowly
              adjusting the number of parallel deliveries to the same destina-

       round robin
              The  queue(1,3)  manager  sorts  delivery  requests  by  destination.
              Round-robin  selection  prevents one destination from dominating
              deliveries to other destinations.

       exponential backoff
              Mail  that  cannot  be  delivered  upon  the  first  attempt  is
              deferred.   The  time(1,2,n) interval between delivery attempts is dou-
              bled after each attempt.

       destination status cache
              The queue(1,3) manager avoids unnecessary delivery attempts by  main-
              taining  a  short-term,  in-memory  list of unreachable destina-

       preemptive message scheduling
              The queue(1,3) manager attempts to minimize the average per-recipient
              delay  while  still  preserving  the correct per-message delays,
              using a sophisticated preemptive message scheduling.

       On an idle system, the queue(1,3) manager waits for the arrival  of  trigger
       events, or it waits for a timer to go off. A trigger is a one-byte mes-
       sage.  Depending on the message received, the  queue(1,3)  manager  performs
       one  of  the following actions (the message is followed by the symbolic
       constant used internally by the software):

              Start a deferred queue(1,3)  scan.   If  a  deferred  queue(1,3)  scan  is
              already  in(1,8)  progress, that scan will be restarted as soon as it

              Start an incoming queue(1,3) scan.  If  an  incoming  queue(1,3)  scan  is
              already  in(1,8)  progress, that scan will be restarted as soon as it

              Ignore deferred queue(1,3) file(1,n) time(1,2,n) stamps. The request affects  the
              next deferred queue(1,3) scan.

              Purge all information about dead transports and destinations.

              Wakeup  call,  This  is used by the master(5,8) server to instantiate
              servers that should not go away forever. The action is to  start
              an incoming queue(1,3) scan.

       The  qmgr(8) daemon reads an entire buffer worth of triggers.  Multiple
       identical trigger requests are collapsed into one, and trigger requests
       are  sorted  so that A and F precede D and I. Thus, in(1,8) order to force a
       deferred queue(1,3) run, one would request A F D; in(1,8)  order  to  notify  the
       queue(1,3) manager of the arrival of new mail(1,8) one would request I.

       None. The qmgr(8) daemon does not interact with the outside world.

       The qmgr(8) daemon is not security sensitive. It reads single-character
       messages from untrusted local users(1,5), and thus  may  be  susceptible  to
       denial of service attacks. The qmgr(8) daemon does not talk to the out-
       side world, and it can be run at fixed  low  privilege  in(1,8)  a  chrooted

       Problems  and  transactions are logged to the syslog(2,3,5,3 Sys::Syslog) daemon.  Corrupted
       message files are saved to the corrupt queue(1,3) for further inspection.

       Depending on the setting of the notify_classes parameter, the  postmas-
       ter is notified of bounces and of other trouble.

       A single queue(1,3) manager process has to compete for disk access(2,5) with mul-
       tiple front-end processes such as cleanup(8). A sudden burst of inbound
       mail(1,8) can negatively impact outbound delivery rates.

       Changes to are not picked up automatically as qmgr(8) is a per-
       sistent process. Use the "postfix reload" command after a configuration

       The  text  below provides only a parameter summary. See postconf(1,5)(5) for
       more details including examples.

       In the text below, transport is the first field in(1,8) a entry.

       allow_min_user (no)
              Allow a recipient address to have `-' as the first character.

       qmgr_clog_warn_time (300s)
              The minimal delay between warnings that a  specific  destination
              is clogging up the Postfix active queue.

       qmgr_message_active_limit (20000)
              The maximal number of messages in(1,8) the active queue.

       qmgr_message_recipient_limit (20000)
              The  maximal  number of recipients held in(1,8) memory by the Postfix
              queue(1,3) manager, and the maximal size of the size  of  the  short-
              term(5,7), in-memory "dead" destination status cache.

       qmgr_message_recipient_minimum (10)
              The minimal number of in-memory recipients for any message.

       default_recipient_limit (10000)
              The default per-transport upper limit on the number of in-memory

       transport_recipient_limit ($default_recipient_limit)
              Idem, for delivery via the named(5,8) message transport.

       default_extra_recipient_limit (1000)
              The default value for the extra per-transport limit  imposed  on
              the number of in-memory recipients.

       transport_extra_recipient_limit ($default_extra_recipient_limit)
              Idem, for delivery via the named(5,8) message transport.

       initial_destination_concurrency (5)
              The  initial  per-destination  concurrency  level  for  parallel
              delivery to the same destination.

       default_destination_concurrency_limit (20)
              The default maximal number of parallel deliveries  to  the  same

       transport_destination_concurrency_limit   ($default_destination_concur-
              Idem, for delivery via the named(5,8) message transport.

       default_destination_recipient_limit (50)
              The default maximal number of recipients per message delivery.

       transport_destination_recipient_limit     ($default_destination_recipi-
              Idem, for delivery via the named(5,8) message transport.

       default_delivery_slot_cost (5)
              How  often  the  Postfix queue(1,3) manager's scheduler is allowed to
              preempt delivery of one message with another.

       transport_delivery_slot_cost ($default_delivery_slot_cost)
              Idem, for delivery via the named(5,8) message transport.

       default_minimum_delivery_slots (3)
              How many recipients a message must have in(1,8) order to  invoke  the
              Postfix queue(1,3) manager's scheduling algorithm at all.

       transport_minimum_delivery_slots ($default_minimum_delivery_slots)
              Idem, for delivery via the named(5,8) message transport.

       default_delivery_slot_discount (50)
              The default value for transport-specific _delivery_slot_discount

       transport_delivery_slot_discount ($default_delivery_slot_discount)
              Idem, for delivery via the named(5,8) message transport.

       default_delivery_slot_loan (3)
              The default  value  for  transport-specific  _delivery_slot_loan

       transport_delivery_slot_loan ($default_delivery_slot_loan)
              Idem, for delivery via the named(5,8) message transport.

       minimal_backoff_time (1000s)
              The minimal time(1,2,n) between attempts to deliver a deferred message.

       maximal_backoff_time (4000s)
              The maximal time(1,2,n) between attempts to deliver a deferred message.

       maximal_queue_lifetime (5d)
              The  maximal  time(1,2,n) a message is queued before it is sent back as

       queue_run_delay (1000s)
              The time(1,2,n) between deferred queue(1,3) scans by the queue(1,3) manager.

       transport_retry_time (60s)
              The time(1,2,n) between attempts by the Postfix queue(1,3) manager  to  con-
              tact a malfunctioning message delivery transport.

       Available in(1,8) Postfix version(1,3,5) 2.1 and later:

       bounce_queue_lifetime (5d)
              The maximal time(1,2,n) a bounce message is queued before it is consid-
              ered undeliverable.

       config_directory (see 'postconf(1,5) -d' output)
              The default location of the Postfix and  con-
              figuration files.

       daemon_timeout (18000s)
              How  much  time(1,2,n)  a  Postfix  daemon process may take to handle a
              request before it is terminated by a built-in watchdog(5,8) timer.

       defer_transports (empty)
              The names of message delivery  transports  that  should  not  be
              delivered  to unless someone issues "sendmail(1,8) -q" or equivalent.

       helpful_warnings (yes)
              Log warnings about problematic configuration settings, and  pro-
              vide helpful suggestions.

       ipc_timeout (3600s)
              The  time(1,2,n)  limit  for  sending  or receiving information over an
              internal communication channel.

       process_id (read-only)
              The process ID of a Postfix command or daemon process.

       process_name (read-only)
              The process name of a Postfix command or daemon process.

       queue_directory (see 'postconf(1,5) -d' output)
              The location of the Postfix top-level queue(1,3) directory.

       syslog_facility (mail(1,8))
              The syslog(2,3,5,3 Sys::Syslog) facility of Postfix logging.

       syslog_name (postfix)
              The mail(1,8) system name that is prepended to the  process  name  in(1,8)
              syslog(2,3,5,3 Sys::Syslog)  records,  so  that  "smtpd" becomes, for example, "post-

       /var/spool/postfix/incoming, incoming queue(1,3)
       /var/spool/postfix/active, active queue(1,3)
       /var/spool/postfix/deferred, deferred queue(1,3)
       /var/spool/postfix/bounce, non-delivery status
       /var/spool/postfix/defer, non-delivery status
       /var/spool/postfix/trace(3x,n,3x _nc_tracebits), delivery status

       trivial-rewrite(8), address routing
       bounce(8), delivery status reports
       postconf(1,5)(5), configuration parameters
       master(5,8)(5), generic daemon options
       master(5,8)(8), process manager
       syslogd(8), system logging

       Use "postconf(1,5) readme_directory" or "postconf(1,5) html_directory" to  locate
       this information.
       SCHEDULER_README, scheduling algorithm
       QSHAPE_README, Postfix queue(1,3) analysis

       The Secure Mailer license must be distributed with this software.

       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA

       Scheduler enhancements:
       Patrik Rak
       Modra 6
       155 00, Prague, Czech Republic


References for this manual (incoming links)