MIME upload email content with microsoft graph
Graph API allows me to get the MIME content of email calling following graph api request: GET https://graph.microsoft.com/beta/me/messages//$value .
As we work on O365 app which changes content of email, it would be great to have possibility to edit the MIME content thru PUT operation.
In addition, apps should be able to create new messages using MIME content.
Any updates on this?
Do you consider it?
The product I work on requires the option to create new messages using MIME content.
Tyler Bream commented
Agreed. We have been looking for this functionality, but are using the EWS API's for now. It would be really nice to be able to use a single api instead of multiple API's to get the desired functionality.
Nhan Thuan Nguyen commented
Yes, I totally agree that there should support a method to import the MIME/RFC-822 message to the desired folder.
Jeff McKay commented
Just to add my voice - yes the ability to import a MIME/RFC-822 message is critical. Along with many other missing features that make Graph inferior to EWS. Is anybody at Microsoft working on this stuff? Would be nice if they posted some kind of schedule of updates/fixes. But it was nice to see that they have delayed getting rid of basic authentication in EWS for year, due to Covid.
Pashkovich, Anatoly commented
It looks odd that you can get message in MIME format but can't put. We really need this API to be implemented.
Scott Morrison commented
This lack of this ability seems to me to to be a major deficiency in Graph to be used a a API for a Mail client. Mail clients need to be able to transfer messages faithfully (with all mime parts and headers) from a external (eg IMAP account) into a Graph account.
This is possible via EWS SOAP interface and is sorely missing in Graph.
Abhishek Kumbhaj commented
Should support setting MIME and saving the message to desired folder
Paul Colby commented
Just to clarify, the "full fidelity" format provided by EWS is not the same as the eml file format used by Outlook. It's actually based on (possibly identical to) the Fast Transfer stream format defined in [MS-OXCFXICS].pdf, but officially opaque in the EWS specification [MS-OXWSBTRF].pdf.
But yes, I definitely want this feature too. And agree that Graph API cannot claim feature parity with EWS without it.
Rafael Masson commented
It should also be possible to create a new *non-draft* message like the APPEND command does in IMAP. I opened a specific feature request for this: https://microsoftgraph.uservoice.com/forums/920506-microsoft-graph-feature-requests/suggestions/39296704-create-a-non-draft-message-via-mime-content-lik
Rafael Masson commented
We should be able to post MIME email content to create a new message (that *isn’t* a draft). Just to allow copying an email coming from another email account, which is a basic feature of any email client. In IMAP parlance, this is the APPEND command. It’s currently impossible to support this functionality when building an email client that uses the Microsoft Graph API.
Requirement - Graph API support for O365 email export/import in eml (binary) format
EWS provides support to export and import emails in the said format, this is particularly useful when we require export of an email or any item with full fidelity that includes all meta-data and attachments.
While Graph API can provide us all the meta-data, but import of an eml file is not permitted. Looking forward for this feature, as this can be used to backup mails on my local machine and restore if it is lost for some reason.
This will also ensure, feature parity between EWS API and Graph API
Graph API for email should support uploading of email MIME.
Advait Toraskar commented
As the Graph API now allows clients to retrieve the MIME content of an Email Message, it would be great if a new mail instance can be created using MIME instead of assigning individual properties i.e the Create Message endpoint should have support for uploading MIME Content.
DHONDT Yves (ENGIE Energy Management) commented
Being able to set the MIME content is useful in the case of signed and encrypted emails.
Most external libraries for generating SMIME content allow the MIME content to be exported. Being able to import that content in the Microsoft Graph API would enable scenarios where secure mails can be sent.
The EWS API supports setting message content via the UpdateItem method (as documented here https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/updateitem-operation).
The product I work on requires the same functionality to be available via MS graph to be able to migrate to it.