From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs99718bkw; Tue, 20 Jul 2010 03:43:56 -0700 (PDT) Received: by 10.231.161.80 with SMTP id q16mr6684155ibx.142.1279622635628; Tue, 20 Jul 2010 03:43:55 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e10si13052142ibg.55.2010.07.20.03.43.55; Tue, 20 Jul 2010 03:43:55 -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 D7F9419783D1; Tue, 20 Jul 2010 06:43:36 -0400 (EDT) X-Greylist: delayed 2235 seconds by postgrey-1.31 at rubyforge.org; Tue, 20 Jul 2010 06:29:05 EDT Received: from atomzentrale.khjk.org (atomzentrale.khjk.org [212.12.50.211]) by rubyforge.org (Postfix) with ESMTP id E8D2219783C0 for ; Tue, 20 Jul 2010 06:29:05 -0400 (EDT) Received: from pesco by atomzentrale.khjk.org with local (Exim 4.63) (envelope-from ) id 1Ob9UH-00080H-VM for sup-talk@rubyforge.org; Tue, 20 Jul 2010 11:51:46 +0200 From: Sven Moritz Hallberg To: sup-talk In-reply-to: <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca> References: <1279590966-sup-4411@hero> <1279591667-sup-6537@gerlach.ca> <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca> Date: Tue, 20 Jul 2010 11:51:45 +0200 Message-Id: <1279618763-sup-4286@khjk.org> User-Agent: Sup/0.11 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 My humble personal opinion: Excerpts from Ben Walton's message of 2010-07-20 04:46:41 +0200: > > 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. Guys, you should really implement this. This is not a policy (touch filesystem or not) issue, but a compliance issue. As it stands, sup is basically violating the Maildir "standard". Note that moving mails away from new has no semantic meaning. The mail doesn't become "read" or unavailable to other MUAs or anything. It's part of Maildir's access/concurrency design. And the fact that sup doesn't "play nice" with other MUAs is in part a direct artifact of this misbehaviour because others (correctly) move the mails out from under sup's nose. If sup did this as it should, the files would stay in place modulo renaming wrt. the file flags ("read" etc.), but that is another issue which can be mitigated in another step. (And to an extent, this issue exists with all MUAs because the format of the flag fields isn't standardized.) -pesco _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk