How to modify a user Personal Calendar ACL?

[dwerthmu]

During the migration from ex 5.5 to scalix we loose any acl that the user has placed on calendars to allow others to view them and make meetings

Is there a way from the command line that we can set each users outlook calendar folder acl to say review or read?

[dannyt]

Hi,

I think currently the only way to manage this is by login in as the user using Outlook or SWA and set the required permissions.

Regards,
Danny

[dwerthmu]

Its seems that I can only change the calendar permissions via SWA. Outlook has the permissions grayed out.

Via outlook we would normally -
Select Tools -> Options -> Calendar Options -> Resource scheduling -> Set permissions

But the "Set permissions" item is grayed out.

ideas?

Thought it would be possible to write a crawler like script like the one to read spam from users mailboxes and feed it to the spamassassin sa-learn scripts.
like: http://www.scalix.com/wiki/index.php?ti ... amAssassin

But have it connect to the calendar and set the perms thatway.. Not sure if if the calendar is available via this connection method. Or possibly via the new caldav connection.

[dannyt]

If a non-migrated user (i.e. a user created locally) can use Outlook can set permission, then the issue may lie with the migrated mailbox in terms of permission.

The Scalix ommapiperms command can be used (see man page) to see if there is anything specicial about permission settings for this mailbox that causes the grey-out.

If this mailbox is actually a resource, then have a look at ommodu man page to see if it needs to be setup as a resource in Scalix as well.

Danny

[dwerthmu]

The ommapiperms gives:


Mailbox
| [Inherited]

Inbox
| [Inherited]

Reminders
| Default: None

Drafts
| Default: None

Tasks
| Default: None

Notes
| Default: None

Journal
| Default: None

Contacts
| Default: None
Calendar
| Default: None


DESIGNATES:
No designates have been configured


Account was created with omaddu like

/opt/scalix/bin/omaddu -n "Full name/saturn/IA=username@host.tld"
-l en_US -p --locked-password username

then used sxmigrate to load the pst file exported from exchange 5.5

[dannyt]

The ommapiperms output looks OK to me. Unfortunately I am not familiar enough with sxmigrate to know whether it is the cause of the problem. Like I said before it might be worth trying without sxmigrate to see if it works or not.

Danny