-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-04-02 at 11:27 +0200, Theo v. Werkhoven wrote:
It probably means these isps use self-signed certs, and your client doesn't recognize the CA (Certificate Authority). Either ask these isps to start using certs which are signed by a known CA, or import the server certificate from these isps and let the client s/w know where to find it.
By the way... gmail uses a certificate, but that fact is not mentioned in their docs, I think. Fetchmail complains: Apr 3 02:00:46 nimrodel fetchmail[2288]: 6.3.2 querying pop.gmail.com (protocol POP3) at Mon Apr 3 02:00:46 2006: poll started Apr 3 02:00:46 nimrodel fetchmail[2288]: Issuer Organization: Equifax Apr 3 02:00:46 nimrodel fetchmail[2288]: Unknown Issuer CommonName Apr 3 02:00:46 nimrodel fetchmail[2288]: Server CommonName: pop.gmail.com Apr 3 02:00:46 nimrodel fetchmail[2288]: pop.gmail.com key fingerprint: 59:51:61:89:CD:DD:B2:35:94:BB:44:97:A0:39:D5:B4 Apr 3 02:00:46 nimrodel spamd[11613]: prefork: child states: II Apr 3 02:00:46 nimrodel fetchmail[2288]: POP3< +OK Gpop ready l38pf1663078nfc How could I get that certificate and tell fetchmail about it? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEMGnztTMYHG2NR9URAr5BAJ4/RsOw6ifHkLJgMxoxhfxbC5wsOgCfRNxP 8nuQb/MC3jEdn9Cazaqht1I= =QhXx -----END PGP SIGNATURE-----