MU-VIEW(1)

📦
version 1.14.2 · 11 versions
, in ubuntu stonking

💌 MU-VIEW(1) — the mu view page, bestie edition

okay so this is a page from the General Commands Manual (the MU VIEW(1) one, yes that's the whole title, slay) and it's all about mu-view 💖

✨ NAME ✨

mu-view — display an e-mail message file 📧

🌸 SYNOPSIS 🌸

mu [COMMON OPTIONS] view [OPTIONS] [FILE...]

🦋 DESCRIPTION 🦋

mu view is the mu command for showing off e-mail message files, like a little runway walk for your mail 💅 It works on message files directly and does not require the message to be indexed in the database. no database drama, we love that for us.

The command shows some common headers (From:, To:, Cc:, Bcc:, Subject: and Date:), the list of attachments, and either the plain-text or html body of the message (if there is one), or its s-expression representation. pick your fighter ✨

If no message file is provided, the command reads the message from standard-input. so you can just pipe it in, main character energy 🫶

🎀 VIEW OPTIONS 🎀

  • -o, --format format — use the given output format. and like, you have options bestie:
    • plain: use the plain-text body; this is the default 🌈
    • html: use the HTML body ✨
    • sexp: show the S-expression representation of the message, for the structural girlies 💜
  • --summary-len number — instead of displaying the full message, output a summary based upon the first number lines of the message. just the appetizer, not the whole meal 🍓
  • --terminate — terminate messages with \f (form-feed) characters when displaying them. this is useful when you want to further process them, iykyk 🔥
  • --decrypt — attempt to decrypt encrypted message bodies. this is only possible if mu was built with crypto-support. no crypto build, no decryption, periodt 💀
  • --auto-retrieve — attempt to retrieve crypto-keys automatically from the network, when needed. going out and getting the keys herself 👑

👑 COMMON OPTIONS 👑

  • -d, --debug — makes mu generate extra debug information, useful for debugging the program itself. debug info goes to the standard logging location; see mu(1). it's giving detective 🔍
  • -q, --quiet — causes mu not to output informational messages and progress information to standard output, but only to the log file. error messages will still be sent to standard error. lowkey important: mu index is much faster with --quiet, so it is recommended you use this option when using mu from scripts etc. quietly thriving fr fr 🤫
  • --log-stderr — causes mu to not output log messages to standard error, in addition to sending them to the standard logging location. bye to the stderr spam 👋
  • --nocolor — do not use ANSI colors. the environment variable NO_COLOR can be used as an alternative to --nocolor. sometimes monochrome is the vibe 🖤
  • -V, --version — prints mu version and copyright information ⭐
  • -h, --help — lists the various command line options 📜

🙈 REPORTING BUGS 🙈

Please report bugs at https://github.com/djcb/mu/issues. (be nice, they fix things 💖)

💜 AUTHOR 💜

Dirk-Jan C. Binnema <djcb@djcbsoftware.nl> — iconic, we stan 👑

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.

bestie that's the legal bit and it means exactly what it says — free software, change it, share it, but there is NO WARRANTY. no cap. 🙏

🔗 SEE ALSO 🔗

so yeah, that's the whole MU VIEW(1) page from the General Commands Manual, and this manpage is part of mu 1.14.2 — copyright © 2008-2026 Dirk-Jan C. Binnema, license GPLv3+ 🎀 read responsibly, format your mail iconically, bye bestie 💅✨🦋

📦 where this page comes from