for reference, isync has the CipherString option since v1.4, which could be used to work around this issue.
maybe the openssl/libssl package changed its default config, or maybe
the affected server simply had its configuration fixed. in either case
it wasn't an isync bug to start with.
