# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1446161558 -3600
# Node ID f6a0f145c46ab918d371c3e0b355125471610dd6
# Parent  0ceeaf1c6e322ba13362f553e609017ba51c9e95
Expanded the mail integration documentation for LMTP and mailboxes, also
mentioning an alias for the calendar system e-mail address.

diff -r 0ceeaf1c6e32 -r f6a0f145c46a docs/wiki/MailIntegration
--- a/docs/wiki/MailIntegration	Fri Oct 30 00:30:52 2015 +0100
+++ b/docs/wiki/MailIntegration	Fri Oct 30 00:32:38 2015 +0100
@@ -51,6 +51,21 @@
 [[/Simple|Simple (list-based identification)]] || Exim, Postfix
 }}}
 
+=== The Calendar System Address ===
+
+Since imip-agent may send messages on behalf of calendar users, the address
+it uses to do so must be recognised by the MTA. This may be done by adding
+an entry to the `/etc/aliases` file such as the one defined in the
+`conf/aliases.example` file:
+
+{{{
+calendar: root
+}}}
+
+More suitable routing can be defined as desired. See the `MESSAGE_SENDER`
+setting defined in the `config.py` file described in the
+[[../Configuration|configuration guide]].
+
 == Invoking the Agent Programs ==
 
 Regardless of identification or delivery mechanisms, the imip-agent software
diff -r 0ceeaf1c6e32 -r f6a0f145c46a docs/wiki/MailIntegration--LDAP
--- a/docs/wiki/MailIntegration--LDAP	Fri Oct 30 00:30:52 2015 +0100
+++ b/docs/wiki/MailIntegration--LDAP	Fri Oct 30 00:32:38 2015 +0100
@@ -27,6 +27,9 @@
 `020_exim4-config_ldap_resources`
 ==
 `020_exim4-config_ldap_people_outgoing_recipients`
+==
+`020_exim4-config_ldap_people_local`
+|| Defines routing for local recipients for delivery to local mailboxes
 }}}
 
 These files can be incorporated into the Exim configuration. On Debian
@@ -62,14 +65,17 @@
 {{{#!table
 '''RFC''' || '''Relevance'''
 ==
-[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
-|| Defines the `mail` attribute
+[[http://tools.ietf.org/html/rfc2307|RFC 2307]]
+|| Defines the `posixAccount` object class
+==
+[[https://tools.ietf.org/html/rfc2739|RFC 2739]]
+|| Defines the `calEntry` object class supporting `calFBURL`
 ==
 [[http://tools.ietf.org/html/rfc2798|RFC 2798]]
 || Defines the `inetOrgPerson` object class
 ==
-[[https://tools.ietf.org/html/rfc2739|RFC 2739]]
-|| Defines the `calEntry` object class supporting `calFBURL`
+[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
+|| Defines the `mail` attribute
 }}}
 
 An additional draft RFC describes the `mailRecipient` object class:
diff -r 0ceeaf1c6e32 -r f6a0f145c46a docs/wiki/MailIntegration--Simple
--- a/docs/wiki/MailIntegration--Simple	Fri Oct 30 00:30:52 2015 +0100
+++ b/docs/wiki/MailIntegration--Simple	Fri Oct 30 00:32:38 2015 +0100
@@ -24,6 +24,9 @@
 ==
 `020_exim4-config_people_outgoing_recipients`
 ==
+`020_exim4-config_people_local`
+|| Defines routing for local recipients for delivery to local mailboxes
+==
 `virtual_people`
 ||<rowspan="3"> Defines recipient identities belonging to known domains
 ==
diff -r 0ceeaf1c6e32 -r f6a0f145c46a docs/wiki/MailboxIntegration
--- a/docs/wiki/MailboxIntegration	Fri Oct 30 00:30:52 2015 +0100
+++ b/docs/wiki/MailboxIntegration	Fri Oct 30 00:32:38 2015 +0100
@@ -1,3 +1,4 @@
+= Mailbox Integration =
 = Mailbox Integration =
 
 Use of the imip-agent software should not affect the solutions chosen to store
@@ -7,32 +8,35 @@
 
 It can, however, be useful to see how delivery to various kinds of mailboxes
 and mail storage is done, in case you have not already decided on a particular
-solution.
-
-== Cyrus ==
+solution. Tested solutions are as follows:
 
-[[http://www.cyrusimap.org/|Cyrus]] is a mail storage system that exposes
-mailboxes using the [[http://tools.ietf.org/html/rfc3501|IMAP]] protocol.
+ * [[http://www.cyrusimap.org/|Cyrus]] is a mail storage system that exposes
+ mailboxes using the [[http://tools.ietf.org/html/rfc3501|IMAP]] protocol
 
-== Dovecot ==
-
-[[http://dovecot.org/|Dovecot]] is a mail server that supports IMAP and
-[[http://tools.ietf.org/html/rfc1939|POP3]]. It can be configured to serve
-mail stored in traditional mailbox formats.
+ * [[http://dovecot.org/|Dovecot]] is a mail server that supports IMAP and
+ [[http://tools.ietf.org/html/rfc1939|POP3]]. It can be configured to serve
+ mail stored in traditional mailbox formats
 
 The Dovecot documentation provides guides for integrating Dovecot with
 [[http://wiki2.dovecot.org/LMTP/Exim|Exim]] and with
 [[http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP|Postfix]].
 
-Example configuration files for Exim and Dovecot are distributed in
-`conf/exim/lmtp`:
+== Exim ==
+
+Example configuration files for Exim are distributed in `conf/exim/lmtp`:
 
 {{{#!table
 '''File''' || '''Purpose'''
 ==
+`30_exim4-config_cyrus_lmtp`
+|| Delivers messages to Cyrus via LMTP
+==
 `30_exim4-config_dovecot_lmtp`
 || Delivers messages to Dovecot via LMTP
 ==
+`890_exim4-config_cyrus_lmtp_local`
+|| Routes messages for local system users to Cyrus
+==
 `890_exim4-config_dovecot_lmtp_local`
 || Routes messages for local system users to Dovecot
 }}}
@@ -41,3 +45,21 @@
 `/etc/exim4/conf.d/transport` directory, whereas the latter would be
 copied into the `/etc/exim4/conf.d/router` directory. The latter file is
 appropriate only if system user identities are to be employed for mail.
+
+== Postfix ==
+
+Example configuration files for Postfix are distributed in `conf/postfix/lmtp`:
+
+{{{#!table
+'''File''' || '''Purpose'''
+==
+`main.cf.example`
+|| Defines mailbox transports for Cyrus and Dovecot
+==
+`master.cf.items`
+|| Defines the LMTP service
+}}}
+
+These files provide example definitions for the `main.cf` and `master.cf`
+files that typically reside under `/etc/postfix`. Their contents can be
+merged with those files as appropriate.