Opening messages is slow: Metadata endpoint
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
Follow up for https://github.com/nextcloud/mail/issues/10384 and https://github.com/nextcloud/mail/issues/13162
Is your feature request related to a problem? Please describe.
Opening a message currently fires separate backend requests for DKIM, itineraries, and (once deferred, #13162) the phishing check. Each request opens its own IMAP connection.
Describe the solution you'd like
Merge DKIM, itineraries, and phishing into a single metadata request. The implementation must use one IMAP connection and reuse the message already fetched/cached for the body instead of re-fetching.
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.
Research direction
Start by tracing the message-opening flow and the separate DKIM, itineraries, and phishing metadata requests described in the issue. Check how the message body is fetched or cached, then verify that one metadata request uses one IMAP connection and reuses that message without fetching it again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- api, backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100