1 = LMTP Delivery = 2 3 When imip-agent is configured to use LMTP, it connects directly to 4 [[../../MailboxIntegration|mail storage solutions]]. By using LMTP from the 5 agent software, the issue of configuring the mail system to integrate with 6 such solutions is avoided, but then those solutions must expose their LMTP 7 interface appropriately. 8 9 {{{#!graphviz 10 //format=svg 11 //transform=notugly 12 digraph lmtp { 13 node [shape=box,fontsize="13.0",fontname="Helvetica",tooltip="LMTP delivery"]; 14 edge [tooltip="LMTP delivery"]; 15 rankdir=LR; 16 17 mail [label="Incoming mail",shape=folder,style=filled,fillcolor=cyan]; 18 19 subgraph { 20 rank=same; 21 personrouter [label="Person router"]; 22 recipients [label="Recipient database",shape=folder]; 23 } 24 25 subgraph { 26 rank=same; 27 personhandler [label="Person handler",style=filled,fillcolor=gold]; 28 } 29 30 mailbox [label="Mailboxes\n(Cyrus, Dovecot, ...)",tooltip="Mailboxes"]; 31 32 mail -> personrouter -> personhandler -> mailbox; 33 34 recipients -> personrouter; 35 } 36 }}} 37 38 Although this topic is largely beyond the scope of this documentation, 39 systems such as Cyrus and Dovecot can be configured to provide a Unix domain 40 socket offering support for LMTP connections. 41 42 == Cyrus == 43 44 For Cyrus on Debian, the following bug report is pertinent: 45 46 * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494746 47 48 A permanent change in permissions on the Cyrus LMTP socket may be required to 49 make delivery available to the `lmtp` group: 50 51 {{{ 52 dpkg-statoverride --force --update --add cyrus lmtp 750 /var/run/cyrus/socket 53 }}} 54 55 See the [[../../SystemUsers|system users]] documentation for a discussion of 56 users and groups.