8 **notmuch** **reply** [option ...] <*search-term*> ...
13 Constructs a reply template for a set of messages.
15 To make replying to email easier, **notmuch reply** takes an existing
16 set of messages and constructs a suitable mail template. Its To:
17 address is set according to the original email in this way: if the
18 Reply-to: header is present and different from any To:/Cc: address it
19 is used, otherwise From: header is used. Unless
20 ``--reply-to=sender`` is specified, values from the To: and Cc: headers
21 are copied, but not including any of the current user's email addresses
22 (as configured in primary\_mail or other\_email in the .notmuch-config
23 file) in the recipient list.
25 It also builds a suitable new subject, including Re: at the front (if
26 not already present), and adding the message IDs of the messages being
27 replied to to the References list and setting the In-Reply-To: field
30 Finally, the original contents of the emails are quoted by prefixing
31 each line with '> ' and included in the body.
33 The resulting message template is output to stdout.
35 Supported options for **reply** include
37 ``--format=``\ (**default**\ \|\ **json**\ \|\ **sexp**\ \|\ **headers-only**)
40 Includes subject and quoted message body as an RFC 2822
44 Produces JSON output containing headers for a reply message
45 and the contents of the original message. This output can be
46 used by a client to create a reply message intelligently.
49 Produces S-Expression output containing headers for a reply
50 message and the contents of the original message. This
51 output can be used by a client to create a reply message
55 Only produces In-Reply-To, References, To, Cc, and Bcc
58 ``--format-version=N``
59 Use the specified structured output format version. This is
60 intended for programs that invoke **notmuch(1)** internally. If
61 omitted, the latest supported version will be used.
63 ``--reply-to=``\ (**all**\ \|\ **sender**)
66 Replies to all addresses.
69 Replies only to the sender. If replying to user's own
70 message (Reply-to: or From: header is one of the user's
71 configured email addresses), try To:, Cc:, and Bcc: headers
72 in this order, and copy values from the first that contains
73 something other than only the user's addresses.
75 ``--decrypt=(false|auto|true)``
77 If ``true``, decrypt any MIME encrypted parts found in the
78 selected content (i.e., "multipart/encrypted" parts). Status
79 of the decryption will be reported (currently only supported
80 with --format=json and --format=sexp), and on successful
81 decryption the multipart/encrypted part will be replaced by
82 the decrypted content.
84 If ``auto``, and a session key is already known for the
85 message, then it will be decrypted, but notmuch will not try
86 to access the user's secret keys.
88 Use ``false`` to avoid even automatic decryption.
90 Non-automatic decryption expects a functioning
91 **gpg-agent(1)** to provide any needed credentials. Without
92 one, the decryption will likely fail.
96 See **notmuch-search-terms(7)** for details of the supported syntax for
99 Note: It is most common to use **notmuch reply** with a search string
100 matching a single message, (such as id:<message-id>), but it can be
101 useful to reply to several messages at once. For example, when a series
102 of patches are sent in a single thread, replying to the entire thread
103 allows for the reply to comment on issues found in multiple patches. The
104 default format supports replying to multiple messages at once, but the
105 JSON and S-Expression formats do not.
110 This command supports the following special exit status codes
113 The requested format version is too old.
116 The requested format version is too new.
122 **notmuch-config(1)**,
123 **notmuch-count(1)**,
125 **notmuch-hooks(5)**,
126 **notmuch-insert(1)**,
128 **notmuch-restore(1)**,
129 **notmuch-search(1)**,
130 **notmuch-search-terms(7)**,