From: Sven Moritz Hallberg <sm@khjk.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] not moving msgs to /cur in Maildir?
Date: Tue, 20 Jul 2010 11:51:45 +0200 [thread overview]
Message-ID: <1279618763-sup-4286@khjk.org> (raw)
In-Reply-To: <1279593880-sup-4595@pinkfloyd.chass.utoronto.ca>
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
next prev parent reply other threads:[~2010-07-20 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 2:00 David Rysdam
2010-07-20 2:15 ` Eric Gerlach
2010-07-20 2:46 ` Ben Walton
2010-07-20 9:51 ` Sven Moritz Hallberg [this message]
2010-07-20 11:07 ` Damien Leone
2010-07-20 14:37 ` Sven Moritz Hallberg
2010-07-20 14:52 ` David Rysdam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1279618763-sup-4286@khjk.org \
--to=sm@khjk.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox