Office 365 – “This message could not be sent. Try sending the message again later”

Error Message: This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000]. You might be receiving this when trying to send from a shared mailbox on the Office 365/On-Premise Exchange or trying to send FROM a distribution list.

Even if you remove current Outlook profile and re-create it again, the error still remains.

Your message did not reach some or all of the intended recipients.

Subject:    Test email

Sent: 8/22/2017 12:44 AM

The following recipient(s) cannot be reached:

Brian Jackson on 8/22/2017 12:44 AM

This message could not be sent. Try sending the message again later, or contact your network administrator.  Error is [0x80070005-00000000-00000000].

This is most likely due to the Global Address Book (GAL) in your Outlook isn’t updating. There are a couple things you can try.

Office 365 Instructions to Fix Error

Solution 1

At first, try updating the address book by going to the Send/Receive tab (Outlook 2010, Outlook 2013 and Outlook 2013) and clicking on Send-Receive Groups -> Download Address Book. In Outlook 2007 you can find Download Address Book button in Tools menu.

download address book office 365

Then click on OK.

office 365 offline GAL

Now try sending again from Outlook using your shared mailbox or in the FROM address with a distribution list. Also, try grabbing the FROM address from the Global Address list instead of the GAL.

global address list

Solution 2

Close Microsoft Outlook and try deleting everything within the “Offline Address Books” folder. It will re-populate.

In Windows 7,8.1 and 10 it is located here:


If you are use outdated Windows XP, check the following path:

C:\Documents and Settings\Username\Local Settings\Application Data\Microsoft\Outlook\

offline address books

Re-launch Outlook, and try again. After updating OAB, the error should be fixed.

Solution 3

You can use Exchange Error Code Look-up tool to resolve error code 0x80070005 to MAPI_E_NO_ACCESS or E_ACCESSDENIED.  This means that you need to add SendAs permission on the shared mailbox to the Exchange user (the error still exist then try to add Send-as permissions using Office 365 web base admin panel). Run the following Exchange PowerShell command:

Add-RecipientPermission "HelpDesk" -AccessRights SendAs -Trustee "Brett Jackson"

If the above information helped you, make sure to check out our official Office 365 Migration Guide.

You may also like:

Add Calendar Permissions in Office 365 via Powersh... This is a tutorial on how to add calendar permissions in Office 365 for your users via Powershell. You can add permissions onto a specific mailbox, or...
Migrate email to Office 365 using WHM If you are like me, then you are simply wanting to migrate your email over to Microsoft Office 365 to take advantage of Exchange. Me and my colleague ...
TheITBros Microsoft Office 365 Migration Guide We just migrated a company to Microsoft Office 365 and we thought we would share our experience and troubleshooting tips. We hope this saves you some ...
Grant Full Access to All Mailboxes in Exchange 200... This is a short tutorial on how to add full access to all mailboxes in Exchange 2007 and 2010 for a an additional user. This can come in handy when sa...
Don’t Archive Notes in Office 365 Are your notes suddenly disappearing in Office 365? That's probably because you have enabled archiving in the Exchange Admin center with a retention p...
  • Kristian Poulsen

    Make sure the user who has problem sending mails from the shared mailbox has “send as” rights. This solved the problem for us (for now at least)

    • Jose E Calderon

      Where is this setting found?

      • Joe Soap

        powershell command.

        Add-RecipientPermission -Trustee -AccessRights sendas

  • tdhaslett

    Even after going through both solutions a day after first setting up the distribution group and permissions, it did not solve this issue for me.

    What did solve it was first going to OWA and sending a message from the DG and then repeating Solution 1 in Outlook.

  • Frank Becker

    I found here 10 other possible solutions to the issue: in my case KB KB 3045224 solved the problem.