{
    "content": [
        {
            "type": "text",
            "text": "# MH-MIME (info)\n\n## NAME\n\nmh-mime - overview of nmh MIME message composition and display\n\n## DESCRIPTION\n\nThe  acronym MIME stands for Multipurpose Internet Mail Extensions, the\nformat of Internet messages used to send multi-media content.  The  nmh\ncommand  suite has support for the display and composition of MIME mes-\nsages, but currently MIME support is not completely integrated into all\ntools.   This  document  provides an overview as to which tools support\nMIME message display, storage, and composition.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **SEE ALSO**\n- **BUGS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "MH-MIME",
        "section": "",
        "mode": "info",
        "summary": "mh-mime - overview of nmh MIME message composition and display",
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "comp",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/comp/1/json"
            },
            {
                "name": "iconv",
                "section": "3",
                "url": "https://www.chedong.com/phpMan.php/man/iconv/3/json"
            },
            {
                "name": "mh-format",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/mh-format/5/json"
            },
            {
                "name": "mhbuild",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/mhbuild/1/json"
            },
            {
                "name": "mhfixmsg",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/mhfixmsg/1/json"
            },
            {
                "name": "mhparam",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/mhparam/1/json"
            },
            {
                "name": "nmh",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/nmh/7/json"
            },
            {
                "name": "repl",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/repl/1/json"
            },
            {
                "name": "whatnow",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/whatnow/1/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 90,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "BUGS",
                "lines": 4,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "mh-mime - overview of nmh MIME message composition and display\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "The  acronym MIME stands for Multipurpose Internet Mail Extensions, the\nformat of Internet messages used to send multi-media content.  The  nmh\ncommand  suite has support for the display and composition of MIME mes-\nsages, but currently MIME support is not completely integrated into all\ntools.   This  document  provides an overview as to which tools support\nMIME message display, storage, and composition.\n\nLocal Character Set Conversion\nAll of the nmh commands convert non-native character sets to the  local\ncharacter  set,  as  specified by the operating system locale settings.\nSee locale(1) for more details on the environment variables used to set\nthe local character set.  Character set conversion will only take place\nif nmh was built with iconv(3) support.  See the  mhparam(1)  man  page\nfor  how  to  determine whether your nmh installation includes iconv(3)\nsupport.\n\nDepending on the source and target character set, it may not be  possi-\nble to convert all characters to the local character set.  In this case\na substitution character will be used for the characters that cannot be\nconverted.\n\nMessage Display\nThe  default  format used by scan(1) will automatically decode MIME-en-\ncoded headers.  If you have a custom scan format, see the examples pro-\nvided with the nmh distribution (found in the \"/etc/nmh\" directory) and\nmh-format(5) for details on how to make  sure  your  MIME  headers  are\nproperly decoded.\n\nBy  default,  if show detects that it is reading a MIME message it will\ninvoke mhshow(1).  The default behavior of mhshow is  to  only  display\ntext  parts  that are not marked as attachments.  See mhshow(1) for de-\ntails on how to control what mhshow will display.\n\nMessage Interrogation and Storage\nThe mhlist(1) command will display a listing of  the  MIME  parts  con-\ntained  within  a message.  That information can be used in conjunction\nwith the mhstore command to save individual parts or content types of a\nmessage.   See  mhlist(1)  and mhstore(1) for more details on how these\ncommands work.\n\nMessage Composition and Reply\nAll messages sent by send(1) will automatically  be  processed  by  mh-\nbuild(1)  before  being  passed to post(1) for message submission.  mh-\nbuild will use the locale settings to mark text content with the appro-\npriate  character set and apply any necessary encoding.  If you wish to\ninclude text in your message using a character set that does not  match\nyour  locale,  you  will need to specify the character set using an mh-\nbuild directive; see mhbuild(1) for more information.\n\nFor attaching files or composing other non-text content, there are  two\noptions: the attach system and mhbuild directives.\n\nThe  attach  system  is best suited for content where one or more files\nare being attached to a message.  You can use the attach system by  ei-\nther  using the attach command at the \"What now?\" prompt, or by insert-\ning an \"Attach:\" header in the message draft containing the name of the\nfile  you  wish to attach to the message (note that all the attach com-\nmand does is place an \"Attach:\" header in the message draft).   mhbuild\nwill  then  automatically include the specified file(s) in the outgoing\nmessage.  See send(1) for details on how mhbuild determines the  proper\ncontent type of attached files.\n\nThe  other  method  of composing MIME messages is to use mhbuild direc-\ntives.  This allows exact control over the contents and format  of  the\nMIME  message,  but has a more complicated syntax.  mhbuild(1) contains\ndetails on the directive syntax and examples of directives for  differ-\nent  media  types.  It is important to note that when using mhbuild di-\nrectives the user must run mhbuild outside of send to have  it  process\ndirectives;  when  being  run  by  send,  mhbuild  is configured to not\nprocess directives so normal user text is not mistaken for a directive.\nWhen  using  directives  a  user typically uses the mime command at the\n\"What now?\" prompt to process them.\n\nWhen replying to messages using repl(1) the traditional  MH  method  of\nincluding  the  original  text  in the reply does not interoperate with\nMIME messages.  The -convertargs switch to repl(1) provides  one  solu-\ntion.       Another      solution:       the      contrib     directory\n(/usr/share/doc/nmh/contrib) contains a Perl program called replyfilter\nwhich  will decode text parts and present them in an appropriate manner\nto be included in a message reply.  See the comments at the top of  re-\nplyfilter for instructions on how to configure nmh to work with it.\n\nMessage Rewrite\nThe  mhfixmsg(1) command can apply various transformations to MIME mes-\nsages, including decoding of text parts, converting the  character  set\nof  text parts, and insertion of text/plain parts to correspond to text\nparts of other subtypes.  mhfixmsg can also repair defects in MIME mes-\nsages,  such  as  mismatched  top-level boundary indicators and invalid\nContent-Transfer-Encoding values.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "comp(1), iconv(3), mh-format(5)  mhbuild(1),  mhfixmsg(1),  mhparam(1),\nnmh(7), repl(1), whatnow(1),\n/usr/share/doc/nmh/contrib/replyfilter,\n/usr/share/doc/nmh/contrib/replaliases\n",
                "subsections": []
            },
            "BUGS": {
                "content": "MIME  support  should be more integrated into all of the nmh tools than\nit currently is.\n\nnmh-1.7.1                         2014-12-15                      MH-MIME(7mh)",
                "subsections": []
            }
        }
    }
}