On Fri, Dec 9, 2011 at 18:13, Oliver Kiddle
Jon Fairbairn wrote:
Long ago, before mh I used an email system that stored email in
files with unique ids, which suggests a way to do this. Switch
to storing messages in (say) date-named accession order folders
with unique filenames (derived from the message-id, or simply
accession numbers) while the mh folders would contain symlinks
to these with numeric names as now. So (to continue the example)
sortm would not rename any message files, but just rearrange the
If you're going to do that, you might aswell name the files using an
SHA hash. It's not like mail files change often. The idea makes me
wonder if git could be used as a mailstore. With a blob for each message
and tag-blobs for classifying messages. Could be nice if you can push
and pull mail between machines.
I don't know whether to say great minds think alike, or that you are sick.
Because I had similar thoughts this morning...
One thing I would like to add, is if that we are going to build an index,
it would be really handy to include the Message-ID in an index. This would
make it very easy for front-ends to thread e-mail, follow references, etc.
I have my fetchmail scripts ignore messages with a duplicate messageid
(using a history of messageids I've received during the last 30 days or so)
to avoid duplicate mail.
It is probably too much to assume that everyone would not have duplicate
copies of a message with the same messageid. Some people may have valid
reasons for this. And there may be messages w/o a message-id.
Jeffrey C. Honig <jch(_at_)honig(_dot_)net>
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>
Nmh-workers mailing list