office 365 / activesync 16 - error forwarding meeting RRS feed

  • Question

  • My ActiveSync client which consistently is able to forward meeting requests on ActiveSync version 12.1 through 14.1 is failing to forward the meeting. The ActiveSync smart forward operation is failing with a wbxml status 120 which corresponds to:



    The server failed to submit the message for delivery.

    Supported by: 14.0, 14.1, 16.0

    This is the same result on exchange 2013 as well as on Outlook 365.

    To reproduce this I open an event that I created in my calendar, then forward the meeting to a new recipient.

    The message looks like this - note that the boundary names and email address has been redacted.

    Date: Mon, 02 Nov 2015 17:30:52 +0100
    Subject: Fwd: test 
    Priority: normal
    X-Priority: normal
    References: 1:12
    To: TestUser Four <>
    MIME-Version: 1.0
    Content-Type: multipart/alternative;boundary=""
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: base64

    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: base64


    Looking at the activesync logs I can see that this is the server error

    RequestHeader : 
    POST /Microsoft-Server-ActiveSync/Proxy/default.eas?Cmd=SmartForward& HTTP/1.1
    Connection: close
    Content-Length: 1646
    Content-Type: application/
    Accept-Encoding: gzip
    Authorization: ********
    User-Agent: WorxMail/10.4-main iPhone/9.1
    X-MS-PolicyKey: 1903012562
    MS-ASProtocolVersion: 14.1
    X-MSExchangeActivityCtx: V=;Id=69feca70-0f79-4fae-8e70-fa9aa376a635;C=;P=
    X-ProxyTargetPort: 444
    X-ProxyTargetServerVersion: 1942061368
    X-DatabaseGuid: 23517351-04e1-4c17-b39e-05e80d564fd5
    X-GCC-PROXYINFO: ALHCYE5RBwHD/rQ1ne9I1dXfVk92ffFqsqIZeFQc1gewWQ0/+X3EKBIFHPTCpqpPHk1quwyq49II,,
    X-SourceCafeServer: AM3PR04CA0031.EURPRD04.PROD.OUTLOOK.COM
    X-IsFromCafe: 1
    X-CafeProxyHandler: NativeHttpProxy
    X-Forwarded-Port: 23796

    RequestBody : 
    <?xml version="1.0" encoding="utf-8" ?>
    <SmartForward xmlns="ComposeMail:">
    <Mime>[Mime Removed] BytesCount = 1594</Mime>

    Command_WorkerThread_Exception : 
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: 
    Exception level: 0
    HttpStatusCode: InternalServerError
    AirSyncStatusCode: MailSubmissionFailed
    [No XmlResponse]
    Exception stack trace:    at Microsoft.Exchange.AirSync.SendMailBase.SendMessage(MessageItem sendMessage)
       at Microsoft.Exchange.AirSync.SmartForwardCommand.ForwardUsingXso(StoreObjectId smartId)
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows...
    Exception type: Microsoft.Exchange.Data.Storage.SendAsDeniedException
    Exception message: Cannot submit message.
    Exception level: 1
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.CoreItem.Submit(SubmitMessageFlags submitFlags, Boolean performAntiSpamCheck)
       at Microsoft.Exchange.Data.Storage.MessageItem.InternalSend(StoreObjectId saveSentMessageFolder, SubmitMessageFlags submitFlags, Boolean doNotMove, Boolean performAntispamCheck)
       at Microsoft.Exchange.Data.Storage.MessageItem.Send(SubmitMessageFlags submitFlags)
       at Microsoft.Exchange.AirSync.SendMailBase.SendMessage(MessageItem sendMessage)
    Inner exception follows...
    Exception type: Microsoft.Mapi.MapiExceptionSendAsDenied
    Exception message: MapiExceptionSendAsDenied: Unable to submit message. (hr=0x80070005, ec=1244)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=124]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=328][latency=31]
        Lid: 52176   ClientVersion: 15.1.312.20
        Lid: 50032   ServerVersion: 15.1.312.6020
        Lid: 35180  
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropSubmitMessage [50]
        Lid: 17082   ROP Error: 0x4DC     
        Lid: 27745  
        Lid: 21921   StoreEc: 0x4DC     
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 37692  
        Lid: 44092  
        Lid: 64952   StoreEc: 0x3EB     
        Lid: 40748   qdwParam: 0xF01000000000001 
        Lid: 57132   qdwParam: 0xE012751C00000001
        Lid: 36423   dwParam: 0x0        Msg:
        Lid: 42092   StoreEc: 0x4DC     
        Lid: 58476  
        Lid: 10786   dwParam: 0x0        Msg: 15.01.0312.001:AM4PR08MB0785
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x4DC     
        Lid: 60547   StoreEc: 0x4DC     
        Lid: 21966  
        Lid: 30158   StoreEc: 0x4DC     
    Exception level: 2
    Exception stack trace:    at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiMessage.SubmitMessageEx(SubmitMessageExFlags submitMessageExFlags)
       at Microsoft.Exchange.Data.Storage.CoreItem.Submit(SubmitMessageFlags submitFlags, Boolean performAntiSpamCheck)
    --- Exception end ---

    AccessState : 

    AccessStateReason : 

    ResponseHeader : 
    HTTP/1.1 200 OK

    ResponseBody : 
    <?xml version="1.0" encoding="utf-8" ?>
    <SmartForward xmlns="ComposeMail:">

    Monday, November 2, 2015 5:14 PM

All replies

  • Lee,
    This forum handles requests related to Open Specifications documentation issues. The Open Specifications can be found at: Your question does not appear to be related to the Open Specifications documentation set.

    Based on the description of your inquiry, I suggest you try the following forums to get assistance:

    If you were implementing ActiveSync protocol on the client side, please let us know and we will review.
    [MS-ASCMD]: Exchange ActiveSync: Command Reference Protocol


    Monday, November 2, 2015 9:39 PM
  • Hi Edgar 

    I am implementing a commercial client side activesync client. I've posted a number of other questions in these forums here earlier - in particular which was related to a similar activesync protocol question.

    This question relates to the behaviour of the activesync protocol on activesync 16 and my understanding was this is the place that those questions can be resolved.

    I'll post the same question on the forum you suggested though.


    Monday, November 2, 2015 10:04 PM
  • Hi Lee,

    One of our engineers will review this and follow up with you.



    Tuesday, November 3, 2015 3:32 AM
  • Hello Lee :

    I'll be assisting you further. Can you please share exchange on-prem logs by sending as an attachment to email address : dochelp at for further analysis ?


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, November 3, 2015 6:33 AM
  • Hello Lee :

    Dropping a note to acknowledge that we have received your log files.

    We will continue to troubleshoot the issue through dochelp and post of our findings on this thread once issue is resolved.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, November 3, 2015 10:57 PM
  • We worked with Lee offline and suggested to implement the AccountId Element in the app's request to resolve the issue. AccountId (SendMail, SmartForward, SmartReply)

    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, January 5, 2016 9:49 PM
  • Hi Tarun Chopra, I am running into a similar issue. Do you know if including the AccountId resolved the issue? If not, do you have any other suggestions?
    Monday, October 24, 2016 2:29 PM
  • Hi IanRagsdale,

    Thank you for your question.  An engineer from the protocols team will contact you soon.

    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Monday, October 24, 2016 3:37 PM
  • Hello Ian:


    Following were the suggestions shared,however, we are not sure if it resolved the issue since Lee added it to the backlog:


    1. Specify following settings command settings:PrimarySmtpAddress ( )

    2. Send AccountId  element in the request ( AccountId (SendMail, SmartForward, SmartReply))  


    If AccountID is not specified and settings:PrimarySmtpAddress is not configured, SendAsDenied exception will be raised.



    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Tuesday, October 25, 2016 3:53 PM