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

[Sven Moritz Hallberg <sm@khjk.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