internetMessageHeaders not returned for Sent Items messages in Outlook Add-in
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
Start by reproducing the reported graphClient .api(...).select("internetMessageHeaders").get() call for equivalent Inbox and Sent Items messages in an Outlook Add-in. Record the SDK version and response differences; the issue is done when the cause is identified and headers are returned consistently, or the behavior is confirmed to be outside the SDK.
Written by the indexing model from the issue text.
Description
Describe the bug
When using the Microsoft Graph SDK for TypeScript in an Outlook Add-in, the API call with
select("internetMessageHeaders") does not return internet headers for messages located in the user’s Sent Items folder.
This issue occurs when attempting to fetch the internet headers of a previous message in the same conversation where the reply is being made to a message from Sent Items.
The same Graph SDK call works correctly for messages located in the Inbox folder and returns the expected internetMessageHeaders.
Observed behavior in Outlook Add-in:
-
Inbox messages → internetMessageHeaders returned correctly
-
Sent Items messages → internetMessageHeaders is missing or empty
This behavior is consistent when using the Graph SDK for TypeScript within the Outlook Add-in runtime.
Expected behavior
Using the Microsoft Graph SDK for TypeScript, the internetMessageHeaders property should be returned for a message regardless of whether it resides in Inbox or Sent Items
The message folder location should not affect the availability of internetMessageHeaders, especially when accessing messages within the same conversation in an Outlook Add-in.
How to reproduce
-
Create or open an Outlook Add-in that uses the Microsoft Graph SDK for TypeScript.
-
Identify an email conversation where:
- An original message exists in the Inbox
- A reply to that message exists in Sent Items
-
From the Outlook Add-in, attempt to fetch internet headers for both messages using the Graph SDK:
const message = await graphClient
.api(`/users/{userId}/messages/{messageId}`)
.select("internetMessageHeaders")
.get();
- Observe the response:
- For Inbox messages, internetMessageHeaders is returned as expected.
- For Sent Items messages, internetMessageHeaders is missing or returned as an empty array.
SDK Version
No response
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_
- Dominant language
- TypeScript
- Stars
- 44
- Forks
- 7
- Avg merge
- 12h 40m
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-typescript
-
ToTriage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoftgraph/msgraph-sdk-typescript#917 · 6 comments ·
-
status:waiting-for-triage ToTriage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoftgraph/msgraph-sdk-typescript#974 · 1 comment ·
-
status:waiting-for-triage ToTriage
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-typescript#912 · 1 comment ·
-
status:waiting-for-triage ToTriage type:feature
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
status:waiting-for-triage ToTriage type:feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoftgraph/msgraph-sdk-typescript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·