begin quoting Lan Barnes as of Mon, Feb 21, 2005 at 10:20:49PM -0800: > On Mon, Feb 21, 2005 at 09:45:32PM -0800, Stewart Stremler wrote: > > begin quoting Lan Barnes as of Mon, Feb 21, 2005 at 04:47:20PM -0800: > > > > Well, use Message-IDs to identify the message. Have some logic that > > trawls through an archive directory or directories to locate contents > > of said message. > > Message-IDs you say. OK. A place to start.
That's what they're there for. :) > > Then start caching where such a message was "last seen", and when; the > > user can then have a ready mechanism to "purge" the database of stale > > information, or not, if they archive everything off on to CDs once a > > year or so. > > Something has to go from "I saw it here" to "here it is." Not finding it "here" would be a place to start. "I last saw it $here. Whoops. It's not there anymore. Let's start looking for it..... ah, $there it is! Update!" [snip] > > Make it work with MailDir & MBox to start... An MUA that doesn't support > > or use one or the other isn't interested in playing nice with anyone else > > *anyway*, and so removes itself from consideration. > > That would be the plan. Maybe a reindex function to occasionally ... you > know, _reindex_. Yup. "I've moved a bunch of stuff around. Let me tell the tool to reindex." Plus, when you drop in a new archive, you can start off with "re"indexing... Alas, the _common_ solution seems to be "Let me take control over all of the data." Y'know, _integrated_ tools.... -Stewart "Not fond of integrated toolsets." Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
