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 - qmqpd(8) </title> 6</head> <body> <pre> 7QMQPD(8) QMQPD(8) 8 9<b>NAME</b> 10 qmqpd - Postfix QMQP server 11 12<b>SYNOPSIS</b> 13 <b>qmqpd</b> [generic Postfix daemon options] 14 15<b>DESCRIPTION</b> 16 The Postfix QMQP server receives one message per connec- 17 tion. Each message is piped through the <a href="cleanup.8.html"><b>cleanup</b>(8)</a> dae- 18 mon, and is placed into the <a href="QSHAPE_README.html#incoming_queue"><b>incoming</b> queue</a> as one single 19 queue file. The program expects to be run from the <a href="master.8.html"><b>mas-</b></a> 20 <a href="master.8.html"><b>ter</b>(8)</a> process manager. 21 22 The QMQP server implements one access policy: only explic- 23 itly authorized client hosts are allowed to use the ser- 24 vice. 25 26<b>SECURITY</b> 27 The QMQP server is moderately security-sensitive. It talks 28 to QMQP clients and to DNS servers on the network. The 29 QMQP server can be run chrooted at fixed low privilege. 30 31<b>DIAGNOSTICS</b> 32 Problems and transactions are logged to <b>syslogd</b>(8). 33 34<b>BUGS</b> 35 The QMQP protocol provides only one server reply per mes- 36 sage delivery. It is therefore not possible to reject 37 individual recipients. 38 39 The QMQP protocol requires the server to receive the 40 entire message before replying. If a message is malformed, 41 or if any netstring component is longer than acceptable, 42 Postfix replies immediately and closes the connection. It 43 is left up to the client to handle the situation. 44 45<b>CONFIGURATION PARAMETERS</b> 46 Changes to <a href="postconf.5.html"><b>main.cf</b></a> are picked up automatically, as 47 <a href="qmqpd.8.html"><b>qmqpd</b>(8)</a> processes run for only a limited amount of time. 48 Use the command "<b>postfix reload</b>" to speed up a change. 49 50 The text below provides only a parameter summary. See 51 <a href="postconf.5.html"><b>postconf</b>(5)</a> for more details including examples. 52 53<b>CONTENT INSPECTION CONTROLS</b> 54 <b><a href="postconf.5.html#content_filter">content_filter</a> (empty)</b> 55 After the message is queued, send the entire mes- 56 sage to the specified <i>transport:destination</i>. 57 58 <b><a href="postconf.5.html#receive_override_options">receive_override_options</a> (empty)</b> 59 Enable or disable recipient validation, built-in 60 content filtering, or address mapping. 61 62<b>RESOURCE AND RATE CONTROLS</b> 63 <b><a href="postconf.5.html#line_length_limit">line_length_limit</a> (2048)</b> 64 Upon input, long lines are chopped up into pieces 65 of at most this length; upon delivery, long lines 66 are reconstructed. 67 68 <b><a href="postconf.5.html#hopcount_limit">hopcount_limit</a> (50)</b> 69 The maximal number of Received: message headers 70 that is allowed in the primary message headers. 71 72 <b><a href="postconf.5.html#message_size_limit">message_size_limit</a> (10240000)</b> 73 The maximal size in bytes of a message, including 74 envelope information. 75 76 <b><a href="postconf.5.html#qmqpd_timeout">qmqpd_timeout</a> (300s)</b> 77 The time limit for sending or receiving information 78 over the network. 79 80<b>TROUBLE SHOOTING CONTROLS</b> 81 <b><a href="postconf.5.html#debug_peer_level">debug_peer_level</a> (2)</b> 82 The increment in verbose logging level when a 83 remote client or server matches a pattern in the 84 <a href="postconf.5.html#debug_peer_list">debug_peer_list</a> parameter. 85 86 <b><a href="postconf.5.html#debug_peer_list">debug_peer_list</a> (empty)</b> 87 Optional list of remote client or server hostname 88 or network address patterns that cause the verbose 89 logging level to increase by the amount specified 90 in $<a href="postconf.5.html#debug_peer_level">debug_peer_level</a>. 91 92 <b><a href="postconf.5.html#soft_bounce">soft_bounce</a> (no)</b> 93 Safety net to keep mail queued that would otherwise 94 be returned to the sender. 95 96<b>TARPIT CONTROLS</b> 97 <b><a href="postconf.5.html#qmqpd_error_delay">qmqpd_error_delay</a> (1s)</b> 98 How long the QMQP server will pause before sending 99 a negative reply to the client. 100 101<b>MISCELLANEOUS CONTROLS</b> 102 <b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b> 103 The default location of the Postfix <a href="postconf.5.html">main.cf</a> and 104 <a href="master.5.html">master.cf</a> configuration files. 105 106 <b><a href="postconf.5.html#daemon_timeout">daemon_timeout</a> (18000s)</b> 107 How much time a Postfix daemon process may take to 108 handle a request before it is terminated by a 109 built-in watchdog timer. 110 111 <b><a href="postconf.5.html#ipc_timeout">ipc_timeout</a> (3600s)</b> 112 The time limit for sending or receiving information 113 over an internal communication channel. 114 115 <b><a href="postconf.5.html#max_idle">max_idle</a> (100s)</b> 116 The maximum amount of time that an idle Postfix 117 daemon process waits for an incoming connection 118 before terminating voluntarily. 119 120 <b><a href="postconf.5.html#max_use">max_use</a> (100)</b> 121 The maximal number of incoming connections that a 122 Postfix daemon process will service before termi- 123 nating voluntarily. 124 125 <b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b> 126 The process ID of a Postfix command or daemon 127 process. 128 129 <b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b> 130 The process name of a Postfix command or daemon 131 process. 132 133 <b><a href="postconf.5.html#qmqpd_authorized_clients">qmqpd_authorized_clients</a> (empty)</b> 134 What clients are allowed to connect to the QMQP 135 server port. 136 137 <b><a href="postconf.5.html#queue_directory">queue_directory</a> (see 'postconf -d' output)</b> 138 The location of the Postfix top-level queue direc- 139 tory. 140 141 <b><a href="postconf.5.html#syslog_facility">syslog_facility</a> (mail)</b> 142 The syslog facility of Postfix logging. 143 144 <b><a href="postconf.5.html#syslog_name">syslog_name</a> (see 'postconf -d' output)</b> 145 The mail system name that is prepended to the 146 process name in syslog records, so that "smtpd" 147 becomes, for example, "postfix/smtpd". 148 149 <b><a href="postconf.5.html#verp_delimiter_filter">verp_delimiter_filter</a> (-=+)</b> 150 The characters Postfix accepts as VERP delimiter 151 characters on the Postfix <a href="sendmail.1.html"><b>sendmail</b>(1)</a> command line 152 and in SMTP commands. 153 154 Available in Postfix version 2.5 and later: 155 156 <b><a href="postconf.5.html#qmqpd_client_port_logging">qmqpd_client_port_logging</a> (no)</b> 157 Enable logging of the remote QMQP client port in 158 addition to the hostname and IP address. 159 160<b>SEE ALSO</b> 161 <a href="http://cr.yp.to/proto/qmqp.html">http://cr.yp.to/proto/qmqp.html</a>, QMQP protocol 162 <a href="cleanup.8.html">cleanup(8)</a>, message canonicalization 163 <a href="master.8.html">master(8)</a>, process manager 164 syslogd(8), system logging 165 166<b>README FILES</b> 167 <a href="QMQP_README.html">QMQP_README</a>, Postfix ezmlm-idx howto. 168 169<b>LICENSE</b> 170 The Secure Mailer license must be distributed with this 171 software. 172 173<b>HISTORY</b> 174 The qmqpd service was introduced with Postfix version 1.1. 175 176<b>AUTHOR(S)</b> 177 Wietse Venema 178 IBM T.J. Watson Research 179 P.O. Box 704 180 Yorktown Heights, NY 10598, USA 181 182 QMQPD(8) 183</pre> </body> </html> 184