X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-reply-1.mdwn;h=ad897b5fb45591af65878fff752bd81f3d06a16e;hb=219490b75a85ca18d449168575a0c7538e71612e;hp=79ef1ff32a92e217f7b5e7b54309862d0566650e;hpb=cf2df983cb6d13042694366be4aba76d4a98048b;p=notmuch-wiki diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 79ef1ff..ad897b5 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -15,70 +15,81 @@ 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 + 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|sexp|headers-only) + + --format=(default|json|sexp|headers-only) default - Includes subject and quoted message body as an RFC 2822 + 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. - sexp 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 + 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. headers-only - Only produces In-Reply-To, References, To, Cc, and Bcc + Only produces In-Reply-To, References, To, Cc, and Bcc headers. - --format-version=N - Use the specified structured output format version. This is - intended for programs that invoke notmuch(1) internally. If - omitted, the latest supported version will be used. + --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. - --reply-to=(all|sender) + --reply-to=(all|sender) 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 + 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 + ers in this order, and copy values from the first that contains something other than only the user's addresses. - --decrypt - 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. + --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. - Decryption expects a functioning gpg-agent(1) to provide any - needed credentials. Without one, the decryption will fail. + Default: auto See notmuch-search-terms(7) for details of the supported syntax for <search-terms>. @@ -116,7 +127,7 @@

COPYRIGHT

-       2014, Carl Worth and many others
+       2009-2022, Carl Worth and many others
-

0.19

+

0.35