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 03:05:00 -0000 [thread overview]
Message-ID: <6d0543c0-3aff-1fa8-7cf5-399ac4aecea1@gmail.com> (raw)
In-Reply-To: <7803ce5e-0a58-1b1f-4699-6d1d75f50f30@ChinaBuckets.com>
On 8/28/2019 8:46 PM, Eliza wrote:
> Hello,
Hi,
> on 2019/8/29 9:35, René Berber wrote:
>> 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).
>
> I have re-installed ca-certificates 2.32-1, then reopen the terminal and
> run fetchmail. the error still exists.
>
> Any idea? thanks.
Check the sslcertpath parameter used by fetchmail, see if it points to
the certificates (/etc/pki/tls/certs or /etc/ssl/certs). Also sslkey if
there is one.
The parameter(s) could/should be in ~/.fetchmailrc .
Your error message said "local issuer certificate". I'm not sure about
that but it seems to be having problems with the _client_ certificate,
not the server. Did you install a cert? Perhaps an identity cert used
by your mailer? Question is, does fetchmail knows were it is (including
any extra certs needed to validate it).
Now the fun part, run:
fetchmail -v
and let's see the detail of what is happening.
--
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 2:54 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 [this message]
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=6d0543c0-3aff-1fa8-7cf5-399ac4aecea1@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).