Forum Discussion

O365SupportKapil's avatar
O365SupportKapil
Copper Contributor
Apr 13, 2020

Issue in SendOnBehalfTo

I Have a client having issue while trying to sendonbehalf email from Shared Mailbox which end user have SendOnBehalfTo permission. When he select From address following error occurred and email not delivered but there is work around if He click on other email address and put sharemailbox email ID manually it works; What is reason behind that and how to fix this?

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

Subject: test
Sent: 4/13/2020 12:16 PM

The following recipient(s) cannot be reached:

Kapil Dev on 4/13/2020 12:16 PM
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: 1d732c71-1d73-4345-9479-719fc4a10f85
X-ServerApplication: Exchange/15.20.2921.022
X-FEServer: CH2PR18CA0013
X-BEServer: DM6PR13MB2476
X-CalculatedBETarget: DM6PR13MB2476.NAMPRD13.PROD.OUTLOOK.COM
X-RequestId: {00CCA698-5A1F-419A-98BD-0F0C4023A237}:245
X-ClientInfo: {825A36BD-7253-4A57-969F-7F4EE9371CB3}:163720047
X-ElapsedTime: 34
X-BackEndHttpStatus: 200
X-ResponseCode: 0
X-DiagInfo: DM6PR13MB2476
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 transport send message. ---> Microsoft.Mapi.MapiExceptionSendAsDenied: MapiExceptionSendAsDenied: Unable to transport send message. (hr=0x80070005, ec=1244)
Diagnostic context:
Lid: 35250
Lid: 36674 dwParam: 0x1
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0x2
Lid: 44866 dwParam: 0x0
Lid: 36674 dwParam: 0x7A
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0x5
Lid: 44866 dwParam: 0x1400
Lid: 36674 dwParam: 0xA
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0x16
Lid: 44866 dwParam: 0xD09
Lid: 36674 dwParam: 0xE
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0xD22
Lid: 44866 dwParam: 0x200
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=2819]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=160][latency=1]
Lid: 52176 ClientVersion: 15.20.2921.24
Lid: 50032 ServerVersion: 15.20.2921.6024
Lid: 35180
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropDeletePropsNoReplicate [122]
Lid: 27962 ROP: ropSetProps [10]
Lid: 27962 ROP: ropFlushRecipients [14]
Lid: 31418 --- ROP Parse Done ---
Lid: 35250
Lid: 36674 dwParam: 0xA
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0x2
Lid: 44866 dwParam: 0x18
Lid: 36674 dwParam: 0x4A
Lid: 61250 dwParam: 0x0
Lid: 45378 dwParam: 0x1D
Lid: 44866 dwParam: 0x0
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=126]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=512][latency=1]
Lid: 52176 ClientVersion: 15.20.2921.24
Lid: 50032 ServerVersion: 15.20.2921.6024
Lid: 35180
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropSetProps [10]
Lid: 27962 ROP: ropTransportSend [74]
Lid: 17082 ROP Error: 0x4DC
Lid: 44949
Lid: 21921 StoreEc: 0x4DC
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 38698
Lid: 41788
Lid: 44092
Lid: 41232
Lid: 60208
Lid: 37136
Lid: 34608
Lid: 55056
Lid: 42768
Lid: 56112
Lid: 52807
Lid: 33016 StoreEc: 0x4DC
Lid: 40748 qdwParam: 0x5BFDA10000000001
Lid: 57132 qdwParam: 0x0
Lid: 63016 dwParam: 0x4A
Lid: 39640 StoreEc: 0x4DC
Lid: 45434 Guid: 6095d98c-4543-4a1e-bc4b-69bcb0489292
Lid: 10786 dwParam: 0x0 Msg: 15.20.2921.022:DM6PR13MB2476:b603f39e-6088-4273-8a93-725d54e0e5ec
Lid: 51330 qdwParam: 0x8D7DFC5E6AD3702
Lid: 39570
Lid: 55954 dwParam: 0xA
Lid: 49266
Lid: 33010 dwParam: 0xA
Lid: 54258 Error: 0x0
Lid: 40002
Lid: 56562 dwParam: 0x0
Lid: 64146 dwParam: 0x4A
Lid: 33010 dwParam: 0x4A
Lid: 54258 Error: 0x4DC
Lid: 1750 ---- Remote Context End ----
Lid: 31418 --- ROP Parse Done ---
Lid: 22753
Lid: 21817 ROP Failure: 0x4DC
Lid: 34722
Lid: 51106 StoreEc: 0x4DC
Lid: 41890
Lid: 58274 StoreEc: 0x4DC
Lid: 59285
Lid: 46997 StoreEc: 0x4DC
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.Storage.MapiAccessor.TransportSendMessage(Object mapiObject, ExTimeZone timezone, PropValue[]& mapiPropValues)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.MapiAccessor.TransportSendMessage(Object mapiObject, ExTimeZone timezone, PropValue[]& mapiPropValues)
a


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(2), failure enum(13), HResult(0x80070005), EC(1244).

  • That's like rule #1 when working with send as/send on behalf of permissions - never ever select any pre-filled entry, either from the auto-complete cache or the from menu. Always make sure to select the address directly from the GAL.

    • O365SupportKapil's avatar
      O365SupportKapil
      Copper Contributor

      VasilMichev Thanks for you response.

      I opened a case with MS and I knew that - how should it work..

      this is what MS responded...

      Recommended Next Steps:

      When a shared mailbox is added as a New Account, Send on Behalf permissions won't work. Send on Behalf permissions only work when the account is auto mapped or added under the advanced mailbox settings.

      For one user, please remove the permissions for the shared mailbox and then add the permissions back using the following PowerShell Command: 

      • Add-MailboxPermission -Identity "Shared Mailbox" -User "User to Add" -AccessRight "Permissions to mailbox" -InheritanceType All -AutoMapping $True

      After the permissions have been applied and the mailbox automatically mapped in Outlook, please test the send of behalf permissions

      Also, on the same user's machine, after the shared mailbox has been automatically mapped, please run the advanced Outlook diagnostic: https://support.microsoft.com/en-us/help/4098558/scan-outlook-by-using-microsoft-support-and-recovery-assistant

      • Marko_Stevcic's avatar
        Marko_Stevcic
        Copper Contributor
        The simplest way to resolve this is to empty Outlook cache folder (AppData\Local\Microsoft\Outlook\RoamCache) and not use autocomplete form.
        *Back up the cache files so that you can restore the files if something goes wrong.
        Manually enter the email address you want to send the message to, or find the person you want to send mail to from the GAL.
    • jd-'s avatar
      jd-
      Copper Contributor

      VasilMichev what do you suggest if the address has been hidden from the GAL? Thanks


  • HelloO365SupportKapil !

    If it works to send on behalf when typing in the email address manually or by chosing it from the GAL then its not a permission error. 

     

    I've seen the same error message happen to me, and the issue then has been auto-complete in the "From" field. So i removed that , redownloaded the GAL and then chose the address from the GAL in the From address field. 

     

    Try that and you should not see this issue again 🙂 

     

    Kind regards
    Oliwer Sjöberg

Resources