imip-agent

docs/wiki/MailboxIntegration

1355:6975cdaac4a4
2017-10-20 Paul Boddie Simplify the interface of the rule periods computation function.
     1 = Mailbox Integration =     2      3 Use of the imip-agent software should not affect the solutions chosen to store     4 mail received by your mail system. However, the software does support direct     5 connections to mail storage solutions employing the LMTP protocol. See the     6 [[../MailIntegration/LMTP|LMTP guide]] for more information.     7      8 It can, however, be useful to see how delivery to various kinds of mailboxes     9 and mail storage is done, in case you have not already decided on a particular    10 solution. Tested solutions are as follows:    11     12 {{{#!table    13 '''Solution''' || '''Details'''    14 ==    15 [[http://www.cyrusimap.org/|Cyrus]] is a mail storage system that exposes    16 mailboxes using the [[http://tools.ietf.org/html/rfc3501|IMAP]] protocol    17 ||    18 The Cyrus documentation provides a guide on integrating Cyrus with    19 [[http://www.cyrusimap.org/docs/cyrus-imapd/2.5.6/install-configure.php#mta|MTAs]].    20 ==    21 [[http://dovecot.org/|Dovecot]] is a mail server that supports IMAP and    22 [[http://tools.ietf.org/html/rfc1939|POP3]]. It can be configured to serve    23 mail stored in traditional mailbox formats    24 ||    25 The Dovecot documentation provides guides for integrating Dovecot with    26 [[http://wiki2.dovecot.org/LMTP/Exim|Exim]] and with    27 [[http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP|Postfix]].    28 ==    29 Traditional Unix mailboxes for local system users    30 ||    31 If routing is defined for local users and if    32 [[../MailIntegration/LocalSMTP|local SMTP]] is employed, no other mail storage    33 solution is required.    34 }}}    35     36 With the traditional Unix mailbox approach, no further configuration should be    37 necessary because Exim and Postfix support delivery to such mailboxes amongst    38 their normal configuration rules. The rest of this document describes the    39 integration of these mail transport agents with other mail storage solutions    40 using LMTP.    41     42 == Exim ==    43     44 Example configuration files for Exim are distributed in `conf/exim/lmtp`:    45     46 {{{#!table    47 '''File''' || '''Purpose'''    48 ==    49 `30_exim4-config_cyrus_lmtp`    50 || Delivers messages to Cyrus via LMTP    51 ==    52 `30_exim4-config_dovecot_lmtp`    53 || Delivers messages to Dovecot via LMTP    54 }}}    55     56 On Debian systems, these files would be copied into the `/etc/exim4/conf.d/transport`    57 directory.    58     59 The mailbox integration for local system users is also found in the    60 `conf/exim/lmtp` directory:    61     62 {{{#!table    63 '''File''' || '''Purpose'''    64 ==    65 `890_exim4-config_cyrus_lmtp_local_system`    66 || Routes messages for local system users to Cyrus    67 ==    68 `890_exim4-config_dovecot_lmtp_local_system`    69 || Routes messages for local system users to Dovecot    70 }}}    71     72 Meanwhile, both the `conf/exim/ldap` and `conf/exim/simple` directories    73 provide the following files. The appropriate file for the chosen configuration    74 should be used:    75     76 {{{#!table    77 '''File''' || '''Purpose'''    78 ==    79 `890_exim4-config_cyrus_lmtp_local_lmtp`    80 || Routes messages for local virtual users to Cyrus    81 ==    82 `890_exim4-config_dovecot_lmtp_local_lmtp`    83 || Routes messages for local virtual users to Dovecot    84 }}}    85     86 On Debian systems, these files would be copied into the `/etc/exim4/conf.d/router`    87 directory. Depending on whether system user identities are to be employed for mail    88 or whether genuine virtual identities (not connected to the system) are to be    89 employed, one type (`local_system` or `local_lmtp`) of these files should be    90 selected.    91     92 == Postfix ==    93     94 Example configuration files for Postfix are distributed in `conf/postfix/lmtp`:    95     96 {{{#!table    97 '''File''' || '''Purpose'''    98 ==    99 `lmtp_generic`   100 || Configures LMTP delivery for local recipients (for installation into   101 .. `/etc/postfix`)   102 ==   103 `master.cf.items`   104 || Enables LMTP delivery for local recipients   105 ==   106 `transport.items`   107 || Defines LMTP delivery methods for local recipients   108 }}}   109    110 These files provide example definitions for the `master.cf` and `transport`   111 files that typically reside under `/etc/postfix`. Their contents can be   112 merged with those files as appropriate.   113    114 == Permissions ==   115    116 Note that remarks about permissions management in the   117 [[../MailIntegration/LMTP|LMTP guide]], concerning communication with mail   118 storage systems such as Cyrus, also apply when getting MTAs such as Postfix   119 to communicate with those systems. Consequently, it may be necessary to add   120 the dedicated MTA system user to a specially-created `lmtp` group. For   121 example:   122    123 {{{   124 adduser postfix lmtp   125 }}}   126    127 See the [[../SystemUsers|system users guide]] for more information on the `lmtp`   128 group.