unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: associating a property with a subpart of a message
Date: Fri, 11 Aug 2017 00:49:08 -0400	[thread overview]
Message-ID: <87valupv3v.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87y3qu3pkf.fsf@tethera.net>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Tue 2017-08-08 14:02:56 -0400, David Bremner wrote:
> A hybrid option would be to use a hash of the file + 1.2.1.1. address
> scheme. My thinking here is a bit vague, but I can imagine such has hash
> being useful either for content addressible mailstore, or for
> disambiguating message-id collisions.

hm, interesting.  That would mean that you'd basically never get to
confidently reuse properties (because every copy of a mail you get
likely differs by some received headers), whereas for some normal mails
where you get multiple copies if you were just hashing the part then
you'd get the same thing.  otoh, if you're going to hash a part, that
raises the question of whether you're hashing the headers as well as the
body of that part, and its possible that those headers are being
rewritten someplace.

I suppose the other approach would be to just opportunistically try the
cached data as long as the message-id is the same thing, though.

is there an easy way to get the hash of the file that contains the
message from notmuch automagically?  do we need to worry about mbox
files as well?

I welcome any other ideas or suggestions!

  --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-08-11  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 23:35 associating a property with a subpart of a message Daniel Kahn Gillmor
2017-08-08 18:02 ` David Bremner
2017-08-11  4:49   ` Daniel Kahn Gillmor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87valupv3v.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).