From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.137.132 with SMTP id w4cs63345bkt; Sun, 11 Apr 2010 11:10:40 -0700 (PDT) Received: by 10.204.30.208 with SMTP id v16mr365943bkc.187.1271009439833; Sun, 11 Apr 2010 11:10:39 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 1si8291452bky.81.2010.04.11.11.10.39; Sun, 11 Apr 2010 11:10:39 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 14AF11D78898; Sun, 11 Apr 2010 14:10:39 -0400 (EDT) X-Greylist: delayed 1051 seconds by postgrey-1.31 at rubyforge.org; Sun, 11 Apr 2010 14:10:33 EDT Received: from cs-smtp-1.Stanford.EDU (cs-smtp-1.Stanford.EDU [171.64.64.25]) by rubyforge.org (Postfix) with ESMTP id 7346F18581F3 for ; Sun, 11 Apr 2010 14:10:33 -0400 (EDT) Received: from c-76-21-40-134.hsd1.ca.comcast.net ([76.21.40.134] helo=snarfed.local) by cs-smtp-1.Stanford.EDU with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1O11L7-0003CP-Su; Sun, 11 Apr 2010 10:52:58 -0700 Date: Sun, 11 Apr 2010 10:52:57 -0700 (PDT) From: Ryan Barrett X-X-Sender: ryanb@snarfed.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 X-Spam-Score: 0.6 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 3.0.4-cs-csdcf (2005-06-05) on cs-smtp-1.Stanford.EDU X-Scan-Signature: dcedbbeaec314583a5a6d4e37e27e533 Cc: sup-talk@rubyforge.org, sjh@foolishpride.org Subject: Re: [sup-talk] current state of synching upstream? 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org ping? anyone successfully using sup in parallel with other client(s)? scott, are you still working on maildir sync? any updates since january? On Thu, 8 Apr 2010, Ryan Barrett wrote: > hi all! i've been looking forward to trying sup since i first heard about it > a couple years ago, and i'm getting pretty close. one of my few remaining > concerns is using sup in parallel with other mail clients, including sup > itself. > > i know best practice is to just use one sup installation and no other > clients, but i also know that synching back upstream is a frequent topic > here. i've seen the discussions of sup-sync --changed, sup-sync-back, maildir > + offlineimap etc. i'm mostly looking to hear about the current state. is > anyone successfully running sup synched with another sup or other client? if > so, how? > > it seems like people have generally agreed that the best approach is to make > sup-sync-back support maildir, and then use offlineimap to sync from maildir > to the source. is that still true? cc'ing scott henson, who mentioned he was > working on maildir sync in january. > > http://rubyforge.org/pipermail/sup-talk/2010-January/003761.html > > more background: > > http://rubyforge.org/pipermail/sup-talk/2009-April/002126.html > > http://rubyforge.org/pipermail/sup-talk/2009-July/002567.html > > -Ryan > > -- > http://snarfed.org/ > -Ryan -- http://snarfed.org/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk