Open elliefm opened 3 years ago
Partially addressed by #3706
Shared mailboxes are still a problem. Fixing that overlaps with some rename/create atomicity improvements we have in the cards, and it might be better to just wait until the updated APIs are ready.
On 3.5, this is bad. Probably need to forbid XFER of mailboxes that aren't top of a tree. I'm not sure what this means for shared mailboxes. Need a lot of tests, too!
XFER of a single mailbox into a 3.5 backend fails (the backend rejects it -- though I'm not sure whether deliberately, or accidentally). But if the original backend is 3.5 and the destination backend is 3.4 or earlier, the 3.5 backend will happily perform an XFER that the other backend will accept, and leaves behind a hole in the mailbox tree on the 3.5 backend.