On Thu, Jul 22, 2021 at 08:20:04PM +0100, Sabahattin Gucukoglu via isync-devel 
wrote:
Without the workaround script below, CAPABILITY is never issued by mbsync, therefore the bodging is still in effect and I got bogus response [...]

ok, from what i gather the short version is that that proxy (?) simply replaces the first five occurrences of "CAPABILITY" sent by the server with "CAPABILITY XAPPLEPUSHSERVICE".

what would be interesting is figuring out whether that count is influenced by anything, e.g., the login, or starttls. to figure that out, you'd need to issue different numbers of capability commmands before the aforementioned commands and see how many subsequent capability commands are botched afterwards. knowing that is important for making the workaround reliable.


_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to