From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 55FFB431FBC for ; Mon, 11 Jan 2010 14:19:30 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QGfssk7ihIYR for ; Mon, 11 Jan 2010 14:19:29 -0800 (PST) Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96]) by olra.theworths.org (Postfix) with ESMTP id 6F5B5431FAE for ; Mon, 11 Jan 2010 14:19:29 -0800 (PST) Received: from lapse.rw.madduck.net (unknown [IPv6:2404:130:0:1000:20a:e4ff:fe30:4316]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "lapse.rw.madduck.net", Issuer "CAcert Class 3 Root" (verified OK)) by clegg.madduck.net (postfix) with ESMTPS id B6F071D4097; Mon, 11 Jan 2010 23:19:20 +0100 (CET) Received: by lapse.rw.madduck.net (Postfix, from userid 1000) id 57641E20; Tue, 12 Jan 2010 11:19:09 +1300 (NZDT) Date: Tue, 12 Jan 2010 11:19:09 +1300 From: martin f krafft To: mailtags discussion list Message-ID: <20100111221909.GA30299@lapse.rw.madduck.net> Mail-Followup-To: mailtags discussion list , notmuch discussion list MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline X-Motto: Keep the good times rollin' X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686 X-Spamtrap: madduck.bogus@madduck.net X-Subliminal-Message: debian/rules! User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.3 at clegg X-Virus-Status: Clean Cc: notmuch discussion list Subject: Idea for storing tags X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 22:19:30 -0000 --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Folks, over in #notmuch, we just floated an idea that I'd like to get out to you. We've been debating storing tags for messages. Therefore I am cross-posting. Please forgive me. So far, there are two approaches: 1. External database, which has the downside of not being synchronisable with standard IMAP, like the rest of your mail (assuming you use IMAP). Also, it's possible for mailstore and database to get out of sync. 2. In-headers, which has the downside of leaking (e.g. when bouncing), and incurs the risks associated with message rewrites (which I think is pretty much ignorable, but it's still there). Also, there's a performance issue, but in the context of an indexer like notmuch, this is negligible. The leakage is real, though and I think it makes in-headers unusable. After all, I don't ever want anyone else to know that I tag e-mails from my boss as "from-idiots", and I forward and bounce mail on a regular basis. I could tell my MTA to remove those headers, but I might forget to do that on a new system. We also previously determined that IMAP keywords are pretty much useless as they are stored per mailbox, not per message, not standardised, and limited in their length anyway [0]. This also means that we don't really need to investigate sensibly storing tags in Maildir (e.g. with xattrs), because IMAP cannot transport them. 0. http://lists.madduck.net/pipermail/mailtags/2007-August/msg00016.html Seriously, who implemented IMAPv4rev1 and what sort of crack were they smoking?? I remember there was some KDE groupware contacts manager that used IMAP to synchronise contacts. At first, this sounds horrible, but when you detach IMAP from RFC822, it becomes a generic synchronising protocol. The next step is then straight forward, and I want to share this idea with you: How about using pseudo-mails stored in Maildir and synchronised by IMAP? E.g. every folder could have a subfolder .TAGS and if we find a way to smartly pair messages between parent and subfolder, we'd have a tag store alongside the mailstore it refers to, but without the danger of leakage, and without having to rewrite messages. The major problem with this is when clients don't understand this "protocol", for then they will display all .TAGS folders as regular IMAP folders, and try to treat the messages therein as regular mails. Somewhere sometime this is bound to blow up and I don't really know how to prevent that. Anyway, the idea is out now. Thoughts? --=20 martin | http://madduck.net/ | http://two.sentenc.es/ =20 echo Prpv a\'rfg cnf har cvcr | tr Pacfghnrvp Cnpstuaeic =20 spamtraps: madduck.bogus@madduck.net --SUOF0GtieIMvvwua 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) iEYEAREDAAYFAktLo90ACgkQIgvIgzMMSnVyxACePZQG9TNH+BUTbYtatVCXYcBf H7oAn2Jg9v6+Mm8lGNE1szBX3DVlv/zy =6OCS -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--