{
    "mode": "man",
    "parameter": "mhbuild",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/mhbuild/1/json",
    "generated": "2026-05-30T06:10:49Z",
    "synopsis": "mhbuild [-help] [-version] file [-auto | -noauto] [-list | -nolist] [-realsize | -norealsize]\n[-headers | -noheaders] [-directives | -nodirectives] [-rfc934mode | -norfc934mode]\n[-contentid | -nocontentid] [-verbose | -noverbose] [-disposition | -nodisposition]\n[-check | -nocheck] [-headerencoding encoding-algorithm  | -autoheaderencoding] [-max‐‐\nunencoded line-length] [-dist]",
    "sections": {
        "NAME": {
            "content": "mhbuild - translate MIME composition drafts for nmh messages\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "mhbuild [-help] [-version] file [-auto | -noauto] [-list | -nolist] [-realsize | -norealsize]\n[-headers | -noheaders] [-directives | -nodirectives] [-rfc934mode | -norfc934mode]\n[-contentid | -nocontentid] [-verbose | -noverbose] [-disposition | -nodisposition]\n[-check | -nocheck] [-headerencoding encoding-algorithm  | -autoheaderencoding] [-max‐‐\nunencoded line-length] [-dist]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "The mhbuild command will translate a MIME composition draft into a valid MIME message.\n\nmhbuild  creates  multi-media messages as specified in RFCs 2045 through 2049.  This includes\nthe encoding of message headers as specified by RFC 2047, and, additionally, the encoding  of\nMIME parameters as specified in RFC 2231.\n\nIf you specify the name of the composition file as “-”, then mhbuild will accept the composi‐\ntion draft on the standard input.  If the translation of this input  is  successful,  mhbuild\nwill  output the new MIME message to the standard output.  This argument must be the last ar‐\ngument on the command line.\n\nOtherwise, if the file argument to mhbuild is the name of a valid composition file,  and  the\ntranslation  is successful, mhbuild will replace the original file with the new MIME message.\nIt will rename the original file to start with the “,” character  and  end  with  the  string\n“.orig”,  e.g.,  if  you  are  editing the file “draft”, it will be renamed to “,draft.orig”.\nThis allows you to easily recover the mhbuild input file.\n",
            "subsections": [
                {
                    "name": "Listing the Contents",
                    "content": "The -list switch tells mhbuild to list the table of contents associated with the MIME message\nthat is created.\n\nThe  -headers  switch indicates that a one-line banner should be displayed above the listing.\nThe -realsize switch tells mhbuild to evaluate the “native” (decoded) format of each  content\nprior  to  listing.  This provides an accurate count at the expense of a small delay.  If the"
                },
                {
                    "name": "-verbose",
                    "content": "present in the message, such as comments in the “Content-Type” header.\n\nIf  the  -disposition  switch is present, then the listing will show any relevant information\nfrom the “Content-Disposition” header.\n"
                },
                {
                    "name": "Simplified Attachment Interface",
                    "content": "For users who wish to simply attach files to text content, mhbuild will scan the  composition\nfile  for  “Attach” headers.  An “Attach” header contains a filename that will be appended to\nthe message using normal MIME encapsulation rules.  One  filename  is  allowed  per  “Attach”\nheader, but multiple “Attach” headers are allowed per composition file.\n\nThese files will be appended after any other MIME content, including any content specified by\nmhbuild directives (see below).  See send(1) for more details.\n\nBy default, the Content-Disposition will be “attachment”.  mhbuild looks for user profile and\nmhn.defaults entries of the form\n\nmhbuild-disposition-type/subtype\nor\nmhbuild-disposition-type\n\nto supply the disposition value.  The only supported values are “attachment” and “inline”.\n"
                },
                {
                    "name": "Convert Interface",
                    "content": "The convert interface is a powerful mechanism that supports replying to MIME messages.  These\nplaceholders are used in the following description:\n\nTYPE           content type/subtype\nCONVERTER      external program, and any fixed arguments, to convert  content,  such  as\nfrom a request to a reply\nARGSTRING      arguments to pass from repl to CONVERTER\nFILE           full path of message being replied to\nThe convert support is based on pseudoheaders of the form\n\nNmh-mhbuild-file-TYPE: FILE\nNmh-mhbuild-args-TYPE: ARGSTRING\n\nin  the draft.  For each such pseudoheader, mhbuild looks in the profile and mhn.defaults for\nthe corresponding TYPE entry to find the converter that supports it:\n\nmhbuild-convert-TYPE: CONVERTER\n\nIt's a fatal error if no such entry is found for TYPE.  An empty entry, e.g.,\n\nmhbuild-convert-text/html:\n\nexcludes parts of that TYPE from the draft.\n\nThe  mhn.defaults  file  contains  default  mhbuild-convert-text/html  and   mhbuild-convert-\ntext/plain  entries.   Profile entries can be used to override corresponding mhn.defaults en‐\ntries, as usual.  Text converters should limit text line lengths to a maximum of  78  charac‐\nters, and must limit them to a maximum of 998 characters, per RFC 5322 Sec. 2.1.1.\n\nFor  each  TYPE  part  in  FILE, mhbuild runs CONVERTER ARGSTRING on the content of the part.\nEach part in FILE that has no corresponding TYPE entry in the profile or mhn.defaults is  ex‐\ncluded from the draft; the user can include them using mhbuild directives.\n\nrepl inserts Nmh-mhbuild-text/html: and Nmh-mhbuild-text/plain: pseudoheaders in every draft.\nThe user can prevent insertion of content parts of either of those types  by  putting  corre‐\nsponding empty entries in their profile.\n\nOnly the highest precedence alternative with a supported TYPE of a multipart/alternative part\nis used.\n\nmhn.defaults.sh selects the text/html-to-text/plain converter at install time.   It  includes\niconv and par, or fmt, in the pipeline only if they are found.\n\nSome  content  types  require  the addition of parameters to the Content-Type header, such as\n“method=REPLY” for text/calendar.  mhbuild looks for a Content-Type  header,  followed  by  a\nblank  line,  at  the beginning of the converter output.  If one is found, it is used for the\ncorresponding part in the reply draft.\n\nThe convert interface doesn't support different ARGSTRINGs or different converters  for  dif‐\nferent  parts of the same TYPE.  That would require associating parts by part number with the\nARGSTRINGs or converters.  Instead, that can be done (currently, without  using  the  convert\nsupport), with mhbuild directives as described below, e.g.,\n\n#text/html;  charset=utf-8  *8bit | mhstore -noverbose -part 42.7 -outfile - | w3m -dump\n-cols 64 -T text/html -O utf-8\n\nThe only way to mix convert pseudoheaders and mhbuild directives is to insert the  directives\nbefore mhbuild is run, which is typically done by entering mime at the “What now?” prompt, or\nwith an -editor mhbuild switch.\n\nThese (optional) setup steps can make the convert support easier to use:\n\n1)   If the par program is installed on your system, it will be set by  default  (in  mhn.de‐\nfaults)  to  filter the converter output.  It helps to set the PARINIT environment vari‐\nable, as described in par(1).\n\n2)   Add this line to your profile:\n\nmhbuild-next: $EDITOR\n\nassuming that your EDITOR environment variable is set; if not, replace EDITOR  with  the\nname  of  your  editor.   Without that profile entry, a response of “e[dit]” at the What\nnow? prompt will require specification of your editor if an -editor  mhbuild  switch  is\nused.\n\n3)   If  using  repl, source the Bourne-shell compatible functions in /usr/share/doc/nmh/con‐\ntrib/replaliases.\nThat script also sets the PARINIT environment variable if it was not set.\n"
                },
                {
                    "name": "Translating the Composition File",
                    "content": "mhbuild is essentially a filter to aid in the composition of  MIME  messages.   mhbuild  will\nconvert  an  mhbuild  “composition  file” into a valid MIME message.  An mhbuild “composition\nfile” is just a file containing plain text that is interspersed with various  mhbuild  direc‐\ntives.   When  this  file is processed by mhbuild, the various directives will be expanded to\nthe appropriate content, and will be encoded according to the MIME standards.  The  resulting\nMIME message can then be sent by electronic mail.\n\nThe  formal syntax for a mhbuild composition file is defined at the end of this document, but\nthe ideas behind this format are not complex.  Basically, the body contains one or more  con‐\ntents.  A content consists of either a directive, indicated with a “#” as the first character\nof a line; or, plaintext (one or more lines of text).  The continuation character,  “\\“,  may\nbe used to enter a single directive on more than one line, e.g.,\n\n#image/png \\\n/home/foobar/junk/picture.png\n\nThere are five kinds of directives: “type” directives, which name the type and subtype of the\ncontent; “external-type” directives, which also name the type and subtype of the content; the\n“message”  directive  (#forw), which is used to forward one or more messages; the “begin” di‐\nrective (#begin), which is used to create a multipart content; and  the  “on/off/pop”  direc‐\ntives (#on, #off, #pop) which control whether any other directives are honored at all.\n\nThe  -directives  switch allows control over whether mhbuild will honor any of the “#”-direc‐\ntives.  This can also be affected with the #on or #off directives, and #pop,  which  restores\nthe  state  of processing to that preceding the most recent #on or #off.  (The #on, #off, and\n#pop directives are always honored, of course.) This allows inclusion  of  plain  text  which\nlooks like mhbuild directives, without causing errors:\n\n#off\n#include <stdio.h>\nprintf(\"Hello, World!\");\n#pop\n\nCurrently the stack depth for the #on/off/pop directives is 32.\n\nThe  “type” directive is used to directly specify the type and subtype of a content.  You may\nonly specify discrete types in this manner (can't specify the types multipart or message with\nthis  directive).   You  may optionally specify the name of a file containing the contents in\n“native” (decoded) format.  If this filename starts with the “|” character,  then  it  repre‐\nsents a command to execute whose output is captured accordingly.  For example,\n\n#audio/basic |raw2audio -F < /usr/lib/sound/giggle.au\n\nIf a filename is not given, mhbuild will look for information in the user's profile to deter‐\nmine how the different contents should be composed.  This is  accomplished  by  consulting  a\ncomposition  string, and executing it under /bin/sh, with the standard output set to the con‐\ntent.  If the -verbose switch is given, mhbuild will echo any commands that are used to  cre‐\nate contents in this way.\n\nThe composition string may contain the following escapes:\n\n%a     Insert parameters from directive\n%f     Insert filename containing content\n%F     %f, and stdout is not re-directed\n%s     Insert content subtype\n%%     Insert character %\n\nFirst, mhbuild will look for an entry of the form:\n\nmhbuild-compose-type/subtype\n\nto  determine  the  command to use to compose the content.  If this isn't found, mhbuild will\nlook for an entry of the form:\n\nmhbuild-compose-type\n\nto determine the composition command.  If this isn't found, mhbuild will complain.\n\nAn example entry might be:\n\nmhbuild-compose-audio/basic: record | raw2audio -F\n\nBecause commands like these will vary, depending on the display environment used  for  login,\ncomposition  strings  for  different contents should probably be put in the file specified by\nthe MHBUILD environment variable, instead of directly in your user profile.\n\nThe “external-type” directives are used to provide a MIME reference to a content, rather than\nenclosing  the  contents itself (for instance, by specifying an ftp site).  Hence, instead of\nproviding a filename as with the type directives, external-parameters  are  supplied.   These\nlook like regular parameters, so they must be separated accordingly.  For example,\n\n#@application/octet-stream; \\\ntype=tar; \\\nconversions=compress \\\n[this is the nmh distribution] \\\n{attachment; filename=\"nmh.tar.gz\"} \\\nname=\"nmh.tar.gz\"; \\\ndirectory=\"/pub/nmh\"; \\\nsite=\"ftp.math.gatech.edu\"; \\\naccess-type=anon-ftp; \\\nmode=\"image\"\n\nYou  must  give a description string to separate the content parameters from the external-pa‐\nrameters (although this string may be empty).  This description string is  specified  by  en‐\nclosing  it  within “[]”.  A disposition string, to appear in a “Content-Disposition” header,\nmay appear in the optional “{}”.\n\nThese parameters are of the form:\n\naccess-type=  usually “anon-ftp”, “mail-server”, or “url”\nname=         filename\npermission=   read-only or read-write\nsite=         hostname\ndirectory=    directoryname (optional)\nmode=         usually “ascii” or “image” (optional)\nsize=         number of octets\nserver=       mailbox\nsubject=      subject to send\nbody=         command to send for retrieval\nurl=          URL of content\n\nA minimum “external-type” directive for the url access-type would be as follows:\n\n#@application/octet-stream [] access-type=url; \\\nurl=\"http://download.savannah.gnu.org/releases/nmh/nmh-1.5.tar.gz\"\n\nAny long URLs will be wrapped according to RFC 2231 rules.\n\nThe “message” directive (#forw) is used to specify a message or group of messages to include.\nYou may optionally specify the name of the folder and which messages are to be forwarded.  If\na folder is not given, it defaults to the current folder.  Similarly, if  a  message  is  not\ngiven,  it  defaults  to the current message.  Hence, the message directive is similar to the\nforw command, except that the former uses the MIME rules for encapsulation rather than  those\nspecified in RFC 934.  For example,\n\n#forw +inbox 42 43 99\n\nIf  you  include  a  single  message, it will be included directly as a content of type “mes‐\nsage/rfc822”.  If you include more than one message, then mhbuild will add a content of  type\n“multipart/digest” and include each message as a subpart of this content.\n\nIf you are using this directive to include more than one message, you may use the -rfc934mode\nswitch.  This switch will indicate that mhbuild should attempt to utilize the MIME encapsula‐\ntion  rules  in such a way that the “multipart/digest” that is created is (mostly) compatible\nwith the encapsulation specified in RFC 934.  If given, then RFC  934  compliant  user-agents\nshould  be able to burst the message on reception -- providing that the messages being encap‐\nsulated do not contain encapsulated messages themselves.  The drawback of  this  approach  is\nthat  the  encapsulations are generated by placing an extra newline at the end of the body of\neach message.\n\nThe “begin” directive is used to create a multipart content.  When using the  “begin”  direc‐\ntive, you must specify at least one content between the begin and end pairs.\n\n#begin\nThis will be a multipart with only one part.\n#end\n\nIf you use multiple directives in a composition draft, mhbuild will automatically encapsulate\nthem inside a multipart content.  Therefore the “begin” directive is only  necessary  if  you\nwish to use nested multiparts, or create a multipart message containing only one part.\n\nFor  all of these directives, the user may include a brief description of the content between\nthe “[” character and the “]” character.  This description will be copied into the  “Content-\nDescription” header when the directive is processed.\n\n#forw [important mail from Bob] +bob 1 2 3 4 5\n\nSimilarly, a disposition string may optionally be provided between “{” and “}” characters; it\nwill be copied into the “Content-Disposition” header when the directive is processed.   If  a\ndisposition  string is provided that does not contain a filename parameter, and a filename is\nprovided in the directive, it will be added to the “Content-Disposition” header.   For  exam‐\nple, the following directive:\n\n#text/plain; charset=iso-8859-1 <>{attachment} /tmp/summary.txt\n\ncreates these message part headers:\n\nContent-Type: text/plain; charset=\"iso-8859-1\"\nContent-Disposition: attachment; filename=\"summary.txt\"\n\nBy default, mhbuild will generate a unique “Content-ID:” for each directive, corresponding to\neach message part; however, the user may override this by defining the ID using the  “<”  and\n“>”  characters.   The  -nocontentid switch suppresses creation of all “Content-ID:” headers,\neven in the top level of the message.\n\nNormally mhbuild will choose an appropriate Content-Transfer-Encoding based  on  the  content\nand  the MIME Content-Type.  However, you can override that in an mhbuild directive by speci‐\nfying “*” and the encoding.  Acceptable encoding values are “8bit”, “qp”  (for  quoted-print‐\nable),  and “b64” (for base64 encoding).  It should be noted that undesired results may occur\nif 8bit or quoted-printable is selected for binary content, due to  the  translation  between\nUnix line endings and the line endings use by the mail transport system.\n\nIn  addition to the various directives, plaintext can be present.  Plaintext is gathered, un‐\ntil a directive is found or the draft is exhausted, and this is made to form a text  content.\nIf the plaintext must contain a “#” at the beginning of a line, simply double it, e.g.,\n\n##when sent, this line will start with only one #\n\nIf  you  want to end the plaintext prior to a directive, e.g., to have two plaintext contents\nadjacent, simply insert a line containing a single “#” character, e.g.,\n\nthis is the first content\n#\nand this is the second\n\nFinally, if the plaintext starts with a line of the form:\n\nContent-Description: text\n\nthen this will be used to describe the plaintext content.  You MUST follow this line  with  a\nblank line before starting your text.\n\nBy default, plaintext is captured as a text/plain content.  You can override this by starting\nthe plaintext with “#<” followed by a content-type specification.  For example, e.g.,\n\n#<text/enriched\nthis content will be tagged as text/enriched\n#\nand this content will be tagged as text/plain\n#\n#<application/x-patch [this is a patch]\nand this content will be tagged as application/x-patch\n\nNote that if you use the “#<” plaintext-form, then the content-description  must  be  on  the\nsame line which identifies the content type of the plaintext.\n\nWhen  composing  a  text  content,  you may indicate the relevant character set by adding the\n“charset” parameter to the directive.\n\n#<text/plain; charset=iso-8859-5\n\nIf a text content contains any 8-bit characters (characters with the high bit  set)  and  the\ncharacter set is not specified as above, then mhbuild will assume the character set is of the\ntype given by the standard locale(1) environment variables.  If these  environment  variables\nare not set, then the character set will be labeled as “x-unknown”.\n\nIf  a  text  content contains only 7-bit characters and the character set is not specified as\nabove, then the character set will be labeled as “us-ascii”.\n\nBy default text content with the high bit set is encoded with an  8-bit  Content-Transfer-En‐\ncoding.   If the text has lines longer than the value of -maxunencoded (which defaults to 78)\nthen the text is encoded using the quoted-printable encoding.\n\nThe -headerencoding switch will indicate which algorithm to use  when  encoding  any  message\nheaders  that contain 8-bit characters.  The valid arguments are base64 for base-64 encoding,\nquoted for quoted-printable encoding, and utf-8 which requires that all  8-bit  header  field\nbodies be encoded as UTF-8 (RFC 6530) and that the message be sent to a SMTP server that sup‐\nports SMTPUTF8 (RFC 6531).  The -autoheaderencoding switch instructs mhbuild to automatically\npick  the  encoding,  either  base64  or  quoted-printable, that results in a shorter encoded\nstring.\n\nPutting this all together, here is an example of a more complex message draft, which will ex‐\npand into a multipart/mixed message containing five parts:\n\nTo: nobody@nowhere.org\ncc:\nSubject: Look and listen to me!\n--------\nThe first part will be text/plain\n#<text/enriched\nThe second part will be text/enriched\n#\nThis third part will be text/plain\n#audio/basic [silly giggle]  \\\n|raw2audio -F < /usr/lib/sounds/giggle.au\n#image/gif   [photo of foobar] \\\n/home/foobar/lib/picture.gif\n"
                },
                {
                    "name": "Integrity Check",
                    "content": "If  mhbuild  is  given the -check switch, then it will also associate an integrity check with\neach “leaf” content.  This will add a Content-MD5 header field to the content, along with the\nmd5  sum  of  the  unencoded contents, per RFC 1864.  This may be used by the receiver of the\nmessage to verify that the contents of the message were not changed in transport.\n"
                },
                {
                    "name": "Transfer Encodings",
                    "content": "After mhbuild constructs the new MIME message by parsing directives, including  files,  etc.,\nit  scans  the  contents of the message to determine which transfer encoding to use.  It will\ncheck for 8-bit data, long lines, spaces at the end of  lines,  and  clashes  with  multipart\nboundaries.  It will then choose a transfer encoding appropriate for each content type.\n\nIf  an integrity check is being associated with each content by using the -check switch, then\nmhbuild will encode each content with a transfer encoding, even if the content contains  only\n7-bit  data.   This  is  to  increase the likelihood that the content is not changed while in\ntransport.\n"
                },
                {
                    "name": "Invoking mhbuild",
                    "content": "Typically, mhbuild is invoked by the whatnow program.  This command will expect the  body  of\nthe  draft to be formatted as an mhbuild composition file.  Once you have composed this input\nfile using a command such as comp, forw, or repl, you invoke mhbuild at the “What now” prompt\nwith\n\nWhat now? mime\n\nprior to sending the draft.  This will cause whatnow to execute mhbuild to translate the com‐\nposition file into MIME format.\n\nNormally it is an error to invoke mhbuild on a file that is  already  in  MIME  format.   The"
                },
                {
                    "name": "-auto",
                    "content": "MIME headers.  The use of -auto also enables the -nodirectives switch.\n\nFinally, you should consider adding this line to your profile:\n\nlproc: show\n\nThis way, if you decide to list after invoking mime, the command\n\nWhat now? list\n\nwill work as you expect.\n\nThe -dist switch is intended to be used by dist.  It will cause mhbuild to not  generate  any\nMIME  headers in the composition file (such as “MIME-Version” or “Content-Type”), but it will\nstill encode message headers according to RFC 2047.\n"
                },
                {
                    "name": "User Environment",
                    "content": "Because the environment in which mhbuild operates may vary for a user, mhbuild will look  for\nthe  environment variable MHBUILD.  If present, this specifies the name of an additional user\nprofile which should be read.  Hence, when a user logs in on a particular machine, this envi‐\nronment  variable  should be set to refer to a file containing definitions useful on that ma‐\nchine.\n\nFinally, mhbuild will attempt to consult\n\n/etc/nmh/mhn.defaults\n\nif it exists.\n\nSee \"Profile Lookup\" in mh-profile(5) for the profile search order, and for how duplicate en‐\ntries are treated.\n"
                },
                {
                    "name": "Syntax of Composition Files",
                    "content": "The following is the formal syntax of a mhbuild “composition file”.\n\nbody         ::=     1*(content | EOL)\n\ncontent      ::=     directive | plaintext\n\ndirective    ::=     \"#\" type \"/\" subtype\n0*(\";\" attribute \"=\" value)\n[ \"(\" comment \")\" ]\n[ \"<\" id \">\" ]\n[ \"[\" description \"]\" ]\n[ \"{\" disposition \"}\" ]\n[ \"*8bit\" | \"*qp\" | \"*b64\" ]\n[ filename ]\nEOL\n\n| \"#@\" type \"/\" subtype\n0*(\";\" attribute \"=\" value)\n[ \"(\" comment \")\" ]\n[ \"<\" id \">\" ]\n[ \"[\" description \"]\" ]\n[ \"{\" disposition \"}\" ]\n[ \"*8bit\" | \"*qp\" | \"*b64\" ]\nexternal-parameters\nEOL\n\n| \"#forw\"\n[ \"<\" id \">\" ]\n[ \"[\" description \"]\" ]\n[ \"{\" disposition \"}\" ]\n[ \"+\"folder ] [ 0*msg ]\nEOL\n\n| \"#begin\"\n[ \"<\" id \">\" ]\n[ \"[\" description \"]\" ]\n[ \"{\" disposition \"}\" ]\n[   \"alternative\"\n| \"parallel\"\n| something-else    ]\nEOL\n1*body\n\"#end\" EOL\n\nplaintext    ::=     [ \"Content-Description:\"\ndescription EOL EOL ]\n1*line\n[ \"#\" EOL ]\n\n| \"#<\" type \"/\" subtype\n0*(\";\" attribute \"=\" value)\n[ \"(\" comment \")\" ]\n[ \"[\" description \"]\" ]\n[ \"{\" disposition \"}\" ]\n[ \"*8bit\" | \"*qp\" | \"*b64\" ]\nEOL\n1*line\n[ \"#\" EOL ]\n\nline         ::=     \"##\" text EOL\n-- interpreted as \"#\"text EOL\n| text EOL\n"
                }
            ]
        },
        "FILES": {
            "content": "mhbuild looks for additional user profile files and mhn.defaults in multiple locations: abso‐\nlute pathnames are accessed directly, tilde expansion is done on  usernames,  and  files  are\nsearched for in the user's Mail directory as specified in their profile.  If not found there,\nthe directory “/etc/nmh” is checked.\n\n$HOME/.mhprofile   The user's profile.\n$MHBUILD            Additional profile entries.\n/etc/nmh/mhn.defaults\nSystem default MIME profile entries.\n",
            "subsections": []
        },
        "PROFILE COMPONENTS": {
            "content": "Path:               To determine the user's nmh directory.\nCurrent-Folder:     To find the default current folder.\nmhbuild-compose-type*:\nTemplate for composing contents.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "mhlist(1), mhshow(1), mhstore(1)\n\nMultipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies (RFC\n2045)\n\nMultipurpose Internet Mail Extensions (MIME) Part Two: Media Types (RFC 2046)\n\nMultipurpose  Internet  Mail Extensions (MIME) Part Three: Message Header Extensions for Non-\nASCII Text (RFC 2047)\n\nInternet Message Format (RFC 5322)\n\nMIME Parameter Value and Encoded Word Extensions: Character Sets,  Languages,  and  Continua‐\ntions (RFC 2231)\n\nProposed Standard for Message Encapsulation (RFC 934)\n\nThe Content-MD5 Header Field (RFC 1864)\n\nDefinition of the URL MIME External-Body Access-Type (RFC 2017)\n\nOverview and Framework for Internationalized Email (RFC 6530)\n\nSMTP Extension for Internationalized Email (RFC 6531)\n",
            "subsections": []
        },
        "DEFAULTS": {
            "content": "",
            "subsections": [
                {
                    "name": "-autoheaderencoding",
                    "content": ""
                },
                {
                    "name": "-contentid",
                    "content": ""
                },
                {
                    "name": "-headers",
                    "content": "-maxunencoded 78"
                },
                {
                    "name": "-nocheck",
                    "content": ""
                },
                {
                    "name": "-nodisposition",
                    "content": ""
                },
                {
                    "name": "-norfc934mode",
                    "content": ""
                },
                {
                    "name": "-noverbose",
                    "content": ""
                },
                {
                    "name": "-realsize",
                    "content": "nmh-1.7.1                                    2016-10-15                                 MHBUILD(1mh)"
                }
            ]
        }
    },
    "summary": "mhbuild - translate MIME composition drafts for nmh messages",
    "flags": [
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "present in the message, such as comments in the “Content-Type” header. If the -disposition switch is present, then the listing will show any relevant information from the “Content-Disposition” header."
        },
        {
            "flag": "",
            "long": null,
            "arg": null,
            "description": "MIME headers. The use of -auto also enables the -nodirectives switch. Finally, you should consider adding this line to your profile: lproc: show This way, if you decide to list after invoking mime, the command What now? list will work as you expect. The -dist switch is intended to be used by dist. It will cause mhbuild to not generate any MIME headers in the composition file (such as “MIME-Version” or “Content-Type”), but it will still encode message headers according to RFC 2047."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "mhlist",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/mhlist/1/json"
        },
        {
            "name": "mhshow",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/mhshow/1/json"
        },
        {
            "name": "mhstore",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/mhstore/1/json"
        }
    ]
}