Re: Fetchmail 6.4.1 not connecting to "mail.twc.com" using sslproto 'auto'

Matthias Andree <[email protected]> Sun, 29 Sep 2019 15:43:31 +0200
Newsgroups	gmane.mail.fetchmail.user
Message-ID	<[email protected]>
Am 29.09.19 um 14:53 schrieb Jerry:
> The old version of Fetchmail would connect and collect mail from my TWC
> mail account just fine. The new version is failing with this error
> message:

Jerry, "timeout" is suspicious and hints to network issues.

The usual drills is: no logs, no support.
http://www.fetchmail.info/fetchmail-FAQ.html#G3

And guess what, fetchmail 6.4.1 does work for me, without or with
--sslproto auto, I can connect to mail.twc.com.
This is on FreeBSD 12.0 RELEASE (OpenSSL 1.1.1a-freebsd  20 Nov 2018)
and Fedora 30 (OpenSSL 1.1.1d FIPS  10 Sep 2019)

> [mandree@hostA _build-asan]$ ./fetchmail mail.twc.com -u testuser -p
> imap --ssl --auth external -vv
> [...]
> fetchmail: 6.4.1 querying mail.twc.com (protocol IMAP) at So 29 Sep
> 2019 15:35:12 CEST: poll started
> Trying to connect to 107.14.73.68/993...connected.
> fetchmail: SSL verify callback depth 2: preverify_ok == 1, err = 0, ok
> fetchmail: Certificate chain, from root to peer, starting at depth 2:
> fetchmail: Issuer Organization: DigiCert Inc
> fetchmail: Issuer CommonName: DigiCert Global Root CA
> fetchmail: Subject CommonName: DigiCert Global Root CA
> fetchmail: SSL verify callback depth 1: preverify_ok == 1, err = 0, ok
> fetchmail: Certificate at depth 1:
> fetchmail: Issuer Organization: DigiCert Inc
> fetchmail: Issuer CommonName: DigiCert Global Root CA
> fetchmail: Subject CommonName: DigiCert SHA2 Secure Server CA
> fetchmail: SSL verify callback depth 0: preverify_ok == 1, err = 0, ok
> fetchmail: Server certificate:
> fetchmail: Issuer Organization: DigiCert Inc
> fetchmail: Issuer CommonName: DigiCert SHA2 Secure Server CA
> fetchmail: Subject CommonName: mail.twc.com
> fetchmail: Subject Alternative Name: imap.mail.twc.com
> [...]
> fetchmail: Subject Alternative Name: mail.twc.com
> fetchmail: mail.twc.com key fingerprint:
> 35:BF:5D:5D:DB:40:B7:C8:30:96:9F:4C:46:9C:15:2B
> fetchmail: SSL/TLS: using protocol TLSv1.2, cipher AES256-GCM-SHA384,
> 256/256 secret/processed bits
> fetchmail: IMAP< * OK IMAP4 server (InterMail vM.8.04.03.24.04
> 201-2389-100-175-1-20180501) ready Sun, 29 Sep 2019 13:35:12 +0000 (UTC)
> fetchmail: IMAP> A0001 CAPABILITY
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UIDPLUS NAMESPACE QUOTA
> fetchmail: IMAP< A0001 OK CAPABILITY completed
> fetchmail: Protocol identified as IMAP4 rev 1
> fetchmail: Authorization failure on [email protected]
> fetchmail: IMAP> A0002 LOGOUT
> fetchmail: IMAP< * BYE IMAP4 server terminating connection
> fetchmail: IMAP< A0002 OK LOGOUT completed
> fetchmail: 6.4.1 querying mail.twc.com (protocol IMAP) at So 29 Sep
> 2019 15:35:13 CEST: poll completed
> fetchmail: Query status=3 (AUTHFAIL)
> fetchmail: normal termination, status 3

_______________________________________________
Fetchmail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fetchmail-users
signature.asc (application/pgp-signature, 833 B)