Share via

Error is [0x80070005-0x000004dc-0x00000524]

Anonymous
2025-01-15T03:42:19+00:00

I have a hotmail account that I have been using for many years. Up until about a month ago, i ahve never had issues sending or receiving emails. Now I am only able to receive emails, but sending any outbound emails comes back with a System Administrator email, with the above error code. I do not share this mailbox with anyone, nor am I sending on behalf of anyone.

I have tried this across multiple PC's with the outlook client and have the same issue across all. However if I send emails from the hotmail online client or my IOS device, the emails go through fine. Please let me know what I can do to fix this.

Outlook | Windows | New Outlook for Windows | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

27 answers

Sort by: Most helpful
  1. Anonymous
    2025-04-07T03:23:34+00:00

    My issue is similar: I run three separate email accounts in Outlook: One O365 / Exchange account and two @MSN accounts which I have had since the days of the old MSN butterfly. They have worked flawlessly this way for years, however a new installation this week netted this precise NDR error Error is [0x80070005-0x0004dc-0x000524] when sending from one of the MSN accounts, which just happens to be the one used by my back office. The inability to send from it was making my work all but impossible.

    I took your detailed advice in the linked workaround posted above a step further because I am not able to make the change to my back office email in EAC as I do not have direct access to do so.

    In Outlook, I selected Address Book, Tools, Options, and the "Custom" radio button from "Check lists in this order". I removed all references to "Global Address Lists", including the offending GAL from my O365 account. Et voila! Mail can be sent, and I can choose the sender from the dropdown to easily change from any mailbox to make easy work of sending back office emails directly to clients! It is literally blowing my mind that I came across this post and I truly thank you!

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-04-11T20:09:30+00:00

    It's on the Ribbon in the Find group. I added this workaround as Workaround 2 in the Known Issue article, Classic Outlook error when sending from Outlook.com "You do not have permission to send on behalf of the specified user." - Microsoft Support.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-02-13T18:03:33+00:00

    Hi all,

    If you are still seeing this issue, I just posted a Known Issue with a workaround until we can get a fix, Classic Outlook error when sending from Outlook.com "You do not have permission to send on behalf of the specified user." - Microsoft Support. If you are able to try the workaround, please let me know if this helps. I can now repro the issue on demand and also confirmed the workaround on my test M365 tenant.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-03-03T15:45:34+00:00

    Workaround #2 is the best option, Classic Outlook error when sending from Outlook.com "You do not have permission to send on behalf of the specified user." - Microsoft Support. Are you able to use that workaround? You can hide the Outlook.com account you are sending from the Global Address List in the M365 account. Or, another option for the time being would be to remove that Outlook.com account from the M365 Exchange Online contacts until this gets fixed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-01-22T22:12:19+00:00

    I have not been able to resolve this and have not had any further responses from Microsoft. There also appears to be no available technical support line for Microsoft to contact on this matter...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments