IMAPMessage::toDbMessage overrides existing message IDs sometimes on bulkUpdate
Open
Nobody has claimed this yet.
1. to develop
bug
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Expected behavior
The existing message ID is kept when updating a DB record
Actual behavior
The message ID doesn't get set by the IMAP server, and thus will upadte the DB record to a new message ID creating faults in Tagging.
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 locating IMAPMessage::toDbMessage and the bulkUpdate path, then trace how an absent IMAP message ID is handled during database updates. Done means an existing database message ID remains unchanged when the server does not provide one, with a regression test covering that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100