From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Cc: Horacio Sanson <hsanson@gmail.com>
Subject: Re: [sup-devel] Experimental Gmail Source
Date: Sat, 11 May 2013 12:15:07 +0200 [thread overview]
Message-ID: <518E1A2B.2080903@gaute.vetsj.com> (raw)
In-Reply-To: <CAHWBo_Y6jEWCH8O+m1iw5_p4qd8ghxgvCsa1+15xR7fh+6S0nA@mail.gmail.com>
On 09. mai 2013 11:28, Horacio Sanson wrote:
> I am trying to implement a new source for Gmail accounts. This is
> copied from my efforts to do the same in Heliotrope.
>
> Here is an experimental implementation that can read the email from
> Gmail and add it to the Sup index:
>
> https://github.com/hsanson/sup/tree/gmail_source
>
> To use:
>
> - Install leveldb gem "sudo gem install leveldb-ruby" - Add a gmail
> source: sup-add gmail://username@gmail.com - Start sup and see how
> it syncs your emails.
>
> Warnings:
>
> - This is experimental - This always syncs only the All mailbox so
> make sure to use an account with not too many emails for testing. -
> All email data and headers are stored in a LevelDB database at:
> ~/.sup/gmail/account
>
> - For some reason I get duplicate "Inbox" and "Sent" labels in the
> list of labels and I am not sure why.
> - I still have no clue on how to handle sync-back. That is how to
propagate
> changes made in sup
> back to Gmail. Any tips on how the maildir source does it would be
> appreciated.
Hi Horacio,
nice work. Working directly with GMail labels is probably a good idea
(the other option is to move messages between IMAP folders). I have a
design question though:
Should remote sources be part of regular sup? Or should rather the
fetching and syncing be put in a separate script which creates a LevelDB
setup like you have it with a Gmail source in sup working directly on it?
Recall that the IMAP source was removed in 52e29ba [1] (discussion
probably on the mailinglist somewhere).
I like this approach for GMail, but I would like to see it for regular
IMAP sources as well with folders as labels.. I briefly experimented
with a maildir-root folder approach [2] which treats all underlying
maildirs as sources which correspond to a label (do not use,
incomplete). It of course presents a plethora of questions on how to
sync messages between labels, but implementing it is is probably
relatively straight forward.
> Help:
>
> - How do I stop the source poll when I quit sup? If I have a large
> amount of emails when polling is running and I quit sup the process
> hangs there.
This normally runs in a separate thread, I don't think maildir really
stops the polling - so I sometimes get an error if I quit sup while the
polling is running and various stuff just disappears underneath the poller.
I don't have the chance to get into your other questions at the moment.
Regards, Gaute
[1] https://github.com/sup-heliotrope/sup/commit/52e29ba
[2] https://github.com/gauteh/sup/tree/maildir-root
next prev parent reply other threads:[~2013-05-11 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:28 Horacio Sanson
2013-05-09 19:13 ` Eric Weikl
2013-05-11 10:15 ` Gaute Hope [this message]
2013-05-11 18:18 ` Horacio Sanson
2013-05-15 2:10 ` Horacio Sanson
2013-05-21 21:47 ` Matthieu Rakotojaona
2013-06-02 2:45 ` Horacio Sanson
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=518E1A2B.2080903@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=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