Forum Discussion
Users can no longer send from shared mailboxes in Outlook for iOS
We had one of our users report that they are no longer able to send mail from a shared mailbox in Outlook for iOS. The mailbox is in Exchange Online. When they tap the button to compose a message with the shared mailbox open, they get an error dialog saying "Something went wrong. Please try again or contact support."
I gave myself "Send as" rights on a shared mailbox and tested it myself and I'm seeing the same thing. Neither Microsoft 365 Support nor Outlook Mobile Support have been any help. Anyone else seeing this issue or have any ideas about how to resolve?
- The issue seems to be (finally!) fixed with version 4.2213.0.
23 Replies
- Ryan SteeleBronze ContributorI now have version 4.2210.1 and am still seeing the same issue. Anyone else?
- Ryan SteeleBronze ContributorAfter some further testing, it seems the issue is specific to sending from a regular user account that I have been given "Send as" rights to. I am able to send from ordinary shared mailboxes successfully.
- shodbyCopper ContributorYes this is our conclusion too, we have a support case open about this. Version 4.2209.0 was where it started - unable to send from EITHER User or Shared delegated mailboxes. We were told this was specifically meant to be fixed by version 4.2210.0, but the fix appears to been half baked, and only fixed it for Shared mailboxes specifically. The 2 subsequent versions since then have not fixed it either. We have provided some more logs so hopefully the next update will fix it fully!
- jjoyce10Copper Contributor
All,
Also seeing the issue after updating outlook to version 4.2209.1 on IOS. Prior to update sending emails from a shared account in outlook app on IOS was working.
We get this error now when hitting the + symbol for creating new emails. "Something went wrong. Please try again or contact support"
We can reply to an email in the shared mailbox.
We can also go to out main mail account in outlook IOS and change the sender to the the shared email account and send the email.
Anyone else managed to solve this? Thanks
- janb500Copper ContributorSame problem on IPad and iPhone. Cannot reply to or forward messages from shared inbox Uninstalled and reinstalled app on iPhone and have now lost my shared mailbox entirely and there is no option to re-add it.
- Steve FensomCopper Contributor
We are also seeing this and at currently available version. This only appears on some clients not all.
- Ryan SteeleBronze Contributor
The Microsoft Outlook Mobile support engineer has advised me that this bug will be fixed in the next release of Outlook for iOS.
- Jas0nCopper ContributorI just confirmed that this morning's update fixes the issue for me.
- Ryan SteeleBronze ContributorUnfortunately, I'm still seeing the same issue after upgrading to version 4.2209.0.
- vTCopper ContributorWe are facing the same issue here - the error also occurs when you try to reply/forward a message using the three dots below the date/time. Workaround for replying/forwarding is to not click on the dots but to use the buttons at the bottom of the screen.
Does someone have a workaround for composing new messages?- vTCopper Contributor
As this only seem to affect shared mailboxes, our workaround is to switch to another mailbox (not the shared one) and click on the plus-sign to compose a new message. You are then able to choose another sender address in the next window (see at the top).
- Jas0nCopper ContributorThis workaround does not work. I tried and looked at the email header from the test email I sent out to an external account. The "From:" address shows my primary SMTP address, not the shared mailbox/alias SMTP address that I had selected. If it should, then this is another bug.
- JoWintersCopper ContributorWe are having the same issue also using the app, seems fine through a browser but I can't see an option to add a shared mailbox on the iphone through the browser.
- Scott440Copper Contributor
Ryan Steele We are having the same issue.. Following
- KatBaylieCopper ContributorFollowing as I had a colleague and student report the exact same issue. Fingers crossed a smart bean out there has an answer to this!