{
    "mode": "man",
    "parameter": "BURST",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/man/BURST/json",
    "generated": "2026-10-22T12:35:37Z",
    "synopsis": "burst [-help] [-version] [+folder] [msgs] [-inplace | -noinplace] [-mime | -nomime] [-au‐\ntomime] [-quiet | -noquiet] [-verbose | -noverbose]",
    "sections": {
        "NAME": {
            "content": "burst - explode digests into nmh messages\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "burst [-help] [-version] [+folder] [msgs] [-inplace | -noinplace] [-mime | -nomime] [-au‐\ntomime] [-quiet | -noquiet] [-verbose | -noverbose]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "burst  considers  the  specified messages in the named folder to be Internet digests, and ex‐\nplodes them in that folder.\n\nIf -inplace is given, each digest is replaced by its “table of contents” and  the  digest  is\nremoved.   burst  then  renumbers the messages which follow the digest, in the folder, making\nroom for each of the exploded messages, which are placed immediately after the “table of con‐\ntents”.\n\nIf -noinplace is given, each digest is preserved, no table of contents is produced,  and  the\nexploded  messages are placed at the end of the folder.  Other messages in the folder are not\naffected.\n\nIf -automime is given, burst will try to determine if the message is formatted with MIME  and\ncontains  MIME  parts  of type “message/rfc822”.  If it does, it will burst the message using\nMIME formatting rules.  The -mime switch can be used to enforce the use of  MIME  formatting.\nThe -nomime switch will force burst to use RFC 934 rules.\n\nThe  -quiet switch directs burst to be silent about reporting messages that are not in digest\nformat.\n\nThe -verbose switch directs burst to tell the user the general actions that it is  taking  to\nexplode the digest.\n\nIt  turns  out that burst works equally well on forwarded messages and blind-carbon-copies as\non Internet digests, provided that the former were generated by forw or send.\n",
            "subsections": []
        },
        "FILES": {
            "content": "$HOME/.mhprofile   The user's profile.\n",
            "subsections": []
        },
        "PROFILE COMPONENTS": {
            "content": "Path:               To determine the user's nmh directory.\nCurrent-Folder:     To find the default current folder.\nMsg-Protect:        To set mode when creating a new message.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "inc(1), pack(1)\n\nProposed Standard for Message Encapsulation (RFC 934)\n",
            "subsections": []
        },
        "DEFAULTS": {
            "content": "+folder             The current folder.\nmsgs                The current message.",
            "subsections": [
                {
                    "name": "-noinplace",
                    "content": ""
                },
                {
                    "name": "-automime",
                    "content": ""
                },
                {
                    "name": "-noquiet",
                    "content": ""
                },
                {
                    "name": "-noverbose",
                    "content": ""
                }
            ]
        },
        "CONTEXT": {
            "content": "If a folder is given, it will become the current folder.  If  -inplace  is  given,  then  the\nfirst message burst becomes the current message.  This leaves the context ready for a show of\nthe  table  of contents of the digest, and a next to see the first message of the digest.  If",
            "subsections": [
                {
                    "name": "-noinplace",
                    "content": "current message.  This leaves the context in a similar, but not identical, state to the  con‐\ntext achieved when using -inplace.\n"
                }
            ]
        },
        "BUGS": {
            "content": "The burst program enforces a limit of approximately 1,000 on the number of messages which may\nbe burst from a single message. There is usually no limit on the number of messages which may\nreside in the folder after the bursting.\n\nAlthough  burst  uses  a  sophisticated algorithm to determine where one encapsulated message\nends and another begins, not all digest creators use an encapsulation algorithm.  In degener‐\nate cases, this usually results in burst finding an encapsulation  boundary  prematurely  and\nsplitting  a  single  encapsulated message into two or more messages.  These erroneous digest\ncreators should be fixed.\n\nFurthermore, any text which appears after the last encapsulated message is not  placed  in  a\nseparate  message  by burst.  This text is usually an “End of digest” string.  As a result of\nthis possibly unfriendly behavior on the part of burst, note that when the -inplace option is\nused, this trailing information is lost.  In practice, this is not a problem since correspon‐\ndents usually place remarks in text prior to the first encapsulated message, and this  infor‐\nmation is not lost.\n\nnmh-1.8                                      2013-02-08                                   BURST(1mh)",
            "subsections": []
        }
    },
    "summary": "burst - explode digests into nmh messages",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "inc",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/inc/1/json"
        },
        {
            "name": "pack",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/pack/1/json"
        }
    ]
}