X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=ad897b5fb45591af65878fff752bd81f3d06a16e;hb=7b185873e25722b59e3c03591b239564ca2543f6;hp=941dd43545e35d5fba828c13a0632806f7c0a0e4;hpb=01b1bc7553d0b0ebf35ac3016c83240b4151ad59;p=notmuch-wiki diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 941dd43..ad897b5 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -1,128 +1,133 @@
- notmuch-reply - Constructs a reply template for a set of messages. + notmuch-reply - constructs a reply template for a set of messages
- notmuch reply [options...] <search-term>... + notmuch reply [option ...] <search-term> ...
Constructs a reply template for a set of messages. --
To make replying to email easier, notmuch reply 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 - --reply-to=sender 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 --reply-to=sender 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 - each line with '> ' and included in the body. -+ 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 reply include --
- --format=(default|json|headers-only) -+ --format=(default|json|sexp|headers-only) -
- default - Includes subject and quoted message body. -+ default + Includes subject and quoted message body as an RFC 2822 + message. -
- json - 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. -+ json 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. -
- headers-only - Only produces In-Reply-To, References, To, Cc, and Bcc - headers. -+ sexp 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. -
- --reply-to=(all|sender) -+ headers-only + Only produces In-Reply-To, References, To, Cc, and Bcc + headers. -
- all (default) - Replies to all addresses. -+ --format-version=N + Use the specified structured output format version. This is inâ + tended for programs that invoke notmuch(1) internally. If omitâ + ted, the latest supported version will be used. -
- sender - 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. -+ --reply-to=(all|sender) -
- --decrypt + all (default) + Replies to all addresses. + + sender 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. + + --decrypt=(false|auto|true) + If true, 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 --for- + mat=json and --format=sexp), and on successful decryption the + multipart/encrypted part will be replaced by the decrypted conâ + tent. + + If auto, 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 false to avoid even automatic decryption. + + Non-automatic decryption expects a functioning gpg-agent(1) to + provide any needed credentials. Without one, the decryption will + likely fail. + + Default: auto + + See notmuch-search-terms(7) for details of the supported syntax for + <search-terms>. + + Note: It is most common to use notmuch reply 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.+
- 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 + + 20 The requested format version is too old. + + 21 The requested format version is too new.+
- See notmuch-search-terms(7) for details of the supported syntax for -+. + notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notâ + much-hooks(5), notmuch-insert(1), notmuch-new(1), notmuch-restore(1), + notmuch-search(1), notmuch-search-terms(7), notmuch-show(1), notâ + much-tag(1)
- Note: It is most common to use notmuch reply with a search string - matching a single message, (such as 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
- notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), not- - much-hooks(5), notmuch-new(1), notmuch-restore(1), notmuch-search(1), - notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1) + 2009-2022, Carl Worth and many others-