On Thu, Aug 01, 2019 at 06:12:28PM +0530, Pankaj Jangid wrote: > Is this of any use? -> > it doesn't tell us anything except that no reply came when one was expected.
that's why i suggested strace - then you'll see whether there is *actually* no reply, or mbsync just doesn't see it due to some bug. however, with mbsync's internal openssl handling, the problem is that you won't see whether the commands were *really* sent or already got stuck in the output queue, because the syscalls will see encrypted traffic. you can only make an estimate based on the expected data size, but that may be hard due to tls overhead and compression. you won't have that problem with the s_client Tunnel, because then mbsync's own syscalls shuffle only plaintext. also, if the problem just disappears, it's a safe bet that mbsync's openssl handling is to blame. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
