From: N.J. M. <nj...@nj...> - 2006-07-25 12:09:59
|
Hi, I have been using fetchmail for about three weeks now and I am very happy with it. But... (You knew a "but" was going to be next. ;-) ) Every time I poll my ISP I get the following errors: fetchmail: Server CommonName mismatch: localhost.localdomain != inmail.njm.f2s.com fetchmail: Server certificate verification error: self signed certificate At first I throught the first one was due to something I was doing wrong, but I now suspect it is nothing to do with me. Can someone confirm that please? My change of mind stems from running fetchmail -v -v -v and redirecting the output to a log file. (The idea for that came from a message I read earlier today on this list, so lurking here for a while does pay. :-) ) In the log I get: fetchmail: Old UID list from inmail.njm.f2s.com: <empty> fetchmail: Scratch list of UIDs: <empty> fetchmail: 6.3.4 querying inmail.njm.f2s.com (protocol POP3) at Tue Jul 25 10:43:33 2006: poll started fetchmail: POP3< +OK imap3.freedom2surf.net Cyrus POP3 v2.2.12-Invoca-RPM-2.2.12-7 server ready <122...@im...> fetchmail: POP3> CAPA fetchmail: POP3< +OK List of capabilities follows fetchmail: POP3< SASL DIGEST-MD5 CRAM-MD5 fetchmail: POP3< STLS fetchmail: POP3< EXPIRE NEVER fetchmail: POP3< LOGIN-DELAY 0 fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< PIPELINING fetchmail: POP3< RESP-CODES fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< USER fetchmail: POP3< IMPLEMENTATION Cyrus POP3 server v2.2.12-Invoca-RPM-2.2.12-7 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: inmail.njm.f2s.com key fingerprint: E1:A1:1A:47:61:46:97:6D:F3:9D:BF:13:59:40:EA:E3 fetchmail: POP3> CAPA (I hope my MUA hasn't mangled that too much.) So it looks like fetchmail is complaining about my ISPs setup. Is that right? For reference, I am running fetchmail 6.3.4 on FreeBSD v6.1 (STABLE). Thanks in advance. Cheers, Nick. -- "We're predicting third stage shutdown at 11 minutes 42 seconds." |