Re: [Fetchmail-users] Unable to fetch mail from "outlook"

[Matthias A. <mat...@gm...>]

Am 10.04.2015 um 22:04 schrieb Jerry:
> On Fri, 10 Apr 2015 19:03:54 +0200, Matthias Andree stated:
> 
>> Now, retracing your previous setup and workaround experiments:
>> When I suggested to use --sslproto tls1 for a workaround,
>> you got longish delays before the failure.
>>
>> I should mention that you need to be sure to specify --ssl in that case
>> to avoid STARTTLS that is implied by fetchmail 6.3.x versions if you
>> give --sslproto tls1.
> 
> Success:
> 
> env LC_ALL=C fetchmail --nodetach -vvv --nosyslog
> Old UID list from pop3.live.com: <empty>
> Scratch list of UIDs: <empty>
> fetchmail: 6.3.26 querying pop3.live.com (protocol POP3) at Fri Apr 10 15:55:38 2015: poll started
> Trying to connect to 134.170.170.231/995...connected.
> fetchmail: Certificate chain, from root to peer, starting at depth 2:
...
> fetchmail: pop3.live.com key fingerprint: 86:60:F6:38:1C:84:A6:AC:94:92:51:2F:67:9A:7D:76
> fetchmail: pop3.live.com fingerprints match.
> fetchmail: POP3< +OK dub0-pop605 POP3 server ready

...

> Anyway, at least it is working again. Thanks for your assistance.

OK, thank you for this feedback.

JFTR, the --ssl is not a general requirement (many servers will also be
happy with STARTTLS), but specific to servers that only offer
SSL/TLS-wrapped POP3 (or IMAP) on port 995 (or 993, for IMAP), but do
not offer STARTTLS or similar on the default ports 110 (for POP3) or 143
(for IMAP).  I suppose you might have removed that in the first
experiment when you added --sslproto, and maybe my instructions weren't
clear on what I was suggesting to do.

Lesson learned: we probably need to be able to specify TLS versions
explicitly in future fetchmail versions so that users can work around
server limitations.  I don't currently think any of this can be
automatic though - version fallback would be too dangerous.