From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.34.76 with SMTP id k12cs28522ebd; Thu, 8 Apr 2010 03:10:58 -0700 (PDT) Received: by 10.204.141.78 with SMTP id l14mr154997bku.85.1270721458667; Thu, 08 Apr 2010 03:10:58 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 26si32105489bwz.21.2010.04.08.03.10.58; Thu, 08 Apr 2010 03:10:58 -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 BE8A618582F5; Thu, 8 Apr 2010 06:10:57 -0400 (EDT) X-Greylist: delayed 1796 seconds by postgrey-1.31 at rubyforge.org; Thu, 08 Apr 2010 06:10:41 EDT Received: from cs-smtp-2.Stanford.EDU (cs-smtp-2.Stanford.EDU [171.64.64.26]) by rubyforge.org (Postfix) with ESMTP id C5A74185827F for ; Thu, 8 Apr 2010 06:10:41 -0400 (EDT) Received: from [208.87.59.218] (helo=snarfed.local) by cs-smtp-2.Stanford.EDU with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1NzoDy-0005B2-9V; Thu, 08 Apr 2010 02:40:34 -0700 Date: Thu, 8 Apr 2010 02:40:32 -0700 (PDT) From: Ryan Barrett X-X-Sender: ryanb@snarfed.org To: sup-talk@rubyforge.org Message-ID: MIME-Version: 1.0 X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 3.0.4-cs-csdcf (2005-06-05) on cs-smtp-2.Stanford.EDU X-Scan-Signature: b64bce576883819501cf77c9371f4538 Cc: sjh@foolishpride.org Subject: [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 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/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk