On Sun, Jun 21, 2015 at 01:32:50PM +0200, Daniel Trstenjak wrote: > > i have no clue what that means, but most likely it has something to do > > with the fact that the tunneled server's ssl certificate does not match > > "mail". you can play with the "openssl s_client" command. if you get > > some more helpful error message, i'd be interested in that (to make > > mbsync more helpful as well). > > ~> openssl s_client -debug -host *** > connect: Connection refused > connect:errno=111 > well, you obviously need to specify the correct port.
> > i suspect that setting CertificateFile to what you get out of getcert > > will fix the problem. > > Thanks! Using the output of getcert seems to work now with this config: > excellent > > now, that obviously should not happen. > > I tried to debug it a bit and 'sock->fd' seems to be correctly > initialized at the beginning and then somehow later on to be > reset, but I didn't followed it until then. > don't worry, i'll debug it at some point. what mbsync version exactly are you using? ------------------------------------------------------------------------------ _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
