Resent-From: "David A. Harding" <dave@dtrt.org>
Resent-Date: Tue, 12 Jan 2010 19:49:59 -0500
Resent-Message-ID: <20100113004959.GB32532@mail.dtrt.org>
Resent-To: mailtags discussion list <mailtags@lists.madduck.net>,
	notmuch discussion list <notmuch@notmuchmail.org>
Date: Tue, 12 Jan 2010 16:39:51 -0500
From: "David A. Harding" <dave@dtrt.org>
To: martin f krafft <madduck@madduck.net>
Message-ID: <20100112213951.GA9932@mail.dtrt.org>
References: <20100111221909.GA30299@lapse.rw.madduck.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100111221909.GA30299@lapse.rw.madduck.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Resent-Date: Tue, 12 Jan 2010 19:49:59 -0500
Subject: Re: [notmuch] Idea for storing tags
Precedence: list

On Tue, Jan 12, 2010 at 11:19:09AM +1300, martin f krafft wrote:
> I think [tag leakage] 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", 

You can cryptographically hash tags so that third-parties can't read
the contents of the in-headers. For security, a salt should be appended
to the tag name to make dictionary attacks on the tags more difficult.
For their owners' convenience, mail clients will want a mapping of hash
to tag name.

> [...] pseudo-mails stored in Maildir and synchronised by IMAP

A single RFC2822 message can store the salt and hash-to-tag database. It
could contain a clear subject and directions to the end user not to move
or delete it. This would not, I think, terribly confuse existing mail
clients or their users.

-Dave
-- 
David A. Harding	    Website:  http://dtrt.org/
1 (609) 997-0765	      Email:  dave@dtrt.org
			Jabber/XMPP:  dharding@jabber.org