microsoftgraph / microsoftgraph/msgraph-metadata

Missing MIME Format Path for `SendMail` and `CreateReply` actions

Open
#389 1 comment 0 reactions 1 assignee View on GitHub

@irvinesunday is already working on this.

Since Jul 26, 2023.

Area: SDK priority:p1
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

The API supports sending mail using MIME format by specifying the MIME content as a base64-encoded string in the request body as shown in the example at https://learn.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=powershell#example-4-send-a-new-message-using-mime-format:

POST https://graph.microsoft.com/v1.0/me/sendMail
Content-type: text/plain

RnJvbTogQWxleCBXaWxiZXIgPEFsZXhXQGNvbnRvc28uY29tPgpUbzogTWVnYW4gQm93ZW4gPE1l
Z2FuQkBjb250b3NvLmNvbT4KU3ViamVjdDogSW50ZXJuYWwgUmVzdW1lIFN1Ym1pc3Npb246IFNh
bGVzIEFzc29jaWF0ZQpUaHJlYWQtVG9waWM6IEludGVybmFsIFJlc3VtZSBTdWJtaXNzaW9uOiBT
YWxlcyBBc3NvY2lhdGUKVGhyZWFkLUluZGV4OiBjb2RlY29kZWNvZGVoZXJlaGVyZWhlcmUKRGF0
ZTogU3VuLCAyOCBGZWIgMjAyMSAwNzoxNTowMCArMDAwMApNZXNzYWdlLUlEOgoJPE1XSFBSMTMw
MU1CMjAwMDAwMDAwRDc2RDlDMjgyMjAwMDA5QUQ5QTlASFdIUFIxMzAxTUIwMDAwLmNvZGVudW0u
cHJvZC5vdXRsb29rLmNvbT4KQ29udGVudC1MYW5ndWFnZTogZW4tVVMKWC1NUy1IYXMtQXR0YWNo
OgpYLU1TLVRORUYtQ29ycmVsYXRvcjoKWC1NUy1Fe

This representation is currently absent in the metadata which leads to downstream tooling and SDKs not generating paths for sending mail in MIME format. Here is the current representation of the OData action in metadata:

<Action Name="sendMail" IsBound="true">
  <Parameter Name="bindingParameter" Type="graph.user" />
  <Parameter Name="Message" Type="graph.message" Nullable="false" />
  <Parameter Name="SaveToSentItems" Type="Edm.Boolean" />
</Action>

Originally reported at https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/844.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.