From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Query for largest msg_id?
Date: Tue, 24 May 2011 12:16:24 +0900 [thread overview]
Message-ID: <BANLkTikn6iB-+f5-xLk2nEAOBL8Dzjfx8A@mail.gmail.com> (raw)
In-Reply-To: <1306185381-sup-6337@whisper>
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
next prev parent reply other threads:[~2011-05-24 3:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 15:17 Horacio Sanson
2011-05-15 15:01 ` William Morgan
2011-05-16 15:02 ` Horacio Sanson
2011-05-17 14:59 ` Horacio Sanson
2011-05-17 15:15 ` Horacio Sanson
2011-05-18 5:05 ` William Morgan
2011-05-20 15:38 ` Horacio Sanson
2011-05-22 22:00 ` William Morgan
2011-05-23 21:22 ` Hamish
2011-05-24 3:16 ` Horacio Sanson [this message]
2011-05-18 4:59 ` William Morgan
2011-05-18 20:09 ` Sascha Silbe
2011-05-19 3:14 ` Alvaro Herrera
2011-05-22 22:05 ` William Morgan
2011-05-23 7:52 ` Gaudenz Steinlin
2011-05-23 16:14 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikn6iB-+f5-xLk2nEAOBL8Dzjfx8A@mail.gmail.com \
--to=hsanson@gmail.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox