MU-VERIFY(1)

✨ MU-VERIFY(1) ✨

okay bestie, welcome to mu-verify from the MU VERIFY(1) manual β€” this is the part of the mu fam that checks your PGP/GPG signatures and spills all the tea about them πŸ’…


🌸 NAME 🌸

mu-verify β€” verify message signatures and show you all the info about them, no cap πŸ”βœ¨


πŸ¦‹ SYNOPSIS πŸ¦‹

mu [COMMON-OPTIONS] verify [OPTIONS] [FILE...]

πŸ’– DESCRIPTION πŸ’–

so like. mu verify is the mu command that verifies message signatures (think PGP/GPG signatures, iykyk) and then displays information about them. it's giving detective energy fr fr πŸ”Ž

the sub-command works on message files, and β€” key detail β€” it does NOT require the message to be indexed in the database. zero database, zero problem, we love a low-maintenance icon πŸŽ€

and if you don't hand it a message file? it just expects the message on standard input instead. so pipe away, bestie 🫢


✨ VERIFY OPTIONS ✨

  • -r, --auto-retrieve β€” go hunt for those keys online (peep the auto-key-retrieve option in the gnupg(1) docs for the deets) πŸ”‘
  • --decrypt β€” attempt to decrypt the message πŸ”“

🌈 COMMON OPTIONS 🌈

  • -d, --debug β€” makes mu produce extra debug information, which is the move when you're debugging the program itself. where does it go? the standard logging location, obviously β€” check mu(1) πŸ›
  • -q, --quiet β€” tells mu to not output informational messages and progress info to standard output, and send them to the log file only instead. error messages still go to standard error, don't worry. also heads up: mu index is much faster with --quiet, so yeah, recommended when you're running mu from scripts and such πŸ“œβœ¨
  • --log-stderr β€” causes mu to not output log messages to standard error, in addition to sending them to the standard logging location πŸ™ˆ
  • --nocolor β€” do not use ANSI colors. the environment variable NO_COLOR works as an alternative to --nocolor, if env vars are more your vibe 🎨🚫
  • -V, --version β€” prints the mu version and copyright information πŸ‘‘
  • -h, --help β€” lists all the various command line options πŸ“‹

πŸ“ EXAMPLES πŸ“

wanna see the aggregated (one-line) info about the verification status in a message? say less:

$ mu verify msgfile

wanna see info about all the signatures? periodt:

$ mu verify --verbose msgfile

and if you literally only care about the exit code, you can do:

$ mu verify --quiet msgfile

which gives you no output at all unless there's an error. silent but slaying πŸ’€βœ¨


😭 REPORTING BUGS 😭

found a bug? pls pls pls report it at https://github.com/djcb/mu/issues β€” the devs wanna know 🫢


πŸ’œ AUTHOR πŸ’œ

Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> β€” the actual main character πŸ‘‘


this manpage is part of mu 1.14.2.

Copyright Β© 2008-2026 Dirk-Jan C. Binnema. License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

fr fr, read that license β€” free software means free to change and redistribute, but also no warranty, so manifest accordingly 🧚

🧚 SEE ALSO 🧚

mu(1) πŸ“–


and that's the whole page, bestie β€” written for MU VERIFY(1), the General Commands Manual edition, straight outta mu 1.14.2 (Β© 2008-2026, GPLv3+, no warranty). mwah, go verify something iconic πŸ’‹βœ¨πŸ¦‹

πŸ“¦ where this page comes from