net-mail/isync-1.3.0-r1 built with openssl 1.1 fails to connect to some sites. For example, when trying to use imap.gmail.com, I get the following failure: SSL error connecting imap.gmail.com (173.194.207.109:993): self signed certificate The problem seems to stem from openssl 1.1 now defaulting to TLS 1.3, and isync not setting the SNI (server name indication), which causes the destination imap server to send the wrong certificate. I have verified that isync-1.3.1 does work correctly, and this probably could be fixed by backporting https://sourceforge.net/p/isync/isync/ci/17babc1695e82ca80d032b79e920fcb86ede2347/ to isync-1.3.0, if we still desire to build this version. Reproducible: Always Steps to Reproduce: 1. Write the attached config file to a file, say /tmp/mbsyncrc. 2. Create an empty maildir directory (in an empty directory, create "tmp", "new" and "cur" subdirectories). 3. Edit /tmp/mbsyncrc to fill in an account name, password, and path to maildir. 4. Make sure gmail account is configured to allow "legacy" applications. 5. Run "mbsync -c /tmp/mbsyncrc -a" Actual Results: SSL error connecting imap.gmail.com (173.194.207.109:993): self signed certificate Expected Results: It should connect and synchronize the mail boxes.
Created attachment 592828 [details] Sample mbsyncrc file This is a sample config file for connecting to gmail.
Since this error happens early, it is probably not necessary to use this with a valid gmail account. It will fail with the certificate error before validating the user and password in the config file.
Maybe then 1.3.1 should be stabilised.
This is kind of stupid. Let's stabilize.
amd64 stable
x86 stable, closing
