DomainKey-Signature: a=rsa-sha1; c=nofws; d=SSpaeth.de; h=from:to:cc:subject
	:in-reply-to:references:date:message-id:mime-version:
	content-type; q=dns; s=sspaeth.de; b=g/DM2PRnW7Z7JpHUiisqCm+jgSG
	3nbkZ3QcRsDiVa6F1IK1F3dHit4CIw8rSDifFc6MGCiyvXNGMX7R+MahDG6XQHcb
	he6gMoOQeWRqvnSdo7n11y0rzcIc0oCC043s5P3xv4LGPo738UIiX/XTGxE5EkXC
	ovGy1H/PTejPgEpc=
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Rob Browning <rlb@defaultvalue.org>
Subject: Re: notmuchsync: handling of the deleted tag
In-Reply-To: <877hie4o1w.fsf@raven.defaultvalue.org>
References: <87bp7vewa5.fsf@raven.defaultvalue.org>
 <87mxrcsb8a.fsf@SSpaeth.de>	<87r5gnomt2.fsf@raven.defaultvalue.org>
 <87zkvb4eiq.fsf@SSpaeth.de>	<877hie4o1w.fsf@raven.defaultvalue.org>
User-Agent: Notmuch/0.3.1-43-g5d515b7 (http://notmuchmail.org) Emacs/23.1.50.1
	(x86_64-pc-linux-gnu)
Date: Thu, 23 Sep 2010 09:30:32 +0200
Message-ID: <87k4mchq7b.fsf@SSpaeth.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: Notmuch developer list <notmuch@notmuchmail.org>
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On 2010-09-22, Rob Browning wrote:
> In general, I think that until/unless notmuchsync can be more assured of
> doing the right thing, and in particular, if the deleted tag is likely
> to become official, notmuchsync should default to not setting it.
>=20
> ...or at least, I'd prefer that.  Then I can add --tag-deleted if/when I
> want to.  Of course defaulting to --tag-deleted would also be OK, as
> long as there's a --no-tag-deleted.

In my workflow it does the right thing as I only "expire" a message if I
am happy that it actually will be deleted. The situation is a bit less
scary that it seemed to me: if a notmuch --revsync examines a mail file,
it is the exact copy that notmuch will point to, and it will mark that
as "deleted" (and eventually "--prune" can delete that very copy). A new
run by notmuchsync --revsync will then be told to look at the second
copy if the first is gone and it will discover that it does not have the
maildir flag "expired" and thus remove the "deleted" tag in the notmuch
db. As such, the tag should reflect the actual status of the mail file
that notmuch points to.

But I can imagine circumstances in which there would be an erroneous tag
be set and I don't want notmuchsync to accidently delete anyones emails,
so I'll disable the "deleted" tag synchronization by default and only
make it an option (that I will use). Solving this in a proper way will
require support from the notmuch API though.

Sebastian
P.S. cworth made clear that he preferred if there were no "official" tags
or some tags that are more queal than others.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkybAhgACgkQVYX1jMgnoGKR4QCaAnbf1lJ1j44mheOHK4IFKmFR
H2MAniCi8SHdjIICtp+IO7MjBczWURMt
=YwbE
-----END PGP SIGNATURE-----
--=-=-=--