From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.218.138 with SMTP id hq10cs26184icb; Wed, 15 Dec 2010 09:18:56 -0800 (PST) Received: by 10.90.103.13 with SMTP id a13mr8694947agc.143.1292433536300; Wed, 15 Dec 2010 09:18:56 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id j6si2649500qcu.166.2010.12.15.09.18.56; Wed, 15 Dec 2010 09:18:56 -0800 (PST) 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; dkim=neutral (body hash did not verify) header.i=@jamestaylor.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id D571919783BA; Wed, 15 Dec 2010 12:18:55 -0500 (EST) X-Greylist: delayed 486 seconds by postgrey-1.31 at rubyforge.org; Wed, 15 Dec 2010 12:15:04 EST Received: from jamestaylor.org (jamestaylor.org [67.207.142.119]) by rubyforge.org (Postfix) with ESMTP id D5422185838C for ; Wed, 15 Dec 2010 12:15:04 -0500 (EST) Received: from jamestaylor.org (localhost [127.0.0.1]) by jamestaylor.org (Postfix) with ESMTP id 9905821411F; Wed, 15 Dec 2010 17:06:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jamestaylor.org; h= content-type:cc:subject:from:to:in-reply-to:references:date :message-id:content-transfer-encoding; s=beta; bh=kCY5rF8aSkmGep o0LHbAHr8onxE=; b=AoeMmficZ2KWEfc0HETxaon95zYEWJG7/4FpyaT+L2vU7B P1Sve7BV4ILli3UOD7B7082MArqU6vd1DCYYI3Y8OxIAUlD+FALD2FPRNE9pcRyt wzoJLZfrBFmIr7Cq4VIDxsTIvJ+snvqWvy2u4vsz9OsjgGf5ahQNpZ9aD3LqI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=jamestaylor.org; h=content-type :cc:subject:from:to:in-reply-to:references:date:message-id: content-transfer-encoding; q=dns; s=beta; b=OfTXF2eKLuDh3BkCFg4Y nma/rU4I8/qeY9ws6xDmofNsprUopM+MABn6IxcZ/fIzt89c9W2fbd954OOz4KoH q8UkNttQomlB0KGlNMFZ9qQ10KS61ghlluIMl1AB5PM745CTMeZZay+bC6Gd7KNC 74EKwi5pvU7lxSjKOAE6PH0= Received: by jamestaylor.org (Postfix, from userid 1000) id 7C30521411E; Wed, 15 Dec 2010 17:06:54 +0000 (UTC) From: James Taylor To: Matthias Vallentin In-reply-to: <20101215081955.GF568@icsi.berkeley.edu> References: <1271023429-sup-9851@zyrg.net> <1271249704-sup-1088@masanjin.net> <1271254358-sup-3024@pinkfloyd.chass.utoronto.ca> <1271260552-sup-9153@masanjin.net> <1271261164-sup-4109@pinkfloyd.chass.utoronto.ca> <20101215081955.GF568@icsi.berkeley.edu> Date: Wed, 15 Dec 2010 17:06:54 +0000 Message-Id: <1292432651-sup-6834@jamestaylor.org> User-Agent: Sup/git Cc: sup-talk , Ben Walton 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Matthias Vallentin's message of Wed Dec 15 08:19:55 +0000 2010: > Does the current version of sup still keep mail in new? As a fairly new > sup user, I am trying to understand the limitations of maildir support > and this one seems to be one. For what it is worth, I've been using maildir-sync for almost six months every day, no problems. I exercise it pretty hard since I usually have at least four imap clients (mobile devices and such) accessing the maildir simultaneously via dovecot imap. Everything works fine. Currently using Damien's latest sync up with the mainline from here: http://git.fensalir.fr/?p=dleone/sup.git;a=shortlog;h=refs/heads/maildir-sync-master Anybody else using this? It seems ready to integrate. -- jt _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk