From: Andrey Repin <anrdaemon@yandex.ru>
To: Eliza <eli@ChinaBuckets.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: fetchmail 6.4.0.rc3-1
Date: Thu, 29 Aug 2019 21:26:00 -0000 [thread overview]
Message-ID: <1126181359.20190829234126@yandex.ru> (raw)
In-Reply-To: <abebcd1b-7831-0d02-26cd-d2ad74bcf09f@ChinaBuckets.com>
Greetings, Eliza!
> fetchmail -v got the same error at the bottom lines.
> unable to get local issuer certificate
> fetchmail: Broken certification chain at: /C=US/O=DigiCert
> Inc/OU=www.digicert.com/CN=GeoTrust RSA CA 2018
> fetchmail: This could mean that the server did not provide the
> intermediate CA's certificate(s), which is nothing fetchmail could do
> anything about. For details, please see the README.SSL-SERVER document
> that ships with fetchmail.
> fetchmail: This could mean that the root CA's signing certificate is not
> in the trusted CA certificate location, or that c_rehash needs to be run
> on the certificate directory. For details, please see the documentation
> of --sslcertpath and --sslcertfile in the manual page.
> fetchmail: OpenSSL reported: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify failed
Point --sslcertfile to /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
--
With best regards,
Andrey Repin
Thursday, August 29, 2019 23:40:57
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-08-29 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 12:53 Corinna Vinschen
2019-08-29 1:35 ` Eliza
2019-08-29 1:47 ` René Berber
2019-08-29 2:54 ` Eliza
2019-08-29 3:05 ` René Berber
2019-08-29 4:48 ` Eliza
2019-08-29 19:20 ` René Berber
2019-08-29 21:26 ` Andrey Repin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126181359.20190829234126@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=eli@ChinaBuckets.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).