Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Opening messages is slow: Phishing detection

Open
#13,162 0 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
php

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.

Description

1. to develop enhancement

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.

Dominant language
JavaScript
Stars
1k
Forks
363
Avg merge
1d 10h
Merged PRs (30d)
80

Getting set up

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.

More from nextcloud/mail

All issues in nextcloud/mail

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.