When two accounts can be merged, how do you plan to handle their respective email folders #315
rustmailer
started this conversation in
General
Replies: 1 comment
|
Thx for looking into this! .. I'll need to look into this again and grind my gears.. my use case was/is as follows:
2 Situation:
Bottow line, i want to carry my MBOX Archive along and re-sync/update it anytime. In my case it will remain the same real EmailAccount. Not sure if this can be considered as Option C. since we do not merge two account but just re-enable a account for syncronisation |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
For example, if we merge Account A into Account B, both have their own list of folders.
In terms of concrete implementation, if we do a hard merge by changing all IDs from Account A to Account B, it would require a reindex, which is quite costly. So, I’m planning to do a soft merge instead by adding a virtual account layer. However, we need to decide how to handle the email folders. Folders from different accounts have their own unique IDs. Both the account ID and folder ID are directly stored as fields within a single document in the Tantivy index, alongside the email body index. I want to avoid rewriting all the documents from Account A.
Discussions based on actual use cases are always welcome. My original plan is that after the merge, at most one account will retain its IMAP configuration and continue downloading emails. Its maximum UID for each folder will be preserved. Even if the maximum UID is lost, it can still be calculated locally. Meanwhile, the merged virtual account will not act as a sub-account for any other merged accounts.
All reactions