1 Return-Path: <madduck@lapse.rw.madduck.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id B5677431FBD
\r
6 for <notmuch@notmuchmail.org>; Thu, 14 Jan 2010 00:04:40 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.36 tagged_above=-999 required=5 tests=[AWL=1.239,
\r
12 BAYES_00=-2.599] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id dDeMlhh9iirW for <notmuch@notmuchmail.org>;
\r
16 Thu, 14 Jan 2010 00:04:39 -0800 (PST)
\r
17 Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 5A5E5431FAE
\r
19 for <notmuch@notmuchmail.org>; Thu, 14 Jan 2010 00:04:39 -0800 (PST)
\r
20 Received: from lapse.rw.madduck.net (unknown
\r
21 [IPv6:2404:130:0:1000:20a:e4ff:fe30:4316])
\r
22 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
23 (Client CN "lapse.rw.madduck.net",
\r
24 Issuer "CAcert Class 3 Root" (verified OK))
\r
25 by clegg.madduck.net (postfix) with ESMTPS id 03CF61D4097;
\r
26 Thu, 14 Jan 2010 09:04:24 +0100 (CET)
\r
27 Received: by lapse.rw.madduck.net (Postfix, from userid 1000)
\r
28 id 1DB8B1D72; Thu, 14 Jan 2010 21:04:21 +1300 (NZDT)
\r
29 Date: Thu, 14 Jan 2010 21:04:21 +1300
\r
30 From: martin f krafft <madduck@madduck.net>
\r
31 To: Carl Worth <cworth@cworth.org>
\r
32 Message-ID: <20100114080421.GA17305@lapse.rw.madduck.net>
\r
33 Mail-Followup-To: Carl Worth <cworth@cworth.org>,
\r
34 mailtags discussion list <mailtags@lists.madduck.net>,
\r
35 notmuch discussion list <notmuch@notmuchmail.org>
\r
36 References: <20100111221909.GA30299@lapse.rw.madduck.net>
\r
37 <87hbqpfp47.fsf@yoom.home.cworth.org>
\r
39 Content-Type: multipart/signed; micalg=pgp-ripemd160;
\r
40 protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga"
\r
41 Content-Disposition: inline
\r
42 In-Reply-To: <87hbqpfp47.fsf@yoom.home.cworth.org>
\r
43 X-Motto: Keep the good times rollin'
\r
44 X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686
\r
45 X-Spamtrap: madduck.bogus@madduck.net
\r
46 X-Subliminal-Message: debian/rules!
\r
47 User-Agent: Mutt/1.5.20 (2009-06-14)
\r
48 X-Virus-Scanned: clamav-milter 0.95.3 at clegg
\r
49 X-Virus-Status: Clean
\r
50 Cc: notmuch discussion list <notmuch@notmuchmail.org>,
\r
51 mailtags discussion list <mailtags@lists.madduck.net>
\r
52 Subject: Re: [notmuch] Idea for storing tags
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Thu, 14 Jan 2010 08:04:40 -0000
\r
69 Content-Type: text/plain; charset=us-ascii
\r
70 Content-Disposition: inline
\r
71 Content-Transfer-Encoding: quoted-printable
\r
73 also sprach Carl Worth <cworth@cworth.org> [2010.01.14.1432 +1300]:
\r
74 > Yes. This approach requires some external means of synchronizing the
\r
75 > tags from one system to another.
\r
77 > I don't understand what it would mean to have the mailstore and the
\r
78 > database out of synch here. This approach doesn't have the tags in the
\r
79 > mailstore by definition, right?
\r
81 You might have marked a message 'read' on one machine and if the two
\r
82 get out of sync on another machine, you might have the same message
\r
85 > > How about using pseudo-mails stored in Maildir and synchronised by
\r
86 > > IMAP? E.g. every folder could have a subfolder .TAGS and if we find
\r
87 > > a way to smartly pair messages between parent and subfolder, we'd
\r
88 > > have a tag store alongside the mailstore it refers to, but without
\r
89 > > the danger of leakage, and without having to rewrite messages.
\r
91 > > Anyway, the idea is out now. Thoughts?
\r
93 > There are a couple of problems that I don't see addressed at all with
\r
94 > this approach. The first is that there's not a one-to-one mapping
\r
95 > between messages and files in the mail store. (I'm CCed on a lot of list
\r
96 > mail meaning that I have multiple files in my mail store for a single
\r
99 Shouldn't this just be solved? I've had formail+procmail delete my
\r
100 duplicates for 10+ years, and while I don't like the fact that
\r
101 I usually get the CC before the list mail, and thus cannot filter on
\r
102 Delivered-To, I have never looked back.
\r
104 > Second, the only reason I would be interested in synchronizing mail
\r
105 > between two systems is so that I could manipulate the tag data in
\r
106 > multiple places, (that is, remove the "unread" tag whether on my
\r
107 > network-disconnected laptop or via web-mail when away from my
\r
108 > laptop). Using imap for synchronizing a file of tags within the mail
\r
109 > store gives you no mechanism for doing any sort of conflict resolution,
\r
110 > right? (Which I think in almost all cases is going to be quite trivial
\r
111 > if there's a chance for a program to resolve it.)
\r
113 I have not thought about this, but you are right. IMAP does not
\r
114 really allow for conflict resolution, which may well be *the* reason
\r
115 why you cannot update existing messages.
\r
117 > [*] Though, I think a plain-text file with tags managed with
\r
118 > something like git (and perhaps a custom merger) could save a lot
\r
119 > of work. Or perhaps a plain-text journal of tag manipulations on
\r
120 > either end that could be replayed on the other.
\r
122 Git is good at conflict resolution if run interactively, but [0]
\r
123 still makes me question whether it can ever take the place of IMAP.
\r
124 However, Asheesh Laroia, who has floated the idea of Git-for-mail at
\r
125 DebConf8 already, has some ideas and hopefully will soon reply to my
\r
126 mail [0], which I just bounced.
\r
128 0. http://notmuchmail.org/pipermail/notmuch/2010/001114.html
\r
131 martin | http://madduck.net/ | http://two.sentenc.es/
\r
133 apt-get source --compile gentoo
\r
135 spamtraps: madduck.bogus@madduck.net
\r
138 Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"
\r
139 Content-Description: Digital signature (see http://martin-krafft.net/gpg/)
\r
140 Content-Disposition: inline
\r
142 -----BEGIN PGP SIGNATURE-----
\r
143 Version: GnuPG v1.4.10 (GNU/Linux)
\r
145 iEYEAREDAAYFAktO0AEACgkQIgvIgzMMSnWOVACg1HfnIN/32SHgriDJcGlmVZ89
\r
146 RIIAoMgoimCO0wyA+zCsofr0vdCbxgNf
\r
148 -----END PGP SIGNATURE-----
\r
150 --opJtzjQTFsWo+cga--
\r
projects / notmuch-archives.git / blob