From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.236.47.138 with SMTP id t10cs164728yhb; Tue, 8 Nov 2011 19:39:28 -0800 (PST) Received: by 10.220.151.132 with SMTP id c4mr75418vcw.143.1320809965126; Tue, 08 Nov 2011 19:39:25 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org. [205.234.109.19]) by mx.google.com with ESMTP id u13si816267vcv.69.2011.11.08.19.39.24; Tue, 08 Nov 2011 19:39:25 -0800 (PST) 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 50FC41779955; Tue, 8 Nov 2011 22:39:24 -0500 (EST) Received: from mail-fx0-f50.google.com (mail-fx0-f50.google.com [209.85.161.50]) by rubyforge.org (Postfix) with ESMTP id F1AAD18581B2 for ; Tue, 8 Nov 2011 22:23:13 -0500 (EST) Received: by faar15 with SMTP id r15so1610236faa.23 for ; Tue, 08 Nov 2011 19:23:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/YgdS2NLemB1TcLeGAbR7VQzjoqGcC+ZZITCnTR2fwo=; b=rofXAHJvmqx/1z4L3hq+Jlv4Tg4GQJXI5xlRGizxtnYmB1Oky8zvQb0RcUYUIBwljD UZfcQvXVhI9WQfNkEmSfflEIFXSzosaEg7IABLD0bi6hCfE0onw4/AtmBSKmQga+Y0GQ Lp1kzOn12bAxI/dfahNC7HtO8VCw/PuigW/8A= Received: by 10.223.76.66 with SMTP id b2mr1784215fak.15.1320808992673; Tue, 08 Nov 2011 19:23:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.93.197 with HTTP; Tue, 8 Nov 2011 19:22:51 -0800 (PST) In-Reply-To: <1320692090-sup-9935@stapelberg.de> References: <1320648596-sup-2551@masanjin.net> <1320692090-sup-9935@stapelberg.de> From: Matthieu Rakotojaona Date: Wed, 9 Nov 2011 04:22:51 +0100 Message-ID: To: Sup developer discussion Subject: Re: [sup-devel] heliotrope-syncback 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Okay, forget about buggy syncback, now comes the IMAP interface ! I've begun to hack ximapd[0], a ruby IMAP server, to work with heliotrope. Unfortunately it is not supported anymore. So far, I can connect with it (but with no security), list "mailboxes" (just like GMail, they are just labels) select one and search for something, all using imap4rev1 specs and, of course, heliotrope as a backend. The most interesting parts like FETCHing and STORing are still a few lines of code away. Of course, the goal is to use something like offlineimap, Because It Works, to sync both mail stores in a reliable fashion. Considering the implementation, I've considered only UIDs, which are heliotrope's message_ids. Both can and must only go up as messages come and go, so it's cool. So if you want to test it, go to https://github.com/rakoo/ximapd-heliotrope. This leads me to the question : what is the license of Heliotrope ? Ximapd seems to be something BSD-like, but Heliotrope has none. Cya ! [0] https://github.com/shugo/ximapd -- Matthieu RAKOTOJAONA _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel