From: Jerry <je...@se...> - 2015-04-10 20:04:12
|
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: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Root CA fetchmail: Subject CommonName: GlobalSign Root CA fetchmail: Certificate at depth 1: fetchmail: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Root CA fetchmail: Subject CommonName: GlobalSign Organization Validation CA - G2 fetchmail: Server certificate: fetchmail: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Organization Validation CA - G2 fetchmail: Subject CommonName: *.hotmail.com fetchmail: Subject Alternative Name: *.hotmail.com fetchmail: Subject Alternative Name: *.live.com fetchmail: Subject Alternative Name: *.outlook.com fetchmail: Subject Alternative Name: hotmail.com 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 fetchmail: POP3> CAPA fetchmail: POP3< -ERR unrecognized command fetchmail: unrecognized command fetchmail: Repoll immediately on ME...@ou...@pop3.glbdns2.microsoft.com Trying to connect to 134.170.170.231/995...connected. fetchmail: Certificate chain, from root to peer, starting at depth 2: fetchmail: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Root CA fetchmail: Subject CommonName: GlobalSign Root CA fetchmail: Certificate at depth 1: fetchmail: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Root CA fetchmail: Subject CommonName: GlobalSign Organization Validation CA - G2 fetchmail: Server certificate: fetchmail: Issuer Organization: GlobalSign nv-sa fetchmail: Issuer CommonName: GlobalSign Organization Validation CA - G2 fetchmail: Subject CommonName: *.hotmail.com fetchmail: Subject Alternative Name: *.hotmail.com fetchmail: Subject Alternative Name: *.live.com fetchmail: Subject Alternative Name: *.outlook.com fetchmail: Subject Alternative Name: hotmail.com 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-pop599 POP3 server ready fetchmail: POP3> USER ME...@ou... fetchmail: POP3< +OK password required fetchmail: POP3> PASS * fetchmail: POP3< +OK mailbox has 0 messages fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 0 0 fetchmail: No mail for ME...@ou... at pop3.live.com fetchmail: POP3> QUIT fetchmail: POP3< +OK mailbox unchanged, POP3 server signing off fetchmail: 6.3.26 querying pop3.live.com (protocol POP3) at Fri Apr 10 15:55:50 2015: poll completed New UID list from pop3.live.com: <empty> fetchmail: not swapping UID lists, no UIDs seen this query fetchmail: Query status=1 (NOMAIL) fetchmail: normal termination, status 1 I have this in the ".fetchmailrc" file: poll pop3.live.com with proto POP3 service 995 timeout 30 and options bad-header accept user 'ME...@ou...' there with password 'PASSWORD' is 'ME' here options flush forcecr dropdelivered smtpname 'ME...@IS...' sslproto tls1 ssl sslfingerprint '86:60:F6:38:1C:84:A6:AC:94:92:51:2F:67:9A:7D:76' Anyway, at least it is working again. Thanks for your assistance. -- Jerry |