|
From: Jamie C. <jca...@we...> - 2005-10-31 05:18:17
|
On Sun, 2005-10-30 at 21:19, Murray Trainer wrote: > On Mon, 2005-10-31 at 04:12, Jamie Cameron wrote: > > On Sat, 2005-10-29 at 23:28, Murray Trainer wrote: > > > On Sun, 2005-10-30 at 03:18, Jamie Cameron wrote: > > > > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > > > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > > > > Hi Craig, > > > > > > > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > > > > > > > Murray > > > > > > > > > > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > > > > Hi Jamie, > > > > > > > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > > > > that would involve an LDAP search for the requested new alias of all > > > > > > > > users under that domain and accepting it if it didn't already exist. > > > > > > > ---- > > > > > > > Alias? email alias? attribute? dn? > > > > > > > > > > > > > > Clarify please > > > > > ----- > > > > > In that event - an attribute of an entry, openldap wouldn't catch that > > > > > and I wouldn't know about other ldap programs. That would be an > > > > > interesting escalation of the power of the LDAP Users and Groups module. > > > > > Considering that some of the attributes are necessarily duplicated > > > > > within the DSA and some are necessarily unique, an option to check for > > > > > uniqueness would have to be very configurable. > > > > > > > > That is quite a good idea for a feature actually .. in the next release, > > > > I will add a Module Config option to specify custom fields that are not > > > > allowed to contain duplicates with other users. Also, the mail alias > > > > field will automatically have this enforced .. > > > > > > I'm wondering if the mail alias being unique should be optional on it's > > > intended use. In my setup I have postfix configured to use an > > > ldap-aliases file to search my LDAP directory for recipients. The > > > search looks for matching mail and alias attributes and returns the > > > matching users uid names which correspond with their Cyrus mailbox names > > > so the mail can be delivered. I just tried adding the same alias e-mail > > > address attribute to two users and an e-mail to the alias is delivered > > > to both of them. This is probably what should happen in this case and > > > is often pretty useful - ie. basic mailing list functionality. Maybe we > > > need separate Personal Mail Aliases and Group Mail Alias entry fields - > > > the former enforcing uniqueness and the latter not. The group alias > > > would normally only be used when we specifically have a need to direct > > > e-mail to a group of users via a common address. > > > > Fair enough .. I will make duplicate checking for the alias manual. > > > > - Jamie > > How about keeping the existing mail aliases field and just adding a > tickbox to allow/disallow duplicates (default ticked or unticked > configurable in the module's config page). That is exactly what I did :-) - Jamie |