Trouble with ACL's and BB's

[Derek]

The idea is to lay out a hierarichal structure of public folders and at a certain point allow regular users to add new files, emails, and sub folders as they please.

I the following:

Code: Select all

ommodacln -t bb -l ":Projects" -g default -c -attach

Restarted Scalix and Outlook, and it functioned just as I expected. (For future reference, what services/daemons need to be restarted for a ommodacln to take effect? I restarted the BB service, but that didn't seem to cut it.)

So I then attempted this:

Code: Select all

 ommodacln -t bb -l ":Projects>01 - Office>1959>0159178CR" -g default -c +attach

Restarted Scalix and Outlook, but I am still unable to add entries to this folder (via post or drag-and-drop). "omshowacl" on that folder shows what I expected: "default read see attach"

What am I doing wrong?

[Derek]

Wanted to add that I just verified via "omchkacln" that the test user does in fact have "attach" permission to the BB mentioned above.

[Derek]

It seems that timing was the problem here, I think..?

The script I wrote creates ~4000 public folders in about 2 minutes, this includes doing the ommodacln's on 97% of them.

After the script ran, I opened Outlook and the folders were there, however I did not have "attach" permissions to the folders for which I did the ommodacln. I closed and reopened Outlook, but this did not fix the problem.

I then restarted Scalix and opened Outlook, still no luck. So one more time I restarted Outlook and then everything was as it should've been.

All I really want to know is, what is needed for changes in BB permissions to take effect in Outlook.

Do I need to restart Scalix?
Can I just restart the bb service?
Does Outlook need to be restarted after Scalix/bbs is restarted?
How long does it take for perm changes to propogate, is there a lag?

I really need to know this as potentially there could be 100 new BBs added everyday (usually it will be between 1 and 10 though). Thanks.

[ScalixSupport]

I think

omexeccda

will be your friend for this. The command forces a rebuild of the SYSTEM directory's index. There is a CDA server process that runs on the server that does the same thing, by default every 5 minutes.

Regards,
Don

[ScalixSupport]

Forget what I said above. I'll have to look at this a bit deeper.

Regards,
Don

[ScalixSupport]

I'm afraid that this is a known issue. In my testing I never saw the permissions being updated in Outlook no matter how many times I restarted Outlook or Scalix.

Currently the way to change permissions on public folders is through outlook. Tedious I know if you are creating a lot of folders.

I can tell you that this is fixed in our next major release due out later this year.

Regards,
Don

[Derek]

I'm confused, what is the "known issue"?

I was able to create the 4000+ public folders setting them up so that only the 4th level has "attach" permission for "default" users.

I don't know, it seemed like it just needed some time for the dust to settle and then the permissions were working correctly.

I can try it again if you like and post my results. I'll at least need to do it one more time for the production server.