+<h2>EXAMPLES</h2>
+<pre>
+ A user just received an encrypted message without indexing its cleart‐
+ ext. After reading it (via <b>notmuch</b> <b>show</b> <b>--decrypt=true</b>), they decide
+ that they want to index its cleartext so that they can easily find it
+ later and read it without having to have access to their secret keys:
+
+ notmuch reindex --decrypt=true id:1234567@example.com
+
+ A user wants to change their policy going forward to start indexing
+ cleartext. But they also want indexed access to the cleartext of all
+ previously-received encrypted messages. Some messages might have al‐
+ ready been indexed in the clear (as in the example above). They can ask
+ notmuch to just reindex the not-yet-indexed messages:
+
+ notmuch config set index.decrypt true
+ notmuch reindex tag:encrypted and not property:index.decryption=success
+
+ Later, the user changes their mind, and wants to stop indexing cleart‐
+ ext (perhaps their threat model has changed, or their trust in their
+ index store has been shaken). They also want to clear all of their old
+ cleartext from the index. Note that they compact the database after‐
+ ward as a workaround for <u>https://trac.xapian.org/ticket/742</u>:
+
+ notmuch config set index.decrypt false
+ notmuch reindex property:index.decryption=success
+ notmuch compact
+</pre>
+