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

365-error

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 in office 365 or trying to send FROM a distribution list. This is most likely due to the address book GAL not updating. There are a couple things you can try.

Office 365 Instructions to Fix Error

Solution 1

First, try updating the address book by going to the Send/Receive tab and clicking on “Download Address Book.”

download-address-book

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 8 it is located here:

C:\Users\Username\AppData\Local\Microsoft\Outlook 

offline-address-books

Re-launch Outlook, and try again.

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

Incoming search terms:

  • 0x80070005-00000000-00000000
  • This message could not be sent Try sending the message again later or contact your network administrator Error is [0x80070005-00000000-00000000]
  • error is [0x80070005-00000000-00000000]
  • [0x80070005-00000000-00000000]
  • error is [0x80070005-00000000-00000000
  • Pingback: TheITBros Unofficial Microsoft Office 365 Migration Guide - Made Easy

  • 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)

  • 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.