thunderbird / thunderbird/thunderbird-android
Cannot copy or move message that is not synchronized with the server (IMAP)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Steps to reproduce:
Use "archive" for a message when you don't have an IMAP archive folder on the server.
Expected behaviour:
I only hit that function by accident. I have no idea what it is supposed to do.
But now that the email message is moved to a (local) archive folder, I expect to be able to move it back to the IMAP folder it was in before.
What happens instead:
When I select copy or move I get the message "Cannot copy or move message that is not synchronized with the server" (I use German language so that might not be the exact English phrase)
When I delete the message it goes to the Trash folder, but from there I cannot copy/move it either.
Effectively this email is kind of lost.
This is similar to a bug[*] in the old Google Code tracker at https://code.google.com/p/k9mail/issues/detail?id=861 which was never resolved.
[*]: I consider this a bug as there is no way of undoing this, no confirmation is required, but an IMAP message "archived" in this way is essentially gone for good
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 with the archive action and the copy/move handling described in the reproduction steps, then trace how messages without an IMAP archive folder are marked and synchronized. Verify the behavior for the local archive and Trash cases, and consider the issue complete when an archived message can be recovered or the destructive action is prevented with clear feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100