Case-sensitive address matching triggers "Reply All" incorrectly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Configure Nextcloud mail App for user@mail.com
- Send an email to User@mail.com
Expected behavior
User@mail.com should be considered as user@mail.com and reply button should only reply to the sender
Actual behavior
User@mail.com is considered as another user, and "Reply All" button is visible. When you reply, the reply is sent to the sender AND to yourself, because of case sensitive address matching.
Mail app version
5.6.7
Nextcloud version
32.0.2
Mailserver or service
postfix/dovecot
Operating system
debian
PHP engine version
PHP 8.3
Nextcloud memory caching
No response
Web server
Apache (supported)
Database
MariaDB
Additional info
No response
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 reproducing the case-sensitive address mismatch in the Nextcloud Mail app with the reported versions and inspect the logic behind the Reply and Reply All buttons. Trace how sender and recipient addresses are compared, then verify that differently cased equivalents are treated as the same address and that replying does not include the sender twice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100