# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1445977031 -3600
# Node ID 7e09dd9862388bcbf8fca23f23c6907130e72ed4
# Parent  6c1808efb8c9e5b9495037e5697dd70957a67ed6
Added recipient identification documentation for mail integration.

diff -r 6c1808efb8c9 -r 7e09dd986238 docs/wiki/MailIntegration
--- a/docs/wiki/MailIntegration	Tue Oct 27 21:16:26 2015 +0100
+++ b/docs/wiki/MailIntegration	Tue Oct 27 21:17:11 2015 +0100
@@ -46,9 +46,9 @@
 {{{#!table
 '''Identification Mechanisms''' || '''Tested with...'''
 ==
-LDAP || Exim, Postfix
+[[/LDAP|LDAP]] || Exim, Postfix
 ==
-Simple (list-based identification) || Exim, Postfix
+[[/Simple|Simple (list-based identification)]] || Exim, Postfix
 }}}
 
 == Delivery ==
diff -r 6c1808efb8c9 -r 7e09dd986238 docs/wiki/MailIntegration--LDAP
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/wiki/MailIntegration--LDAP	Tue Oct 27 21:17:11 2015 +0100
@@ -0,0 +1,88 @@
+= LDAP Mail Integration =
+
+LDAP can be used to identify mail recipients by configuring the mail transport
+agent (MTA) to issue queries to a suitable service. Where necessary, the
+following definitions need to be incorporated into the example configuration
+files given below:
+
+|| '''Definition'''        || '''Purpose''' ||
+|| `LDAP_SERVICE_BIND_DN`  || LDAP user identity to connect to the service ||
+|| `LDAP_SERVICE_PASSWORD` || LDAP user password for connection ||
+|| `LDAP_HOST`             || The host providing the LDAP service ||
+|| `LDAP_PORT`             || The port number of the LDAP service ||
+|| `LDAP_BASE_DN`          || The section of the database to search ||
+
+== Using LDAP with Exim ==
+
+Example configuration files for Exim are distributed in `conf/exim/ldap`:
+
+{{{#!table
+'''File''' || '''Purpose'''
+==
+`010_exim4-config_ldap_people_outgoing`
+||<rowspan="4"> Defines recipients and outgoing mail routing
+==
+`020_exim4-config_ldap_people`
+==
+`020_exim4-config_ldap_resources`
+==
+`020_exim4-config_ldap_people_outgoing_recipients`
+}}}
+
+These files can be incorporated into the Exim configuration. On Debian
+systems, they can be copied into `/etc/exim4/conf.d/router`.
+
+== Using LDAP with Postfix ==
+
+Example configuration files for Postfix are distributed in `conf/postfix/ldap`:
+
+{{{#!table
+'''File''' || '''Purpose'''
+==
+`main.cf.example`
+|| Defines recipients and outgoing mail routing (for inclusion in `main.cf`)
+==
+`virtual_alias_maps_people.cf`
+||<rowspan="3"> Defines recipients and outgoing mail routing
+==
+`virtual_alias_maps_people_outgoing.cf`
+==
+`virtual_alias_maps_resources.cf`
+}}}
+
+These files can be incorporated into the Postfix configuration. On Debian
+systems, `main.cf.example` can be merged into `/etc/postfix/main.cf`,
+whereas the remaining files would be installed into `/etc/postfix/ldap`.
+
+== LDAP Representations for Mail Recipients ==
+
+Relevant LDAP resources for structuring recipient information include the
+following:
+
+{{{#!table
+'''RFC''' || '''Relevance'''
+==
+[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
+|| Defines the `mail` attribute
+==
+[[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`
+}}}
+
+An additional draft RFC describes the `mailRecipient` object class:
+
+ * https://tools.ietf.org/html/draft-lachman-ldap-mail-routing-03
+
+Resource schemas for LDAP are not effectively standardised for the purposes of
+this software. A useful object class, `inetResource`, was defined for the
+iPlanet Calendar Server:
+
+ * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqrf/index.html#anocg
+ * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqr8/index.html
+
+Although Kolab maintains notions of resources, they are tied up with the
+notion of a shared folder and the `kolabSharedFolder` object class, although the
+`mailRecipient` object class is employed by resources in Kolab.
diff -r 6c1808efb8c9 -r 7e09dd986238 docs/wiki/MailIntegration--Simple
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/wiki/MailIntegration--Simple	Tue Oct 27 21:17:11 2015 +0100
@@ -0,0 +1,58 @@
+= Simple Mail Integration =
+
+Since the use of [[../LDAP|LDAP]] can be somewhat challenging and also excessive
+in some situations, examples of maintaining recipient information are provided
+that use an approach involving simple textual lists of identities.
+
+In this simpler environment, recipient details must be manually edited in the
+virtual identity files, but this permits a very transparent way of
+administering the system.
+
+== Using Lists with Exim ==
+
+Example configuration file for Exim are distributed in `conf/exim/simple`:
+
+{{{#!table
+'''File''' || '''Purpose'''
+==
+`010_exim4-config_people_outgoing`
+||<rowspan="4"> Defines recipients and outgoing mail routing
+==
+`020_exim4-config_people`
+==
+`020_exim4-config_resources`
+==
+`020_exim4-config_people_outgoing_recipients`
+==
+`virtual_people`
+||<rowspan="3"> Defines recipient identities belonging to known domains
+==
+`virtual_people_outgoing_recipients`
+==
+`virtual_resources`
+==
+`virtual_domains`
+|| Defines recipient domains
+==
+`virtual_people_local`
+|| Defines recipients and local users for delivery to local mailboxes
+}}}
+
+== Using Lists with Postfix ==
+
+Example configuration file for Postfix are distributed in `conf/postfix/simple`:
+
+{{{#!table
+'''File''' || '''Purpose'''
+==
+`main.cf.example`
+|| Defines recipients and outgoing mail routing (for inclusion in `main.cf`)
+==
+`virtual_alias_maps`
+||<rowspan="2"> Defines recipients and outgoing mail routing
+==
+`virtual_alias_maps_people_outgoing`
+==
+`virtual_alias_maps_local`
+|| Defines recipients and local users for delivery to local mailboxes
+}}}