Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 67 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       lmtp [generic Postfix daemon options]


       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
       problem reports are sent to the bounce(8) or defer(8) dae­
       mon 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:

              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


       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.


       RFC 821 (SMTP protocol)
       RFC 1651 (SMTP service extensions)
       RFC 1652 (8bit-MIME transport)



       The following main.cf parameters are  especially  relevant
       to  this  program. See the Postfix main.cf file for syntax
       details and for default values.  Use  the  postfix  reload
       command after a configuration change.


              Verbose  logging  level  increment  for  hosts that
              match a pattern in the debug_peer_list parameter.

              List of domain or network patterns. When  a  remote
              host  matches  a pattern, increase the verbose log­
              ging  level  by  the  amount   specified   in   the
              debug_peer_level parameter.

              Recipient    of   protocol/policy/resource/software
              error notices.

              When this parameter includes  the  protocol  class,
              send  mail  to  the  postmaster with transcripts of
              LMTP sessions with protocol errors.

              Do not wait for the server response  after  sending

              The  TCP  port to be used when connecting to a LMTP
              server.  Used as backup if the lmtp service is  not
              found in services(4).

Authentication controls

              Enable  per-session  authentication as per RFC 2554
              (SASL).  By default, Postfix is built without  SASL

              Lookup tables with per-host or domain name:password
              entries.  No entry for a host means no  attempt  to

              Zero or more of the following.


Resource controls

              Should  we cache the connection to the LMTP server?
              The effectiveness of  cached  connections  will  be
              determined  by  the  number of LMTP servers in use,
              and the concurrency limit specified  for  the  LMTP
              client.  Cached connections are closed under any of
              the following conditions:

              ·      The LMTP client idle time limit is  reached.
                     This  limit  is  specified  with the Postfix
                     max_idle configuration parameter.

              ·      A delivery  request  specifies  a  different
                     destination than the one currently cached.

              ·      The  per-process  limit  on  the  number  of
                     delivery requests is reached.  This limit is
                     specified  with the Postfix max_use configu­
                     ration parameter.

              ·      Upon the onset of another delivery  request,
                     the  LMTP server associated with the current
                     session does not respond to  the  RSET  com­

              Limit the number of parallel deliveries to the same
              destination  via  this  mail  delivery   transport.
              transport  is  the name of the service as specified
              in the master.cf file.  The default limit is  taken
              from    the   default_destination_concurrency_limit

              Limit the number of recipients per message delivery
              via  this mail delivery transport. transport is the
              name of the service as specified in  the  master.cf
              file.    The   default  limit  is  taken  from  the
              default_destination_recipient_limit parameter.

              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

              Timeout  for  sending  the  LHLO  command,  and for
              receiving the server response.

              Timeout for sending the MAIL FROM command, and  for
              receiving the server response.

              Timeout  for  sending  the RCPT TO command, and for
              receiving the server response.

              Timeout for  sending  the  DATA  command,  and  for
              receiving the server response.

              Timeout for sending the message content.

              Timeout  for  sending  the  "."  command,  and  for
              receiving the server response. When no response  is
              received,  a warning is logged that the mail may be
              delivered multiple times.

              Timeout for  sending  the  RSET  command,  and  for
              receiving the server response.

              Timeout  for  sending  the  QUIT  command,  and for
              receiving the server response.


       bounce(8) non-delivery status reports
       local(8) local mail delivery
       master(8) process manager
       qmgr(8) queue manager
       services(4) Internet services and aliases
       spawn(8) auxiliary command spawner
       syslogd(8) system logging


       The Secure Mailer license must be  distributed  with  this


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


More information about the site can be found in the FAQ



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds