Share via

Shared Mailbox send on behalf error from sys admin no perms when have perms

Anonymous
2023-02-15T21:49:25+00:00

Error code below with redacted names for privacy.

New shared mailbox, all permissions have been removed and re-added as a test.

Haven't tried any PowerShell commands yet was hoping to not have to.

Can open another mailbox through the Outlook Web app and it will send fine through there.

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

      Subject:     test

      Sent:  16/02/2023 10:46 am

The following recipient(s) cannot be reached:

      <Name> on 16/02/2023 10:46 am

            This message could not be sent. You do not have the permission to send the message on behalf of the specified user.

__________________________________________________

Diagnostic information for administrators:

__________________________________________________

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

Exchange response headers:

      request-id: 57b5ec93-a4a2-2aee-b9f8-7add4bea3e5a

      X-ServerApplication: Exchange/15.20.6086.026

      X-FEServer: SY5PR01CA0064

      X-BEServer: ME3P282MB2761

      X-CalculatedBETarget: ME3P282MB2761.AUSP282.PROD.OUTLOOK.COM

      X-RequestId: {F9539952-1918-4EDF-8684-D9607E80BD7C}:140

      X-ClientInfo: {89DF358C-3ED0-40AB-A38A-698500761286}:78640037

      X-ElapsedTime: 93

      X-BackEndHttpStatus: 200

      X-ResponseCode: 0

      X-DiagInfo: ME3P282MB2761

      X-RequestType: Execute

__________________________________________________

ROPs Summary:

      0: ropSetProps (10) Processed(1) Completed(0)

            ROP result: 0

            Response codes: 0

      1: ropSetProps (10) Processed(1) Completed(0)

            ROP result: 0

            Response codes: 0

      2: ropFlushRecipients (14) Processed(1) Completed(0)

            ROP result: 0

            Response codes: 0

      3: ropSetProps (10) Processed(1) Completed(0)

            ROP result: 0

            Response codes: 0

      4: ropTransportSend (74) Processed(1) Completed(0)

            ROP result: 0

            Response codes: 1244

__________________________________________________

Response Exceptions:

ROP Index: 4

ROP Associated: ropTransportSend (74)

Microsoft.Exchange.Data.Storage.SendAsDeniedException: Can't send message. ---> Microsoft.Mapi.MapiExceptionSendAsDenied: MapiExceptionSendAsDenied: Unable to send message. (hr=0x80070005, ec=1244)

0.35250:0A001A00, 1.36674:01000000, 1.61250:00000000, 1.45378:02000000, 1.44866:00000000, 1.36674:01000000, 1.61250:00000000, 1.45378:05000000, 1.44866:00000000, 1.36674:7A000000, 1.61250:00000000, 1.45378:08000000, 1.44866:00140000, 1.36674:0A000000, 1.61250:00000000, 1.45378:19000000, 1.44866:6C0E0000, 1.36674:0E000000, 1.61250:00000000, 1.45378:880E0000, 1.44866:09020000, 16.55847:A60B0000, 17.43559:0000000034020000000000000000000000000000, 20.52176:140FC6971A0000104B020000, 20.50032:140FC6978A17F01FA4000000, 0.53414:12000000, 0.35180:14000000, 255.23226:15000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.31418:5A020000, 0.35250:14004967, 1.36674:0A000000, 1.61250:00000000, 1.45378:02000000, 1.44866:18000000, 1.36674:4A000000, 1.61250:00000000, 1.45378:1D000000, 1.44866:00000000, 16.55847:7E000000, 17.43559:00000000E0030000000000000F00000000000000, 20.52176:140FC6971A00101077020000, 20.50032:140FC6978A17000058000000, 0.53414:7C020000, 0.35180:0A000B7C, 255.23226:5D000000, 255.27962:0A000000, 255.27962:4A000000, 255.17082:DC040000, 0.44949:86020000, 4.21921:DC040000, 255.27962:FA000000, 255.1494:8B020000, 0.38698:46000000, 1.41134:46000000, 0.37692:86000000, 0.44092:86000000, 0.40348:1A010480, 0.34608:00000000, 0.55056:1A010480, 0.42768:05000780, 0.56112:00000000, 0.52807:05000780, 1.41134:46000000, 4.33016:DC040000, 7.40748:010000000000010B05000780, 7.57132:000000000000000005000780, 4.39640:DC040000, 1.63016:4A000000, 8.45434:7E013AD8159377458891D197BEF27AC300000000, 1.46798:13000000, 5.10786:0000000031352E32302E363038362E3032363A4D4533503238324D42323736313A35336164306533332D376132322D343630622D393236362D3562313438323135363464373A32373339323A2E4E4554204672616D65776F726B20342E382E393033322E3000201000000000, 7.51330:57590BF89D0FDB0812000000, 0.39570:00000000, 1.55954:0A000000, 1.33010:0A000000, 2.54258:00000000, 0.40002:A4000000, 1.56562:00000000, 1.33010:0A000000, 2.54258:00000000, 0.40002:00000000, 1.56562:00000000, 1.64146:4A000000, 1.33010:4A000000, 2.54258:DC040000, 1.33010:4A000000, 2.54258:DC040000, 255.1750:E5020000, 255.31418:0A00403A, 0.22753:C1000000, 255.21817:DC040000, 0.34722:0A00773A, 4.51106:DC040000, 0.41890:EF020000, 4.58274:DC040000, 0.59285:CC000000, 4.46997:DC040000

   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException, MapiStore mapiStore)

   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException, MapiStore mapiStore)

   at Microsoft.Mapi.MapiBase.ThrowIfError(String message, Int32 hr)

   at Microsoft.Mapi.MapiMessage.TransportSendMessage(PropValue[]& propsToReturn)

   at Microsoft.Exchange.Data.StoreObjects.MapiAccessorExtensionMethods.TransportSendMessage(IStoreSession storeSession, Object mapiObject, ExTimeZone timezone, PropValue[]& mapiPropValues)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Data.StoreObjects.MapiAccessorExtensionMethods.TransportSendMessage(IStoreSession storeSession, Object mapiObject, ExTimeZone timezone, PropValue[]& mapiPropValues)

   at Microsoft.Exchange.Data.Storage.CoreItem.TransportSend(PropertyDefinition[]& properties, Object[]& values)

   at Microsoft.Exchange.RpcClientAccess.Handler.Message.TransportSend()

   at Microsoft.Exchange.RpcClientAccess.Handler.RopHandler.<>c__DisplayClass156_0.<TransportSend>b__0()

   at Microsoft.Exchange.RpcClientAccess.Handler.ExceptionTranslator.TryExecuteCatchAndTranslateExceptionsTResult

Transport-Send failed: failure enum(25), HResult(0x00000000), EC(1244).

Transport-Send failed: failure enum(22), HResult(0x00000000), EC(1244).

Submit-Message failed: message id(4), failure enum(13), HResult(0x80070005), EC(1244).

Outlook | Windows | Classic Outlook for Windows | For home

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

2 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-16T03:11:49+00:00

    Hi Simbarashe,

    This is purely office 365 online.

    No on site AD or service.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-02-16T02:25:17+00:00

    Hello Dale Chapman1,

    Good day! Thanks for posting in Microsoft Community. We are happy to assist you.

    May I know if you have a hybrid deployment of on-premises Exchange Server and Exchange Online in Office 365?

    The error message you are getting “This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524].” Is usually happens when The value of the LegacyExchangeDN attribute changes during the mailbox move. This issue occurs if the old LegacyExchangeDN attribute wasn't added as an X500 address to the email addresses for the recipient when the mailbox was moved.

    To solve this issue, you need to manually update the user's email addresses by adding the value of the LegacyExchangeDN attribute as an X500 address. To do this, determine what the X500 address is, and then add it to the user's email addresses. For detailed steps on how to determine and add the X500 address please see the attached document "0x80070005-0x0004dc-0x000524" error when a user sends updates to Calendar items that were created before Exchange Online migration - Microsoft Support

    We look forward to hearing from you; Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. Thank you for your cooperation.

    Sincerely,

    Simbarashe | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments