Moving email conversations sometimes necessary several times
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- An email conversation with multiple replies
- Click on "move conversation" (DE: Unterhaltung verschieben)
- Select a folder in your mailbox
Expected behavior
The entire conversation is moved to the selected folder.
Actual behavior
After moving the conversation, you will receive a notification that a new email has arrived. Then, without reloading the page, an email within this mail conversation will reappear in your mailbox inbox. This can happen several times, depending on the size of the conversation.
You then have to manually move this “new” unmoved email/email conversation to the desired folder and repeat this until it is actually moved and does not reappear in your inbox after moving.
This doesn't happen all the time, just now and then. I have no idea what could be causing it. I can't see any error messages or anything like that in the logs.
Mail app version
5.6.10
Nextcloud version
32.0.3
Mailserver or service
No response
Operating system
No response
PHP engine version
PHP 8.3
Nextcloud memory caching
No response
Web server
None
Database
None
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
Reproduce the issue in the Nextcloud Mail app using a conversation with multiple replies and the reported move-conversation steps. Start by tracing the move and subsequent new-mail notification behavior, then verify that the entire conversation remains in the selected folder without reappearing in the inbox or requiring repeated moves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100