From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: fetchmail 6.4.0.rc3-1
Date: Thu, 29 Aug 2019 01:47:00 -0000 [thread overview]
Message-ID: <fd184d4d-65d3-17e7-9279-b823138639b0@gmail.com> (raw)
In-Reply-To: <6b849bb1-c86e-0fe5-9ece-ad9d5ed180a6@ChinaBuckets.com>
On 8/28/2019 8:15 PM, Eliza wrote:
> I still got the error:
>
> 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
You probably have to (re)install (package) ca-certificates.
Or, if you are using your own installed certificate, it may be installed
in the wrong place (i.e. that causes the not found error seen above, its
either not installed, or not in the right place).
HTH
--
R.Berber
--
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
next prev parent reply other threads:[~2019-08-29 1:35 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 [this message]
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
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=fd184d4d-65d3-17e7-9279-b823138639b0@gmail.com \
--to=rene.berber@gmail.com \
--cc=cygwin@cygwin.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).