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: [EMAIL PROTECTED] mail: [EMAIL PROTECTED] quota: 200000000S On Fri, 28 Jan 2005 14:19:52 +0100, Sander Holthaus - Orange XL <[EMAIL PROTECTED]> 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? > > Kind Regards, > Sander Holthaus > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > courier-users mailing list > [email protected] > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users > -- ________________________________ saxon jones technical infrastructure admin Interbaun Communications, inc. Suite 200, 18404 Stony Plain Road Edmonton, AB T5S2M8 CANADA Email: [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
