-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-12-29 at 06:33 +0200, roach wrote:
But this "temporary" error hasn't changed since Dec 14, when it started. I have googled, and found an email thread in "debian-user" ([OT] Gmail POP fails), with some people
Me.
It's kind of comforting to know we are not alone :-}
reporting the exact same error even earlier than me, with diferent email configurations, but no solution.
Still no solution here.
I have not found any mention of this in gmail help either.
Ditto, I also contacted Gmail on 29 November and have yet to receive a responce. Personally I don't think POP access is a priority for Gmail - they make their money from ad's, which you don't see with POP.
Possibly. But some providers also send publicity in the email (it says so in the "contract"), or separate emails. It's interesting to note how many hit points they get from Spam Assassin ;-) I had to white-list them, my conscience was itching a bit :-p
How about you people? Any clues, pointers?
I finally gave up and deleted 20MB of the 22MB of backed-up mail in my Gmail account. The last 2MB I archived and then, with an empty Gmail inbox, I sent a message to myself from my Mighty account.
I then tried to download it from Gmail - it worked for the first time in 26 days. I managed to download mail.
Ah!
I then let some list mail in (no attachment, nothing funny) and tried to download again. Nothing, lockup - same error message as above.
Oh :-(
Remove, try again. Send myself mail, download - success.
Conclusion: My Gmail account doesn't like list mail. :-(
Yagh. But there are a good number of people using gmail on this list! Oh, well, perhaps they use webmail...
I've given up on Gmail...
...maybe later?
Sorry I can't give you good news, Carlos. :-(
No, you clarified what you have already tried. We know there is nothing we can do on our side except complain. I'll let the account fill up unread... it will not show nice in their stats. When I have time, I'll find out whom to complain, and I will do so - - with a note not to bother answering till the problem is solved, as I will not see it. Let us leave this tread here, unless there is further development, so that others can find it in the archive and know there is no solution. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDtD5ZtTMYHG2NR9URApnnAJ9sl95zvVTJ+c1KgyBsWZWNdM1BiQCeJdJw bpyVJKpDx7x+xD31dTZVq8k= =BuOr -----END PGP SIGNATURE-----