From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.236.136 with SMTP id uu8csp38090vdc; Tue, 16 Apr 2013 14:29:24 -0700 (PDT) X-Received: by 10.224.177.5 with SMTP id bg5mr1267801qab.33.1366147763873; Tue, 16 Apr 2013 14:29:23 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id g10si3199551qab.103.2013.04.16.14.29.23; Tue, 16 Apr 2013 14:29:23 -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 (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 7A3112E126; Tue, 16 Apr 2013 21:29:24 +0000 (UTC) Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by rubyforge.org (Postfix) with ESMTP id 8FE102E0F2 for ; Tue, 16 Apr 2013 21:26:51 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id u12so718431wey.19 for ; Tue, 16 Apr 2013 14:26:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-pgp-key:user-agent; bh=FTMpfKGNiqsBmllUmDI9ed731yBhHu/j95MNOr+Nc9s=; b=zosM5pYxKmwCFSyiQVEojMS6g9xrE4BsQCi7qBGVFjWPkB6BExC1vTjMG8pDP41DY0 fSOmetnjKhq+39oZgG6KWm/xD+xTv8VOT3lBKQ21s6NTMcQMv/ik6HkQij373fgZIqRI psi6nQbUSc+ue9pM39HV6a3WUgGAZWtxDmtm46AFIN/XtI4EcBDEB87boslZLgqAb7K0 3zHoopVUedGc8SO9v/o9YQfl3dLfqIRJB7HXN5cth8Lm0fihhXbbCPgEGIrCAvsOCPGr JTmL4Z3Ydja4RbUEOgDuGKHs3dgIcK2rGZ4B2zxO8BKeUgSlqZxHnqo8TS2nhPBo8FTg MmxQ== X-Received: by 10.180.205.226 with SMTP id lj2mr15020951wic.5.1366147609541; Tue, 16 Apr 2013 14:26:49 -0700 (PDT) Received: from kpad (155-29-190-109.dsl.ovh.fr. [109.190.29.155]) by mx.google.com with ESMTPS id ek4sm21898599wib.11.2013.04.16.14.26.48 (version=TLSv1.2 cipher=AES128-SHA bits=128/128); Tue, 16 Apr 2013 14:26:48 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]); by kpad (OpenSMTPD) with ESMTP id b837ef64; for ; Tue, 16 Apr 2013 21:21:46 +0000 (UTC) Date: Tue, 16 Apr 2013 23:21:45 +0200 From: Matthieu Rakotojaona To: sup talk Message-ID: <20130416212145.GB2339@kpad.otokar.looc2011.eu> References: <51692285.8000709@gaute.vetsj.com> <51695AF1.2070701@gaute.vetsj.com> <5169925C.1060701@gaute.vetsj.com> <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint> <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1366143381-sup-8459@mint> X-PGP-Key: http://otokar.looc2011.eu/static/matthieu.rakotojaona.asc User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError 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 04/16, Eric Weikl wrote: > Hi everyone, > > I created a new branch with all the commits from Damien Leone and Edward > Yang related to maildir syncback and put it here: > > https://github.com/sup-heliotrope/sup/tree/maildir-sync > > I skipped some advanced stuff like Edward's inotify support for now. We > can add that later. > > I performed some basic testing, but it would be great if some more people > could give it a try. There's some documentation in the wiki: > > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback > > Cheers, > Eric Fantastic. Not being able to sync back was what prevented me from using it. After much work and discouragement with heliotrope, I will gladly try this ! On a longer-term note, syncing back to maildir has the limitation that non-standard flags (i.e labels) will not be handled, unless we start defining some custom way of storing them or modifying the original emails, which I highly dislike (this is how mu[0] works). But that's just something to keep in mind for future times, when we have a stable, up-to-date sup release. Let's do this ! =] [0] http://www.djcbsoftware.nl/code/mu/ -- Matthieu Rakotojaona _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk