Bugzilla

I used the offline mode to create a 100% reproducible situation.

But the actual issue might be deeper and more severe: Unstable Internet. Even if the offline mode is not enabled, there are cases where the message is not transferred to the server and then gets thrown away. (Riding a train throu a tunnel). If IIRC, we have offline detection which switches to offline mode when the internet is away, but that has lag. So making IMAP read-only during offline would not solve the issue if offline mode is not (yet) enabled but internet is down.

This describes a somewhat different bug, but I still think it is worth mentioning to find the proper solution for *this* bug, which is a rock solid offline -> online IMAP handling. We should not depend on state detection and prevent the move/copy, but make sure that a message which is only in offline msgStore (I hope I use the right terminology here) never gets removed before it has been acknowledged by the server.

I used the offline mode to create a 100% reproducible situation.

But the actual issue might be deeper and more severe: Unstable Internet. Even if the offline mode is not enabled, there are cases where the message is not transferred to the server and then gets thrown away. (Riding a train throu a tunnel). IIRC, we have offline detection which switches to offline mode when the internet is away, but that has lag. So making IMAP read-only during offline would not solve the issue if offline mode is not (yet) enabled but internet is down.

This describes a somewhat different bug, but I still think it is worth mentioning to find the proper solution for *this* bug, which is a rock solid offline -> online IMAP handling. We should not depend on state detection and prevent the move/copy, but make sure that a message which is only in offline msgStore (I hope I use the right terminology here) never gets removed before it has been acknowledged by the server.