program constructs MIME messages with attached files. The user can specify
the content type (application/octet-stream, text/plain or a user specified
type), content type encoding (7bit, 8bit, binary, base64 and auto-detect),
content disposition (attached or inline) and the content boundry string.
The user can also specify some mail related options: subject, from-address,
to-addres, carbon-copy addres, prolog-text and epilog-text.
The output of the MIME-tool program can be sent directly to the
mail, mailx or sendmail
commands (or any other command that accepts RFC-822 formatted messages).
Specifying 7-bit encoding for an attachment that contains 8-bit data will
convert any data bytes whose high-bit is set to question marks.
7-bit ASCII encoding
8-bit ASCII encoding
application/octet-stream content type
low detail debugging
high detail debugging
write a subpart
disposition: inline (instead of attachment)
explicit content type
text/plain content type
omit disposition line
unknown encoding, auto-detect
very verbose messages
copy existing MIME part
override the filename in the disposition header
don't add a filename parameter in the disposition header
Using MIME-tool to write a mail message to a file:
Most of the header values are not properly quoted or folded, so long or
complex values for these headers may cause problems. Specifically, the
from-address, to-address, carbon-copy-address and content-type headers
may not be properly quoted or folded.
For some reason, certain e-mail clients (espcially from a large software
company located in Redmond, Washington) don't seem to recognize file
attachments as attachments, but instead displays them as inline attachments.
(maybe this isn't MIME-tool's fault, but I've gotten a few e-mails about it,
so I'm mentioning it here)