Hi, I just updated to isync 1.5.0, and now `mbsync -a` fails with a short error message (`read: unexpected EOF`). Calling mbsync for a single channel works fine. Verbose mode reveals that the execution for all channels fails with the error message above when synchronizing the second channel, so I played around with .mbsyncrc and changed the order of the channels.
To my surprise, I found working orders, and they all have one aspect in common (the only remote store using XOAUTH2 must come first). This is mysterious, because this channel occupied the third position in the initial order (which failed at the second channel). Although I found a practical solution (i.e. a working order), I would be grateful if someone could explain what is going on here. - Jan _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
