From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.204.14 with SMTP id b14cs83980wfg; Tue, 5 Jul 2011 02:33:16 -0700 (PDT) Received: by 10.229.41.211 with SMTP id p19mr5323879qce.117.1309858395258; Tue, 05 Jul 2011 02:33:15 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id i10si8480314qca.191.2011.07.05.02.33.14; Tue, 05 Jul 2011 02:33:15 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B67CA1858363 for ; Tue, 5 Jul 2011 05:33:14 -0400 (EDT) Received: from mail-vx0-f178.google.com (mail-vx0-f178.google.com [209.85.220.178]) by rubyforge.org (Postfix) with ESMTP id EF0A71858367 for ; Tue, 5 Jul 2011 05:32:59 -0400 (EDT) Received: by vxk12 with SMTP id 12so5546859vxk.23 for ; Tue, 05 Jul 2011 02:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=tbdtU9yTKxMuJ3RgsuVJ526MhqQRB+tFkbBURR7LsSw=; b=D4LceU1OijLcswvmFkcJSIc6V+QQIq7DXZ87NMP3a9UPZgCUAldHL86NvfMjbMcc4n rkOhesIvAkf9zzwc2q2YiH9hkXVhL3+bpZM7sdDmcWf2a3BdY/kgH2oXTTf9zCfi5FnU tuxVpuWTlvJmgqh0diM+jEhYJqG9vsXf3v2jg= MIME-Version: 1.0 Received: by 10.52.177.200 with SMTP id cs8mr5835574vdc.72.1309858379283; Tue, 05 Jul 2011 02:32:59 -0700 (PDT) Received: by 10.52.187.162 with HTTP; Tue, 5 Jul 2011 02:32:59 -0700 (PDT) Received: by 10.52.187.162 with HTTP; Tue, 5 Jul 2011 02:32:59 -0700 (PDT) Date: Tue, 5 Jul 2011 10:32:59 +0100 Message-ID: From: Hamish D To: Sup developer discussion Subject: Re: [sup-devel] gmail limits [was: Heliotrope improving but still found some issues] X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1604208820==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============1604208820== Content-Type: multipart/alternative; boundary=20cf3071cc04673e3904a74f2b79 --20cf3071cc04673e3904a74f2b79 Content-Type: text/plain; charset=UTF-8 On 5 Jul 2011 02:53, "Horacio Sanson" 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 --20cf3071cc04673e3904a74f2b79 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 5 Jul 2011 02:53, "Horacio Sanson" <hsanson@gmail.com> wrote:
> The second problem is actually not heliotrope problem. Is the artifici= al
> limitations imposed by Gmail. After running heliotrope-add for some ti= me it
> would fail when the IMAP fetch returns nil. Just after it failed I tri= ed to
> use my current email reader (kmail) and got an interesting error sayin= g:
> "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 p= ace
> 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 sit= uation and give a sensible error message - 'gmail won't give any mo= re messages now, please try again after an hour' or something along tho= se lines. I got through over 12000 messages before hitting trouble, so peop= le with smaller accounts may never hit the problem and would like the speed= to be as high as possible.

Hamish Downer

--20cf3071cc04673e3904a74f2b79-- --===============1604208820== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============1604208820==--