Hello, Today, I start experiencing issues when mbsync connects to an Outlook server. The relevant part in my config is (used to work flawlessly until today):
Host outlook.office365.com Port 993 CertificateFile /etc/ssl/cert.pem This is the output when running `mbsync -VD hw`: isync 1.5.0 called with: '-VD' 'hw' Reading configuration file ~/.mbsyncrc merge ops (in Channel 'hw'): ... N: [ 3] Callback leave list_store N: [ 3] Leave list_store N: [ 2] Callback leave connect_store N: [ 2] Leave connect_store Connecting to outlook.office365.com (52.98.236.146:993)... Socket error on outlook.office365.com (52.98.236.146:993): timeout. F: Callback enter bad store F: Enter cancel_store F: Leave cancel_store N: Enter free_store N: Leave free_store F: Callback leave bad store However, other clients seem to be able to connect to the IMAP server and when I tried openssl s_client -connect outlook.office365.com:993 -quiet -no_ign_eof I get the expected: depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA verify return:1 depth=1 C = US, O = DigiCert Inc, CN = DigiCert Cloud Services CA-1 verify return:1 depth=0 C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, CN = outlook.com verify return:1 * OK The Microsoft Exchange IMAP4 service is ready Any ideas on how to resolve this? I assume it's an isync issue, but I might be mistaken. -- Al ________________________________ Heriot-Watt University was founded in 1821 and is a registered Scottish charity (SC000278). _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel