Search code examples
outlookoffice-jsoutlook-web-addinsoutlook-restapimicrosoft-graph-mail

Outlook API, Message Moved to "Sent Items" still beign marked as "[Draft]"

I'm working on an Outlook Add-in, using office.js, where users can send secure emails using backend service.

In compose mode, when the user sends the email, using the add-in of course, the add-in will then move the message to "Sent Items" folder using the Outlook API /message/{id}/move and everything goes OK with the exception that the message in question still being marked as "Draft" by Outlook which is really annoying and does confuse the user who just sent the email by telling him that "this message hasn't been sent"

enter image description here

I searched through the API to see if there is a way to mark an email as "SENT" in order to prevent Outlook from showing this RED hint but with no luck so far!

So, My Question Is: Is there any way to overcome this misleading msg by marking the email as it was sent by Outlook?

Thanks in advance.

Solution

  • Finally, I was able to achieve a perfect solution for this challenge.

    Based on:

    The approach/steps I followed to mark a mailItem as "SENT" (and not shown as 'draft') and put it in "SentItems" Folder are as follow:

    • First, Save the mailItem as "draft" using Office.context.mailbox.item.currentMail.saveAsync then retrieve its ID
    • Clone this draft mailItem properties eg: 'Sender', 'Subject', 'Body', 'ToRecipients'..etc so you get an exact copy of it.
    • With the newly cloned mailItem, add '[SingleValueExtendedProperties]' property with this value :
    [
  {
     PropertyId: 'Integer 0x0E07',
     Value: '1'
  }
];
    • Serialize the new item as JSON and POST it to "sentitems" folder as follows: 
    xhr.open('POST', restHost + '/v2.0/me/MailFolders/sentitems/messages/');
xhr.send(clonedEmailJson);
    • On success, with xhr.status=201 [created], Remove the draft mailitem using a [DELETE] request

    And you will end up having a new mail item created in your "sentItems" folder which appears as it was sent by Outlook :)

    This was a very helpful solution to me because my users are using my add-in to send secure emails (using 3rd party API) and NOT Outlook, So, I wanted them to have the same UX/feeling as when they use Outlook.

    Note:

    Although the solution worked for me perfectly, it came with a price! On slow internet connections or in case emails containing large attachments, the process can be remarkably slow, because the addin will first save the draft to the remote Exchange Server, get its ID, then duplicate it and send it again to the server, then remove the draft-ed one.