MMIME(1)
π mmime(1) β the MIME-making bestie π
okay so listen. mmime is a little general-commands-manual icon whose whole personality is creating MIME messages, and honestly? she ate. π
π¦ NAME π¦
mmime β literally makes MIME messages for you. no cap.
β¨ SYNOPSIS β¨
mmime [-c | -r] [-t content-type] < message
that's it. that's the whole vibe check. she reads from stdin like the main character she is. π
π DESCRIPTION π
so here's the tea, bestie: mmime generates a multipart/mixed message straight from standard input. she extends, wraps, and encodes the header as necessary β whatever it takes, she's doing it β and she replaces lines in the message body that look like this:
#content/type[#content-disposition] path[>filename]
...with a whole MIME part. that part has Content-Type = content/type, and it consists of the contents of the file found at path. iconic behavior honestly.
quick breakdown of the squiggly bits:
content-dispositionis optional and defaults toattachment(she's not clingy, she just defaults there π«Ά)filenameis optional and defaults to the basename of path
The options are as follows:
-cβ Check mode π΅οΈββοΈ: don't output anything, exit with status1if MIME-encoding the message is required, or else exit with status0. she's just peeking, not touching.-rβ Raw mode π: don't expand MIME parts in the body, generate atext/plainmessage. keep it simple, keep it plain.-t content-typeβ OverrideContent-Typefor the toplevel part. defaults tomultipart/mixed. you're the boss, you pick the type π
πΈ ENVIRONMENT πΈ
MBLAZE_RELAXED_MIMEβ if set,mmime -cwill relax the body line length check and only consider bodies with lines longer than998characters need to be MIME formatted. yes bestie,998. that's the number. she's chill like that when you set this. π§
β EXIT STATUS β
the mmime utility exits 0 on success, and >0 if an error occurs. periodt.
π heads up: any nonzero exit means something went sideways, so keep an eye on that number.
π₯ SEE ALSO π₯
makemime(1),mhbuild(1)β the other girls in the MIME friend group- N. Freed and N. Borenstein, Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, RFC 2045, November 1996.
- N. Freed and N. Borenstein, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types, RFC 2046, November 1996.
- K. Moore, MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text, RFC 2047, November 1996.
- N. Freed and K. Moore, MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations, RFC 2231, November 1997.
- P. Resnick (ed.), Internet Message Format, RFC 5322, October 2008.
like, the reading list is giving homework but it's also giving β¨foundational knowledgeβ¨ so slay, go read it, iykyk.
π AUTHORS π
Leah Neukirchen <leah@vuxu.org> β the legend herself π
π LICENSE π
mmime is in the public domain. fr fr, no strings.
to the extent possible under law, the creator of this work has waived all copyright and related or neighboring rights to this work.
http://creativecommons.org/publicdomain/zero/1.0/
ππ and that's the whole page, bestie! this one's from the Debian edition of the manual, dated July 22, 2016 β so she's vintage but she's so still relevant. go make some MIME messages, you're gonna do amazing π«Άβ¨π
π¦ where this page comes from
- alpine 3.24: mblaze-doc 1.4-r0 Β· CC0-1.0
- nixos 26.05: mblaze 1.4
- nixpkgs unstable: mblaze 1.4
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms