REFORMIME(1)

✨ REFORMIME(1) ✨

okay bestie, gather round, because reformime is genuinely one of those tools that looks quiet and then eats 💅 — it's the MIME E-mail reformatting tool, and it's about to become your whole personality. Manual page by S. Varshavchik, vibes by me. Let's go 🦋

---

🌸 NAME 🌸

reformime — MIME E-mail reformatting tool. that's it, that's the girl 👑

---

🎀 SYNOPSIS 🎀

reformime [options...]

---

💖 DESCRIPTION 💖

so reformime is a utility for reformatting MIME messages. iconic behaviour, no notes.

generally speaking, reformime expects to see an RFC 2045[1] compliant message sitting on standard input — except in a few cases, like with the -m option. she's flexible but she has boundaries 🫶

If you give her no options at all, reformime prints out the MIME structure of the message. That output is made of what we call "MIME reference tags", one per line. Like this:

1
1.1
1.2

so what is this telling you? this message contains two different MIME sections, bestie. the first line of the MIME structure output will always contain 1, which refers to the entire message. in this case the whole message happens to be a multipart/mixed message. 1.1 refers to the first section of that multipart message, which happens to be a text/plain section. 1.2 refers to the second section of the message, which happens to be an application/octet-stream section. slay 💅

now — if the message is not a MIME message, or it doesn't contain any attachments, reformime prints only 1, which refers to the entire message itself:

1

and here's the output from reformime when the first part of the message was itself a multipart/alternative section:

1
1.1
1.1.1
1.1.2
1.2

arbitrarily complex MIME constructs are possible. lowkey terrifying, highkey impressive. 🌈

---

✨ OPTIONS ✨

• -d — parse a delivery status notification MIME message (RFC 3464[2]). reformime expects to see on standard input a MIME message that consists of a delivery status notification, as defined by RFC 1894. reformime reads the message and prints on standard output a list of addresses and their corresponding delivery status, as specified in the delivery status notification. Each line printed by reformime consists of a delivery status, a space, and the address. reformime then terminates with a 0 exit status. reformime produces no output and terminates with an exit status of 1 if the standard input does not contain a delivery status notification.

International domain names get converted to the system locale's encoding. If the conversion is not possible: an address given in the delivery status notification directly in UTF-8 has its non-converted characters replaced by their hexadecimal values; a punycode-encoded address gets displayed as is. For best results the system locale's encoding should be UTF-8. 💜

• -D — like the -d except that reformime lists the address found in the Original-Recipient: header, if it exists.
• -e — extract the contents of the indicated MIME section, and display it on standard output. The -s option is required when -e is specified. If the specified section or sections use either the base64 or quoted-printable encoding method, reformime automatically decodes it. In this case you're better off redirecting the standard output into a file. 📁
• -i — display MIME information for each section. reformime displays the contents of the Content-Type: header, any encoding used, and the character set. reformime also displays the byte offset in the message where each section starts and ends (and where the actual contents of the section start, after skipping all the headers).
• -V — check for correctness of each section's MIME metadata. No output is produced when all MIME sections pass all tests. Any issues are reported, together with their MIME section, for example:

Warnings (1.1):
    Bad hexadecimal quoted-printable encoding

Warning messages indicate which MIME section they're reported for — section 1.1 in this example had a problem with its encoding.

Issues that affect the ability to parse the MIME message itself are reported as fatal errors (together with any warnings, if any, for whatever it's worth). Fatal errors result in reformime terminating with a non-0 exit code. 💀

• -m — create a multipart/digest MIME message digest.
• -r — rewrite message, adding or standardizing RFC 2045[1] MIME headers.
• -r7 — like -r but also convert 8bit-encoded MIME sections to quoted-printable.
• -r8 — like -r but also convert quoted-printable-encoded MIME sections to 8bit, except in some situations, see below.
• -rU — unconditionally convert quoted-printable-encoded MIME sections to 8bit, even when the resulting message may not necessarily comply with Internet message formatting standards. See below for more information.
• -s section — display MIME information for this section only. section is a MIME specification tag. The -s option is required if -e is also specified, and is optional with -i.

Multiple sections may be specified by separating them with commas. reformime processes each section using the other options that were specified. 🍓

• -x — extract the contents of the indicated MIME section to a file.
• -X — pipe the contents of the indicated MIME section to a program.

---

🧚 Extracting RFC 2045 MIME section(s) to file(s) 🧚

The -x and -X options extract a specific MIME section to a file or to a pipe to an external program. Use the -s option to identify the MIME section to extract. If the -s option is not specified, every MIME section in the message is extracted, one at a time. If -s lists multiple sections, each section gets extracted separately. quoted-printable and base64 encoding are automatically decoded. 🎀

• -x — interactive extraction. reformime prints the MIME content type of each section. Answer with 'y' or 'Y' to extract the MIME section. Specify the filename at the next prompt. reformime prompts with a default filename. reformime tries to choose the default filename based on the MIME headers, if possible. If not, a randomly-generated filename is the default option. 🎲
• -xPREFIX — automatic extraction. reformime automatically extracts one or more MIME sections, and saves them to a file. The filename is formed by taking PREFIX, and appending the default filename to it. Note that there's no space between -x and PREFIX. For example:

reformime -xfiles-

This command saves MIME sections as files-attachment1.dat, then files-attachment2.dat, etc. reformime tries to append the filename specified in the MIME headers for each section, where possible. reformime replaces all suspect characters with the underscore character.

• -X prog arg1 arg2 ... — the -X option must be the last option to reformime. reformime runs an external program prog, and pipes the contents of the MIME section to the program. reformime sets the environment variable CONTENT_TYPE to the MIME content type. The environment variable FILENAME gets set to the default filename of reformime's liking. If the -s option is not specified, the program runs once for every MIME section in the message. The external program, prog, must terminate with a zero exit status in order for reformime to proceed to the next MIME section in the message (or the next section specified by -s). In any case, if prog terminates with a non-zero exit status, reformime terminates with the exit status of 20 plus prog's exit status. 🫶

💅 Note 💅

reformime extracts every MIME section in the message unless the -s option is specified. This includes even the text/plain MIME content that usually precedes a binary attachment. like, yes, the boring part too. sorry bestie 😭

---

🌟 Adding RFC 2045 MIME headers 🌟

The -r option performs the following actions:

If there is no Mime-Version:, Content-Type:, or Content-Transfer-Encoding: header, reformime adds one.

If the Content-Transfer-Encoding: header contains 8bit or raw, but only seven-bit data is found, reformime changes the Content-Transfer-Encoding header to 7bit.

-r7 does the same thing, but also converts 8bit-encoded content that contains eight-bit characters to quoted-printable encoding.

-r8 does the same thing, but also converts quoted-printable-encoded content to 8bit, except in some situations. The content remains quoted-printable if converting it results in excessively long lines of text.

-rU always converts quoted-printable-encoded content to 8bit potentially resulting in excessively long lines of text.

⚠️ The resulting message should not be resubmitted for mail delivery, as a delivery failure may occur. like, do not do it. i'm begging. 🙈

---

🌈 Creating multipart/digest MIME digests 🌈

The -m option creates a MIME digest. reformime reads a list of filenames on standard input. Each line read from standard input contains the name of a file that is presumed to contain an RFC 2822-formatted message. reformime splices all files into a multipart/digest MIME section, and writes it to standard output. ✨

---

💜 Translating MIME headers 💜

The following options do not read a message from standard input. These options process MIME headers via the command line, and are designed to be conveniently used by mail-handling scripts. iykyk 🧚

• -h "header" — decode a MIME-encoded "header" and print the decoded 8-bit content on standard output. The decoding gets carried out as if the contents occurred in the "Subject" header. Example:

$ reformime -h '=?iso-8859-1?Q?H=F3la!?='
Hóla!

• -H "header" — like -h except that header is parsed as a list of email addresses, like "From" or "To".
• -o "text" — MIME-encode "text", and print the results on standard output.
• -O "text" — like the -o option, except that text is a structured header with RFC 2822 addresses.
• -c "charset" — use charset as the character set setting, by the -h, -H, -o and -O options.
• -u — this "undocumented" option reads a MIME message on standard input, and converts its contents to an UTF-8-encoded character stream, which is written to standard output.

The standard output receives a concatenated amalgam of the headers and "text" MIME object data. It is meant to be used as part of a generic search function. This option decodes various kinds of header MIME encoding, the quoted-printable and base64 transfer encodings of "text" MIME objects. An extra newline character is appended to each MIME entity, ensuring that MIME entities that don't end with a trailing newline will not end up having the next MIME entity's first header line glued to it. no glued headers in this house 💅

---

👑 SEE ALSO 👑

reformail(1)[3], sendmail(8), mailbot(1)[4], maildrop(1)[5], maildropfilter(5)[6], egrep(1), grep(1), sendmail(8).

---

🎀 AUTHOR 🎀

Sam Varshavchik : Author

📚 NOTES 📚

okay bestie, here's the receipts section — every link the page is standing on, in order, no skips 💅 these are the sources the whole thing cites, so if you wanna go deeper than the vibe, this is where you go:

1. RFC 2045 — http://www.rfc-editor.org/rfc/rfc2045.txt
2. RFC 3464 — https://www.rfc-editor.org/rfc/rfc3464.txt
3. reformail(1) — http://www.courier-mta.org/maildrop/reformail.html
4. mailbot(1) — http://www.courier-mta.org/maildrop/mailbot.html
5. maildrop(1) — http://www.courier-mta.org/maildrop/maildrop.html
6. maildropfilter(5) — http://www.courier-mta.org/maildrop/maildropfilter.html

---

and that's the whole page, bestie!! 🎀✨ this one ships as part of the Courier Mail Server, dated 01/10/2026, and it lives in section 1 as REFORMIME(1) — go forth and reformat those MIME messages, you absolute icon 👑💖🦋

no cap, you read the entire thing. main character behavior fr fr. periodt 💅