On Tue, 2014-10-14 at 20:31 +0200, Ángel González wrote: > Milan Crha wrote: > > On Tue, 2014-10-14 at 13:54 +0100, Pete Biggs wrote: > > > > > > > I'm not an SSL expert, but is there some manual way of instigating > > > the SSL connection with the server to see what algorithms are being > > > offered? > > Pete, you may inspect them looking at a packet capture (eg. wireshark), > which is what I asked Kevin if he could provide.
I'll have a look at doing that tomorrow - too late now! > > Try executing: > $ gnutls-cli imap.mail.me.com -p 993 > That connected OK: ======= $ gnutls-cli imap.mail.me.com -p 993 Processed 153 CA certificate(s). Resolving 'imap.mail.me.com'... Connecting to '17.172.34.111:993'... - Certificate type: X.509 - Got a certificate list of 3 certificates. [info on 3 certificates here] - Status: The certificate is trusted. - Description: (TLS1.2-PKIX)-(RSA)-(AES-128-GCM)-(AEAD) - Session ID: xxxxxxxx - Version: TLS1.2 - Key Exchange: RSA - Cipher: AES-128-GCM - MAC: AEAD - Compression: NULL - Handshake was completed - Simple Client Mode: * OK [CAPABILITY st11p00mm-iscream010 14G XAPPLEPUSHSERVICE IMAP4 IMAP4rev1 SASL-IR AUTH=ATOKEN AUTH=PLAIN] iSCREAM ready to rumble (14G:4357) st11p00mm-iscream010 [46:4135:21:49:20:80] ======== So I suppose I need to see what Evo is doing to see why it can't connect. P. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
