1
0
mirror of https://github.com/djcb/mu.git synced 2024-06-22 07:06:48 +02:00
mu/man/mu-verify.1.org
Jeremy Sowden c76aa53156 man: fix formatting of NAME sections
The command names are formatted inconsistently, e.g.:

    * NAME

    ~mu add~ - add one or more messages to the database

versus:

    * NAME

    *mu cfind* is the *mu* command to find contacts in the *mu* database and export them

versus:

    * NAME

    mu server - the mu backend for the mu4e e-mail client

and the format, with a space between "mu" and the subcommand, is not compatible
with mandb(8).  Use formatting which is consistent and replace the spaces with
hyphens.

Signed-off-by: Jeremy Sowden <azazel@debian.org>
2024-03-06 21:12:32 +00:00

56 lines
1.3 KiB
Org Mode

#+TITLE: MU VERIFY
#+MAN_CLASS_OPTIONS: :section-id "@SECTION_ID@" :date "@MAN_DATE@"
* NAME
mu-verify - verify message signatures and display information about them
* SYNOPSIS
*mu [common-options] verify [options] [<file> ... ]*
* DESCRIPTION
*mu verify* is the *mu* command for verifying message signatures (such as PGP/GPG
signatures) and displaying information about them. The sub-command works on
message files, and does not require the message to be indexed in the database.
If no message file is provided, the command expects the message on
standard-input.
* VERIFY OPTIONS
** -r, --auto-retrieve
attempt to find keys online (see the *auto-key-retrieve* option in the *gnupg(1)*
documentation).
** decrypt
attempt to decrypt the message
#+include: "common-options.inc" :minlevel 1
* EXAMPLES
To display aggregated (one-line) information about the verification status in a
message:
#+begin_example
$ mu verify msgfile
#+end_example
To display information about all the signatures:
#+begin_example
$ mu verify --verbose msgfile
#+end_example
If you only want to use the exit code, you can use:
#+begin_example
$ mu verify --quiet msgfile
#+end_example
which does not give any output unless there is an error.
#+include: "prefooter.inc" :minlevel 1
* SEE ALSO
*mu(1)*