Dear all,Thanks for writing and maintaining the extremely useful isync package! I’m using version 1.1.2 of isync, as packaged in Debian “testing”, to synchronize with several IMAP servers. Very recently, after an upgrade of the libssl1.0.0 package from Debian version 1.0.1k-3 to 1.0.2a-1, mbsync stopped working for the IMAP server at my work. However, it is still working for another IMAP server that I use. Downgrading libssl1.0.0 to the old version makes the issue disappear.
In my ~/.mbsyncrc both remote IMAP accounts are defined according to the following scheme
IMAPAccount some-remote-account Host imap.some.org User myuser Pass secret UseIMAPS yes CertificateFile /home/cwg/14-x509-certs/some.pemWith the old libssl (1.0.1k-3), “mbsync -V” gives the following output (I only show the lines that are relevant for the remote account)
M: * OK The Microsoft Exchange IMAP4 service is ready. M: >>> 1 CAPABILITYM: * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN STARTTLS UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
M: 1 OK CAPABILITY completed.
M: >>> 2 LOGIN <user> <pass>
M: 2 OK LOGIN completed.
M: >>> 3 NAMESPACE
M: * NAMESPACE (("" "/")) NIL NIL
M: 3 OK NAMESPACE completed.
M: >>> 4 LIST "" "*"
With the newer libssl (1.0.2a-1), the same mbsync gives instead
Socket error from imap.cea.fr (1.2.3.4:993): Connection reset by
peer
I would like to see this issue resolved, but I’m not even sure whether it’s due to isync or openssl or our IMAP server. Any help on narrowing it down is appreciated.
Christoph
signature.asc
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
