DomainKey-Signature: a=rsa-sha1; c=nofws; d=SSpaeth.de; h=from:to:subject
	:in-reply-to:references:date:message-id:mime-version:
	content-type; q=dns; s=sspaeth.de; b=QsitrIoB5FtOtWtYAIgVhBB2IsN
	9nG4QDRk9Ow21/883/JMDSoJmdYHdmuMX1Tvp/b1RdTRLVl873nWs/x/HxAzjJ9x
	sl7nYg94WRJxz7XvKH9Kcky7QCN2ht6vK6hUmk0YoZg+5PDj32FfmMr88Nh4ZWq4
	Gk/84LOjckdAWnHE=
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Notmuch developer list <notmuch@notmuchmail.org>
Subject: notmuchsync default behavior change (was: 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 10:01:54 +0200
Message-ID: <87eickhor1.fsf@SSpaeth.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=

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.
> ...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.

notmuchsync does not want to delete anyones' e-mails by accident and
although I believe that syncing the "deleted" tag should usually be
safe, I can think of situations with multiple copies of a mail where
things could go wrong. I therefore disabled syncing of the maildir flag
"trashed" and the notmuch tag "deleted" by default. It has to be
explicitly be enabled with the new --sync-deleted option.

Sebastian

------------------------------------------------------------------
For reference, this could be a szenario where things turn out bad:

- Send a mail with FCC to your Sent folder and BCC yourself. You have
then 2 mail copies with the same mail id (1 notmuch entry)

- "Expire" your BCC copy via some mail/webclient, it gets maildir flag
"T"

- notmuch --revsync will examine new mails and in case the BCC copy is
what notmuch points to, notmuchsync will then add the notmuch tag
"deleted" to that mail id.

- notmuchsync --prune deletes the BCC mail copy but does not remove the
  "deleted" tag in the notmuch db (it probably should for safety
  reasons).

- 'notmuch new' will now recognize the BCC copy as removed and point to the
  "Sent/FCC" copy as the current file, but it still carries the "deleted"
  tag for the mail.

- notmuchsync --prune will happily delete your Sent/FCC copy of the
  mail, or notmuchsync --sync will mark your Sent/FCC copy with the
  "expired" maildir flag.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkybCXIACgkQVYX1jMgnoGKH8gCfZ5/k1+/0djyZwgnxHWvCZHY4
G18An20A3MELeF9mTyOk2aKVpBG2V+J4
=y1tC
-----END PGP SIGNATURE-----
--=-=-=--