Consider Internal Addresses in Phishing Detection
Open
Nobody has claimed this yet.
1. to develop
enhancement
- 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.
As a Nextcloud Mail user, I find the phishing warnings confusing when the sender is listed in my internal address list.
Describe the solution you'd like
Please take internal addresses into account and hide the phishing warning for these senders.
Describe alternatives you've considered
No response
Additional context
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 phishing-warning behavior and how the internal address list is read in the Mail app. Confirm how sender addresses are compared, then make the warning stay hidden for matching internal senders while preserving warnings for other messages. Verify the behavior with the relevant existing tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100