On 13 Dec 2021, at 17:49, Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > On Mon, Dec 13, 2021 at 02:26:13PM +0000, Sabahattin Gucukoglu via > isync-devel wrote: >> Not that I would wish to prejudice the author(s) of imapsync, another paid >> tool for IMAP migration, but what would it take for mbsync, whose interface >> and configuration I much prefer, to be usable for one-way syncs in the >> fashion of imapsync? > > that depends on what exactly is missing from your perspective.
One-way (possibly stateless) sync, with optional deletion of messages from the source, with optional removal of empty folders. I am aware that this can be implemented with a multi-stage process, but imapsync does it rather better for this particular use case (maintain a relationship with an existing provider, while making the transition to a self-hosted server or another provider) by maintaining a locally-hosted copy of what would be stored on the source at the destination. >> And, yes, I’ll pay for it. As patron, not as customer, you understand. :) > > to be pedantic about the terminology, "pay for it" means more or less "cover > the real cost of development at market prices". that would be anything from a > hundred to a few thousand euros, depending on how much needs to be done. > patronage or sponsorship (whether individual or crowd-sourced) would > minimally mean "cover subsistence", for a period of time that actually > matters. anything less is really just a token of appreciation - which is all > fine, but should be kept in mind to manage expectations. I specifically mean the latter, i.e. incentives should be aligned with your users because “the market” might not value user needs. Of course I reserve the right to say exactly how much, and for how long. :) Thanks for isync. It’s much appreciated. Cheers, Sabahattin _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
