On 2024-08-16 16:50, Oswald Buddenhagen via isync-devel wrote: > On Fri, Aug 16, 2024 at 10:46:22AM +0200, Jan Eden via isync-devel wrote: > > Although I found a practical solution (i.e. a working order), I would > > be > > grateful if someone could explain what is going on here. > > > a bug, rather obviously. > > is the problem reproducible with `mbsync -ls`? > if not, with `mbsync -a -l`?
The problem is reproducible with both commands. > does specifying the stores/channels on the command line in different > orders yield different results, or does it depend only on the config > file? I get three different results when specifying the channels directly, depending on their order: 1. read: unexpected EOF 2. IMAP error: unexpected tag BAD 3. IMAP error: unexpected tag BAD read: unexpected EOF > run the simplest failing invocation through valgrind/memcheck. make sure > to build with -Og -g3, as otherwise the traces won't be too useful. I installed isync via homebrew (slightly altering the formula to compile with OAuth2 support), and am not familiar enough with the compile process to build the binary manually (sorry!). > if valgrind finds no problems, run with -Dn, one working and one failing > invocation, so we can compare the logs. it may also make sense to repeat > that with strace. > > mail me the logs in private. I did that and will send the logs. Interestingly, the working config prints the IMAP error message quoted above: ## faulty config ## $ mbsync -a -Dn > fail.log read: unexpected EOF ## working config ## $ mbsync -a -Dn > success.log IMAP error: unexpected tag BAD Thanks, Jan _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
