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