qmqpd.8.html   [plain text]

<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
<html> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<title> Postfix manual - qmqpd(8) </title>
</head> <body> <pre>
QMQPD(8)                                                              QMQPD(8)

       qmqpd - Postfix QMQP server

       <b>qmqpd</b> [generic Postfix daemon options]

       The  Postfix  QMQP server receives one message per connec-
       tion.  Each message is piped through the  <a href="cleanup.8.html"><b>cleanup</b>(8)</a>  dae-
       mon,  and  is placed into the <a href="QSHAPE_README.html#incoming_queue"><b>incoming</b> queue</a> as one single
       queue file.  The program expects to be run from  the  <a href="master.8.html"><b>mas-</b></a>
       <a href="master.8.html"><b>ter</b>(8)</a> process manager.

       The QMQP server implements one access policy: only explic-
       itly authorized client hosts are allowed to use  the  ser-

       The QMQP server is moderately security-sensitive. It talks
       to QMQP clients and to DNS servers  on  the  network.  The
       QMQP server can be run chrooted at fixed low privilege.

       Problems and transactions are logged to <b>syslogd</b>(8).

       The  QMQP protocol provides only one server reply per mes-
       sage delivery. It is  therefore  not  possible  to  reject
       individual recipients.

       The  QMQP  protocol  requires  the  server  to receive the
       entire message before replying. If a message is malformed,
       or  if  any netstring component is longer than acceptable,
       Postfix replies immediately and closes the connection.  It
       is left up to the client to handle the situation.

       Changes   to  <a href="postconf.5.html"><b>main.cf</b></a>  are  picked  up  automatically,  as
       <a href="qmqpd.8.html"><b>qmqpd</b>(8)</a> processes run for only a limited amount of  time.
       Use the command "<b>postfix reload</b>" to speed up a change.

       The  text  below  provides  only  a parameter summary. See
       <a href="postconf.5.html"><b>postconf</b>(5)</a> for more details including examples.

       <b><a href="postconf.5.html#content_filter">content_filter</a> (empty)</b>
              After the message is queued, send the  entire  mes-
              sage to the specified <i>transport:destination</i>.

       <b><a href="postconf.5.html#receive_override_options">receive_override_options</a> (empty)</b>
              Enable  or  disable  recipient validation, built-in
              content filtering, or address mapping.

       <b><a href="postconf.5.html#line_length_limit">line_length_limit</a> (2048)</b>
              Upon input, long lines are chopped up  into  pieces
              of  at  most this length; upon delivery, long lines
              are reconstructed.

       <b><a href="postconf.5.html#hopcount_limit">hopcount_limit</a> (50)</b>
              The maximal number of  Received:   message  headers
              that is allowed in the primary message headers.

       <b><a href="postconf.5.html#message_size_limit">message_size_limit</a> (10240000)</b>
              The  maximal  size in bytes of a message, including
              envelope information.

       <b><a href="postconf.5.html#qmqpd_timeout">qmqpd_timeout</a> (300s)</b>
              The time limit for sending or receiving information
              over the network.

       <b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b>
              The  increment  in  verbose  logging  level  when a
              remote client or server matches a  pattern  in  the
              <a href="postconf.5.html#debug_peer_list">debug_peer_list</a> parameter.

       <b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a> (empty)</b>
              Optional  list  of remote client or server hostname
              or network address patterns that cause the  verbose
              logging  level  to increase by the amount specified
              in $<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>.

       <b><a href="postconf.5.html#soft_bounce">soft_bounce</a> (no)</b>
              Safety net to keep mail queued that would otherwise
              be returned to the sender.

       <b><a href="postconf.5.html#qmqpd_error_delay">qmqpd_error_delay</a> (1s)</b>
              How  long the Postfix QMQP server will pause before
              sending a negative reply to the remote QMQP client.

       <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
              The  default  location  of  the Postfix <a href="postconf.5.html">main.cf</a> and
              <a href="master.5.html">master.cf</a> configuration files.

       <b><a href="postconf.5.html#daemon_timeout">daemon_timeout</a> (18000s)</b>
              How much time a Postfix daemon process may take  to
              handle  a  request  before  it  is  terminated by a
              built-in watchdog timer.

       <b><a href="postconf.5.html#ipc_timeout">ipc_timeout</a> (3600s)</b>
              The time limit for sending or receiving information
              over an internal communication channel.

       <b><a href="postconf.5.html#max_idle">max_idle</a> (100s)</b>
              The  maximum  amount  of  time that an idle Postfix
              daemon process waits  for  an  incoming  connection
              before terminating voluntarily.

       <b><a href="postconf.5.html#max_use">max_use</a> (100)</b>
              The  maximal  number of incoming connections that a
              Postfix daemon process will service  before  termi-
              nating voluntarily.

       <b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b>
              The  process  ID  of  a  Postfix  command or daemon

       <b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b>
              The process name of a  Postfix  command  or  daemon

       <b><a href="postconf.5.html#qmqpd_authorized_clients">qmqpd_authorized_clients</a> (empty)</b>
              What  remote QMQP clients are allowed to connect to
              the Postfix QMQP server port.

       <b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b>
              The location of the Postfix top-level queue  direc-

       <b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b>
              The syslog facility of Postfix logging.

       <b><a href="postconf.5.html#syslog_name">syslog_name</a> (see 'postconf -d' output)</b>
              The  mail  system  name  that  is  prepended to the
              process name in syslog  records,  so  that  "smtpd"
              becomes, for example, "postfix/smtpd".

       <b><a href="postconf.5.html#verp_delimiter_filter">verp_delimiter_filter</a> (-=+)</b>
              The  characters  Postfix  accepts as VERP delimiter
              characters on the Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command  line
              and in SMTP commands.

       Available in Postfix version 2.5 and later:

       <b><a href="postconf.5.html#qmqpd_client_port_logging">qmqpd_client_port_logging</a> (no)</b>
              Enable  logging  of  the remote QMQP client port in
              addition to the hostname and IP address.

<b>SEE ALSO</b>
       <a href="http://cr.yp.to/proto/qmqp.html">http://cr.yp.to/proto/qmqp.html</a>, QMQP protocol
       <a href="cleanup.8.html">cleanup(8)</a>, message canonicalization
       <a href="master.8.html">master(8)</a>, process manager
       syslogd(8), system logging

       <a href="QMQP_README.html">QMQP_README</a>, Postfix ezmlm-idx howto.

       The  Secure  Mailer  license must be distributed with this

       The qmqpd service was introduced with Postfix version 1.1.

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

</pre> </body> </html>