On Sun, Nov 21, 2021 at 12:59:28PM -0500, Antoine Beaupré wrote:
https://anarc.at/blog/2021-11-21-mbsync-vs-offlineimap/
Let me know what you think.
well, apparently the manual page should mention the example file. ^^
(i don't want the examples inline, as i loathe excessively long manual
pages.)
the question about the renaming can be implictly answered by mentioning
https://cr.yp.to/proto/maildir.html, but i guess i can plainly say
"strip the ,U=xxx" just as well.
progress logging under systemd wouldn't work very well - each update is
actually a line, only ended with \r instead of \n (which translates into
\r\n). this would utterly dwarf the output you're getting with -V, which
you already found too noisy. i guess the progress meter should be
rate-limited, but the real point is that progress reporting is kinda
anti-thetical to background operation.
the syntax of the config file is as tricky as any DSL, but it's actually
quite minimalistic. i could do away with the "weird" colons by moving
the box names into Patterns; this actually mirrors an item from the TODO
file.
I'm particularly curious to hear about
performance on slow links, it seems like mbsync is significantly
impacted compared to SMD.
first make sure that the server uses compression, either via the
COMPRESS imap extension (you can watch the traffic with -Dn; use a cheap
action like -l) or via TLS (dunno how to test that - openssl s_client
might tell).
the base imap protocol that mbsync uses isn't very efficient for
resyncs. a proper fix would require using the QRESYNC extension, but
that's a major project (also in the TODO). as a workaround, you can do
partial syncs, though it may be challenging to automate that
sufficiently to make it both reliable and convenient when working with
multiple clients.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
