On Mon, Sep 02, 2019 at 08:34:27PM +0200, Mathieu Carpentier wrote: > But the thing is that I'd like to know how mbsync handle the > situation. > you can try setting PipelineDepth to a low (one-digit) number to effectively limit bandwidth. other than that, you can use a rate-limiting local proxy (possibly via Tunnel if you find one that works with pipes), or configure a qdisc in your kernel. this has been asked before, so you may find something in the list archive.
> Will it be able to retry at next sync ? > yes > How can I be sure that mbsync fetched all messages ? > that might actually be a problem as far as elegant solutions are concerned; the topic has been repeatedly discussed on the list. my own background fetcher just greps mbsync's stderr, which is reliable enough. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
