15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] LDAP aliasing
FromSent OnAttachments
Saxon JonesJan 21, 2005 12:43 pm 
Sam VarshavchikJan 21, 2005 4:54 pm 
Zenon PanoussisJan 25, 2005 11:49 am 
Sam VarshavchikJan 25, 2005 3:57 pm 
Zenon PanoussisJan 26, 2005 5:43 pm 
Sam VarshavchikJan 26, 2005 5:50 pm 
Laurence MooreJan 26, 2005 5:55 pm 
Sander Holthaus - Orange XLJan 26, 2005 6:36 pm 
Sam VarshavchikJan 27, 2005 7:42 pm 
Robert PfisterJan 28, 2005 12:57 am 
Sander Holthaus - Orange XLJan 28, 2005 6:12 am 
Saxon JonesJan 28, 2005 2:54 pm 
Zenon PanoussisJan 29, 2005 12:22 pm 
Saxon JonesFeb 3, 2005 3:25 pm 
Sam VarshavchikFeb 3, 2005 3:56 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] LDAP aliasingActions...
From:Saxon Jones (saxo@gmail.com)
Date:Jan 28, 2005 2:54:02 pm
List:net.sourceforge.lists.courier-users

Maybe I'm completely missing your goal here, but why not assign multiple mail attributes to the one account? For example:

# 56555, interbaun.com dn: uid=56555,dc=interbaun,dc=com objectClass: account objectClass: interbaunMailAccount homeDirectory: /Mail/mailboxes/stor03/04/55/56555 userPassword:: <removed> uid: 56555 mail: sax@interbaun.com mail: sax@shittyshittybangbang.com quota: 200000000S

On Fri, 28 Jan 2005 14:19:52 +0100, Sander Holthaus - Orange XL <in@orangexl.com> wrote:

Plus, I have to question whether it is proper to have recursive LDAP aliases in the first place. That means that, for example, an alias that expands out to a hundred addresses will cause a hundred additional round-trip LDAP lookups. Every time. This does not sound like a right design to me.

It makes more sense to me to have all the recursive alias resolutions done once, and save the expanded alias list in the LDAP directory.

This is exactly how Courier's native mail aliases work. With native aliases, I don't look up every address every time. The makealiases script reads the alias file, expands all aliases recursively, and builds a GDBM/DB database where the aliases are already expanded. This eliminates a lot of waste from the code that receives new messages. Only a single lookup is required for an E-mail address.

An LDAP-based setup should be structured in the same way.

That's a good point. Personally, I would use recursive lookups to map several aliases on to a single mail-address. In the current situation, I would have to maintain and keep track of the same maildrop-address in several places. If the mail-address changes, I need to change several maildrop-fields. With recursive lookups, I would only need to change one.

What the best solution is, depends. Performance-wise, you indeed do not want recursive LDAP-lookups. In terms of Functionality and Maintainability, you do might want recursive lookups, even though they are bad. I think it is just not always possible to make an LDAP-based setup or change one, to get arround either recursive lookups or multiple entries.

Perhaps the recursive LDAP-patch could be optionally compiled in and included in the Courier-distribution?

technical infrastructure admin Interbaun Communications, inc. Suite 200, 18404 Stony Plain Road Edmonton, AB T5S2M8 CANADA