1 = LDAP Mail Integration = 2 3 LDAP can be used to identify mail recipients by configuring the mail transport 4 agent (MTA) to issue queries to a suitable service. Where necessary, the 5 following definitions need to be incorporated into the example configuration 6 files given below: 7 8 || '''Definition''' || '''Purpose''' || 9 || `LDAP_SERVICE_BIND_DN` || LDAP user identity to connect to the service || 10 || `LDAP_SERVICE_PASSWORD` || LDAP user password for connection || 11 || `LDAP_HOST` || The host providing the LDAP service || 12 || `LDAP_PORT` || The port number of the LDAP service || 13 || `LDAP_BASE_DN` || The section of the database to search || 14 15 == Using LDAP with Exim == 16 17 Example configuration files for Exim are distributed in `conf/exim/ldap`: 18 19 {{{#!table 20 '''File''' || '''Purpose''' 21 == 22 `010_exim4-config_ldap_people_outgoing` 23 ||<rowspan="4"> Defines recipients and outgoing mail routing 24 == 25 `020_exim4-config_ldap_people` 26 == 27 `020_exim4-config_ldap_resources` 28 == 29 `020_exim4-config_ldap_people_outgoing_recipients` 30 }}} 31 32 These files can be incorporated into the Exim configuration. On Debian 33 systems, they can be copied into `/etc/exim4/conf.d/router`. 34 35 == Using LDAP with Postfix == 36 37 Example configuration files for Postfix are distributed in `conf/postfix/ldap`: 38 39 {{{#!table 40 '''File''' || '''Purpose''' 41 == 42 `main.cf.example` 43 || Defines recipients and outgoing mail routing (for inclusion in `main.cf`) 44 == 45 `virtual_alias_maps_people.cf` 46 ||<rowspan="3"> Defines recipients and outgoing mail routing 47 == 48 `virtual_alias_maps_people_outgoing.cf` 49 == 50 `virtual_alias_maps_resources.cf` 51 }}} 52 53 These files can be incorporated into the Postfix configuration. On Debian 54 systems, `main.cf.example` can be merged into `/etc/postfix/main.cf`, 55 whereas the remaining files would be installed into `/etc/postfix/ldap`. 56 57 == LDAP Representations for Mail Recipients == 58 59 Relevant LDAP resources for structuring recipient information include the 60 following: 61 62 {{{#!table 63 '''RFC''' || '''Relevance''' 64 == 65 [[http://tools.ietf.org/html/rfc4524|RFC 4524]] 66 || Defines the `mail` attribute 67 == 68 [[http://tools.ietf.org/html/rfc2798|RFC 2798]] 69 || Defines the `inetOrgPerson` object class 70 == 71 [[https://tools.ietf.org/html/rfc2739|RFC 2739]] 72 || Defines the `calEntry` object class supporting `calFBURL` 73 }}} 74 75 An additional draft RFC describes the `mailRecipient` object class: 76 77 * https://tools.ietf.org/html/draft-lachman-ldap-mail-routing-03 78 79 Resource schemas for LDAP are not effectively standardised for the purposes of 80 this software. A useful object class, `inetResource`, was defined for the 81 iPlanet Calendar Server: 82 83 * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqrf/index.html#anocg 84 * http://docs.oracle.com/cd/E19566-01/819-4437/6n6jckqr8/index.html 85 86 Although Kolab maintains notions of resources, they are tied up with the 87 notion of a shared folder and the `kolabSharedFolder` object class, although the 88 `mailRecipient` object class is employed by resources in Kolab.