Constructs a reply template for a set of messages.
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.
-
- 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.
- Finally, the original contents of the emails are quoted by prefixing
+ Finally, the original contents of the emails are quoted by prefixing
each line with '> ' and included in the body.
The resulting message template is output to stdout.
Supported options for <b>reply</b> include
- <b>--format=</b>(<b>default</b>|<b>json</b>|<b>sexp</b>|<b>headers-only</b>)
+
+ <b>--format=(default|json|sexp|headers-only)</b>
<b>default</b>
- Includes subject and quoted message body as an RFC 2822
+ Includes subject and quoted message body as an RFC 2822
message.
- <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.
+ <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.
- <b>sexp</b> Produces S-Expression output containing headers for a
- reply message and the contents of the original message.
- This output can be used by a client to create a reply
+ <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.
<b>headers-only</b>
- Only produces In-Reply-To, References, To, Cc, and Bcc
+ Only produces In-Reply-To, References, To, Cc, and Bcc
headers.
- <b>--format-version=N</b>
- Use the specified structured output format version. This is
- intended for programs that invoke <a href='../notmuch-1/'>notmuch</a>(1) internally. If
- omitted, the latest supported version will be used.
+ <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.
- <b>--reply-to=</b>(<b>all</b>|<b>sender</b>)
+ <b>--reply-to=(all|sender)</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
+ <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
+ ers in this order, and copy values from the first that
contains something other than only the user's addresses.
- <b>--decrypt</b>
- Decrypt any MIME encrypted parts found in the selected con‐
- tent (ie. "multipart/encrypted" parts). Status of the decryp‐
- tion will be reported (currently only supported with --for‐
- mat=json and --format=sexp) and on successful decryption the
- multipart/encrypted part will be replaced by the decrypted
- content.
+ <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.
- Decryption expects a functioning <b>gpg-agent</b>(1) to provide any
- needed credentials. Without one, the decryption will 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>.
<h2>COPYRIGHT</h2>
<pre>
- 2014, Carl Worth and many others
+ 2009-2022, Carl Worth and many others
</pre>
-<h2>0.18.1</h2>
+<h2>0.35</h2>
projects / notmuch-wiki / blobdiff