Since I'm assuming that the Dovecot team were not planning on fixing shared folder replication since they were going to go for obox anyway, any chance one could revisit the shared folder issue again?
Shared folder replication #4
Hi @mumpfpuffel ,
I know about the missing support for shared folders (with replication) since a long time. That's the main reason, I did not use the feature in my setups in the past.
Unfortunately, the reason why it could not be used for replication is not replication itself but missing support for shared folders in dsync. Wormhole is just a fork of the removed replication code and still uses Dovecot's dsync. In fact, if I also would had have to fork the dsync code (the highly efficient mechanism in Dovecot to synchronize mailboxes across different machines), I probably would not have created this project.
So, if you want replication support for shared folders, you still have to generate a solution for the root problem: missing support of dsync shared folders or (to use the words of the Dovecot devs [https://doc.dovecot.org/2.3/configuration_manual/replication/]):
This is because there’s currently a per-user lock that prevents multiple dsyncs from working simultaneously on the same user. But with shared folders multiple users can be syncing the same folder. So this would need additional locks (e.g. shared folders would likely need to lock the owner user, and public folders would likely need a per-folder lock or maybe a global public folder lock). There are no plans to fix this.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?