1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/wiki/MailIntegration--LDAP Tue Oct 27 21:17:11 2015 +0100
1.3 @@ -0,0 +1,88 @@
1.4 += LDAP Mail Integration =
1.5 +
1.6 +LDAP can be used to identify mail recipients by configuring the mail transport
1.7 +agent (MTA) to issue queries to a suitable service. Where necessary, the
1.8 +following definitions need to be incorporated into the example configuration
1.9 +files given below:
1.10 +
1.11 +|| '''Definition''' || '''Purpose''' ||
1.12 +|| `LDAP_SERVICE_BIND_DN` || LDAP user identity to connect to the service ||
1.13 +|| `LDAP_SERVICE_PASSWORD` || LDAP user password for connection ||
1.14 +|| `LDAP_HOST` || The host providing the LDAP service ||
1.15 +|| `LDAP_PORT` || The port number of the LDAP service ||
1.16 +|| `LDAP_BASE_DN` || The section of the database to search ||
1.17 +
1.18 +== Using LDAP with Exim ==
1.19 +
1.20 +Example configuration files for Exim are distributed in `conf/exim/ldap`:
1.21 +
1.22 +{{{#!table
1.23 +'''File''' || '''Purpose'''
1.24 +==
1.25 +`010_exim4-config_ldap_people_outgoing`
1.26 +||<rowspan="4"> Defines recipients and outgoing mail routing
1.27 +==
1.28 +`020_exim4-config_ldap_people`
1.29 +==
1.30 +`020_exim4-config_ldap_resources`
1.31 +==
1.32 +`020_exim4-config_ldap_people_outgoing_recipients`
1.33 +}}}
1.34 +
1.35 +These files can be incorporated into the Exim configuration. On Debian
1.36 +systems, they can be copied into `/etc/exim4/conf.d/router`.
1.37 +
1.38 +== Using LDAP with Postfix ==
1.39 +
1.40 +Example configuration files for Postfix are distributed in `conf/postfix/ldap`:
1.41 +
1.42 +{{{#!table
1.43 +'''File''' || '''Purpose'''
1.44 +==
1.45 +`main.cf.example`
1.46 +|| Defines recipients and outgoing mail routing (for inclusion in `main.cf`)
1.47 +==
1.48 +`virtual_alias_maps_people.cf`
1.49 +||<rowspan="3"> Defines recipients and outgoing mail routing
1.50 +==
1.51 +`virtual_alias_maps_people_outgoing.cf`
1.52 +==
1.53 +`virtual_alias_maps_resources.cf`
1.54 +}}}
1.55 +
1.56 +These files can be incorporated into the Postfix configuration. On Debian
1.57 +systems, `main.cf.example` can be merged into `/etc/postfix/main.cf`,
1.58 +whereas the remaining files would be installed into `/etc/postfix/ldap`.
1.59 +
1.60 +== LDAP Representations for Mail Recipients ==
1.61 +
1.62 +Relevant LDAP resources for structuring recipient information include the
1.63 +following:
1.64 +
1.65 +{{{#!table
1.66 +'''RFC''' || '''Relevance'''
1.67 +==
1.68 +[[http://tools.ietf.org/html/rfc4524|RFC 4524]]
1.69 +|| Defines the `mail` attribute
1.70 +==
1.71 +[[http://tools.ietf.org/html/rfc2798|RFC 2798]]
1.72 +|| Defines the `inetOrgPerson` object class
1.73 +==
1.74 +[[https://tools.ietf.org/html/rfc2739|RFC 2739]]
1.75 +|| Defines the `calEntry` object class supporting `calFBURL`
1.76 +}}}
1.77 +
1.78 +An additional draft RFC describes the `mailRecipient` object class:
1.79 +
1.80 + * https://tools.ietf.org/html/draft-lachman-ldap-mail-routing-03
1.81 +
1.82 +Resource schemas for LDAP are not effectively standardised for the purposes of
1.83 +this software. A useful object class, `inetResource`, was defined for the
1.84 +iPlanet Calendar Server:
1.85 +
1.86 + * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqrf/index.html#anocg
1.87 + * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqr8/index.html
1.88 +
1.89 +Although Kolab maintains notions of resources, they are tied up with the
1.90 +notion of a shared folder and the `kolabSharedFolder` object class, although the
1.91 +`mailRecipient` object class is employed by resources in Kolab.