On Sat, Jul 03, 2010 at 02:15:53AM +0200, Fran Garcia wrote:
> Basically the schema should :
>
> - Be OpenLDAP compatible
Not a problem.
> - Allow multidomain
I don't know what this means.
> - Host transports for each defined account / email address.
This is not a good idea. Avoid using LDAP for transport lookups.
Instead:
- rewrite envelope recipients to an appropriate destination
domain via virtual(5) (i.e. virtual_alias_maps).
- explicitly set virtual_alias_domains (even if empty).
- Map each destination domain to a suitable transport via
an indexed file (Berkeley DB hash or btree, CDB, ...)
> - Integrate with dovecot and/or cyrus-imapd.
Postfix will happily use any schema in which lookup keys
(typically email addresses) can be mapped to a result
value (or list of values which are transformed to a comma-separated
result string) by a query as explained in:
http://www.postfix.org/ldap_table.5.html
http://www.postfix.org/LDAP_README.html
Postfix has no preferred LDAP schemas, it operates at a higher level of
abstraction, i.e. virtual_alias_maps, transport_maps, ... which can be
implemented via LDAP if you so choose. The mapping between an actual
LDAP dataset and the conceptual Postfix key/value table is up to you.
--
Viktor.
