Re: [fetchmail-users] How to avoid these annoying reports

[Rob M. <rob...@gm...>]

On 8/20/07, Anne Wilson <can...@go...> wrote:
>
> That's better.  Here are the beginning, up to the end of the first mailbox,
> and the last mailbox.  All the others are like the last one.
>
<---SNIP--->
> fetchmail: 6.3.8 querying mailhost.zen.co.uk (protocol POP3) at Mon 20 Aug
> 2007 12:51:18 BST: poll completed
> fetchmail: 6.3.8 querying zencphosting09.zen.co.uk (protocol POP3) at Mon 20
> Aug 2007 12:51:18 BST: poll started
> fetchmail: Trying to connect to 82.71.204.15/110...connected.
> fetchmail: POP3< +OK Hello there.
> fetchmail: POP3> CAPA
> fetchmail: POP3< +OK Here's what I can do:
> fetchmail: POP3< STLS
> fetchmail: POP3< TOP
> fetchmail: POP3< USER
> fetchmail: POP3< LOGIN-DELAY 10
> fetchmail: POP3< PIPELINING
> fetchmail: POP3< UIDL
> fetchmail: POP3< IMPLEMENTATION Courier Mail Server
> fetchmail: POP3< .
> fetchmail: POP3> STLS
> fetchmail: POP3< +OK Begin SSL/TLS negotiation now.
> fetchmail: Issuer Organisation: Unknown
> fetchmail: Issuer CommonName: zencphosting09.zen.co.uk
> fetchmail: Server CommonName: zencphosting09.zen.co.uk
> fetchmail: zencphosting09.zen.co.uk key fingerprint:
> 01:A0:29:54:2F:03:DB:AE:79:8D:B8:B9:BB:9A:1F:9A
> fetchmail: Server certificate verification error: self signed certificate

Right, try another go at the openssl command, but use port 995 (POP3S)
instead of 993 (IMAPS).  If that fails then, as Matthias said, you
could use:

sslfingerprint 01:A0:29:54:2F:03:DB:AE:79:8D:B8:B9:BB:9A:1F:9A

before the "user" line.

Be warned however that if/when the fingerprint changes fetchmail will
(quite reasonably) refuse to communicate with that server.
Alternatively, assuming you're running in daemon mode, just ignore the
warning you'll (only) get at startup :)

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche