Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 62 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

qmgr



SYNOPSIS

       qmgr [generic Postfix daemon options]


DESCRIPTION

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

       Mail  addressed  to  the  local  double-bounce  address is
       silently discarded.  This stops potential loops caused  by
       undeliverable bounce notifications.


MAIL QUEUES

       The qmgr daemon maintains the following queues:

       incoming
              Inbound mail from the network, or mail picked up by
              the local pickup agent from the maildrop directory.

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

       deferred
              Mail that could not be  delivered  upon  the  first
              attempt.  The  queue manager implements exponential
              backoff  by  doubling  the  time  between  delivery
              attempts.

       corrupt
              Unreadable  or  damaged  queue files are moved here
              for inspection.

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


DELIVERY STATUS REPORTS

       The  qmgr daemon keeps an eye on per-message delivery sta­
       tus reports in  the  following  directories.  Each  status
       report file has the same name as the corresponding message
       file:

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

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

       fairness
              When  the  active queue has room, the queue manager
              takes one message from the incoming queue  and  one
              from the deferred queue. This prevents a large mail
              backlog from blocking the delivery of new mail.

       slow start
              This strategy eliminates "thundering herd" problems
              by slowly adjusting the number of parallel deliver­
              ies to the same destination.

       round robin
              The queue manager sorts delivery requests by desti­
              nation.   Round-robin selection prevents one desti­
              nation from dominating deliveries to other destina­
              tions.

       exponential backoff
              Mail  that  cannot  be  delivered  upon  the  first
              attempt is deferred.   The  time  interval  between
              delivery attempts is doubled after each attempt.

       destination status cache
              The   queue  manager  avoids  unnecessary  delivery
              attempts by  maintaining  a  short-term,  in-memory
              list of unreachable destinations.


TRIGGERS

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

       D (QMGR_REQ_SCAN_DEFERRED)
              Start a deferred queue scan.  If a  deferred  queue
              scan  is  already  in  progress,  that scan will be
              restarted as soon as it finishes.

       I (QMGR_REQ_SCAN_INCOMING)
              Start an incoming queue scan. If an incoming  queue
              scan  is  already  in  progress,  that scan will be
              restarted as soon as it finishes.

       A (QMGR_REQ_SCAN_ALL)
              Ignore deferred queue file time stamps. The request
              affects the next deferred queue scan.

       F (QMGR_REQ_FLUSH_DEAD)
              Purge  all  information  about  dead transports and
              destinations.


STANDARDS

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


SECURITY

       The  qmgr  daemon is not security sensitive. It reads sin­
       gle-character messages from  untrusted  local  users,  and
       thus  may be susceptible to denial of service attacks. The
       qmgr daemon does not talk to the outside world, and it can
       be run at fixed low privilege in a chrooted environment.


DIAGNOSTICS

       Problems and transactions are logged to the syslog daemon.
       Corrupted message files are saved to the corrupt queue for
       further inspection.

       Depending  on the setting of the notify_classes parameter,
       the postmaster is notified of bounces and of  other  trou­
       ble.


BUGS

       A  single  queue  manager  process has to compete for disk
       access with multiple front-end processes such as smtpd.  A
       sudden  burst  of  inbound mail can negatively impact out­
       bound delivery rates.


CONFIGURATION PARAMETERS

       The following main.cf parameters are  especially  relevant
       to  this  program. See the Postfix main.cf file for syntax
       details and for default values.  Use  the  postfix  reload
       command after a configuration change.


Miscellaneous

       allow_min_user
              Do  not  bounce recipient addresses that begin with
              '-'.

       queue_directory
              Top-level directory of the Postfix queue.


Active queue controls

       qmgr_clog_warn_time
              Minimal delay between warnings that a specific des­
              tination is clogging up the active queue. Specify 0
              to disable.

       qmgr_message_active_limit
              Limit the number of messages in the active queue.

       qmgr_message_recipient_limit
              Limit the number of in-memory recipients.

              of a deferred message.

       maximal_queue_lifetime
              Maximal  time in days a message is queued before it
              is sent back as undeliverable.

       queue_run_delay
              Time in seconds between deferred queue scans. Queue
              scans do not overlap.

       transport_retry_time
              Time  in seconds between attempts to contact a bro­
              ken delivery transport.


Concurrency controls

       In the text below, transport is the first field in a  mas­
       ter.cf entry.

       qmgr_fudge_factor (valid range: 10..100)
              The  percentage  of  delivery resources that a busy
              mail system will use up for  delivery  of  a  large
              mailing  list  message.  With 100%, delivery of one
              message does not begin before the previous  message
              has  been  delivered.  This results in good perfor­
              mance for large mailing lists, but results in  poor
              response  time for one-to-one mail.  With less than
              100%, response time for one-to-one  mail  improves,
              but  large  mailing  list delivery performance suf­
              fers. In the worst case, recipients near the begin­
              ning  of  a  large list receive a burst of messages
              immediately, while recipients near the end of  that
              list  receive  that  same burst of messages a whole
              day later.

       initial_destination_concurrency
              Initial per-destination concurrency level for  par­
              allel delivery to the same destination.

       default_destination_concurrency_limit
              Default  limit on the number of parallel deliveries
              to the same destination.

       transport_destination_concurrency_limit
              Limit on the number of parallel deliveries  to  the
              same  destination,  for delivery via the named mes­
              sage transport.


Recipient controls

       default_destination_recipient_limit
              Default limit on the number of recipients per  mes­
              sage transfer.

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

                                                          QMGR(8)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.05 Seconds