From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: associating a property with a subpart of a message
Date: Wed, 02 Aug 2017 19:35:45 -0400 [thread overview]
Message-ID: <87wp6lbl0u.fsf@fifthhorseman.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
hey folks--
I have some message properties i'd like to cache in notmuch that
strictly apply to specific subparts of the message. (e.g. session keys
for an encrypted part, signature verification status of a signed part)
let's assume that for any given copy of a message, we have a reliable
"address" scheme for a part (e.g. "1.2.1.1").
However, this becomes confusing with multiple copies of a given message.
It's possible that one copy of the message has one MIME structure, but
mangling (by MTAs, mailing lists, etc) result in a different MIME
structure in another copy.
For cryptographic properties, it might be nice to associate a subpart
with a particular cryptographic digest of the subpart itself.
Alternately, from a filesystem perspective, maybe it would be better to
label the subpart based on the underlying physical file, and the
subpart's "address".
Are there other options?
If you wanted to associate a message property with a subpart of a given
message in a way that was reliable, especially in this new era of
multiple copies of a message, how would you do it?
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2017-08-02 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 23:35 Daniel Kahn Gillmor [this message]
2017-08-08 18:02 ` associating a property with a subpart of a message David Bremner
2017-08-11 4:49 ` Daniel Kahn Gillmor
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=87wp6lbl0u.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.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).