![]() |
![]() |
![]() |
Evolution Connector for Microsoft Exchange Programmers Reference Manual | ![]() |
---|
Delegation |
Delegation is a hodgepodge of several different bits of functionality. The big picture idea is "someone else deals with your mail or calendar, or you deal with theirs".
When you make someone a delegate in Outlook, the dialog lets you do a bunch of things:
You can edit their permissions on all of your folders in one easy place.
If you give them "Editor" permission on your Calendar, you can cause them to also get copies of your meeting requests.
If you make at least one person get copies of your meeting requests, you can make yourself not get them any more.
You can make it possible (on a per-delegate basis) for your delegates to be able to see "Private" appointments, contacts, and tasks in your folders. (Normally other people can't see your Private items regardless of what permissions you give them.)
Your delegate automatically becomes able to send mail from your address. Outlook doesn't actually allow you to enable/disable this functionality independently of calling someone a delegate, although it's possible to do so.
Different pieces of this information are stored in different places:
Permissions information is stored in the
Who-can-send-mail-as-who data is kept in Active
Directory. Your delegates are stored in the
multivalued publicDelegates
property on
your AD entry. When you modify that property, AD automatically
maintains back links in other entries'
publicDelegatesBL
properties. (Thus, by
checking your own publicDelegatesBL
property, you can find out who you are a delegate for.)
Three multivalued MAPI properties on
NON_IPM_SUBTREE/Freebusy%20Data/LocalFreebusy.EML
also track your delegates:
|
display names of delegates |
|
ENTRYIDS of delegates |
|
boolean "can see private items" values |
Meeting request forwarding is controlled by a server-side rule in
Inbox with a PR_RULE_MSG_PROVIDER
of
"Schedule+ EMS Interface
"