Date: Tue, 19 Jan 2010 10:24:27 -0500
From: Jameson Rollins <jrollins@finestructure.net>
To: Marten Veldthuis <marten@veldthuis.com>
Message-ID: <20100119152427.GL8342@finestructure.net>
References: <87pr57jvkz.fsf@SSpaeth.de>
	<201001181641.25647.sojkam1@fel.cvut.cz>
	<87hbqjwgmf.fsf@SSpaeth.de> <87my0a5i80.fsf@SSpaeth.de>
	<87my0aqgw9.fsf@veldthuis.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="rAc+36e7LRL7Dg7x"
Content-Disposition: inline
In-Reply-To: <87my0aqgw9.fsf@veldthuis.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] Introducing notmuchsync
Precedence: list


--rAc+36e7LRL7Dg7x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 19, 2010 at 04:00:06PM +0100, Marten Veldthuis wrote:
> On Tue, 19 Jan 2010 14:37:03 +0100, "Sebastian Spaeth" <Sebastian@SSpaeth=
=2Ede> wrote:
> >  - Move read files from 'new' to 'cur' folder. At what point is that
> >    moving typically done in Maildir? When the user has actually looked
> >    at the mail?
>=20
> Yes, exactly that.

Actually, I don't think this is exactly correct.  I believe that the
move from new to cur should be done by the MUA when the MUA actually
processes the message, but before the user views the message.  The S
flag should then be added by the MUA when the user actually views the
message.  The MTA should be delivering messages to new, and the MUA
should move it to cur.  That is at least how's it's described by DJB
for qmail (see THE MAILDIR STRUCTURE section in the qmail man page):

http://qmail.org/man/man5/maildir.html

I can't find an official "spec", though, and the cr.yp.to maildir page
is a little vague on the issue:

http://cr.yp.to/proto/maildir.html

Currently notmuch itself does not really conform to what I believe is
the maildir spec, which makes it a little difficult to use with other
MUAs.  Notmuch does not move messages from new to cur, or modify the
flags.  I've been arguing that notmuch should conform to this spec
directly, by moving messages from new to cur when it processes the
maildir, and by keeping tags synced with the maildir message flags.

jamie.

--rAc+36e7LRL7Dg7x
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: attachment

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLVc6nAAoJEO00zqvie6q8UTEQAJ71/Rc04isBHo6fZ11pxbDP
EdGPIdeBt3c3/FyXcRJjpXFDCWcH84rAaXnPPlc1dPBSaa3ysqAklBejYVaLHhI7
NOuantW7icSyoaKbwW8wSEbu7Sb04XoQoSJIad+M2MVF31uX5uoIglZN94D1zaLL
dkJTYmelXlRe3r4SoOtBUcqBK7OFdH/GjWQRbfed2tkd60JQ/P1FvQvny+3RVvFv
Uf7/MalUrRPr8GYj+wfEPsbB8XbD4R/t9HNM4odtYf7CLhQGOJfV21YUc0aQIG+H
UUA5RKyQo0vu079HMKQwuiGjgY7jKpZfwbJ5frKQoR/A3WyspijR9VjnTN+vW1Y5
8MYpF24bjmAGpkqprqyH4QAHQrI1G4BRj7QVafOfP6vEeL1LLNH7Cta/oPBUY6xu
GcDkSY2gTHauk71tp0lN6vjcpSFXkYJsKlUBrrVT0wDIg3SYLSVD6P+QZSa1SPk6
G/s3gb/EMlIW0huX3d5UuJuMjrSoa42A3iLiSbCOO8nFFWqdRVJ1yQDtWiXxyzOS
fuyJtLP/+yihzafoswjrMv2NG/VesiVJQjg/+9yjgNjWbbl47IIARrM3d9QpMlz+
IaANKlHgxgjb6JlI1qCxh9UjwSZdOiQYtMeTbqGJbCzKWgxqpuSpB1PMtDWPfk5s
Zk/W1OCI44v5cN4+KAHa
=Grd4
-----END PGP SIGNATURE-----

--rAc+36e7LRL7Dg7x--