<h1>NOTMUCH-REPLY(1)</h1>
<h2>NAME</h2>
-
<pre>
- notmuch-reply - Constructs a reply template for a set of messages.
+ notmuch-reply - constructs a reply template for a set of messages
</pre>
<h2>SYNOPSIS</h2>
-
<pre>
- <b>notmuch</b> <b>reply</b> [<u>options</u>...] <<u>search-term</u>>...
+ <b>notmuch</b> <b>reply</b> [option ...] <<u>search-term</u>> ...
</pre>
<h2>DESCRIPTION</h2>
-
<pre>
Constructs a reply template for a set of messages.
-</pre>
-<pre>
To make replying to email easier, <b>notmuch</b> <b>reply</b> takes an existing set
- of messages and constructs a suitable mail template. The Reply-to:
- header (if any, otherwise From:) is used for the To: address. Unless
- <b>--reply-to=sender</b> is specified, values from the To: and Cc: headers are
- copied, but not including any of the current user's email addresses (as
- configured in primary_mail or other_email in the .notmuch-config file)
- in the recipient list.
-</pre>
-
-<pre>
- It also builds a suitable new subject, including Re: at the front (if
- not already present), and adding the message IDs of the messages being
- replied to to the References list and setting the In-Reply-To: field
+ of messages and constructs a suitable mail template. Its To: address is
+ set according to the original email in this way: if the Reply-to:
+ header is present and different from any To:/Cc: address it is used,
+ otherwise From: header is used. Unless <b>--reply-to=sender</b> is specified,
+ values from the To: and Cc: headers are copied, but not including any
+ of the current user's email addresses (as configured in primary_mail or
+ other_email in the .notmuch-config file) in the recipient list.
+
+ It also builds a suitable new subject, including Re: at the front (if
+ not already present), and adding the message IDs of the messages being
+ replied to to the References list and setting the In-Reply-To: field
correctly.
-</pre>
-<pre>
- Finally, the original contents of the emails are quoted by prefixing
- each line with '> ' and included in the body.
-</pre>
+ Finally, the original contents of the emails are quoted by prefixing
+ each line with '> ' and included in the body.
-<pre>
The resulting message template is output to stdout.
-</pre>
-<pre>
Supported options for <b>reply</b> include
-</pre>
-<pre>
- <b>--format=</b>(<b>default</b>|<b>json</b>|<b>headers-only</b>)
-</pre>
+ <b>--format=(default|json|sexp|headers-only)</b>
-<pre>
- <b>default</b>
- Includes subject and quoted message body.
-</pre>
+ <b>default</b>
+ Includes subject and quoted message body as an RFC 2822
+ message.
-<pre>
- <b>json</b>
- Produces JSON output containing headers for a reply mes-
- sage and the contents of the original message. This out-
- put can be used by a client to create a reply message
- intelligently.
-</pre>
+ <b>json</b> Produces JSON output containing headers for a reply mes‐
+ sage and the contents of the original message. This out‐
+ put can be used by a client to create a reply message in‐
+ telligently.
-<pre>
- <b>headers-only</b>
- Only produces In-Reply-To, References, To, Cc, and Bcc
- headers.
-</pre>
+ <b>sexp</b> Produces S-Expression output containing headers for a re‐
+ ply message and the contents of the original message.
+ This output can be used by a client to create a reply
+ message intelligently.
-<pre>
- <b>--reply-to=</b>(<b>all</b>|<b>sender</b>)
-</pre>
+ <b>headers-only</b>
+ Only produces In-Reply-To, References, To, Cc, and Bcc
+ headers.
-<pre>
- <b>all</b> (default)
- Replies to all addresses.
-</pre>
+ <b>--format-version=N</b>
+ Use the specified structured output format version. This is in‐
+ tended for programs that invoke <a href='../notmuch-1/'>notmuch</a>(1) internally. If omit‐
+ ted, the latest supported version will be used.
-<pre>
- <b>sender</b>
- Replies only to the sender. If replying to user's own
- message (Reply-to: or From: header is one of the user's
- configured email addresses), try To:, Cc:, and Bcc:
- headers in this order, and copy values from the first
- that contains something other than only the user's
- addresses.
-</pre>
+ <b>--reply-to=(all|sender)</b>
-<pre>
- <b>--decrypt</b>
+ <b>all</b> <b>(default)</b>
+ Replies to all addresses.
+
+ <b>sender</b> Replies only to the sender. If replying to user's own
+ message (Reply-to: or From: header is one of the user's
+ configured email addresses), try To:, Cc:, and Bcc: head‐
+ ers in this order, and copy values from the first that
+ contains something other than only the user's addresses.
+
+ <b>--decrypt=(false|auto|true)</b>
+ If <b>true</b>, decrypt any MIME encrypted parts found in the selected
+ content (i.e., "multipart/encrypted" parts). Status of the de‐
+ cryption will be reported (currently only supported with <b>--for-</b>
+ <b>mat=json</b> and <b>--format=sexp</b>), and on successful decryption the
+ multipart/encrypted part will be replaced by the decrypted con‐
+ tent.
+
+ If <b>auto</b>, and a session key is already known for the message,
+ then it will be decrypted, but notmuch will not try to access
+ the user's secret keys.
+
+ Use <b>false</b> to avoid even automatic decryption.
+
+ Non-automatic decryption expects a functioning <b>gpg-agent</b>(1) to
+ provide any needed credentials. Without one, the decryption will
+ likely fail.
+
+ Default: <b>auto</b>
+
+ See <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7) for details of the supported syntax for
+ <search-terms>.
+
+ Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
+ matching a single message, (such as id:<message-id>), but it can be
+ useful to reply to several messages at once. For example, when a series
+ of patches are sent in a single thread, replying to the entire thread
+ allows for the reply to comment on issues found in multiple patches.
+ The default format supports replying to multiple messages at once, but
+ the JSON and S-Expression formats do not.
</pre>
+<h2>EXIT STATUS</h2>
<pre>
- Decrypt any MIME encrypted parts found in the selected con-
- tent (ie. "multipart/encrypted" parts). Status of the
- decryption will be reported (currently only supported with
- --format=json) and the multipart/encrypted part will be
- replaced by the decrypted content.
+ This command supports the following special exit status codes
+
+ <b>20</b> The requested format version is too old.
+
+ <b>21</b> The requested format version is too new.
</pre>
+<h2>SEE ALSO</h2>
<pre>
- See <b>notmuch-search-terms</b>(7) for details of the supported syntax for
- <search-terms>.
+ <a href='../notmuch-1/'>notmuch</a>(1), <a href='../notmuch-config-1/'>notmuch-config</a>(1), <a href='../notmuch-count-1/'>notmuch-count</a>(1), <a href='../notmuch-dump-1/'>notmuch-dump</a>(1), <a href='../notmuch-hooks-5/'>not‐</a>
+ <a href='../notmuch-hooks-5/'>much-hooks</a>(5), <a href='../notmuch-insert-1/'>notmuch-insert</a>(1), <a href='../notmuch-new-1/'>notmuch-new</a>(1), <a href='../notmuch-restore-1/'>notmuch-restore</a>(1),
+ <a href='../notmuch-search-1/'>notmuch-search</a>(1), <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7), <a href='../notmuch-show-1/'>notmuch-show</a>(1), <a href='../notmuch-tag-1/'>not‐</a>
+ <a href='../notmuch-tag-1/'>much-tag</a>(1)
</pre>
+<h2>AUTHOR</h2>
<pre>
- Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
- matching a single message, (such as id:<message-id>), but it can be
- useful to reply to several messages at once. For example, when a series
- of patches are sent in a single thread, replying to the entire thread
- allows for the reply to comment on issues found in multiple patches.
- The default format supports replying to multiple messages at once, but
- the JSON format does not.
+ Carl Worth and many others
</pre>
-<h2>SEE ALSO</h2>
-
+<h2>COPYRIGHT</h2>
<pre>
- <b>notmuch</b>(1), <b>notmuch-config</b>(1), <b>notmuch-count</b>(1), <b>notmuch-dump</b>(1), <b>not-</b>
- <b>much-hooks</b>(5), <b>notmuch-new</b>(1), <b>notmuch-restore</b>(1), <b>notmuch-search</b>(1),
- <b>notmuch-search-terms</b>(7), <b>notmuch-show</b>(1), <b>notmuch-tag</b>(1)
+ 2009-2022, Carl Worth and many others
</pre>
-<h1>Notmuch 0.13.2</h1>
+<h2>0.35</h2>
projects / notmuch-wiki / blobdiff