[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sup-devel] Query for largest msg_id?
On Tue, May 24, 2011 at 6:22 AM, Hamish <dmishd@gmail.com> wrote:
> Excerpts from Horacio Sanson's message of Fri May 20 16:38:30 +0100 2011:
>> On Wed, May 18, 2011 at 2:05 PM, William Morgan wrote:
>> > Reformatted excerpts from Horacio Sanson's message of 2011-05-17:
>> >> I implemented a new version of the GMail -> Heliotrope sync script and
>> >> attach it here in hopes someone will test it and provide some
>> >> feedback/comments.
>
> This sounds awesome. I've already downloaded my gmail email using
> offlineimap (into maildir format), and I'm wondering if it's possible to
> get your script to use the local copies first, and only then get the new
> emails from gmail - so as to save redownloading several hundred
> megabytes of email ...
>
Unfortunately this script is GMail specific and I make use of some
GMail only extensions (X-GM-LABELS, XLIST, etc) that render the
script unusable for any other mail store. My main motivation for
creating this script was to get rid of offlineimap as this would store
each message twice, once in offlineimap folders and once in heliotrope
store.
> I'm keen to try it out, but don't want to use it on my main account as I
> imagine it would take a long time. Maybe I'll just set up a second
> account with some test email to play with it.
>
Please do not use this script with your main account,... It won't
affect your GMail data since I use read-only mode (IMAP examine) but
it still has some problems I need to handle before I can guarantee
that Heliotrope is 100% sync with GMail after running the script. For
instance sometimes GMail fails to send me the message body or timeouts
generating some IMAP exceptions I need to handle more gracefully.
If you have a test account with some messages any testing is greatly
appreciated...
> If it's just too hard to do, I'll just have to do the whole thing
> anyway, but it won't be too bad as just a one off job.
>
> Thanks for your work though
> Hamish
> _______________________________________________
> Sup-devel mailing list
> Sup-devel@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-devel
>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel