Write repair step that resyncs messages that have a broken message ID
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 48m
- Merged PRs (30d)
- 87
Description
We've fixed the issue that creates the broken message IDs (see https://github.com/nextcloud/mail/issues/5597), but we haven't fixed the database cache entries for them.
Write a repair step that looks for a broken message id (one that doesn't contain a closing angle bracket or any angle brackets at all).
Collect all UIDs, delete the database cache entries, and resync them from IMAP.
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 reading issue #5597 and locating the repair-step entry point in the project. Identify how broken message IDs are detected, how cache entries and UIDs are handled, and how IMAP resync is triggered. Done means affected UIDs are collected, their database cache entries are removed, and the messages are resynchronized from IMAP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100