1.1 --- a/docs/wiki/MailIntegration Fri Oct 30 00:30:52 2015 +0100
1.2 +++ b/docs/wiki/MailIntegration Fri Oct 30 00:32:38 2015 +0100
1.3 @@ -51,6 +51,21 @@
1.4 [[/Simple|Simple (list-based identification)]] || Exim, Postfix
1.5 }}}
1.6
1.7 +=== The Calendar System Address ===
1.8 +
1.9 +Since imip-agent may send messages on behalf of calendar users, the address
1.10 +it uses to do so must be recognised by the MTA. This may be done by adding
1.11 +an entry to the `/etc/aliases` file such as the one defined in the
1.12 +`conf/aliases.example` file:
1.13 +
1.14 +{{{
1.15 +calendar: root
1.16 +}}}
1.17 +
1.18 +More suitable routing can be defined as desired. See the `MESSAGE_SENDER`
1.19 +setting defined in the `config.py` file described in the
1.20 +[[../Configuration|configuration guide]].
1.21 +
1.22 == Invoking the Agent Programs ==
1.23
1.24 Regardless of identification or delivery mechanisms, the imip-agent software
2.1 --- a/docs/wiki/MailIntegration--LDAP Fri Oct 30 00:30:52 2015 +0100
2.2 +++ b/docs/wiki/MailIntegration--LDAP Fri Oct 30 00:32:38 2015 +0100
2.3 @@ -27,6 +27,9 @@
2.4 `020_exim4-config_ldap_resources`
2.5 ==
2.6 `020_exim4-config_ldap_people_outgoing_recipients`
2.7 +==
2.8 +`020_exim4-config_ldap_people_local`
2.9 +|| Defines routing for local recipients for delivery to local mailboxes
2.10 }}}
2.11
2.12 These files can be incorporated into the Exim configuration. On Debian
2.13 @@ -62,14 +65,17 @@
2.14 {{{#!table
2.15 '''RFC''' || '''Relevance'''
2.16 ==
2.17 -[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
2.18 -|| Defines the `mail` attribute
2.19 +[[http://tools.ietf.org/html/rfc2307|RFC 2307]]
2.20 +|| Defines the `posixAccount` object class
2.21 +==
2.22 +[[https://tools.ietf.org/html/rfc2739|RFC 2739]]
2.23 +|| Defines the `calEntry` object class supporting `calFBURL`
2.24 ==
2.25 [[http://tools.ietf.org/html/rfc2798|RFC 2798]]
2.26 || Defines the `inetOrgPerson` object class
2.27 ==
2.28 -[[https://tools.ietf.org/html/rfc2739|RFC 2739]]
2.29 -|| Defines the `calEntry` object class supporting `calFBURL`
2.30 +[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
2.31 +|| Defines the `mail` attribute
2.32 }}}
2.33
2.34 An additional draft RFC describes the `mailRecipient` object class:
3.1 --- a/docs/wiki/MailIntegration--Simple Fri Oct 30 00:30:52 2015 +0100
3.2 +++ b/docs/wiki/MailIntegration--Simple Fri Oct 30 00:32:38 2015 +0100
3.3 @@ -24,6 +24,9 @@
3.4 ==
3.5 `020_exim4-config_people_outgoing_recipients`
3.6 ==
3.7 +`020_exim4-config_people_local`
3.8 +|| Defines routing for local recipients for delivery to local mailboxes
3.9 +==
3.10 `virtual_people`
3.11 ||<rowspan="3"> Defines recipient identities belonging to known domains
3.12 ==
4.1 --- a/docs/wiki/MailboxIntegration Fri Oct 30 00:30:52 2015 +0100
4.2 +++ b/docs/wiki/MailboxIntegration Fri Oct 30 00:32:38 2015 +0100
4.3 @@ -1,3 +1,4 @@
4.4 += Mailbox Integration =
4.5 = Mailbox Integration =
4.6
4.7 Use of the imip-agent software should not affect the solutions chosen to store
4.8 @@ -7,32 +8,35 @@
4.9
4.10 It can, however, be useful to see how delivery to various kinds of mailboxes
4.11 and mail storage is done, in case you have not already decided on a particular
4.12 -solution.
4.13 -
4.14 -== Cyrus ==
4.15 +solution. Tested solutions are as follows:
4.16
4.17 -[[http://www.cyrusimap.org/|Cyrus]] is a mail storage system that exposes
4.18 -mailboxes using the [[http://tools.ietf.org/html/rfc3501|IMAP]] protocol.
4.19 + * [[http://www.cyrusimap.org/|Cyrus]] is a mail storage system that exposes
4.20 + mailboxes using the [[http://tools.ietf.org/html/rfc3501|IMAP]] protocol
4.21
4.22 -== Dovecot ==
4.23 -
4.24 -[[http://dovecot.org/|Dovecot]] is a mail server that supports IMAP and
4.25 -[[http://tools.ietf.org/html/rfc1939|POP3]]. It can be configured to serve
4.26 -mail stored in traditional mailbox formats.
4.27 + * [[http://dovecot.org/|Dovecot]] is a mail server that supports IMAP and
4.28 + [[http://tools.ietf.org/html/rfc1939|POP3]]. It can be configured to serve
4.29 + mail stored in traditional mailbox formats
4.30
4.31 The Dovecot documentation provides guides for integrating Dovecot with
4.32 [[http://wiki2.dovecot.org/LMTP/Exim|Exim]] and with
4.33 [[http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP|Postfix]].
4.34
4.35 -Example configuration files for Exim and Dovecot are distributed in
4.36 -`conf/exim/lmtp`:
4.37 +== Exim ==
4.38 +
4.39 +Example configuration files for Exim are distributed in `conf/exim/lmtp`:
4.40
4.41 {{{#!table
4.42 '''File''' || '''Purpose'''
4.43 ==
4.44 +`30_exim4-config_cyrus_lmtp`
4.45 +|| Delivers messages to Cyrus via LMTP
4.46 +==
4.47 `30_exim4-config_dovecot_lmtp`
4.48 || Delivers messages to Dovecot via LMTP
4.49 ==
4.50 +`890_exim4-config_cyrus_lmtp_local`
4.51 +|| Routes messages for local system users to Cyrus
4.52 +==
4.53 `890_exim4-config_dovecot_lmtp_local`
4.54 || Routes messages for local system users to Dovecot
4.55 }}}
4.56 @@ -41,3 +45,21 @@
4.57 `/etc/exim4/conf.d/transport` directory, whereas the latter would be
4.58 copied into the `/etc/exim4/conf.d/router` directory. The latter file is
4.59 appropriate only if system user identities are to be employed for mail.
4.60 +
4.61 +== Postfix ==
4.62 +
4.63 +Example configuration files for Postfix are distributed in `conf/postfix/lmtp`:
4.64 +
4.65 +{{{#!table
4.66 +'''File''' || '''Purpose'''
4.67 +==
4.68 +`main.cf.example`
4.69 +|| Defines mailbox transports for Cyrus and Dovecot
4.70 +==
4.71 +`master.cf.items`
4.72 +|| Defines the LMTP service
4.73 +}}}
4.74 +
4.75 +These files provide example definitions for the `main.cf` and `master.cf`
4.76 +files that typically reside under `/etc/postfix`. Their contents can be
4.77 +merged with those files as appropriate.