Date: Fri, 15 Jan 2010 11:32:33 +1300
From: martin f krafft <madduck@madduck.net>
To: mailtags discussion list <mailtags@lists.madduck.net>,
	notmuch discussion list <notmuch@notmuchmail.org>
Message-ID: <20100114223233.GA22864@lapse.rw.madduck.net>
Mail-Followup-To: mailtags discussion list <mailtags@lists.madduck.net>,
	notmuch discussion list <notmuch@notmuchmail.org>
References: <20100111221909.GA30299@lapse.rw.madduck.net>
	<87hbqpfp47.fsf@yoom.home.cworth.org>
	<20100114080421.GA17305@lapse.rw.madduck.net>
	<87k4vke349.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-ripemd160;
	protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd"
Content-Disposition: inline
In-Reply-To: <87k4vke349.fsf@yoom.home.cworth.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [notmuch] Idea for storing tags
Precedence: list


--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

also sprach Carl Worth <cworth@cworth.org> [2010.01.15.1124 +1300]:
> > You might have marked a message 'read' on one machine and if the two
> > get out of sync on another machine, you might have the same message
> > unread there.
>=20
> That's a different issue though. With two databases there's clearly the
> opportunity for the two databases to be out of synch.
>=20
> But you talked about the database being out of synch with respect to the
> mailstore. And that's something I just don't understand, (given the
> assumption that all tags are stored in the database---which was the
> explicit description of the case of interest).

Yes, we are talking about the situation where the tagstore is
seperate from the mailstore, and that they are both synchronised
with a server, or between machines, separately. If for some reason
you only synchronise the mailstore =E2=80=94 say because the connection
drops before the sync of the tagstore completes =E2=80=94 then you end up
with an out-of-sync situation, because the mailstore-sync will have
pulled in a new message, but not the associated tags. So if you had
already read this message on another machine and tagged it 'done',
then it would show up on this machine as 'new' without the 'done'
tag, because the tags were not synchronised.

The only way to really solve this is by transferring a message and
its tags in a transactional way.

> > Shouldn't this just be solved? I've had formail+procmail delete my
> > duplicates for 10+ years, and while I don't like the fact that
> > I usually get the CC before the list mail, and thus cannot filter on
> > Delivered-To, I have never looked back.
>=20
> Notmuch has access to all the information it needs to allow you to
> delete the CC version once the list mail arrives. So you could do
> notmuch-based deletion now and avoid losing the Delivered-To header if
> you want.

Of course. I hadn't thought that far.

However, there are still benefits to formail, namely avoiding having
to run duplicates through potentially expensive spamfilters.

> I think that synchronizing the mail store and synchronizing the
> tags information are tasks that have different requirements, and
> for which we may well want different tools.

Fair enough. Maybe I am just paranoid about the stores getting out
of sync (see above).

--=20
martin | http://madduck.net/ | http://two.sentenc.es/
=20
"we all know linux is great...
 it does infinite loops in 5 seconds."
                                                     -- linus torvalds
=20
spamtraps: madduck.bogus@madduck.net

--vkogqOf2sHV7VnPd
Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"
Content-Description: Digital signature (see http://martin-krafft.net/gpg/)
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAktPm34ACgkQIgvIgzMMSnUF7QCglzthX01OAmAEUQjwRZ0Wb0Wx
YY8AoM0uYHBcB/22YflVBcVb/OsAzw6j
=FnB6
-----END PGP SIGNATURE-----

--vkogqOf2sHV7VnPd--