294 lines
14 KiB
HTML
294 lines
14 KiB
HTML
<!doctype html public "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
"http://www.w3.org/TR/html4/loose.dtd">
|
|
<html> <head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
|
<title> Postfix manual - lmtp(8) </title>
|
|
</head> <body> <pre>
|
|
LMTP(8) LMTP(8)
|
|
|
|
<b>NAME</b>
|
|
lmtp - Postfix local delivery via LMTP
|
|
|
|
<b>SYNOPSIS</b>
|
|
<b>lmtp</b> [generic Postfix daemon options]
|
|
|
|
<b>DESCRIPTION</b>
|
|
The LMTP client processes message delivery requests from
|
|
the queue manager. Each request specifies a queue file, a
|
|
sender address, a domain or host to deliver to, and recip-
|
|
ient information. This program expects to be run from the
|
|
<a href="master.8.html"><b>master</b>(8)</a> process manager.
|
|
|
|
The LMTP client updates the queue file and marks recipi-
|
|
ents as finished, or it informs the queue manager that
|
|
delivery should be tried again at a later time. Delivery
|
|
status reports are sent to the <a href="bounce.8.html"><b>bounce</b>(8)</a>, <a href="defer.8.html"><b>defer</b>(8)</a> or
|
|
<a href="trace.8.html"><b>trace</b>(8)</a> daemon as appropriate.
|
|
|
|
The LMTP client connects to the destination specified in
|
|
the message delivery request. The destination, usually
|
|
specified in the Postfix <a href="transport.5.html"><b>transport</b>(5)</a> table, has the form:
|
|
|
|
<b>unix</b>:<i>pathname</i>
|
|
Connect to the local UNIX-domain server that is
|
|
bound to the specified <i>pathname</i>. If the process
|
|
runs chrooted, an absolute pathname is interpreted
|
|
relative to the changed root directory.
|
|
|
|
<b>inet</b>:<i>host</i>, <b>inet:</b><i>host</i>:<i>port</i> (symbolic host)
|
|
|
|
<b>inet</b>:[<i>addr</i>], <b>inet</b>:[<i>addr</i>]:<i>port</i> (numeric host)
|
|
Connect to the specified IPV4 TCP port on the spec-
|
|
ified local or remote host. If no port is speci-
|
|
fied, connect to the port defined as <b>lmtp</b> in <b>ser-</b>
|
|
<b>vices</b>(4). If no such service is found, the
|
|
<b><a href="postconf.5.html#lmtp_tcp_port">lmtp_tcp_port</a></b> configuration parameter (default
|
|
value of 24) will be used.
|
|
|
|
The LMTP client does not perform MX (mail
|
|
exchanger) lookups since those are defined only for
|
|
mail delivery via SMTP.
|
|
|
|
If neither <b>unix:</b> nor <b>inet:</b> are specified, <b>inet:</b> is
|
|
assumed.
|
|
|
|
<b>SECURITY</b>
|
|
The LMTP client is moderately security-sensitive. It talks
|
|
to LMTP servers and to DNS servers on the network. The
|
|
LMTP client can be run chrooted at fixed low privilege.
|
|
|
|
<b>STANDARDS</b>
|
|
<a href="http://www.faqs.org/rfcs/rfc821.html">RFC 821</a> (SMTP protocol)
|
|
<a href="http://www.faqs.org/rfcs/rfc1651.html">RFC 1651</a> (SMTP service extensions)
|
|
<a href="http://www.faqs.org/rfcs/rfc1652.html">RFC 1652</a> (8bit-MIME transport)
|
|
<a href="http://www.faqs.org/rfcs/rfc1870.html">RFC 1870</a> (Message Size Declaration)
|
|
<a href="http://www.faqs.org/rfcs/rfc2033.html">RFC 2033</a> (LMTP protocol)
|
|
<a href="http://www.faqs.org/rfcs/rfc2554.html">RFC 2554</a> (AUTH command)
|
|
<a href="http://www.faqs.org/rfcs/rfc2821.html">RFC 2821</a> (SMTP protocol)
|
|
<a href="http://www.faqs.org/rfcs/rfc2920.html">RFC 2920</a> (SMTP Pipelining)
|
|
|
|
<b>DIAGNOSTICS</b>
|
|
Problems and transactions are logged to <b>syslogd</b>(8). Cor-
|
|
rupted message files are marked so that the queue manager
|
|
can move them to the <b>corrupt</b> queue for further inspection.
|
|
|
|
Depending on the setting of the <b><a href="postconf.5.html#notify_classes">notify_classes</a></b> parameter,
|
|
the postmaster is notified of bounces, protocol problems,
|
|
and of other trouble.
|
|
|
|
<b>CONFIGURATION PARAMETERS</b>
|
|
Changes to <b>main.cf</b> are picked up automatically, as <a href="lmtp.8.html">lmtp(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">postconf(5)</a> for more details including examples.
|
|
|
|
<b>COMPATIBILITY CONTROLS</b>
|
|
<b><a href="postconf.5.html#lmtp_skip_quit_response">lmtp_skip_quit_response</a> (no)</b>
|
|
Wait for the response to the LMTP QUIT command.
|
|
|
|
<b>TROUBLE SHOOTING CONTROLS</b>
|
|
<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#error_notice_recipient">error_notice_recipient</a> (postmaster)</b>
|
|
The recipient of postmaster notifications about
|
|
mail delivery problems that are caused by policy,
|
|
resource, software or protocol errors.
|
|
|
|
<b><a href="postconf.5.html#notify_classes">notify_classes</a> (resource, software)</b>
|
|
The list of error classes that are reported to the
|
|
postmaster.
|
|
|
|
<b>EXTERNAL CONTENT INSPECTION CONTROLS</b>
|
|
Available in Postfix version 2.1 and later:
|
|
|
|
<b><a href="postconf.5.html#lmtp_send_xforward_command">lmtp_send_xforward_command</a> (no)</b>
|
|
Send an XFORWARD command to the LMTP server when
|
|
the LMTP LHLO server response announces XFORWARD
|
|
support.
|
|
|
|
<b>SASL AUTHENTICATION CONTROLS</b>
|
|
<b><a href="postconf.5.html#lmtp_sasl_auth_enable">lmtp_sasl_auth_enable</a> (no)</b>
|
|
Enable SASL authentication in the Postfix LMTP
|
|
client.
|
|
|
|
<b><a href="postconf.5.html#lmtp_sasl_password_maps">lmtp_sasl_password_maps</a> (empty)</b>
|
|
Optional LMTP client lookup tables with one user-
|
|
name:password entry per host or domain.
|
|
|
|
<b><a href="postconf.5.html#lmtp_sasl_security_options">lmtp_sasl_security_options</a> (noplaintext, noanonymous)</b>
|
|
What authentication mechanisms the Postfix LMTP
|
|
client is allowed to use.
|
|
|
|
<b>RESOURCE AND RATE CONTROLS</b>
|
|
In the text below, <i>transport</i> is the name of the service as
|
|
specified in the <b>master.cf</b> file.
|
|
|
|
<b><a href="postconf.5.html#lmtp_cache_connection">lmtp_cache_connection</a> (yes)</b>
|
|
Keep Postfix LMTP client connections open for up to
|
|
$<a href="postconf.5.html#max_idle">max_idle</a> seconds.
|
|
|
|
<i>transport</i><b>_destination_concurrency_limit ($<a href="postconf.5.html#default_destination_concurrency_limit">default_destina</a>-</b>
|
|
<b><a href="postconf.5.html#default_destination_concurrency_limit">tion_concurrency_limit</a>)</b>
|
|
Limit the number of parallel deliveries to the same
|
|
destination via this mail delivery transport.
|
|
|
|
<i>transport</i><b>_destination_recipient_limit ($<a href="postconf.5.html#default_destination_recipient_limit">default_destina</a>-</b>
|
|
<b><a href="postconf.5.html#default_destination_recipient_limit">tion_recipient_limit</a>)</b>
|
|
Limit the number of recipients per message delivery
|
|
via this mail delivery transport.
|
|
|
|
This parameter becomes significant if the LMTP
|
|
client is used for local delivery. Some LMTP
|
|
servers can optimize delivery of the same message
|
|
to multiple recipients. The default limit for local
|
|
mail delivery is 1.
|
|
|
|
Setting this parameter to 0 will lead to an
|
|
unbounded number of recipients per delivery. How-
|
|
ever, this could be risky since it may make the
|
|
machine vulnerable to running out of resources if
|
|
messages are encountered with an inordinate number
|
|
of recipients. Exercise care when setting this
|
|
parameter.
|
|
|
|
<b><a href="postconf.5.html#lmtp_connect_timeout">lmtp_connect_timeout</a> (0s)</b>
|
|
The LMTP client time limit for completing a TCP
|
|
connection, or zero (use the operating system
|
|
built-in time limit).
|
|
|
|
<b><a href="postconf.5.html#lmtp_lhlo_timeout">lmtp_lhlo_timeout</a> (300s)</b>
|
|
The LMTP client time limit for receiving the LMTP
|
|
greeting banner.
|
|
|
|
<b><a href="postconf.5.html#lmtp_xforward_timeout">lmtp_xforward_timeout</a> (300s)</b>
|
|
The LMTP client time limit for sending the XFORWARD
|
|
command, and for receiving the server response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_mail_timeout">lmtp_mail_timeout</a> (300s)</b>
|
|
The LMTP client time limit for sending the MAIL
|
|
FROM command, and for receiving the server
|
|
response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_rcpt_timeout">lmtp_rcpt_timeout</a> (300s)</b>
|
|
The LMTP client time limit for sending the RCPT TO
|
|
command, and for receiving the server response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_data_init_timeout">lmtp_data_init_timeout</a> (120s)</b>
|
|
The LMTP client time limit for sending the LMTP
|
|
DATA command, and for receiving the server
|
|
response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_data_xfer_timeout">lmtp_data_xfer_timeout</a> (180s)</b>
|
|
The LMTP client time limit for sending the LMTP
|
|
message content.
|
|
|
|
<b><a href="postconf.5.html#lmtp_data_done_timeout">lmtp_data_done_timeout</a> (600s)</b>
|
|
The LMTP client time limit for sending the LMTP
|
|
".", and for receiving the server response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_rset_timeout">lmtp_rset_timeout</a> (120s)</b>
|
|
The LMTP client time limit for sending the RSET
|
|
command, and for receiving the server response.
|
|
|
|
<b><a href="postconf.5.html#lmtp_quit_timeout">lmtp_quit_timeout</a> (300s)</b>
|
|
The LMTP client time limit for sending the QUIT
|
|
command, and for receiving the server response.
|
|
|
|
<b>MISCELLANEOUS CONTROLS</b>
|
|
<b><a href="postconf.5.html#config_directory">config_directory</a> (see 'postconf -d' output)</b>
|
|
The default location of the Postfix main.cf and
|
|
master.cf 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#disable_dns_lookups">disable_dns_lookups</a> (no)</b>
|
|
Disable DNS lookups in the Postfix SMTP and LMTP
|
|
clients.
|
|
|
|
<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#lmtp_tcp_port">lmtp_tcp_port</a> (24)</b>
|
|
The default TCP port that the Postfix LMTP client
|
|
connects to.
|
|
|
|
<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 the next service request
|
|
before exiting.
|
|
|
|
<b><a href="postconf.5.html#max_use">max_use</a> (100)</b>
|
|
The maximal number of connection requests before a
|
|
Postfix daemon process terminates.
|
|
|
|
<b><a href="postconf.5.html#process_id">process_id</a> (read-only)</b>
|
|
The process ID of a Postfix command or daemon pro-
|
|
cess.
|
|
|
|
<b><a href="postconf.5.html#process_name">process_name</a> (read-only)</b>
|
|
The process name of a Postfix command or daemon
|
|
process.
|
|
|
|
<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-
|
|
tory.
|
|
|
|
<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> (postfix)</b>
|
|
The mail system name that is prepended to the pro-
|
|
cess name in syslog records, so that "smtpd"
|
|
becomes, for example, "postfix/smtpd".
|
|
|
|
<b>SEE ALSO</b>
|
|
<a href="bounce.8.html">bounce(8)</a>, delivery status reports
|
|
<a href="qmgr.8.html">qmgr(8)</a>, queue manager
|
|
<a href="postconf.5.html">postconf(5)</a>, configuration parameters
|
|
services(4), Internet services and aliases
|
|
<a href="master.8.html">master(8)</a>, process manager
|
|
syslogd(8), system logging
|
|
|
|
<b>README FILES</b>
|
|
<a href="LMTP_README.html">LMTP_README</a>, Postfix LMTP client howto
|
|
<a href="VIRTUAL_README.html">VIRTUAL_README</a>, virtual delivery agent howto
|
|
|
|
<b>LICENSE</b>
|
|
The Secure Mailer license must be distributed with this
|
|
software.
|
|
|
|
<b>AUTHOR(S)</b>
|
|
Wietse Venema
|
|
IBM T.J. Watson Research
|
|
P.O. Box 704
|
|
Yorktown Heights, NY 10598, USA
|
|
|
|
Alterations for LMTP by:
|
|
Philip A. Prindeville
|
|
Mirapoint, Inc.
|
|
USA.
|
|
|
|
Additional work on LMTP by:
|
|
Amos Gouaux
|
|
University of Texas at Dallas
|
|
P.O. Box 830688, MC34
|
|
Richardson, TX 75083, USA
|
|
|
|
LMTP(8)
|
|
</pre> </body> </html>
|