Here are some screenshot how you add a shared mailbox using “ New Outlook” experience, which honors private flag:Īnd here using the “legacy” Outlook for Mac, which doesn’t honor the private flag: RecommendationsĪs you can see, this flag is not really intended to protect privacy. Note: This does only affect Outlook for Mac, when the switch has not been toggled to use the “ New Outlook“. The resolution for this is to grant the delegate on the root folder the permission FolderVisible:Ĭannot access another user’s mailbox folder – Exchange | Microsoft Docsīut the consequence now is,delegates using Outlook for Mac are able to see private flagged items! However, when you are a delegate and have Outlook for Windows, you will most likely receive the following error: Open a shared Mail, Calendar or People folder in Outlook for Mac () Open and use a shared mailbox in Outlook () Usually you would add to your profile an additional mailbox using the process described here: Outlook for Mac is using this protocol for communicating with Exchange and here the issue starts. Both are related to Exchange Web Services (EWS). This means that if you are using one of these protocols (for whatever reasons! But I’ve seen this…) to access a mailbox on Exchange, the private flag is not honored even from Outlook!Īs you might have seen there are 2 items on the list with exception. IMAP4 or POP3 protocol doesn’t support this flag.
Note: The list might not be complete or the behavior is changing!
I was recently approached by colleagues as users complaint that delegates could see private flagged items even they have not been granted this permission. You might argue that you have not granted “Delegate can see my private items”, but this is ONLY honored by certain clients and in certain conditions. When you flag e-mails or calendar items as private, it will not ensure privacy! This is something, which cannot be stressed enough:
0 kommentar(er)
