Roger B.A. Klorese writes:
They're properly called "dynamic groups" -- that is, a list whose membership is defined not as a static list of addresses but as a dynamic LDAP query that is evaluated at runtime.
And what exactly is do “dynamic” about it? If it's another LDAP query, that reads another set of addresses, why can't those addresses simply be defined for the original alias?
For administrative reasons. Overhead of managing static mailing lists get extremely large when mail aliases are intensively used through an organization.
For example, imagine an organization which has the following mailing lists: * a mailing list for all users except those who are in the "outsiders" and "dismissed" organizational units; * a separate mailing list for each organization unit (e.g. "sales", "helpdesk") * a separate mailing list for each local branch (e.g. "detroit", "washington")
Adding and removing users becomes an administrative nightmare where a user must be manually added to/removed from multiple mailing lists.
With dynamic groups, one can instead specify members by an LDAP filter.
E.g. to specify a mailing list of all employees from Washington:
ldap:///dc=example,dc=com,o=Company??sub?(&(dc=washington)(objectclass=CourierMailAccount))
Best regards, -- Aleksander Adamowski Jabber JID (to nie e-mail!): [EMAIL PROTECTED] GG#: 274614 ICQ UIN: 19780575 http://olo.office.altkom.com.pl
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
