God knows why, but iCloud IMAP (imaps://imap.mail.me.com:993) bodges responses 
(even lines within literals) so that every occurrence of CAPABILITY is 
immediately followed by XAPPLEPUSHSERVICE, and STARTTLS preceded by a space 
character is discarded. I can only assume it’s some side-effect of trying to 
insert support for their push protocol behind a TLS terminator for a server 
that does not otherwise support it, perhaps. (And in which case, irony.)

Anyway the problem goes away and literal payloads all have the right sizes, and 
sync completes successfully, if I write a little wrapper script that just adds 
a CAPABILITY request immediately after login. Presumably that satisfies the 
workaround and IMAP becomes transparent again. If you can add this hack into 
isync, that would be cool.

Cheers,
Sabahattin



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

Reply via email to