Public folders, ACLs, and the SAC..
Posted: Mon Apr 17, 2006 5:39 pm
Hi,
First off: I'm really disappointed that the SAC can't manipulate the creation and permissions of the public folders.
So, that being said. I need to come up with a way to create the acl's in such a way that permissions are automatically assigned to folder based on "groups" (he hopes).. Reading through the ACL section of the admin guide I see a number of wild card examples using the OU1-4 to set permissions. I see the OU1 and OU2 specify the "mail node" which leaves OU3 and OU4. But I don't see a way to manipulate those attributes in the SAC.
I created a group and added my test user to it. I see the attribute "PARENT-DL=" added to the OR address. Can I use this to make a ACL "automatically update" when users are provisioned via the SAC and added to group(s)?
I'm rolling out scalix to 1,000+ users in 50 different geographic location with many subdivisions within each. There's a lot of information passed between the different groups and the corporate office. Permissions alone are going to be a nightmare but needing to add each user individually to an ACL is out of the question.
Can someone please recommend a clean way to manage the public folders so I can have my non-CLI support team add users and get things provisioned properly by using what can be managed via the SAC?
Thanks all,
chrisj
First off: I'm really disappointed that the SAC can't manipulate the creation and permissions of the public folders.
So, that being said. I need to come up with a way to create the acl's in such a way that permissions are automatically assigned to folder based on "groups" (he hopes).. Reading through the ACL section of the admin guide I see a number of wild card examples using the OU1-4 to set permissions. I see the OU1 and OU2 specify the "mail node" which leaves OU3 and OU4. But I don't see a way to manipulate those attributes in the SAC.
I created a group and added my test user to it. I see the attribute "PARENT-DL=" added to the OR address. Can I use this to make a ACL "automatically update" when users are provisioned via the SAC and added to group(s)?
I'm rolling out scalix to 1,000+ users in 50 different geographic location with many subdivisions within each. There's a lot of information passed between the different groups and the corporate office. Permissions alone are going to be a nightmare but needing to add each user individually to an ACL is out of the question.
Can someone please recommend a clean way to manage the public folders so I can have my non-CLI support team add users and get things provisioned properly by using what can be managed via the SAC?
Thanks all,
chrisj