Opening messages is slow: Phishing detection
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Follow up for https://github.com/nextcloud/mail/issues/10384
Is your feature request related to a problem? Please describe.
Opening a message must be quick.
The /body (and HTML body) response must not be blocked by checks that can run afterwards.
Describe the solution you'd like
Defer the phishing check off the /body path, the same way DKIM and itineraries are deferred, so it no longer delays body delivery. The deferred check must reuse the already-fetched/cached message rather than trigger an extra IMAP fetch.
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 at the /body response path and trace how phishing detection currently runs. Compare the deferred DKIM and itineraries checks, then verify how the already-fetched or cached message is reused instead of causing another IMAP fetch. Done means body delivery no longer waits for phishing detection and the deferred check avoids an extra fetch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100