Forum Discussion
'Save Sent Item to' function not working in shared mailbox
Christoph Maerz and SaschaSeipp thanks for the instructions! I tried to follow them, and was able to add the shared mailbox account, it worked but I was unable to view the contents.
The error message stated: The folder cannot be expanded.
Is there something I am missing? Because the instructions make sense to add using my own credentials and therefore be able to save sent emails to a designated folder (using Save Sent Item To function).
Thank you.
Carly2102: I think there will be problems if you have the mailbox auto-mapped and also add it as its own account. As far as I know, the only way to remove the automapping is to remove the full access permissions and then set them again without automapping. I do not know how to do that with the web GUI, but this would be the PowerShell approach:
Remove-MailboxPermission -Identity $smb -User $accessuser -AccessRights FullAccess
Add-MailboxPermission -Identity $smb -User $accessuser -AccessRights FullAccess -InheritanceType All -AutoMapping $falseMy experience comes from users trying to add a mailbox manually as a shared folder in addition to automapping. I have no experience with automapping and adding as another account, I just assume it could lead to the same issues. So just give it a try. 🙂
- Carly2102Oct 13, 2020Copper Contributor
SaschaSeippThank you so much, I'm going to try this today!
- Carly2102Dec 15, 2020Copper Contributor
Carly2102 Update on this query... The Save Sent Item to functionality does not work for shared mailboxes. Only for Regular Mailboxes. I converted the shared mailbox to a Regular Mailbox and bought a licence for it, but the functionality still does not work.
I believe the Save Sent Item to only works for your primary email address account. Is there a workaround?
- cliqhxJan 12, 2021Copper Contributor
Carly2102 We are expiriencing the same issue. I also have a shared-mailbox in my Outlook and can't use the "Save Sent item to" function. I tried the same things as mentioned in this post and nothing changed. Is Microsoft working on this bug to be fixed in an update?