1 <h1>NOTMUCH-REPLY(1)</h1>
5 notmuch-reply - Constructs a reply template for a set of messages.
10 <b>notmuch</b> <b>reply</b> [<u>options</u>...] <<u>search-term</u>>...
15 Constructs a reply template for a set of messages.
17 To make replying to email easier, <b>notmuch</b> <b>reply</b> takes an existing set
18 of messages and constructs a suitable mail template. The Reply-to:
19 header (if any, otherwise From:) is used for the To: address. Unless
20 <b>--reply-to=sender</b> is specified, values from the To: and Cc: headers are
21 copied, but not including any of the current user's email addresses (as
22 configured in primary_mail or other_email in the .notmuch-config file)
23 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 <b>reply</b> include
37 <b>--format=</b>(<b>default</b>|<b>json</b>|<b>headers-only</b>)
40 Includes subject and quoted message body.
43 Produces JSON output containing headers for a reply mes-
44 sage and the contents of the original message. This out-
45 put can be used by a client to create a reply message
49 Only produces In-Reply-To, References, To, Cc, and Bcc
52 <b>--reply-to=</b>(<b>all</b>|<b>sender</b>)
55 Replies to all addresses.
58 Replies only to the sender. If replying to user's own
59 message (Reply-to: or From: header is one of the user's
60 configured email addresses), try To:, Cc:, and Bcc:
61 headers in this order, and copy values from the first
62 that contains something other than only the user's
67 Decrypt any MIME encrypted parts found in the selected con-
68 tent (ie. "multipart/encrypted" parts). Status of the
69 decryption will be reported (currently only supported with
70 --format=json) and the multipart/encrypted part will be
71 replaced by the decrypted content.
73 See <a href='../notmuch-search-terms-7/'>notmuch-search-terms</a>(7) for details of the supported syntax for
76 Note: It is most common to use <b>notmuch</b> <b>reply</b> with a search string
77 matching a single message, (such as id:<message-id>), but it can be
78 useful to reply to several messages at once. For example, when a series
79 of patches are sent in a single thread, replying to the entire thread
80 allows for the reply to comment on issues found in multiple patches.
81 The default format supports replying to multiple messages at once, but
82 the JSON format does not.
87 <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>
88 <a href='../notmuch-hooks-5/'>much-hooks</a>(5), <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),
89 <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/'>notmuch-tag</a>(1)
92 <h2>Notmuch 0.13.2</h2>