paul@933 | 1 | = E-Mail Integration = |
paul@933 | 2 | |
paul@934 | 3 | To act as a part of an e-mail system, imip-agent provides a number of programs |
paul@934 | 4 | that may be invoked by mail transfer agents (MTAs) upon sending or receiving |
paul@934 | 5 | messages. In order to uphold portability and to minimise configuration issues, |
paul@934 | 6 | these programs need only be registered as simple mail handlers or transports, |
paul@934 | 7 | thus potentially supporting a wide range of MTAs. |
paul@933 | 8 | |
paul@934 | 9 | Once imip-agent has processed a message, it may then deliver it to its |
paul@934 | 10 | intended recipient. The mail storage systems that may receive messages from |
paul@934 | 11 | imip-agent need only support the delivery mechanisms used by imip-agent. |
paul@934 | 12 | Otherwise, few constraints should be imposed by each kind of system on the |
paul@934 | 13 | other. |
paul@933 | 14 | |
paul@933 | 15 | == MTAs == |
paul@933 | 16 | |
paul@934 | 17 | Currently, imip-agent supports [[http://exim.org/|Exim]] and |
paul@934 | 18 | [[http://www.postfix.org/|Postfix]], although this support should be readily |
paul@934 | 19 | broadened, and offers configuration resources for these supported systems so |
paul@934 | 20 | as to allow imip-agent to be deployed within existing mail-sending and |
paul@934 | 21 | delivery infrastructures. |
paul@933 | 22 | |
paul@933 | 23 | {{{#!table |
paul@933 | 24 | || '''Identifying Recipients''' || '''Integrating imip-agent''' || '''Notes''' |
paul@933 | 25 | == |
paul@933 | 26 | '''Exim''' |
paul@933 | 27 | || Routers identify recipients of mail that shall be handled by imip-agent |
paul@933 | 28 | || Transports invoke imip-agent programs |
paul@934 | 29 | || Exim is widely deployed as the default MTA for Debian. Consequently, it is |
paul@949 | 30 | .. desirable to support this software in imip-agent. |
paul@933 | 31 | == |
paul@933 | 32 | '''Postfix''' |
paul@934 | 33 | || Virtual aliases identify recipients of mail that shall be handled by |
paul@934 | 34 | .. imip-agent |
paul@933 | 35 | || Transports invoke imip-agent programs |
paul@933 | 36 | || Postfix is also widely deployed and is sometimes preferred by administrators. |
paul@933 | 37 | }}} |
paul@933 | 38 | |
paul@933 | 39 | == Identification of Recipients == |
paul@933 | 40 | |
paul@934 | 41 | In principle, any mechanism supported by the MTA can be used to identify |
paul@934 | 42 | recipients; imip-agent does not employ identification mechanisms of its own. |
paul@934 | 43 | Thus, the task of identifying recipients is one of MTA configuration, with the |
paul@934 | 44 | following mechanisms tested: |
paul@933 | 45 | |
paul@933 | 46 | {{{#!table |
paul@933 | 47 | '''Identification Mechanisms''' || '''Tested with...''' |
paul@933 | 48 | == |
paul@933 | 49 | LDAP || Exim, Postfix |
paul@933 | 50 | == |
paul@933 | 51 | Simple (list-based identification) || Exim, Postfix |
paul@933 | 52 | }}} |
paul@933 | 53 | |
paul@933 | 54 | == Delivery == |
paul@933 | 55 | |
paul@934 | 56 | To deliver messages to their ultimate recipients after having processed them, |
paul@934 | 57 | imip-agent currently employs either local SMTP connections or |
paul@934 | 58 | [[https://tools.ietf.org/html/rfc2033|LMTP]]. There is nothing in principle |
paul@934 | 59 | preventing imip-agent from also supporting other common delivery mechanisms, |
paul@934 | 60 | however. Currently, Cyrus-IMAP and Dovecot have both been tested with |
paul@934 | 61 | imip-agent, along with delivery to local system users. |