-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-12-31 at 09:24 -0800, Carl William Spitzer IV wrote:
No, nothing of the sort. The server is there and it answers and allows login et all: it just says there is no new email, when there are hundreds.
http://www.linuxforums.org/forum/t41552-the-complete-guide-to-using-gmail-wi...
Nothing new there. There is a fine guide at gmail site. I wish I could make myself understood... :-( I repeat that it worked, then it stopped working. There is nothing wrong with my configuration. Unless that page mentions the exact error I'm seeing, it is useless.
Try this and if you still cant get in check their pop and smtp addresses.
http://www.iopus.com/guides/bestpopsmtp.htm
do you have ssl setup??
Yes. I repeat that it is not a problem with my configuration. See the logs: Dec 14 14:18:55 nimrodel fetchmail[13065]: POP3> USER **@gmail.com Dec 14 14:18:56 nimrodel fetchmail[13065]: POP3< +OK send PASS Dec 14 14:18:56 nimrodel fetchmail[13065]: POP3> PASS * Dec 14 14:18:57 nimrodel fetchmail[13065]: POP3< +OK Welcome. Dec 14 14:19:00 nimrodel fetchmail[13065]: POP3> STAT Dec 14 14:19:00 nimrodel fetchmail[13065]: POP3< +OK 8 24000 It worked. It had been working for weeks. Then, a minute and a half later, in the same run, it didn't: Dec 14 14:20:20 nimrodel fetchmail[13359]: POP3> USER **@gmail.com Dec 14 14:20:21 nimrodel fetchmail[13359]: POP3< +OK send PASS Dec 14 14:20:21 nimrodel fetchmail[13359]: POP3> PASS * * Dec 14 14:20:31 nimrodel fetchmail[13359]: POP3< +OK [SYS/TEMP] Due to a temporary system problem, this mailbox will seem empty. Dec 14 14:20:34 nimrodel fetchmail[13359]: POP3> STAT Dec 14 14:20:34 nimrodel fetchmail[13359]: POP3< +OK 0 0 Dec 14 14:20:34 nimrodel fetchmail[13359]: No mail for ***@gmail.com at pop.gmail.com *** Notice that I can log in perfectly, *** *** it just says there is no new email. *** - From then on, it did not ever work again. I have not changed my configuration, it is dated Dec 9th. Therefore, it is not my configuration! So, please, lets stop this subject. Unless somebody knows something specific to the _exact_ error some of us are seeing, more chit-chat is useless and OT. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDt8xVtTMYHG2NR9URApXDAJ9cxK5XilhPMT7ME9s8mmaMFiEQsACeI4S+ UHQFKRjmiQNlWSXbNSMX/EE= =RKWz -----END PGP SIGNATURE-----