Re: [sup-talk] not moving msgs to /cur in Maildir?

From: Damien Leone <damien.leone@fensalir.fr>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] not moving msgs to /cur in Maildir?
Date: Tue, 20 Jul 2010 13:07:47 +0200	[thread overview]
Message-ID: <1279623541-sup-4351@mailer> (raw)
In-Reply-To: <1279618763-sup-4286@khjk.org>

[-- Attachment #1.1: Type: text/plain, Size: 1275 bytes --]

Hi,

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. :)

Cheers,

[0] http://www.mail-archive.com/sup-devel@rubyforge.org/msg00566.html

--
Damien Leone <damien.leone@fensalir.fr>

Web: http://dleone.fensalir.fr/
GPG: 0x82EB4DDF

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk