Re: [sup-devel] gmail limits [was: Heliotrope improving but still found some issues]

* Re: [sup-devel] gmail limits [was: Heliotrope improving but still found some issues]
@ 2011-07-05  9:32 Hamish D
  0 siblings, 0 replies; only message in thread
From: Hamish D @ 2011-07-05  9:32 UTC (permalink / raw)
  To: Sup developer discussion

[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]

On 5 Jul 2011 02:53, "Horacio Sanson" <hsanson@gmail.com> wrote:
> The second problem is actually not heliotrope problem. Is the artificial
> limitations imposed by Gmail. After running heliotrope-add for some time
it
> would fail when the IMAP fetch returns nil. Just after it failed I tried
to
> use my current email reader (kmail) and got an interesting error saying:
> "exceeded IMAP bandwidth limits". These indicates the nil is due to Gmail
> limiting the maximum bandwidth I can consume downloading emails.
>
> Maybe limiting the rate of gmail-dumper so it reads mails at a lower pace
> would eliminate these problems or simply stop reading emails for some time
> when we get the first nil response.

I would prefer if heliotrope could recognise the IMAP limit exceeded
situation and give a sensible error message - 'gmail won't give any more
messages now, please try again after an hour' or something along those
lines. I got through over 12000 messages before hitting trouble, so people
with smaller accounts may never hit the problem and would like the speed to
be as high as possible.

Hamish Downer

[-- Attachment #1.2: Type: text/html, Size: 1304 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

^ permalink raw reply	[flat|nested] only message in thread