Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.
Solved
Exchange 2010, SharedMailbox and Private emails
Posted on 2013-01-02
Has anybody come across the following before?
We have a large number of exchange 2010 mailboxes of type SharedMailbox. Today a user reported that they had been sent an email by another user, to a SharedMailbox, but that it had not arrived. Upon closer inspection Outlook 2010 sowed
Inbox (1)
for that shared mailbox, showing that it had one new email but nothing was visible in the emails listed for the inbox.
Go into OWA, switch to the SharedMailbox and there it is! The email that is marked as private.
Anyone know why outlook does not show these emails in a shared mailbox?
Can it be forced to?
We have a large number of exchange 2010 mailboxes of type SharedMailbox. Today a user reported that they had been sent an email by another user, to a SharedMailbox, but that it had not arrived. Upon closer inspection Outlook 2010 sowed
Inbox (1)
for that shared mailbox, showing that it had one new email but nothing was visible in the emails listed for the inbox.
Go into OWA, switch to the SharedMailbox and there it is! The email that is marked as private.
Anyone know why outlook does not show these emails in a shared mailbox?
Can it be forced to?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
12
7-
2
- +1
22 Comments
Active today
Check this
http://www.msoutlook.info/question/438
http://www.msoutlook.info/question/438
Nope. This is NOT a Shared Mailbox, it IS an exchange 2010 mailbox of type SharedMailbox. Delegate permissions are not given on a SharedMailbox, in fact there is NO logon user to access the SharedMailbox and give delegate access, It is all done with EMC.
To do so would entail converting the mailbox back to a usermailbox, and manually creating an outlook profile, opening it, changing the delegate permissions etc,....
We have hundereds of sharedmailboxes, some with hundereds of users having full access to them.
A solution that involves a months work is not on the books.
We have hundereds of sharedmailboxes, some with hundereds of users having full access to them.
A solution that involves a months work is not on the books.
"This is by design"
I do love answers like that, so useful.
If you feel the need to make such comments then at least have the good manners to back it up with hard evidence.
I do love answers like that, so useful.
If you feel the need to make such comments then at least have the good manners to back it up with hard evidence.
When it comes to the Shared Mailbox then any email that is marked as private is hidden for all but the intended recipients. This includes emails sent directly to the shared mailbox that are subsequently moved to another shared mailbox, they effectively disappear to preserve the privacy of the message.
Dare I say it, it is by design, the marking of the message as private is done at the senders end
To quote the great Sembee
http://social.technet.microsoft.com/Forums/eu/exchange2010/thread/16e856ce-2ef1-4f93-8cf7-9931d98890b9
Dare I say it, it is by design, the marking of the message as private is done at the senders end
To quote the great Sembee
http://social.technet.microsoft.com/Forums/eu/exchange2010/thread/16e856ce-2ef1-4f93-8cf7-9931d98890b9
But NOTHING has been "Moved". It was sent directly to the sharedmailbox, not MOVED to it.
What is the point of a SharedMailbox, WITHOUT an enabled login user, if emails can arive in it that can NOT be read in outlook but CAN be read in owa by the same user?
Please remember we are not talking about a UserMailbox that has had another user set as a Delegate but about a mailbox of type SharedMailbox that hundereds of users have been given Fullaccess & sendAs permissions on it from EMC.
What is the point of a SharedMailbox, WITHOUT an enabled login user, if emails can arive in it that can NOT be read in outlook but CAN be read in owa by the same user?
Please remember we are not talking about a UserMailbox that has had another user set as a Delegate but about a mailbox of type SharedMailbox that hundereds of users have been given Fullaccess & sendAs permissions on it from EMC.
Active today
Neilsr: As mentioned DLeaver above, it is design limitation. Sembee mentioned a rule option try that out.
There is no Rule option to clear a private flag in either Outlook or via an exchange transport rule.
Also what Sembee talks about is Moving items that are marked as Private INTO a shared mailbox and hem then being non visible.
It would seem that it is yet again another MS oversight in providing half of a solution to an age old problem of shared mailboxes.
Also what Sembee talks about is Moving items that are marked as Private INTO a shared mailbox and hem then being non visible.
It would seem that it is yet again another MS oversight in providing half of a solution to an age old problem of shared mailboxes.
I take it all back!!
I found an example of a rule for transport rules :D Oh happy days.... Off to test.....
http://social.technet.microsoft.com/Forums/uk/exchange2010/thread/2afd06f3-c7f9-4aac-aa3a-fae2ec42d477
I found an example of a rule for transport rules :D Oh happy days.... Off to test.....
http://social.technet.microsoft.com/Forums/uk/exchange2010/thread/2afd06f3-c7f9-4aac-aa3a-fae2ec42d477
:(
The rule correctly identifies the emails as private.....
The rule correctly prepends the subject text with Was Private.....
But alas it does NOT remove the Sensitivity header. The email is still marked as private.
Triple checked all spulling... restarted transport service.... no good :(
The rule correctly identifies the emails as private.....
The rule correctly prepends the subject text with Was Private.....
But alas it does NOT remove the Sensitivity header. The email is still marked as private.
Triple checked all spulling... restarted transport service.... no good :(
Active today
Thanks for sharing the result. Something similar discussed here
http://ilsselfhelp.plymouth.ac.uk/default.asp?id=839&Lang=1
However answer is same, as i posted in first comment and you are right, what is the meaning for a shared mailbox, if we need to enable it. I see this as a bug in this case.
Hope you understood my point.
http://ilsselfhelp.plymouth.ac.uk/default.asp?id=839&Lang=1
However answer is same, as i posted in first comment and you are right, what is the meaning for a shared mailbox, if we need to enable it. I see this as a bug in this case.
Hope you understood my point.
Interestingly I changed the rule so that instead of Removing the Sensitivity header it SET the Sensitivity header to NONE
Now when i open the email and inspect its properties, the header shows
Sensitivity: NONE
BUT on the properties sheet for the email it shows.....
So if outlook is NOT using the standard message header "Sensitivity" Where is it getting that info from???
Now when i open the email and inspect its properties, the header shows
Sensitivity: NONE
BUT on the properties sheet for the email it shows.....
So if outlook is NOT using the standard message header "Sensitivity" Where is it getting that info from???
Active today
Good Question, unfortunately no answer. I guess you already researched lot on this issue.
At LAST!!
Use the transport rule as above BUT use
Set "Sensitivity" with "Normal"
All works fine :D
Many thanks for pointing me in the right direction and keeping the convo going, I might have given up otherwise!
Neil
Use the transport rule as above BUT use
Set "Sensitivity" with "Normal"
All works fine :D
Many thanks for pointing me in the right direction and keeping the convo going, I might have given up otherwise!
Neil
This looks like an older thread.
But i'm searching for a resolution to the same.
The transport rule above looks like a Client Side outlook rule.
So what's the point of that if the shared mailbox is being accessed as a secondary outlook account? (users that have full access to the mailbox and the mailbox auto-maps into their outlook)
Wait this rule is performed on the Hub Transport (Exchange 2010) so it is not an outlook client rule.
Sorry about that
But i'm searching for a resolution to the same.
The transport rule above looks like a Client Side outlook rule.
So what's the point of that if the shared mailbox is being accessed as a secondary outlook account? (users that have full access to the mailbox and the mailbox auto-maps into their outlook)
Wait this rule is performed on the Hub Transport (Exchange 2010) so it is not an outlook client rule.
Sorry about that
Featured Post
If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
- Software-Other
- Exchange
- Email Servers
- Email Software
- Exchange 2007
- *Exchange Server 2010
By default Outlook 2016 displays only one time zone in the Calendar. The following article explains how to display two time zones in one calendar view.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Mail Flow >> Rules tab.: To cr…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses
Course of the Month8 days, 7 hours left to enroll
598 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.