X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-properties-7.mdwn;h=44d455a4f4147e12d7a30b9d82401ce145c48baa;hb=85fe2a1e7df8ccbb172ebf5f10e3cf574a08944a;hp=8cb4c67c90edbee5d4afe5bdf36da5096e4c6dfa;hpb=ed52cd4055a160d4264b71aebe9e4276298da29e;p=notmuch-wiki diff --git a/manpages/notmuch-properties-7.mdwn b/manpages/notmuch-properties-7.mdwn index 8cb4c67..44d455a 100644 --- a/manpages/notmuch-properties-7.mdwn +++ b/manpages/notmuch-properties-7.mdwn @@ -57,13 +57,13 @@ index.decryption If a message contains encrypted content, and notmuch tries to decrypt that content during indexing, it will add the property - index.decryption=success when the cleartext was successfully - indexed. If notmuch attempts to decrypt any part of a message + index.decryption=success when the cleartext was successfully in‐ + dexed. If notmuch attempts to decrypt any part of a message during indexing and that decryption attempt fails, it will add the property index.decryption=failure to the message. - Note that it's possible for a single message to have both - index.decryption=success and index.decryption=failure. Consider + Note that it's possible for a single message to have both in- + dex.decryption=success and index.decryption=failure. Consider an encrypted e-mail message that contains another encrypted e-mail message as an attachment -- if the outer message can be decrypted, but the attached part cannot, then both properties @@ -75,22 +75,22 @@ sage. session-key - When notmuch-show(1) or nomtuch-reply encounters a message with an - encrypted part, if notmuch finds a session-key property associated - with the message, it will try that stashed session key for decryp‐ - tion. + When notmuch-show(1) or notmuch-reply(1) encounters a message with + an encrypted part, if notmuch finds a session-key property associ‐ + ated with the message, it will try that stashed session key for de‐ + cryption. If you do not want to use any stashed session keys that might be present, you should pass those programs --decrypt=false. Using a stashed session key with "notmuch show" will speed up ren‐ - dering of long encrypted threads. It also allows the user to - destroy the secret part of any expired encryption-capable subkey - while still being able to read any retained messages for which they - have stashed the session key. This enables truly deletable e-mail, - since (once the session key and asymmetric subkey are both - destroyed) there are no keys left that can be used to decrypt any - copy of the original message previously stored by an adversary. + dering of long encrypted threads. It also allows the user to de‐ + stroy the secret part of any expired encryption-capable subkey while + still being able to read any retained messages for which they have + stashed the session key. This enables truly deletable e-mail, since + (once the session key and asymmetric subkey are both destroyed) + there are no keys left that can be used to decrypt any copy of the + original message previously stored by an adversary. However, access to the stashed session key for an encrypted message permits full byte-for-byte reconstruction of the cleartext message. @@ -107,13 +107,35 @@ tion of the algorithm-specific key. For example, an AES-128 key might be stashed in a notmuch property as: ses- sion-key=7:14B16AF65536C28AF209828DFE34C9E0. + + index.repaired + Some messages arrive in forms that are confusing to view; they can + be mangled by mail transport agents, or the sending mail user agent + may structure them in a way that is confusing. If notmuch knows how + to both detect and repair such a problematic message, it will do so + during indexing. + + If it applies a message repair during indexing, it will use the in- + dex.repaired property to note the type of repair(s) it performed. + + index.repaired=skip-protected-headers-legacy-display indicates that + when indexing the cleartext of an encrypted message, notmuch skipped + over a "legacy-display" text/rfc822-headers part that it found in + that message, since it was able to index the built-in protected + headers directly. + + index.repaired=mixedup indicates the repair of a "Mixed Up" en‐ + crypted PGP/MIME message, a mangling typically produced by Micro‐ + soft's + https://tools.ietf.org/html/draft-dkg-openpgp-pgpmime-message-mangling + for more information.

SEE ALSO

        notmuch(1), notmuch-config(1), notmuch-dump(1), notmuch-insert(1), not‐
-       much-new(1), notmuch-reindex(1), notmuch-reply(1),  notmuch-restore(1),
-       notmuch-show(1), *notmuch-search-terms(7)
+       much-new(1),  notmuch-reindex(1), notmuch-reply(1), notmuch-restore(1),
+       notmuch-search-terms(7), notmuch-show(1)

AUTHOR

@@ -123,7 +145,7 @@

COPYRIGHT

-       2009-2018, Carl Worth and many others
+       2009-2021, Carl Worth and many others
-

0.28

+

0.33