From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs113858bkw; Tue, 20 Jul 2010 07:49:42 -0700 (PDT) Received: by 10.231.169.10 with SMTP id w10mr7037220iby.106.1279637380273; Tue, 20 Jul 2010 07:49:40 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id c18si13616308ibi.51.2010.07.20.07.49.39; Tue, 20 Jul 2010 07:49:40 -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 4FC6119783CC; Tue, 20 Jul 2010 10:49:39 -0400 (EDT) Received: from atomzentrale.khjk.org (atomzentrale.khjk.org [212.12.50.211]) by rubyforge.org (Postfix) with ESMTP id 88A431858387 for ; Tue, 20 Jul 2010 10:37:58 -0400 (EDT) Received: from pesco by atomzentrale.khjk.org with local (Exim 4.63) (envelope-from ) id 1ObDxF-0002kj-3I for sup-talk@rubyforge.org; Tue, 20 Jul 2010 16:37:57 +0200 From: Sven Moritz Hallberg To: sup-talk In-reply-to: <1279623541-sup-4351@mailer> References: <1279590966-sup-4411@hero> <1279591667-sup-6537@gerlach.ca> <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca> <1279618763-sup-4286@khjk.org> <1279623541-sup-4351@mailer> Date: Tue, 20 Jul 2010 16:37:57 +0200 Message-Id: <1279636271-sup-2393@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 Excerpts from Damien Leone's message of 2010-07-20 13:07:47 +0200: > Excerpts from Sven Moritz Hallberg's message of Tue Jul 20 11:51:45 +0200 2010: > > 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.) > > All of this is getting supported in the maildir-sync [0] branch that I > encourage you to test and review so it can be quickly merged into the > master branch. :) Ah, thanks for that! I'll try to check it out! _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk