{ "mode": "man", "parameter": "lmtp", "section": "8postfix", "url": "https://www.chedong.com/phpMan.php/man/lmtp/8postfix/json", "generated": "2026-10-05T17:53:43Z", "synopsis": "smtp [generic Postfix daemon options] [flags=DORX]", "sections": { "NAME": { "content": "smtp - Postfix SMTP+LMTP client\n", "subsections": [] }, "SYNOPSIS": { "content": "smtp [generic Postfix daemon options] [flags=DORX]\n", "subsections": [] }, "DESCRIPTION": { "content": "The Postfix SMTP+LMTP client implements the SMTP and LMTP mail delivery protocols. It\nprocesses message delivery requests from the queue manager. Each request specifies a queue\nfile, a sender address, a domain or host to deliver to, and recipient information. This pro‐\ngram expects to be run from the master(8) process manager.\n\nThe SMTP+LMTP client updates the queue file and marks recipients as finished, or it informs\nthe queue manager that delivery should be tried again at a later time. Delivery status re‐\nports are sent to the bounce(8), defer(8) or trace(8) daemon as appropriate.\n\nThe SMTP+LMTP client looks up a list of mail exchanger addresses for the destination host,\nsorts the list by preference, and connects to each listed address until it finds a server\nthat responds.\n\nWhen a server is not reachable, or when mail delivery fails due to a recoverable error condi‐\ntion, the SMTP+LMTP client will try to deliver the mail to an alternate host.\n\nAfter a successful mail transaction, a connection may be saved to the scache(8) connection\ncache server, so that it may be used by any SMTP+LMTP client for a subsequent transaction.\n\nBy default, connection caching is enabled temporarily for destinations that have a high vol‐\nume of mail in the active queue. Connection caching can be enabled permanently for specific\ndestinations.\n", "subsections": [] }, "SMTP DESTINATION SYNTAX": { "content": "The Postfix SMTP+LMTP client supports multiple destinations separated by comma or whitespace\n(Postfix 3.5 and later). SMTP destinations have the following form:\n\ndomainname\n\ndomainname:port\nLook up the mail exchangers for the specified domain, and connect to the specified\nport (default: smtp).\n\n[hostname]\n\n[hostname]:port\nLook up the address(es) of the specified host, and connect to the specified port (de‐\nfault: smtp).\n\n[address]\n\n[address]:port\nConnect to the host at the specified address, and connect to the specified port (de‐\nfault: smtp). An IPv6 address must be formatted as [ipv6:address].\n", "subsections": [] }, "LMTP DESTINATION SYNTAX": { "content": "The Postfix SMTP+LMTP client supports multiple destinations separated by comma or whitespace\n(Postfix 3.5 and later). LMTP destinations have the following form:\n\nunix:pathname\nConnect to the local UNIX-domain server that is bound to the specified pathname. If\nthe process runs chrooted, an absolute pathname is interpreted relative to the Postfix\nqueue directory.\n\ninet:hostname\n\ninet:hostname:port\n\ninet:[address]\n\ninet:[address]:port\nConnect to the specified TCP port on the specified local or remote host. If no port is\nspecified, connect to the port defined as lmtp in services(4). If no such service is\nfound, the lmtptcpport configuration parameter (default value of 24) will be used.\nAn IPv6 address must be formatted as [ipv6:address].\n", "subsections": [] }, "SINGLE-RECIPIENT DELIVERY": { "content": "By default, the Postfix SMTP+LMTP client delivers mail to multiple recipients per delivery\nrequest. This is undesirable when prepending a Delivered-to: or X-Original-To: message\nheader. To prevent Postfix from sending multiple recipients per delivery request, specify\n\ntransportdestinationrecipientlimit = 1\n\nin the Postfix main.cf file, where transport is the name in the first column of the Postfix\nmaster.cf entry for this mail delivery service.\n", "subsections": [] }, "COMMAND ATTRIBUTE SYNTAX": { "content": "", "subsections": [ { "name": "flags=DORX (optional)", "content": "Optional message processing flags.\n\nD Prepend a \"Delivered-To: recipient\" message header with the envelope recipient\naddress. Note: for this to work, the transportdestinationrecipientlimit must\nbe 1 (see SINGLE-RECIPIENT DELIVERY above for details).\n\nThe D flag also enforces loop detection: if a message already contains a Deliv‐\nered-To: header with the same recipient address, then the message is returned\nas undeliverable. The address comparison is case insensitive.\n\nThis feature is available as of Postfix 3.5.\n\nO Prepend an \"X-Original-To: recipient\" message header with the recipient address\nas given to Postfix. Note: for this to work, the transportdestinationrecipi‐\nentlimit must be 1 (see SINGLE-RECIPIENT DELIVERY above for details).\n\nThis feature is available as of Postfix 3.5.\n\nR Prepend a \"Return-Path: \" message header with the envelope sender ad‐\ndress.\n\nThis feature is available as of Postfix 3.5.\n\nX Indicates that the delivery is final. This flag affects the status reported in\n\"success\" DSN (delivery status notification) messages, and changes it from \"re‐\nlayed\" into \"delivered\".\n\nThis feature is available as of Postfix 3.5.\n" } ] }, "SECURITY": { "content": "The SMTP+LMTP client is moderately security-sensitive. It\ntalks to SMTP or LMTP servers and to DNS servers on the\nnetwork. The SMTP+LMTP client can be run chrooted at fixed\nlow privilege.\n", "subsections": [] }, "STANDARDS": { "content": "RFC 821 (SMTP protocol)\nRFC 822 (ARPA Internet Text Messages)\nRFC 1651 (SMTP service extensions)\nRFC 1652 (8bit-MIME transport)\nRFC 1870 (Message Size Declaration)\nRFC 2033 (LMTP protocol)\nRFC 2034 (SMTP Enhanced Error Codes)\nRFC 2045 (MIME: Format of Internet Message Bodies)\nRFC 2046 (MIME: Media Types)\nRFC 2554 (AUTH command)\nRFC 2821 (SMTP protocol)\nRFC 2782 (SRV resource records)\nRFC 2920 (SMTP Pipelining)\nRFC 3207 (STARTTLS command)\nRFC 3461 (SMTP DSN Extension)\nRFC 3463 (Enhanced Status Codes)\nRFC 4954 (AUTH command)\nRFC 5321 (SMTP protocol)\nRFC 6531 (Internationalized SMTP)\nRFC 6533 (Internationalized Delivery Status Notifications)\nRFC 7672 (SMTP security via opportunistic DANE TLS)\n", "subsections": [] }, "DIAGNOSTICS": { "content": "Problems and transactions are logged to syslogd(8) or postlogd(8). Corrupted message files\nare marked so that the queue manager can move them to the corrupt queue for further inspec‐\ntion.\n\nDepending on the setting of the notifyclasses parameter, the postmaster is notified of\nbounces, protocol problems, and of other trouble.\n", "subsections": [] }, "BUGS": { "content": "SMTP and LMTP connection reuse for TLS (without closing the SMTP or LMTP connection) is not\nsupported before Postfix 3.4.\n\nSMTP and LMTP connection reuse assumes that SASL credentials are valid for all destinations\nthat map onto the same IP address and TCP port.\n", "subsections": [] }, "CONFIGURATION PARAMETERS": { "content": "Before Postfix version 2.3, the LMTP client is a separate program that implements only a sub‐\nset of the functionality available with SMTP: there is no support for TLS, and connections\nare cached in-process, making it ineffective when the client is used for multiple domains.\n\nMost smtpxxx configuration parameters have an lmtpxxx \"mirror\" parameter for the equivalent\nLMTP feature. This document describes only those LMTP-related parameters that aren't simply\n\"mirror\" parameters.\n\nChanges to main.cf are picked up automatically, as smtp(8) processes run for only a limited\namount of time. Use the command \"postfix reload\" to speed up a change.\n\nThe text below provides only a parameter summary. See postconf(5) for more details including\nexamples.\n", "subsections": [] }, "COMPATIBILITY CONTROLS": { "content": "", "subsections": [ { "name": "ignore_mx_lookup_error (no)", "content": "Ignore DNS MX lookups that produce no response.\n" }, { "name": "smtp_always_send_ehlo (yes)", "content": "Always send EHLO at the start of an SMTP session.\n" }, { "name": "smtp_never_send_ehlo (no)", "content": "Never send EHLO at the start of an SMTP session.\n" }, { "name": "smtp_defer_if_no_mx_address_found (no)", "content": "Defer mail delivery when no MX record resolves to an IP address.\n" }, { "name": "smtp_line_length_limit (998)", "content": "The maximal length of message header and body lines that Postfix will send via SMTP.\n" }, { "name": "smtp_pix_workaround_delay_time (10s)", "content": "How long the Postfix SMTP client pauses before sending \".\" in order to work\naround the PIX firewall \".\" bug.\n" }, { "name": "smtp_pix_workaround_threshold_time (500s)", "content": "How long a message must be queued before the Postfix SMTP client turns on the PIX\nfirewall \".\" bug workaround for delivery through firewalls with \"smtp\nfixup\" mode turned on.\n" }, { "name": "smtp_pix_workarounds (disable_esmtp, delay_dotcrlf)", "content": "A list that specifies zero or more workarounds for CISCO PIX firewall bugs.\n" }, { "name": "smtp_pix_workaround_maps (empty)", "content": "Lookup tables, indexed by the remote SMTP server address, with per-destination\nworkarounds for CISCO PIX firewall bugs.\n" }, { "name": "smtp_quote_rfc821_envelope (yes)", "content": "Quote addresses in Postfix SMTP client MAIL FROM and RCPT TO commands as required by\nRFC 5321.\n" }, { "name": "smtp_reply_filter (empty)", "content": "A mechanism to transform replies from remote SMTP servers one line at a time.\n" }, { "name": "smtp_skip_5xx_greeting (yes)", "content": "Skip remote SMTP servers that greet with a 5XX status code.\n" }, { "name": "smtp_skip_quit_response (yes)", "content": "Do not wait for the response to the SMTP QUIT command.\n\nAvailable in Postfix version 2.0 and earlier:\n" }, { "name": "smtp_skip_4xx_greeting (yes)", "content": "Skip SMTP servers that greet with a 4XX status code (go away, try again later).\n\nAvailable in Postfix version 2.2 and later:\n" }, { "name": "smtp_discard_ehlo_keyword_address_maps (empty)", "content": "Lookup tables, indexed by the remote SMTP server address, with case insensitive lists\nof EHLO keywords (pipelining, starttls, auth, etc.) that the Postfix SMTP client will\nignore in the EHLO response from a remote SMTP server.\n" }, { "name": "smtp_discard_ehlo_keywords (empty)", "content": "A case insensitive list of EHLO keywords (pipelining, starttls, auth, etc.) that the\nPostfix SMTP client will ignore in the EHLO response from a remote SMTP server.\n" }, { "name": "smtp_generic_maps (empty)", "content": "Optional lookup tables that perform address rewriting in the Postfix SMTP client, typ‐\nically to transform a locally valid address into a globally valid address when sending\nmail across the Internet.\n\nAvailable in Postfix version 2.2.9 and later:\n" }, { "name": "smtp_cname_overrides_servername (version dependent)", "content": "When the remote SMTP servername is a DNS CNAME, replace the servername with the result\nfrom CNAME expansion for the purpose of logging, SASL password lookup, TLS policy de‐\ncisions, or TLS certificate verification.\n\nAvailable in Postfix version 2.3 and later:\n" }, { "name": "lmtp_discard_lhlo_keyword_address_maps (empty)", "content": "Lookup tables, indexed by the remote LMTP server address, with case insensitive lists\nof LHLO keywords (pipelining, starttls, auth, etc.) that the Postfix LMTP client will\nignore in the LHLO response from a remote LMTP server.\n" }, { "name": "lmtp_discard_lhlo_keywords (empty)", "content": "A case insensitive list of LHLO keywords (pipelining, starttls, auth, etc.) that the\nPostfix LMTP client will ignore in the LHLO response from a remote LMTP server.\n\nAvailable in Postfix version 2.4.4 and later:\n" }, { "name": "send_cyrus_sasl_authzid (no)", "content": "When authenticating to a remote SMTP or LMTP server with the default setting \"no\",\nsend no SASL authoriZation ID (authzid); send only the SASL authentiCation ID (auth‐\ncid) plus the authcid's password.\n\nAvailable in Postfix version 2.5 and later:\n" }, { "name": "smtp_header_checks (empty)", "content": "Restricted headerchecks(5) tables for the Postfix SMTP client.\n" }, { "name": "smtp_mime_header_checks (empty)", "content": "Restricted mimeheaderchecks(5) tables for the Postfix SMTP client.\n" }, { "name": "smtp_nested_header_checks (empty)", "content": "Restricted nestedheaderchecks(5) tables for the Postfix SMTP client.\n" }, { "name": "smtp_body_checks (empty)", "content": "Restricted bodychecks(5) tables for the Postfix SMTP client.\n\nAvailable in Postfix version 2.6 and later:\n" }, { "name": "tcp_windowsize (0)", "content": "An optional workaround for routers that break TCP window scaling.\n\nAvailable in Postfix version 2.8 and later:\n" }, { "name": "smtp_dns_resolver_options (empty)", "content": "DNS Resolver options for the Postfix SMTP client.\n\nAvailable in Postfix version 2.9 - 3.6:\n" }, { "name": "smtp_per_record_deadline (no)", "content": "Change the behavior of the smtp*timeout time limits, from a time limit per read or\nwrite system call, to a time limit to send or receive a complete record (an SMTP com‐\nmand line, SMTP response line, SMTP message content line, or TLS protocol message).\n\nAvailable in Postfix version 2.9 and later:\n" }, { "name": "smtp_send_dummy_mail_auth (no)", "content": "Whether or not to append the \"AUTH=<>\" option to the MAIL FROM command in SASL-authen‐\nticated SMTP sessions.\n\nAvailable in Postfix version 2.11 and later:\n" }, { "name": "smtp_dns_support_level (empty)", "content": "Level of DNS support in the Postfix SMTP client.\n\nAvailable in Postfix version 3.0 and later:\n" }, { "name": "smtp_delivery_status_filter ($default_delivery_status_filter)", "content": "Optional filter for the smtp(8) delivery agent to change the delivery status code or\nexplanatory text of successful or unsuccessful deliveries.\n" }, { "name": "smtp_dns_reply_filter (empty)", "content": "Optional filter for Postfix SMTP client DNS lookup results.\n\nAvailable in Postfix version 3.3 and later:\n" }, { "name": "smtp_balance_inet_protocols (yes)", "content": "When a remote destination resolves to a combination of IPv4 and IPv6 addresses, ensure\nthat the Postfix SMTP client can try both address types before it runs into the\nsmtpmxaddresslimit.\n\nAvailable in Postfix 3.5 and later:\n" }, { "name": "info_log_address_format (external)", "content": "The email address form that will be used in non-debug logging (info, warning, etc.).\n\nAvailable in Postfix 3.6 and later:\n" }, { "name": "dnssec_probe (ns:.)", "content": "The DNS query type (default: \"ns\") and DNS query name (default: \".\") that Postfix may\nuse to determine whether DNSSEC validation is available.\n" }, { "name": "known_tcp_ports (lmtp=24, smtp=25, smtps=submissions=465, submission=587)", "content": "Optional setting that avoids lookups in the services(5) database.\n\nAvailable in Postfix version 3.7 and later:\n" }, { "name": "smtp_per_request_deadline (no)", "content": "Change the behavior of the smtp*timeout time limits, from a time limit per plaintext\nor TLS read or write call, to a combined time limit for sending a complete SMTP re‐\nquest and for receiving a complete SMTP response.\n" }, { "name": "smtp_min_data_rate (500)", "content": "The minimum plaintext data transfer rate in bytes/second for DATA requests, when dead‐\nlines are enabled with smtpperrequestdeadline.\n" }, { "name": "header_from_format (standard)", "content": "The format of the Postfix-generated From: header.\n\nAvailable in Postfix version 3.8 and later:\n" }, { "name": "use_srv_lookup (empty)", "content": "Enables discovery for the specified service(s) using DNS SRV records.\n" }, { "name": "ignore_srv_lookup_error (no)", "content": "When SRV record lookup fails, fall back to MX or IP address lookup as if SRV record\nlookup was not enabled.\n" }, { "name": "allow_srv_lookup_fallback (no)", "content": "When SRV record lookup fails or no SRV record exists, fall back to MX or IP address\nlookup as if SRV record lookup was not enabled.\n" } ] }, "MIME PROCESSING CONTROLS": { "content": "Available in Postfix version 2.0 and later:\n", "subsections": [ { "name": "disable_mime_output_conversion (no)", "content": "Disable the conversion of 8BITMIME format to 7BIT format.\n" }, { "name": "mime_boundary_length_limit (2048)", "content": "The maximal length of MIME multipart boundary strings.\n" }, { "name": "mime_nesting_limit (100)", "content": "The maximal recursion level that the MIME processor will handle.\n" } ] }, "EXTERNAL CONTENT INSPECTION CONTROLS": { "content": "Available in Postfix version 2.1 and later:\n", "subsections": [ { "name": "smtp_send_xforward_command (no)", "content": "Send the non-standard XFORWARD command when the Postfix SMTP server EHLO response an‐\nnounces XFORWARD support.\n" } ] }, "SASL AUTHENTICATION CONTROLS": { "content": "", "subsections": [ { "name": "smtp_sasl_auth_enable (no)", "content": "Enable SASL authentication in the Postfix SMTP client.\n" }, { "name": "smtp_sasl_password_maps (empty)", "content": "Optional Postfix SMTP client lookup tables with one username:password entry per\nsender, remote hostname or next-hop domain.\n" }, { "name": "smtp_sasl_security_options (noplaintext, noanonymous)", "content": "Postfix SMTP client SASL security options; as of Postfix 2.3 the list of available\nfeatures depends on the SASL client implementation that is selected with\nsmtpsasltype.\n\nAvailable in Postfix version 2.2 and later:\n" }, { "name": "smtp_sasl_mechanism_filter (empty)", "content": "If non-empty, a Postfix SMTP client filter for the remote SMTP server's list of of‐\nfered SASL mechanisms.\n\nAvailable in Postfix version 2.3 and later:\n" }, { "name": "smtp_sender_dependent_authentication (no)", "content": "Enable sender-dependent authentication in the Postfix SMTP client; this is available\nonly with SASL authentication, and disables SMTP connection caching to ensure that\nmail from different senders will use the appropriate credentials.\n" }, { "name": "smtp_sasl_path (empty)", "content": "Implementation-specific information that the Postfix SMTP client passes through to the\nSASL plug-in implementation that is selected with smtpsasltype.\n" }, { "name": "smtp_sasl_type (cyrus)", "content": "The SASL plug-in type that the Postfix SMTP client should use for authentication.\n\nAvailable in Postfix version 2.5 and later:\n" }, { "name": "smtp_sasl_auth_cache_name (empty)", "content": "An optional table to prevent repeated SASL authentication failures with the same re‐\nmote SMTP server hostname, username and password.\n" }, { "name": "smtp_sasl_auth_cache_time (90d)", "content": "The maximal age of an smtpsaslauthcachename entry before it is removed.\n" }, { "name": "smtp_sasl_auth_soft_bounce (yes)", "content": "When a remote SMTP server rejects a SASL authentication request with a 535 reply code,\ndefer mail delivery instead of returning mail as undeliverable.\n\nAvailable in Postfix version 2.9 and later:\n" }, { "name": "smtp_send_dummy_mail_auth (no)", "content": "Whether or not to append the \"AUTH=<>\" option to the MAIL FROM command in SASL-authen‐\nticated SMTP sessions.\n" } ] }, "STARTTLS SUPPORT CONTROLS": { "content": "Detailed information about STARTTLS configuration may be found in the TLSREADME document.\n", "subsections": [ { "name": "smtp_tls_security_level (empty)", "content": "The default SMTP TLS security level for the Postfix SMTP client.\n" }, { "name": "smtp_sasl_tls_security_options ($smtp_sasl_security_options)", "content": "The SASL authentication security options that the Postfix SMTP client uses for TLS en‐\ncrypted SMTP sessions.\n" }, { "name": "smtp_starttls_timeout (300s)", "content": "Time limit for Postfix SMTP client write and read operations during TLS startup and\nshutdown handshake procedures.\n" }, { "name": "smtp_tls_CAfile (empty)", "content": "A file containing CA certificates of root CAs trusted to sign either remote SMTP\nserver certificates or intermediate CA certificates.\n" }, { "name": "smtp_tls_CApath (empty)", "content": "Directory with PEM format Certification Authority certificates that the Postfix SMTP\nclient uses to verify a remote SMTP server certificate.\n" }, { "name": "smtp_tls_cert_file (empty)", "content": "File with the Postfix SMTP client RSA certificate in PEM format.\n" }, { "name": "smtp_tls_mandatory_ciphers (medium)", "content": "The minimum TLS cipher grade that the Postfix SMTP client will use with mandatory TLS\nencryption.\n" }, { "name": "smtp_tls_exclude_ciphers (empty)", "content": "List of ciphers or cipher types to exclude from the Postfix SMTP client cipher list at\nall TLS security levels.\n" }, { "name": "smtp_tls_mandatory_exclude_ciphers (empty)", "content": "Additional list of ciphers or cipher types to exclude from the Postfix SMTP client ci‐\npher list at mandatory TLS security levels.\n" }, { "name": "smtp_tls_dcert_file (empty)", "content": "File with the Postfix SMTP client DSA certificate in PEM format.\n" }, { "name": "smtp_tls_dkey_file ($smtp_tls_dcert_file)", "content": "File with the Postfix SMTP client DSA private key in PEM format.\n" }, { "name": "smtp_tls_key_file ($smtp_tls_cert_file)", "content": "File with the Postfix SMTP client RSA private key in PEM format.\n" }, { "name": "smtp_tls_loglevel (0)", "content": "Enable additional Postfix SMTP client logging of TLS activity.\n" }, { "name": "smtp_tls_note_starttls_offer (no)", "content": "Log the hostname of a remote SMTP server that offers STARTTLS, when TLS is not already\nenabled for that server.\n" }, { "name": "smtp_tls_policy_maps (empty)", "content": "Optional lookup tables with the Postfix SMTP client TLS security policy by next-hop\ndestination; when a non-empty value is specified, this overrides the obsolete\nsmtptlspersite parameter.\n" }, { "name": "smtp_tls_mandatory_protocols (see 'postconf -d' output)", "content": "TLS protocols that the Postfix SMTP client will use with mandatory TLS encryption.\n" }, { "name": "smtp_tls_scert_verifydepth (9)", "content": "The verification depth for remote SMTP server certificates.\n" }, { "name": "smtp_tls_secure_cert_match (nexthop, dot-nexthop)", "content": "How the Postfix SMTP client verifies the server certificate peername for the \"secure\"\nTLS security level.\n" }, { "name": "smtp_tls_session_cache_database (empty)", "content": "Name of the file containing the optional Postfix SMTP client TLS session cache.\n" }, { "name": "smtp_tls_session_cache_timeout (3600s)", "content": "The expiration time of Postfix SMTP client TLS session cache information.\n" }, { "name": "smtp_tls_verify_cert_match (hostname)", "content": "How the Postfix SMTP client verifies the server certificate peername for the \"verify\"\nTLS security level.\n" }, { "name": "tls_daemon_random_bytes (32)", "content": "The number of pseudo-random bytes that an smtp(8) or smtpd(8) process requests from\nthe tlsmgr(8) server in order to seed its internal pseudo random number generator\n(PRNG).\n" }, { "name": "tls_high_cipherlist (see 'postconf -d' output)", "content": "The OpenSSL cipherlist for \"high\" grade ciphers.\n" }, { "name": "tls_medium_cipherlist (see 'postconf -d' output)", "content": "The OpenSSL cipherlist for \"medium\" or higher grade ciphers.\n" }, { "name": "tls_null_cipherlist (eNULL:!aNULL)", "content": "The OpenSSL cipherlist for \"NULL\" grade ciphers that provide authentication without\nencryption.\n\nAvailable in in Postfix version 2.3..3.7:\n" }, { "name": "tls_low_cipherlist (see 'postconf -d' output)", "content": "The OpenSSL cipherlist for \"low\" or higher grade ciphers.\n" }, { "name": "tls_export_cipherlist (see 'postconf -d' output)", "content": "The OpenSSL cipherlist for \"export\" or higher grade ciphers.\n\nAvailable in Postfix version 2.4 and later:\n" }, { "name": "smtp_sasl_tls_verified_security_options ($smtp_sasl_tls_security_options)", "content": "The SASL authentication security options that the Postfix SMTP client uses for TLS en‐\ncrypted SMTP sessions with a verified server certificate.\n\nAvailable in Postfix version 2.5 and later:\n" }, { "name": "smtp_tls_fingerprint_cert_match (empty)", "content": "List of acceptable remote SMTP server certificate fingerprints for the \"fingerprint\"\nTLS security level (smtptlssecuritylevel = fingerprint).\n" }, { "name": "smtp_tls_fingerprint_digest (see 'postconf -d' output)", "content": "The message digest algorithm used to construct remote SMTP server certificate finger‐\nprints.\n\nAvailable in Postfix version 2.6 and later:\n" }, { "name": "smtp_tls_protocols (see postconf -d output)", "content": "TLS protocols that the Postfix SMTP client will use with opportunistic TLS encryption.\n" }, { "name": "smtp_tls_ciphers (medium)", "content": "The minimum TLS cipher grade that the Postfix SMTP client will use with opportunistic\nTLS encryption.\n" }, { "name": "smtp_tls_eccert_file (empty)", "content": "File with the Postfix SMTP client ECDSA certificate in PEM format.\n" }, { "name": "smtp_tls_eckey_file ($smtp_tls_eccert_file)", "content": "File with the Postfix SMTP client ECDSA private key in PEM format.\n\nAvailable in Postfix version 2.7 and later:\n" }, { "name": "smtp_tls_block_early_mail_reply (no)", "content": "Try to detect a mail hijacking attack based on a TLS protocol vulnerability\n(CVE-2009-3555), where an attacker prepends malicious HELO, MAIL, RCPT, DATA commands\nto a Postfix SMTP client TLS session.\n\nAvailable in Postfix version 2.8 and later:\n" }, { "name": "tls_disable_workarounds (see 'postconf -d' output)", "content": "List or bit-mask of OpenSSL bug work-arounds to disable.\n\nAvailable in Postfix version 2.11-3.1:\n" }, { "name": "tls_dane_digest_agility (on)", "content": "Configure RFC7671 DANE TLSA digest algorithm agility.\n" }, { "name": "tls_dane_trust_anchor_digest_enable (yes)", "content": "Enable support for RFC 6698 (DANE TLSA) DNS records that contain digests of trust-an‐\nchors with certificate usage \"2\".\n\nAvailable in Postfix version 2.11 and later:\n" }, { "name": "smtp_tls_trust_anchor_file (empty)", "content": "Zero or more PEM-format files with trust-anchor certificates and/or public keys.\n" }, { "name": "smtp_tls_force_insecure_host_tlsa_lookup (no)", "content": "Lookup the associated DANE TLSA RRset even when a hostname is not an alias and its ad‐\ndress records lie in an unsigned zone.\n" }, { "name": "tlsmgr_service_name (tlsmgr)", "content": "The name of the tlsmgr(8) service entry in master.cf.\n\nAvailable in Postfix version 3.0 and later:\n" }, { "name": "smtp_tls_wrappermode (no)", "content": "Request that the Postfix SMTP client connects using the SUBMISSIONS/SMTPS protocol in‐\nstead of using the STARTTLS command.\n\nAvailable in Postfix version 3.1 and later:\n" }, { "name": "smtp_tls_dane_insecure_mx_policy (see 'postconf -d' output)", "content": "The TLS policy for MX hosts with \"secure\" TLSA records when the nexthop destination\nsecurity level is dane, but the MX record was found via an \"insecure\" MX lookup.\n\nAvailable in Postfix version 3.2 and later:\n" }, { "name": "tls_eecdh_auto_curves (see 'postconf -d' output)", "content": "The prioritized list of elliptic curves supported by the Postfix SMTP client and\nserver.\n\nAvailable in Postfix version 3.4 and later:\n" }, { "name": "smtp_tls_connection_reuse (no)", "content": "Try to make multiple deliveries per TLS-encrypted connection.\n" }, { "name": "smtp_tls_chain_files (empty)", "content": "List of one or more PEM files, each holding one or more private keys directly followed\nby a corresponding certificate chain.\n" }, { "name": "smtp_tls_servername (empty)", "content": "Optional name to send to the remote SMTP server in the TLS Server Name Indication\n(SNI) extension.\n\nAvailable in Postfix 3.5, 3.4.6, 3.3.5, 3.2.10, 3.1.13 and later:\n" }, { "name": "tls_fast_shutdown_enable (yes)", "content": "A workaround for implementations that hang Postfix while shutting down a TLS session,\nuntil Postfix times out.\n\nAvailable in Postfix version 3.8 and later:\n" }, { "name": "tls_ffdhe_auto_groups (see 'postconf -d' output)", "content": "The prioritized list of finite-field Diffie-Hellman ephemeral (FFDHE) key exchange\ngroups supported by the Postfix SMTP client and server.\n\nAvailable in Postfix 3.9, 3.8.1, 3.7.6, 3.6.10, 3.5.20 and later:\n" }, { "name": "tls_config_file (default)", "content": "Optional configuration file with baseline OpenSSL settings.\n" }, { "name": "tls_config_name (empty)", "content": "The application name passed by Postfix to OpenSSL library initialization functions.\n" } ] }, "OBSOLETE STARTTLS CONTROLS": { "content": "The following configuration parameters exist for compatibility with Postfix versions before\n2.3. Support for these will be removed in a future release.\n", "subsections": [ { "name": "smtp_use_tls (no)", "content": "Opportunistic mode: use TLS when a remote SMTP server announces STARTTLS support, oth‐\nerwise send the mail in the clear.\n" }, { "name": "smtp_enforce_tls (no)", "content": "Enforcement mode: require that remote SMTP servers use TLS encryption, and never send\nmail in the clear.\n" }, { "name": "smtp_tls_enforce_peername (yes)", "content": "With mandatory TLS encryption, require that the remote SMTP server hostname matches\nthe information in the remote SMTP server certificate.\n" }, { "name": "smtp_tls_per_site (empty)", "content": "Optional lookup tables with the Postfix SMTP client TLS usage policy by next-hop des‐\ntination and by remote SMTP server hostname.\n" }, { "name": "smtp_tls_cipherlist (empty)", "content": "Obsolete Postfix < 2.3 control for the Postfix SMTP client TLS cipher list.\n" } ] }, "RESOURCE AND RATE CONTROLS": { "content": "", "subsections": [ { "name": "smtp_connect_timeout (30s)", "content": "The Postfix SMTP client time limit for completing a TCP connection, or zero (use the\noperating system built-in time limit).\n" }, { "name": "smtp_helo_timeout (300s)", "content": "The Postfix SMTP client time limit for sending the HELO or EHLO command, and for re‐\nceiving the initial remote SMTP server response.\n" }, { "name": "lmtp_lhlo_timeout (300s)", "content": "The Postfix LMTP client time limit for sending the LHLO command, and for receiving the\ninitial remote LMTP server response.\n" }, { "name": "smtp_xforward_timeout (300s)", "content": "The Postfix SMTP client time limit for sending the XFORWARD command, and for receiving\nthe remote SMTP server response.\n" }, { "name": "smtp_mail_timeout (300s)", "content": "The Postfix SMTP client time limit for sending the MAIL FROM command, and for receiv‐\ning the remote SMTP server response.\n" }, { "name": "smtp_rcpt_timeout (300s)", "content": "The Postfix SMTP client time limit for sending the SMTP RCPT TO command, and for re‐\nceiving the remote SMTP server response.\n" }, { "name": "smtp_data_init_timeout (120s)", "content": "The Postfix SMTP client time limit for sending the SMTP DATA command, and for receiv‐\ning the remote SMTP server response.\n" }, { "name": "smtp_data_xfer_timeout (180s)", "content": "The Postfix SMTP client time limit for sending the SMTP message content.\n" }, { "name": "smtp_data_done_timeout (600s)", "content": "The Postfix SMTP client time limit for sending the SMTP \".\", and for receiving the re‐\nmote SMTP server response.\n" }, { "name": "smtp_quit_timeout (300s)", "content": "The Postfix SMTP client time limit for sending the QUIT command, and for receiving the\nremote SMTP server response.\n\nAvailable in Postfix version 2.1 and later:\n" }, { "name": "smtp_mx_address_limit (5)", "content": "The maximal number of MX (mail exchanger) IP addresses that can result from Postfix\nSMTP client mail exchanger lookups, or zero (no limit).\n" }, { "name": "smtp_mx_session_limit (2)", "content": "The maximal number of SMTP sessions per delivery request before the Postfix SMTP\nclient gives up or delivers to a fall-back relay host, or zero (no limit).\n" }, { "name": "smtp_rset_timeout (20s)", "content": "The Postfix SMTP client time limit for sending the RSET command, and for receiving the\nremote SMTP server response.\n\nAvailable in Postfix version 2.2 and earlier:\n" }, { "name": "lmtp_cache_connection (yes)", "content": "Keep Postfix LMTP client connections open for up to $maxidle seconds.\n\nAvailable in Postfix version 2.2 and later:\n" }, { "name": "smtp_connection_cache_destinations (empty)", "content": "Permanently enable SMTP connection caching for the specified destinations.\n" }, { "name": "smtp_connection_cache_on_demand (yes)", "content": "Temporarily enable SMTP connection caching while a destination has a high volume of\nmail in the active queue.\n" }, { "name": "smtp_connection_reuse_time_limit (300s)", "content": "The amount of time during which Postfix will use an SMTP connection repeatedly.\n" }, { "name": "smtp_connection_cache_time_limit (2s)", "content": "When SMTP connection caching is enabled, the amount of time that an unused SMTP client\nsocket is kept open before it is closed.\n\nAvailable in Postfix version 2.3 and later:\n" }, { "name": "connection_cache_protocol_timeout (5s)", "content": "Time limit for connection cache connect, send or receive operations.\n\nAvailable in Postfix version 2.9 - 3.6:\n" }, { "name": "smtp_per_record_deadline (no)", "content": "Change the behavior of the smtp*timeout time limits, from a time limit per read or\nwrite system call, to a time limit to send or receive a complete record (an SMTP com‐\nmand line, SMTP response line, SMTP message content line, or TLS protocol message).\n\nAvailable in Postfix version 2.11 and later:\n" }, { "name": "smtp_connection_reuse_count_limit (0)", "content": "When SMTP connection caching is enabled, the number of times that an SMTP session may\nbe reused before it is closed, or zero (no limit).\n\nAvailable in Postfix version 3.4 and later:\n" }, { "name": "smtp_tls_connection_reuse (no)", "content": "Try to make multiple deliveries per TLS-encrypted connection.\n\nAvailable in Postfix version 3.7 and later:\n" }, { "name": "smtp_per_request_deadline (no)", "content": "Change the behavior of the smtp*timeout time limits, from a time limit per plaintext\nor TLS read or write call, to a combined time limit for sending a complete SMTP re‐\nquest and for receiving a complete SMTP response.\n" }, { "name": "smtp_min_data_rate (500)", "content": "The minimum plaintext data transfer rate in bytes/second for DATA requests, when dead‐\nlines are enabled with smtpperrequestdeadline.\n\nImplemented in the qmgr(8) daemon:\n" }, { "name": "transport_destination_concurrency_limit ($default_destination_concurrency_limit)", "content": "A transport-specific override for the defaultdestinationconcurrencylimit parameter\nvalue, where transport is the master.cf name of the message delivery transport.\n" }, { "name": "transport_destination_recipient_limit ($default_destination_recipient_limit)", "content": "A transport-specific override for the defaultdestinationrecipientlimit parameter\nvalue, where transport is the master.cf name of the message delivery transport.\n" } ] }, "SMTPUTF8 CONTROLS": { "content": "Preliminary SMTPUTF8 support is introduced with Postfix 3.0.\n", "subsections": [ { "name": "smtputf8_enable (yes)", "content": "Enable preliminary SMTPUTF8 support for the protocols described in RFC 6531, RFC 6532,\nand RFC 6533.\n" }, { "name": "smtputf8_autodetect_classes (sendmail, verify)", "content": "Detect that a message requires SMTPUTF8 support for the specified mail origin classes.\n\nAvailable in Postfix version 3.2 and later:\n" }, { "name": "enable_idna2003_compatibility (no)", "content": "Enable 'transitional' compatibility between IDNA2003 and IDNA2008, when converting\nUTF-8 domain names to/from the ASCII form that is used for DNS lookups.\n" } ] }, "TROUBLE SHOOTING CONTROLS": { "content": "", "subsections": [ { "name": "debug_peer_level (2)", "content": "The increment in verbose logging level when a nexthop destination, remote client or\nserver name or network address matches a pattern given with the debugpeerlist para‐\nmeter.\n" }, { "name": "debug_peer_list (empty)", "content": "Optional list of nexthop destination, remote client or server name or network address\npatterns that, if matched, cause the verbose logging level to increase by the amount\nspecified in $debugpeerlevel.\n" }, { "name": "error_notice_recipient (postmaster)", "content": "The recipient of postmaster notifications about mail delivery problems that are caused\nby policy, resource, software or protocol errors.\n" }, { "name": "internal_mail_filter_classes (empty)", "content": "What categories of Postfix-generated mail are subject to before-queue content inspec‐\ntion by nonsmtpdmilters, headerchecks and bodychecks.\n" }, { "name": "notify_classes (resource, software)", "content": "The list of error classes that are reported to the postmaster.\n" } ] }, "MISCELLANEOUS CONTROLS": { "content": "", "subsections": [ { "name": "best_mx_transport (empty)", "content": "Where the Postfix SMTP client should deliver mail when it detects a \"mail loops back\nto myself\" error condition.\n" }, { "name": "config_directory (see 'postconf -d' output)", "content": "The default location of the Postfix main.cf and master.cf configuration files.\n" }, { "name": "daemon_timeout (18000s)", "content": "How much time a Postfix daemon process may take to handle a request before it is ter‐\nminated by a built-in watchdog timer.\n" }, { "name": "delay_logging_resolution_limit (2)", "content": "The maximal number of digits after the decimal point when logging sub-second delay\nvalues.\n" }, { "name": "disable_dns_lookups (no)", "content": "Disable DNS lookups in the Postfix SMTP and LMTP clients.\n" }, { "name": "inet_interfaces (all)", "content": "The local network interface addresses that this mail system receives mail on.\n" }, { "name": "inet_protocols (see 'postconf -d output')", "content": "The Internet protocols Postfix will attempt to use when making or accepting connec‐\ntions.\n" }, { "name": "ipc_timeout (3600s)", "content": "The time limit for sending or receiving information over an internal communication\nchannel.\n" }, { "name": "lmtp_assume_final (no)", "content": "When a remote LMTP server announces no DSN support, assume that the server performs\nfinal delivery, and send \"delivered\" delivery status notifications instead of \"re‐\nlayed\".\n" }, { "name": "lmtp_tcp_port (24)", "content": "The default TCP port that the Postfix LMTP client connects to.\n" }, { "name": "max_idle (100s)", "content": "The maximum amount of time that an idle Postfix daemon process waits for an incoming\nconnection before terminating voluntarily.\n" }, { "name": "max_use (100)", "content": "The maximal number of incoming connections that a Postfix daemon process will service\nbefore terminating voluntarily.\n" }, { "name": "process_id (read-only)", "content": "The process ID of a Postfix command or daemon process.\n" }, { "name": "process_name (read-only)", "content": "The process name of a Postfix command or daemon process.\n" }, { "name": "proxy_interfaces (empty)", "content": "The remote network interface addresses that this mail system receives mail on by way\nof a proxy or network address translation unit.\n" }, { "name": "smtp_address_preference (any)", "content": "The address type (\"ipv6\", \"ipv4\" or \"any\") that the Postfix SMTP client will try\nfirst, when a destination has IPv6 and IPv4 addresses with equal MX preference.\n" }, { "name": "smtp_bind_address (empty)", "content": "An optional numerical network address that the Postfix SMTP client should bind to when\nmaking an IPv4 connection.\n" }, { "name": "smtp_bind_address6 (empty)", "content": "An optional numerical network address that the Postfix SMTP client should bind to when\nmaking an IPv6 connection.\n" }, { "name": "smtp_helo_name ($myhostname)", "content": "The hostname to send in the SMTP HELO or EHLO command.\n" }, { "name": "lmtp_lhlo_name ($myhostname)", "content": "The hostname to send in the LMTP LHLO command.\n" }, { "name": "smtp_host_lookup (dns)", "content": "What mechanisms the Postfix SMTP client uses to look up a host's IP address.\n" }, { "name": "smtp_randomize_addresses (yes)", "content": "Randomize the order of equal-preference MX host addresses.\n" }, { "name": "syslog_facility (mail)", "content": "The syslog facility of Postfix logging.\n" }, { "name": "syslog_name (see 'postconf -d' output)", "content": "A prefix that is prepended to the process name in syslog records, so that, for exam‐\nple, \"smtpd\" becomes \"prefix/smtpd\".\n\nAvailable with Postfix 2.2 and earlier:\n" }, { "name": "fallback_relay (empty)", "content": "Optional list of relay hosts for SMTP destinations that can't be found or that are un‐\nreachable.\n\nAvailable with Postfix 2.3 and later:\n" }, { "name": "smtp_fallback_relay ($fallback_relay)", "content": "Optional list of relay destinations that will be used when an SMTP destination is not\nfound, or when delivery fails due to a non-permanent error.\n\nAvailable with Postfix 3.0 and later:\n" }, { "name": "smtp_address_verify_target (rcpt)", "content": "In the context of email address verification, the SMTP protocol stage that determines\nwhether an email address is deliverable.\n\nAvailable with Postfix 3.1 and later:\n" }, { "name": "lmtp_fallback_relay (empty)", "content": "Optional list of relay hosts for LMTP destinations that can't be found or that are un‐\nreachable.\n\nAvailable with Postfix 3.2 and later:\n" }, { "name": "smtp_tcp_port (smtp)", "content": "The default TCP port that the Postfix SMTP client connects to.\n\nAvailable in Postfix 3.3 and later:\n" }, { "name": "service_name (read-only)", "content": "The master.cf service name of a Postfix daemon process.\n\nAvailable in Postfix 3.7 and later:\n" }, { "name": "smtp_bind_address_enforce (no)", "content": "Defer delivery when the Postfix SMTP client cannot apply the smtpbindaddress or\nsmtpbindaddress6 setting.\n" } ] }, "SEE ALSO": { "content": "generic(5), output address rewriting\nheaderchecks(5), message header content inspection\nbodychecks(5), body parts content inspection\nqmgr(8), queue manager\nbounce(8), delivery status reports\nscache(8), connection cache server\npostconf(5), configuration parameters\nmaster(5), generic daemon options\nmaster(8), process manager\ntlsmgr(8), TLS session and PRNG management\npostlogd(8), Postfix logging\nsyslogd(8), system logging\n", "subsections": [] }, "README FILES": { "content": "Use \"postconf readmedirectory\" or \"postconf htmldirectory\" to locate this information.\nSASLREADME, Postfix SASL howto\nTLSREADME, Postfix STARTTLS howto\n", "subsections": [] }, "LICENSE": { "content": "The Secure Mailer license must be distributed with this software.\n\nAUTHOR(S)\nWietse Venema\nIBM T.J. Watson Research\nP.O. Box 704\nYorktown Heights, NY 10598, USA\n\nWietse Venema\nGoogle, Inc.\n111 8th Avenue\nNew York, NY 10011, USA\n\nCommand pipelining in cooperation with:\nJon Ribbens\nOaktree Internet Solutions Ltd.,\nInternet House,\nCanal Basin,\nCoventry,\nCV1 4LY, United Kingdom.\n\nSASL support originally by:\nTill Franke\nSuSE Rhein/Main AG\n65760 Eschborn, Germany\n\nTLS support originally by:\nLutz Jaenicke\nBTU Cottbus\nAllgemeine Elektrotechnik\nUniversitaetsplatz 3-4\nD-03044 Cottbus, Germany\n\nRevised TLS and SMTP connection cache support by:\nVictor Duchovni\nMorgan Stanley\n\nSMTP(8postfix)", "subsections": [] } }, "summary": "smtp - Postfix SMTP+LMTP client", "flags": [], "examples": [], "see_also": [ { "name": "generic", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/generic/5/json" }, { "name": "headerchecks", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/headerchecks/5/json" }, { "name": "bodychecks", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/bodychecks/5/json" }, { "name": "qmgr", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/qmgr/8/json" }, { "name": "bounce", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/bounce/8/json" }, { "name": "scache", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/scache/8/json" }, { "name": "postconf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/postconf/5/json" }, { "name": "master", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/master/5/json" }, { "name": "master", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/master/8/json" }, { "name": "tlsmgr", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/tlsmgr/8/json" }, { "name": "postlogd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/postlogd/8/json" }, { "name": "syslogd", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/syslogd/8/json" } ] }