-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-01-23 at 06:43 +0200, roach wrote:
On Sunday 22 January 2006 01:58, James Knott wrote:
Why's that? Is there a problem with their servers?
Gmail POP is not standard compliant & it has been reported to be non-functional for some users.
I don't know if it is standard: fetchmail did not have any problems with it - not that it can be infered from that fact, as fetchmail works with ms exchange and such :-p Post a complaint on their web page somewhere, after searching their help for the particular error we got; that's what I did, and they solved it - after two or three weeks. I think their database, where they list who should get pop3 and what pop3, got stuck. In the other old thread I reported it as solved and how. An interesting thing is that they have a mail server certificate: | 6.2.5 querying pop.gmail.com (protocol POP3) at Mon Jan 23 12:53:16 2006: poll started | Issuer Organization: Equifax | Unknown Issuer CommonName | Server CommonName: pop.gmail.com | pop.gmail.com key fingerprint: 59:51:61:89:CD:DD:B2:35:94:BB:44:97:A0:39:D5:B4 | Warning: server certificate verification: unable to get local issuer certificate | Issuer Organization: Equifax | Unknown Issuer CommonName | Server CommonName: pop.gmail.com | Warning: server certificate verification: certificate not trusted | Issuer Organization: Equifax | Unknown Issuer CommonName | Server CommonName: pop.gmail.com | Warning: server certificate verification: unable to verify the first certificate | POP3< +OK Gpop ready. l22pf2613979nfc It works, of course, but without the certificate. It would be nice. But it is not mentioned in the pop3 help they have. How can the server certificate be obtained? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD1NJrtTMYHG2NR9URAr8mAJ9b9gD6NxizbJvAXX/10cjIk5LShACcC01C VplQPVitXymz/BQ62FHGbts= =Ycfj -----END PGP SIGNATURE-----