From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs80298bkw; Mon, 19 Jul 2010 19:46:56 -0700 (PDT) Received: by 10.231.14.200 with SMTP id h8mr5183790iba.188.1279594016019; Mon, 19 Jul 2010 19:46:56 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 16si12043971ibr.79.2010.07.19.19.46.55; Mon, 19 Jul 2010 19:46:56 -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 1418C18583A9; Mon, 19 Jul 2010 22:46:55 -0400 (EDT) Received: from www.cquest.utoronto.ca (www.cquest.utoronto.ca [192.82.128.5]) by rubyforge.org (Postfix) with ESMTP id 11381185839E for ; Mon, 19 Jul 2010 22:46:41 -0400 (EDT) Received: from pinkfloyd.chass.utoronto.ca ([128.100.160.254]:57787 ident=93) by www.cquest.utoronto.ca with esmtp (Exim 4.43) id 1Ob2qv-0000dF-LS for sup-talk@rubyforge.org; Mon, 19 Jul 2010 22:46:41 -0400 Received: from bwalton by pinkfloyd.chass.utoronto.ca with local (Exim 4.63) (envelope-from ) id 1Ob2qv-0002ir-JX for sup-talk@rubyforge.org; Mon, 19 Jul 2010 22:46:41 -0400 From: Ben Walton To: sup-talk In-reply-to: <1279591667-sup-6537@gerlach.ca> References: <1279590966-sup-4411@hero> <1279591667-sup-6537@gerlach.ca> Date: Mon, 19 Jul 2010 22:46:41 -0400 Message-Id: <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca> User-Agent: Sup/git Subject: Re: [sup-talk] not moving msgs to /cur in Maildir? 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 Eric Gerlach's message of Mon Jul 19 22:15:17 -0400 2010: > I've also just started with sup, and though I don't know about sup's > behaviour (I think it should be moving mail from new/ to cur/ as > well) I haven't looked at the most recent Maildir changes[1], but as is sup's way it hasn't traditionally altered the filesystem at all. It treats all mail sources as read-only, which in this case means it doesn't do the ln new/foo cur/foo; rm new/foo steps. HTH. -Ben [1] There was talk of implementing this as one step toward having sup play nicer with other MUA's. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk