Oswald Buddenhagen <[email protected]> writes: > On Wed, May 29, 2013 at 02:54:34PM +0800, Eric Abrahamsen wrote: >> but I'd have to think about moving messages between groups, and how >> badly I would want that propagated. >> > one possible approach would be syncing the accounts separately, and then > merging and virtualizing them with notmuch or a similar tool on the > client side. as long as the moving operations are properly mapped back > to the same physical mailboxes, propagation should work.
Whoa, that's interesting. And confusing! I'll give it some research. >> So even with a single account, I would still need a single dovecot >> invocation for each mailbox, is that right? >> > i presume you mean s/dovecot/mbsync/? if so, no, you can sync an > arbitrary number of boxes in one run. it's still independent channels, > though. No, I meant dovecot -- I was thinking again of the original workflow I had planned: mbsync to bring the messages down to maildirs, and then accessing those maildirs in gnus via dovecot (which would allow two-way syncing). Each "server" in gnus is a single invocation of dovecot, which I think would mean separate servers for each box of each account, which seemed excessive. But who knows, I have to admit this is all more flexible (and thus abstruse) than I expected. ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
