1 <h1>NOTMUCH-REPLY(1)</h1>
6 notmuch-reply - Constructs a reply template for a set of messages.
12 <b>notmuch</b> <b>reply</b> [<u>options</u>...] <<u>search-term</u>>...
18 Constructs a reply template for a set of messages.
22 To make replying to email easier, <b>notmuch</b> <b>reply</b> takes an existing set
23 of messages and constructs a suitable mail template. The Reply-to:
24 header (if any, otherwise From:) is used for the To: address. Unless
25 <b>--reply-to=sender</b> is specified, values from the To: and Cc: headers are
26 copied, but not including any of the current user's email addresses (as
27 configured in primary_mail or other_email in the .notmuch-config file)
28 in the recipient list.
32 It also builds a suitable new subject, including Re: at the front (if
33 not already present), and adding the message IDs of the messages being
34 replied to to the References list and setting the In-Reply-To: field
39 Finally, the original contents of the emails are quoted by prefixing
40 each line with '> ' and included in the body.
44 The resulting message template is output to stdout.
48 Supported options for <b>reply</b> include
52 <b>--format=</b>(<b>default</b>|<b>json</b>|<b>headers-only</b>)
57 Includes subject and quoted message body.
62 Produces JSON output containing headers for a reply mes-
63 sage and the contents of the original message. This out-
64 put can be used by a client to create a reply message
70 Only produces In-Reply-To, References, To, Cc, and Bcc
75 <b>--reply-to=</b>(<b>all</b>|<b>sender</b>)
80 Replies to all addresses.
85 Replies only to the sender. If replying to user's own
86 message (Reply-to: or From: header is one of the user's
87 configured email addresses), try To:, Cc:, and Bcc:
88 headers in this order, and copy values from the first
89 that contains something other than only the user's
98 Decrypt any MIME encrypted parts found in the selected
99 content (ie. "multipart/encrypted" parts). Status of the
100 decryption will be reported (currently only supported with
101 --format=json) and the multipart/encrypted part will be
102 replaced by the decrypted content.
106 See <b>notmuch-search-terms</b>(7) for details of the supported syntax for
111 Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
112 matching a single message, (such as id:<message-id>), but it can be
113 useful to reply to several messages at once. For example, when a series
114 of patches are sent in a single thread, replying to the entire thread
115 allows for the reply to comment on issues found in multiple patches.
116 The default format supports replying to multiple messages at once, but
117 the JSON format does not.
123 <b>notmuch</b>(1), <b>notmuch-config</b>(1), <b>notmuch-count</b>(1), <b>notmuch-dump</b>(1), <b>not-</b>
124 <b>much-hooks</b>(5), <b>notmuch-new</b>(1), <b>notmuch-restore</b>(1), <b>notmuch-search</b>(1),
125 <b>notmuch-search-terms</b>(7), <b>notmuch-show</b>(1), <b>notmuch-tag</b>(1)
128 <h2>Notmuch 0.13.2</h2>