1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/wiki/MailIntegration Mon Oct 26 13:49:51 2015 +0100
1.3 @@ -0,0 +1,39 @@
1.4 += E-Mail Integration =
1.5 +
1.6 +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.
1.7 +
1.8 +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.
1.9 +
1.10 +== MTAs ==
1.11 +
1.12 +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.
1.13 +
1.14 +{{{#!table
1.15 +|| '''Identifying Recipients''' || '''Integrating imip-agent''' || '''Notes'''
1.16 +==
1.17 +'''Exim'''
1.18 +|| Routers identify recipients of mail that shall be handled by imip-agent
1.19 +|| Transports invoke imip-agent programs
1.20 +|| Exim is widely deployed as the default MTA for Debian. Consequently, it is desirable to support this software in imip-agent.
1.21 +==
1.22 +'''Postfix'''
1.23 +|| Virtual aliases identify recipients of mail that shall be handled by imip-agent
1.24 +|| Transports invoke imip-agent programs
1.25 +|| Postfix is also widely deployed and is sometimes preferred by administrators.
1.26 +}}}
1.27 +
1.28 +== Identification of Recipients ==
1.29 +
1.30 +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:
1.31 +
1.32 +{{{#!table
1.33 +'''Identification Mechanisms''' || '''Tested with...'''
1.34 +==
1.35 +LDAP || Exim, Postfix
1.36 +==
1.37 +Simple (list-based identification) || Exim, Postfix
1.38 +}}}
1.39 +
1.40 +== Delivery ==
1.41 +
1.42 +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.