none
Exchange server replies 103 to my EAS SendMail command RRS feed

  • Question

  • All my other requests like Sync, FolderSync, Provision work well so far. But the server responds 200 OK with wbxml body that says status is 103 several seconds after I send the SendMail request (all of the other responses I got so far are returned immediately. Not sure if this matters). In the response header, we have:

    X-MS-ASError: Message = Invalid Root Node. Expected: 'SendMail' Found: 'WbxmlConversionError'; Severity = Error

    My request is as follows (personal info like email addresses masked out):

    POST /Microsoft-Server-ActiveSync?User=xxx&DeviceType=SP&DeviceId=mztb4fe7e0a1da2dc4b7af79241cbbe9&Cmd=SendMail

    MS-ASProtocolVersion: 14.0

    Content-Type: application/vnd.ms-sync.wbxml

    Accept: */*

    Authorization: Basic a2g...(mask out)

    host: ...(mask out)

    Body stream with my decoding :

    03 01 6a - <?xml version="1.0" encoding="utf-8"?>

    00 - string table

    00 15 - page switch to ComposeMail

    45 - <SendMail xmlns:”ComposeMail">

    51 - <ClientId>

    03 31 35 32 33 35 00 - string “15235”

    01 - </ClientId>

    08 - <SaveInSentItems/>

    50 - <Mime>

    C3 - OPAQUE

    00 00 00 AF - length

    46 72 6F 6D 3A 20 4D 65 40 61 2E 63 6F 6D 0D 0A - From: Me@a.com\r\n

    54 6F 3A 20 54 65 73 74 40 61 2E 63 6F 6D 0D 0A -To: Test@a.com\r\n

    43 63 3A 20 0D 0A - Cc: \r\n

    42 63 63 3A 20 0D 0A - Bcc: \r\n

    53 75 62 6A 65 63 74 3A 20 57 68 79 0D 0A - Subject: Why\r\n

    4D 49 4D 45 2D 56 65 72 73 69 6F 6E 3A 20 31 2E 30 0D 0A - MIME-Version: 1.0\r\n

    43 6F 6E 74 65 6E 74 2D 54 79 70 65 3A 20 74 65 78 74 2F 70 6C 61 69 6E 3B 20 63 68 61 72 73 65 74 3D 22 69 73 6F 2D 38 38 35 39 2D 31 22 0D 0A - Content-Type: text/plain; charset=\"iso-8859-1\"\r\n

    43 6F 6E 74 65 6E 74 2D 54 72 61 6E 73 66 65 72 2D 45 6E 63 6F 64 

    69 6E 67 3A 20 62 61 73 65 36 34 0D 0A - Content-Transfer-Encoding: base64\r\n

    0D 0A - \r\n

    62 6D 39 30 49 48 64 76 63 6D 73 68 - “not work!”(transferred to base64)

    01 - </Mime>

    01 - </SendMail>

    What did I miss?


    • Edited by xxxken Friday, April 13, 2018 9:13 PM
    Friday, April 13, 2018 5:22 PM

All replies

  • Hi xxxken,

    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

    Friday, April 13, 2018 8:46 PM
    Moderator
  • Hello xxxken:

    I'll be helping you with this inquiry. Kindly send fiddler trace of the scenario to dochelp at Microsoft.com for further analysis. In addition, please confirm if the target server is on-prem Exchange server or Exchange Online.

    Thanks


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Friday, April 13, 2018 9:25 PM
  • just notice that length should be multi-byte integer format....let me try that first
    Friday, April 13, 2018 9:35 PM
  • Hi, thanks for your contact. I just solved the problem. The length should be mb. I completely ignored this.
    Friday, April 13, 2018 10:13 PM
  • Hello xxxken:

    Thank you for the update and glad that your issue got resolved.

    You can use EASTester tool to generate working traces and compare with yours, here are the examples of sample requests in that tool:  https://github.com/dseph/EasTester/tree/master/EASTester/EASTester/Examples

    In addition, we have a EAS fiddler inspector that can decode EAS specific fiddler traffic: https://blogs.msdn.microsoft.com/webdav_101/2015/07/21/eas-inspector-for-fiddler-1-4/

    Hopefully these resources will help you in the development.

    Thanks.


    Tarun Chopra | Escalation Engineer | Open Specifications Support Team

    Friday, April 13, 2018 10:41 PM