From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.177.71 with SMTP id co7csp5447vdc; Thu, 9 May 2013 02:28:23 -0700 (PDT) X-Received: by 10.60.47.1 with SMTP id z1mr3850288oem.134.1368091702805; Thu, 09 May 2013 02:28:22 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id x3si1289208oec.1.2013.05.09.02.28.22 for ; Thu, 09 May 2013 02:28:22 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 9B0B02E0EA; Thu, 9 May 2013 09:28:22 +0000 (UTC) Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by rubyforge.org (Postfix) with ESMTP id 686322E0AC for ; Thu, 9 May 2013 09:28:11 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id h2so3152883oag.19 for ; Thu, 09 May 2013 02:28:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=RCZkygXJRCPMW/1yroiuNFiaUHELMN/2+mSRq/M8jRo=; b=q4+Ez2rj4kCpYcI0BODw/pieUNp8udag15LrEhLDoejdM426UtVE3DKDF6UQtO1ZIH wuPibThieIJ3R64L9yzE5Z0n/v/JPu89z0i50T7NMqSG0E0pERwNgFsp9xP7htQ9QpcF PsJSrUuPa5e9Y/bYzvY/1e+sv8yybjdHUyBi0jigmfnrZDIj9vmdGcGmg5d+C3+DqvD8 FfmUw0fLiBUE+AXXi8cB6ZrJEBrVhfabmnDUiHXzNTOENStdhSeFRzQf9HI9CxR9xVEK cgrfXv8VDhM+P6NS2uY6lFH7KPPwctu4AGT+aQRm/EKL/4j6pR3p80zog6RStFwUAVHk 4yEg== MIME-Version: 1.0 X-Received: by 10.182.112.202 with SMTP id is10mr3732078obb.8.1368091690539; Thu, 09 May 2013 02:28:10 -0700 (PDT) Received: by 10.182.123.2 with HTTP; Thu, 9 May 2013 02:28:10 -0700 (PDT) Date: Thu, 9 May 2013 18:28:10 +0900 Message-ID: From: Horacio Sanson To: Sup developer discussion Subject: [sup-devel] Experimental Gmail Source 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="===============2518086790657451159==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============2518086790657451159== Content-Type: multipart/alternative; boundary=089e015369be3c1ff204dc45abe3 --089e015369be3c1ff204dc45abe3 Content-Type: text/plain; charset=ISO-8859-1 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 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. Does sup has a mechanism to stop the polling in progress? - 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. regards Horacio Sanson --089e015369be3c1ff204dc45abe3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
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 th= at can read the email from Gmail and add it to the Sup index:

https://github.com/hsanson/sup/tree/gmail_source

To use:

=A0 - Install le= veldb gem "sudo gem install leveldb-ruby"
=A0 - Add a gmail source: =A0 sup-add gmail://username@gmail.com
=A0 - Start sup = and see how it syncs your emails.

Warn= ings:

=A0 - This is experimental
= =A0 - This always syncs only the All mailbox so make sure to use an
=A0 =A0 =A0account with not too many emails for testing.
=A0 - All email data and headers are stored in a LevelDB database at:
=
=A0 =A0 =A0 =A0~/.sup/gmail/account

Help:

=A0 - How do I stop the= source poll when I quit sup? If I have a large amount
=A0 =A0 of emails when polling is running and I quit sup the pro= cess hangs there.
=A0 =A0 Does sup has a mechanism to stop = the polling in progress?
=A0 - For some reason I get duplic= ate "Inbox" and "Sent" labels in the list of
=A0 =A0 labels and I am not sure why.
=A0 - I st= ill have no clue on how to handle sync-back. That is how to propagate
=
=A0 =A0 changes made in sup back to Gmail. Any tips on how the m= aildir source
=A0 =A0 does it would be appreciated.

=
regards
Horacio Sanson
--089e015369be3c1ff204dc45abe3-- --===============2518086790657451159== 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 --===============2518086790657451159==--