From 583a9d46f1f71a099dc2bec366be4012b89045a1 Mon Sep 17 00:00:00 2001
From: Wietse Venema
-LMTP(8) LMTP(8)
-
-NAME
- lmtp - Postfix local delivery via LMTP
-
-SYNOPSIS
- lmtp [generic Postfix daemon options]
-
-DESCRIPTION
- 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
- master(8) 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 bounce(8), defer(8) or
- trace(8) daemon as appropriate.
-
- The LMTP client connects to the destination specified in
- the message delivery request. The destination, usually
- specified in the Postfix transport(5) table, has the form:
-
- unix:pathname
- Connect to the local UNIX-domain server that is
- bound to the specified pathname. If the process
- runs chrooted, an absolute pathname is interpreted
- relative to the changed root directory.
-
- inet:host, inet:host:port (symbolic host)
-
- inet:[addr], inet:[addr]:port (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 lmtp in ser-
- vices(4). If no such service is found, the
- lmtp_tcp_port 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 unix: nor inet: are specified, inet: is
- assumed.
-
-SECURITY
- 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.
-
-STANDARDS
- RFC 821 (SMTP protocol)
- RFC 1651 (SMTP service extensions)
- RFC 1652 (8bit-MIME transport)
- RFC 1870 (Message Size Declaration)
- RFC 2033 (LMTP protocol)
- RFC 2034 (Enhanced Status codes)
- RFC 2554 (AUTH command)
- RFC 2821 (SMTP protocol)
- RFC 2920 (SMTP Pipelining)
- RFC 3463 (Enhanced Status codes)
-
-DIAGNOSTICS
- Problems and transactions are logged to syslogd(8). Cor-
- rupted message files are marked so that the queue manager
- can move them to the corrupt queue for further inspection.
-
- Depending on the setting of the notify_classes parameter,
- the postmaster is notified of bounces, protocol problems,
- and of other trouble.
-
-CONFIGURATION PARAMETERS
- Changes to main.cf are picked up automatically, as lmtp(8)
- processes run for only a limited amount of time. Use the
- command "postfix reload" to speed up a change.
-
- The text below provides only a parameter summary. See
- postconf(5) for more details including examples.
-
-COMPATIBILITY CONTROLS
- lmtp_skip_quit_response (no)
- Wait for the response to the LMTP QUIT command.
-
-TROUBLE SHOOTING CONTROLS
- debug_peer_level (2)
- The increment in verbose logging level when a
- remote client or server matches a pattern in the
- debug_peer_list parameter.
-
- debug_peer_list (empty)
- 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 $debug_peer_level.
-
- error_notice_recipient (postmaster)
- The recipient of postmaster notifications about
- mail delivery problems that are caused by policy,
- resource, software or protocol errors.
-
- notify_classes (resource, software)
- The list of error classes that are reported to the
- postmaster.
-
-EXTERNAL CONTENT INSPECTION CONTROLS
- Available in Postfix version 2.1 and later:
-
- lmtp_send_xforward_command (no)
- Send an XFORWARD command to the LMTP server when
- the LMTP LHLO server response announces XFORWARD
- support.
-
-SASL AUTHENTICATION CONTROLS
- lmtp_sasl_auth_enable (no)
- Enable SASL authentication in the Postfix LMTP
- client.
-
- lmtp_sasl_password_maps (empty)
- Optional LMTP client lookup tables with one user-
- name:password entry per host or domain.
-
- lmtp_sasl_security_options (noplaintext, noanonymous)
- What authentication mechanisms the Postfix LMTP
- client is allowed to use.
-
-RESOURCE AND RATE CONTROLS
- In the text below, transport is the name of the service as
- specified in the master.cf file.
-
- lmtp_cache_connection (yes)
- Keep Postfix LMTP client connections open for up to
- $max_idle seconds.
-
- transport_destination_concurrency_limit ($default_destina-
- tion_concurrency_limit)
- Limit the number of parallel deliveries to the same
- destination via this mail delivery transport.
-
- transport_destination_recipient_limit ($default_destina-
- tion_recipient_limit)
- 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.
-
- lmtp_connect_timeout (0s)
- The LMTP client time limit for completing a TCP
- connection, or zero (use the operating system
- built-in time limit).
-
- lmtp_lhlo_timeout (300s)
- The LMTP client time limit for receiving the LMTP
- greeting banner.
-
- lmtp_xforward_timeout (300s)
- The LMTP client time limit for sending the XFORWARD
- command, and for receiving the server response.
-
- lmtp_mail_timeout (300s)
- The LMTP client time limit for sending the MAIL
- FROM command, and for receiving the server
- response.
-
- lmtp_rcpt_timeout (300s)
- The LMTP client time limit for sending the RCPT TO
- command, and for receiving the server response.
-
- lmtp_data_init_timeout (120s)
- The LMTP client time limit for sending the LMTP
- DATA command, and for receiving the server
- response.
-
- lmtp_data_xfer_timeout (180s)
- The LMTP client time limit for sending the LMTP
- message content.
-
- lmtp_data_done_timeout (600s)
- The LMTP client time limit for sending the LMTP
- ".", and for receiving the server response.
-
- lmtp_rset_timeout (20s)
- The LMTP client time limit for sending the RSET
- command, and for receiving the server response.
-
- lmtp_quit_timeout (300s)
- The LMTP client time limit for sending the QUIT
- command, and for receiving the server response.
-
-MISCELLANEOUS CONTROLS
- config_directory (see 'postconf -d' output)
- The default location of the Postfix main.cf and
- master.cf configuration files.
-
- daemon_timeout (18000s)
- How much time a Postfix daemon process may take to
- handle a request before it is terminated by a
- built-in watchdog timer.
-
- delay_logging_resolution_limit (2)
- The maximal number of digits after the decimal
- point when logging sub-second delay values.
-
- disable_dns_lookups (no)
- Disable DNS lookups in the Postfix SMTP and LMTP
- clients.
-
- ipc_timeout (3600s)
- The time limit for sending or receiving information
- over an internal communication channel.
-
- lmtp_tcp_port (24)
- The default TCP port that the Postfix LMTP client
- connects to.
-
- max_idle (100s)
- The maximum amount of time that an idle Postfix
- daemon process waits for the next service request
- before exiting.
-
- max_use (100)
- The maximal number of connection requests before a
- Postfix daemon process terminates.
-
- 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 -d' output)
- The location of the Postfix top-level queue direc-
- tory.
-
- syslog_facility (mail)
- The syslog facility of Postfix logging.
-
- syslog_name (postfix)
- The mail system name that is prepended to the
- process name in syslog records, so that "smtpd"
- becomes, for example, "postfix/smtpd".
-
-SEE ALSO
- bounce(8), delivery status reports
- qmgr(8), queue manager
- postconf(5), configuration parameters
- master(5), generic daemon options
- services(4), Internet services and aliases
- master(8), process manager
- syslogd(8), system logging
-
-README FILES
- LMTP_README, Postfix LMTP client howto
- VIRTUAL_README, virtual delivery agent howto
-
-LICENSE
- The Secure Mailer license must be distributed with this
- software.
-
-AUTHOR(S)
- Wietse Venema
- IBM T.J. Watson Research
- P.O. Box 704
- Yorktown Heights, NY 10598, USA
-
- Modifications for LMTP by:
- Philip A. Prindeville
- Mirapoint, Inc.
- USA.
-
- SASL support originally by:
- Till Franke
- SuSE Rhein/Main AG
- 65760 Eschborn, Germany
-
- Additional work on LMTP by:
- Amos Gouaux
- University of Texas at Dallas
- P.O. Box 830688, MC34
- Richardson, TX 75083, USA
-
- LMTP(8)
-
diff --git a/postfix/html/lmtp.8.html b/postfix/html/lmtp.8.html
new file mode 120000
index 000000000..6ec40f8f3
--- /dev/null
+++ b/postfix/html/lmtp.8.html
@@ -0,0 +1 @@
+smtp.8.html
\ No newline at end of file
diff --git a/postfix/html/postconf.5.html b/postfix/html/postconf.5.html
index fa2eef1fd..6f314d737 100644
--- a/postfix/html/postconf.5.html
+++ b/postfix/html/postconf.5.html
@@ -893,6 +893,14 @@ a "type:table" lookup table is matched when a
(the lookup result is ignored). Continue long lines by starting the
next line with whitespace.
+Example: +
+ ++authorized_submit_users = !www, static:all ++
This feature is available in Postfix 2.2 and later.
@@ -1366,6 +1374,17 @@ requires that the directory is listed with the connection_cache_protocol_timeout +(default: 5s)Time limit for connection cache connect, send or receive +operations. The time limit is enforced in the client.
+ +This feature is available in Postfix 2.3 and later.
+ +Optional list of relay hosts for SMTP destinations that can't be -found or that are unreachable.
+found or that are unreachable. With Postfix 2.3 this parameter +is renamed to smtp_fallback_relay.By default, mail is returned to the sender when a destination is -not found, and delivery is deferred if a destination is unreachable. +not found, and delivery is deferred when a destination is unreachable.
The fallback relays must be SMTP destinations. Specify a domain, @@ -2311,7 +2331,8 @@ host, host:port, [host]:port, [address] or [address]:port; the form [host] turns off MX lookups. If you specify multiple SMTP destinations, Postfix will try them in the specified order.
-Note: do not use the fallback_relay feature when relaying mail +
Note: before Postfix 2.2, do not use the fallback_relay feature +when relaying mail for a backup or primary MX domain. Mail would loop between the Postfix MX host and the fallback_relay host when the final destination is unavailable.
@@ -2328,7 +2349,8 @@ as the right-hand side for backup or primary MX domain entries. -These are default settings in Postfix version 2.2 and later. +
Postfix version 2.2 and later will not use the fallback_relay feature +for destinations that it is MX host for.
@@ -2984,6 +3006,28 @@ This feature is available in Postfix 2.1 and later. this length; upon delivery, long lines are reconstructed. + + +The LMTP-specific version of the smtp_bind_address configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_bind_address6 configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_connection_cache_destinations +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_connection_cache_on_demand +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_connection_reuse_time_limit +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_defer_if_no_mx_address_found +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +Lookup tables, indexed by the remote LMTP server address, with +case insensitive lists of LHLO keywords (pipelining, starttls, +auth, etc.) that the LMTP client will ignore in the LHLO response +from a remote LMTP server. See lmtp_discard_lhlo_keywords for +details.
+ +This feature is available in Postfix 2.3 and later.
-The LMTP client time limit for receiving the LMTP greeting -banner. When the server drops the connection without sending a -greeting banner, or when it sends no greeting banner within the -deadline, the LMTP client tries the next address on the mail -exchanger list.
+ +A case insensitive list of LHLO keywords (pipelining, starttls, +auth, etc.) that the LMTP client will ignore in the LHLO response +from a remote LMTP server.
+ +This feature is available in Postfix 2.3 and later.
+ +Notes:
+ +Specify the silent-discard pseudo keyword to prevent +this action from being logged.
+ +Use the lmtp_discard_lhlo_keyword_address_maps feature to +discard LHLO keywords selectively.
+ +The LMTP-specific version of the smtp_enforce_tls configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_generic_maps configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_host_lookup configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +-Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). -The default time unit is s (seconds). +The hostname to send in the LMTP LHLO command. +
+ ++The default value is the machine hostname. Specify a hostname or +[ip.add.re.ss].
++This information can be specified in the main.cf file for all LMTP +clients, or it can be specified in the master.cf file for a specific +client, for example: +
+ ++ /etc/postfix/master.cf: + mylmtp ... lmtp -o lmtp_lhlo_name=foo.bar.com ++ +
+This feature is available in Postfix 2.3 and later. +
+ + +The LMTP client time limit for sending the LHLO command, and +for receiving the initial server response.
+ +Time units: s (seconds), m (minutes), h (hours), d (days), w +(weeks). The default time unit is s (seconds).
+ + +The LMTP-specific version of the smtp_line_length_limit +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+The LMTP-specific version of the smtp_mx_address_limit configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_mx_session_limit configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_pix_workaround_delay_time +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_pix_workaround_threshold_time +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_quote_rfc821_envelope +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_randomize_addresses +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_sasl_mechanism_filter +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_sasl_tls_security_options +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_sender_dependent_authentication +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_skip_5xx_greeting +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_starttls_timeout configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +The LMTP-specific version of the smtp_tls_enforce_peername +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_tls_note_starttls_offer +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_tls_per_site configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_tls_scert_verifydepth +configuration parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ + +The LMTP-specific version of the smtp_use_tls configuration +parameter. See there for details.
+ +This feature is available in Postfix 2.3 and later.
+ +A sender-dependent override for the global relayhost parameter setting. The tables are searched by the sender address and by the -sender @domain. This information is overruled with relay_transport, +@domain. This information is overruled with relay_transport, default_transport and with the transport(5) table.
@@ -5994,6 +6365,9 @@ IP address), [] or non-default TCP port), as specified in main.cf or in the transport map, +
+Optional list of relay hosts for SMTP destinations that can't be +found or that are unreachable. With Postfix 2.2 and earlier this +parameter is called fallback_relay.
+ ++By default, mail is returned to the sender when a destination is +not found, and delivery is deferred when a destination is unreachable. +
+ +The fallback relays must be SMTP destinations. Specify a domain, +host, host:port, [host]:port, [address] or [address]:port; the form +[host] turns off MX lookups. If you specify multiple SMTP +destinations, Postfix will try them in the specified order.
+ +To prevent mailer loops between MX hosts and fall-back hosts, +Postfix version 2.3 and later will not use the smtp_fallback_relay +feature for destinations that it is MX host for.
+ +