Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing .eml Extension in the file name and Null MIME Type for .eml Attachments #2712

Open
aashima-cloudextend opened this issue Oct 16, 2024 · 0 comments
Labels
type:bug A broken experience

Comments

@aashima-cloudextend
Copy link

Describe the bug

When retrieving .eml file attachments using the Microsoft Graph SDK for Outlook mail items, the attachment name does not include the .eml extension, and the content-type/mime-type is returned as null. This results in improper handling of .eml files on the client side.

Expected behavior

When fetching .eml attachments, the expected output should include:

The attachment name should be formatted as attachment.eml.
The content-type/mime-type should be message/rfc822 or similar, indicating that the file is an email message.

Expected behaviour with the example of pdf file and the existing behaviour for .eml file
image

How to reproduce

Make an API call to retrieve a message that contains an .eml attachment using the endpoint:
GET https://graph.microsoft.com/v1.0/me/messages/{messageId}/attachments
Identify an attachment with the .eml type from the response.
Call the endpoint to get the content of the attachment:
GET https://graph.microsoft.com/v1.0/me/messages/{messageId}/attachments/{attachmentId}/$value
Observe that the name of the attachment does not include the .eml extension and that the content-type/mime-type is null.

SDK Version

5.16.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@aashima-cloudextend aashima-cloudextend added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Oct 16, 2024
@shemogumbe shemogumbe removed the status:waiting-for-triage An issue that is yet to be reviewed or assigned label Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

2 participants