Michael Fair wrote:
>
> > True, speed of transformation could be an issue for some. On the other
> > hand, using regexp would defeat the purpose of LDAP.
> >
> > For example, lets say you have two addresses which map to the same
> > mailbox: [EMAIL PROTECTED] and [EMAIL PROTECTED] (this is practical when
> > people have different domains according to language). If you simply
> > performed a regexp transformation, gombas_foo_com and gombas_bar_com
> > would not return the same mailbox. On the other hand, consider the
> > following LDAP entry:
> >
> > uid: [EMAIL PROTECTED]
> > uid: [EMAIL PROTECTED]
> > mailfoldermap: gombas_foo_bar_com
>
> I can't say that I know how to do it "right",
> but an equally valid approach is to consider that
> one domain is the "home" domain and all others are
> aliases to that domain. In the example above my
> current configurations (not using LDAP at all) would
> have first rewritten bar.com as foo.com using a
> domain alises scheme I set up using exim, then
> it would have done the regex substition, and tried
> to deliver the message.
>
That is indeed a good idea to solve the domain
alias problem, but it does not take advantage of
any of the convenient services provided by LDAP.
Consider for a moment a setup which involves
more than one machine running cyrus-imapd, would
you have to keep a distinct alias table on each
machine to resolve domain aliases? Compare this
to a centralised approach using a single config
located in an LDAP directory.
Furthermore, mail retrieval services such as
imap and pop are only part of an LDAP solution.
Consider that Postfix might also wish to share
the domain alias configurations. Would your exim
approach allow for Postfix and Cyrus-imapd to
use a single set of configurations, instead of
creating duplicates?
Let me know what you think, this is still work
in progress.
Marc - Sitepak
