Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

80 lines (56 sloc) 1.949 kb
.TH MU VERIFY 1 "September 2012" "User Manuals"
.SH NAME
mu verify\- verify message signatures and display information about them
.SH SYNOPSIS
.B mu verify [options] <msgfile>
.SH DESCRIPTION
\fBmu verify\fR is the \fBmu\fR 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.
\fBmu verify\fR depends on \fBgpg\fR, and uses the one it finds in your
\fBPATH\fR. If you want to use another one, you need to set \fBMU_GPG_PATH\fB
to the full path to the desired \fBgpg\fR.
.SH OPTIONS
.TP
\fB\-r\fR, \fB\-\-auto\-retrieve\fR
attempt to find keys online (see the \fBauto-key-retrieve\fR option in the
\fBgnupg(1)\fR documentation).
\" .TP
\" \fB\-u\fR, \fB\-\-use\-agent\fR attempt to use the GPG-agent (see the the
\" \fBgnupg-agent(1)\fR documentation). Note that GPG-agent is running many
\" desktop-evironment; you can check whether this is the case using:
\" .nf
\" $ env | grep GPG_AGENT_INFO
\" .fi
.SH EXAMPLES
To display aggregated (one-line) information about the signatures in a message:
.nf
$ mu verify --verbose msgfile
.fi
To display information about all the signatures:
.nf
$ mu verify --verbose msgfile
.fi
If you only want to use the exit code, you can use:
.nf
$ mu verify --quiet msgfile
.fi
which does not give any output.
.SH RETURN VALUE
\fBmu verify\fR returns 0 when all signatures could be verified to be good,
and returns some non-zero error code when this is not the case.
.nf
| code | meaning |
|------+--------------------------------|
| 0 | ok |
| 1 | some non-verified signature(s) |
.fi
.SH BUGS
Please report bugs if you find them:
.BR http://code.google.com/p/mu0/issues/list
.SH AUTHOR
Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>
.SH "SEE ALSO"
.BR mu(1)
.BR gpg(1)
Jump to Line
Something went wrong with that request. Please try again.