> > Well, if you want to do it, then do it right and provide a generic
mapping
> > layer like Postfix has. LDAP is nice and cool, but a simple regexp map
> > would be a _lot_ faster for transforming "[EMAIL PROTECTED]" to either
> > "atif_4unet_net" or "uid=atif, dc=4unet, dc=net, ou=Users, ...". And
such a
> > layer could also be used to transform MUA-specified folder names to
on-disk
> > path names solving the separator problem on-the-fly...
> >
> 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.
I can also create aliases within bar.com though
I haven't found a need to. All my implementations
seem to center on the idea that one domain is the
"home" domain or preferred domain, and all others
are just alises of that domain and therefore any
mail sent to bar.com is always desired to go to
foo.com. Since I really can't describe the problem
specifically enough where one answer is clearly
more accurate and correct then the other, I merely
present how I (and many others) have solved the
same problems using the regex technique.
-- Michael --
