From: Matthias A. <mat...@gm...> - 2020-12-03 00:17:12
|
Am 02.12.20 um 23:57 schrieb Joe Acquisto-j4: >> Am 02.12.20 um 22:02 schrieb Joe Acquisto-j4: >>> fetchmail: 6.3.26 Now gettting this error: >>> >>> fetchmail: OpenSSL reported: error:1416F086:SSL >> routines:tls_process_server_certificate:certificate verify failed >>> fetchmail: mail.xxxhost.com: SSL connection failed. >>> fetchmail: socket error while fetching from in...@jb...@mail.xxxhost.com >>> fetchmail: Query status=2 (SOCKET) >>> >>> Cert on my end appears valid. >> Oh, and in case mail.xxxhost.com is the true name, I offer my apologies >> for assuming it were made up, then the operator of mail.xxxhost.com >> needs to fix the certificate and/or configuration, or you need to >> configure to poll from an alternative hostname that is vacares.com or >> ends in .vacares.com. >> >> . . . > It was an obfuscated name, out of habit. > > gnutls seems to like the cert, though it would not connect on 993, resorted to 443. Well, 993 is for IMAP under TLS wrapper, and 995 for POP3 under TLS wrapper, or you tell that tool to do starttls and use 110 (POP3) or 143 (IMAP). Resorting to HTTP may or may not work - there may be transparent proxies, different certificate configuration for web vs. mail service, so the results may not transfer. > I can post the output if you think it of any value. 995 might be POP3, or you could run gnutls or openssl such that they try starttls. > It appears to be an intermittent problem, I suspect maybe the other end is doing some > load sharing or updating. > > In any event I will try to update soon as I can. OK, so if problems persist, please provide the log, per https://www.fetchmail.info/fetchmail-FAQ.html#G3 Regards, Matthias |