From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.58.247.3 with SMTP id ya3csp445843vec; Thu, 20 Sep 2012 16:59:15 -0700 (PDT) Received: by 10.50.186.169 with SMTP id fl9mr219776igc.9.1348185554240; Thu, 20 Sep 2012 16:59:14 -0700 (PDT) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id ph1si10756312icb.17.2012.09.20.16.59.13; Thu, 20 Sep 2012 16:59:14 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2F5D72E07C; Thu, 20 Sep 2012 23:59:13 +0000 (UTC) Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) by rubyforge.org (Postfix) with ESMTP id 04EF52E06F for ; Thu, 20 Sep 2012 23:58:55 +0000 (UTC) Received: by weyu7 with SMTP id u7so1825256wey.23 for ; Thu, 20 Sep 2012 16:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KmZ8S2VaZx9jJTyJsyKUo1RzaQgrbzQW0Nxd1jS9+HE=; b=rnell1kkhiipQd/zSjfyhh429Pu8r8o0VPM9fm2pQN1KcoMCkoHfzWinjEuAAIScrZ mlMRwy7M8rUHBhkMXAmCdiQbltdBbr7UEMS4ukb7GsuIKwOZnHCF9bKR2fKQd/xOBNst BQUzAxp2AtPohCr5NDiMppOKmAxL8Ju7SHYoF4pKu0nkACy9ZXsrtXxKOpcq1hJYMU+W OtBStaASzEibBo9mp1J9z9clM+4hvGpA8YAsFqKmENK+zr4IejJbYiflUkOR1JvSNsVP dYkHsiXTsRqJg8dYUVOkx117b0F/qN3NKBWEFvWR3XZnHfUr+cKB1zqgcmQWOZ/17UgG 9Aqw== Received: by 10.216.207.73 with SMTP id m51mr1932626weo.116.1348185535171; Thu, 20 Sep 2012 16:58:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.177.10 with HTTP; Thu, 20 Sep 2012 16:58:34 -0700 (PDT) In-Reply-To: <1348177473-sup-7941@monad> References: <20120919211500.GH48050@armakuni.lastninja.net> <1348123080-sup-7217@pruts.nl> <1348177473-sup-7941@monad> From: Matthieu Rakotojaona Date: Fri, 21 Sep 2012 01:58:34 +0200 Message-ID: To: Steven Hum Cc: sup-talk Subject: Re: [sup-talk] any testimonials from users who transitioned from mutt? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Fri, Sep 21, 2012 at 12:25 AM, Steven Hum wrote: > Even then, I am not sure if heliotrope will address the maildir > back sync issue (there is an imaptrope fork which may address this). If > it doesn't, it may not provide me with any benefit towards my offline > mail usage. I guess you're talking about https://github.com/rakoo/imaptrope. This was actually the only reason why I didn't use heliotrope/turnsole (and sup before it) full-time : I didn't want to do some gymnastics back and forth for my mail, like everyone here. That's why I started imaptrope. Unfortunately, I arrived to a point where using http doesn't give me sufficient speed for the task. So I set out to integrate it directly in heliotrope. The result of my work is at https://github.com/rakoo/heliotrope/tree/imap. You can now run an imap server along the http one with the following command : ruby -Ilib bin/heliotrope-server -d /path/to/data --with-imap and connect to it on localhost:10142. As I explain in the README, the goal is not to do a fully functional IMAP server, but just enough bits to work with OfflineIMAP. This software does a great job, and will be a very helpful tool for a smooth transition. This will be better than reimplementing some 2-way-syncing-magic once again. For the moment, heliotrope -> maildir works with a standard offlineimap installation. Yay ! Don't do it on big mailboxes though, because it will be horribly long (and by big I mean 100 messages. Yes, that's not big, I'm working on it) It is saddening to see that many people are interested in this great project yet seems to be dying. I was thinking this may be due to William abandoning sup in favor of heliotrope, and everyone still following the former ? Anyway, I'll be happily hacking on heliotrope, so everyone who is willing to continue is warmly invited to test things out ! -- Matthieu RAKOTOJAONA _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk